This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SCADA connect with excel

Hi!

I want to add real-time SCADA signals, but I've got a problem. Due to strict security protocols of our company, I have no direct access to operational data. Although, I can generate reports ( .XLSX format), which are near real-time (considering the 10-15min hydraulic timesteps). I can see that, when I establish a SCADA signal connection to a .XLSX file, it is opened for good, so no external software can write that specific file until watercad is closed or scada signal is deleted. This behaviour prevents me to overwrite/update the .xls report that contains my signal data.

Do you know any workaround for this issue?

What I was thinking about (but not sure if it can resolve the issue):

- create an access database

- Link my excel sheet to the database

- establish scada connect to the access database file

Best regards,

Attila BIBOK

  • Hi Attila,

    Even though I have been using Excel for 20 years I would still not call myself an expert, but my feeling is that Excel doesn't really support concurrent access all that well. The problem with SCADA signals is that we can't really tell when they will need to open the SCADA connection, thus cannot guarantee any particular window where the connection will be closed to allow another user to update data.

    What you describe as a potential work around should work because Access allows concurrent access to data, but if you try it and run into any issues, be sure to write back and let us know. We are committed to help users establish robust work flows around these kinds of use cases.

    Kind Regards,
    Wayne.



  • Hi Wayne,

    Thank you for your answer. I'm going to look into the aforementioned workaround.

    Best regards,

    Attila Bibok

    Technical Development Engineer

    Budapest Waterworks

    Email: attila.bibok@vizmuvek.hu

    Web: www.vizmuvek.hu

  • Hi!

    The problem is: Referenced(linked) tables, such as XLS sheets are cannot be referenced through simple MS access database connection. Direct ODBC connection has some driver issues, which i couldn't resolve on my office PC (Win7 64bit, office 2010)...

    But I have found an even more suitable workaround. It is kind of tricky, but It works flawlessly. The method is the following:

    -Database source...

    -Connection: Click Edit...

    In Database Connection dialog:

    -Choose: OLEDB Source as Data Source Type

    -Click on the "..." button at Data Source field.

    In Connection properties dialog:

    -Click Change button at Data source

    In Change Data source dialog:

    Choose Microsoft Access Database File - Data provider: same .Net Framework Data Provider

    -Press OK

    In connection properties dialog:

    -Database file name: Choose the .accdb you are about the use with the REFERENCED table.

    -Leave other field as default

    -Press OK (It shows  ODBC connection, but there are no driver issues)

    -Press OK

    -Now you can select the referenced table from the Table name list and do everything like it would be a static table.

    NOTE: You have to prepare your linked references to be refeshed automaticly as the following link shows:

    I hope this is going to help someone someday.

    Best regards,

    Attila Bibok

    Technical Development Engineer

    Budapest Waterworks

    Email: attila.bibok@vizmuvek.hu

    Web: www.vizmuvek.hu

  • Hi Attila,

    That's good news. So to be clear, you are using an Access database for the SCADA signals and using an OLEDB Source connection, specified as "Microsoft Access Database File" it seems.

    I think you are saying that you tried the in-built Access 2007/2010/2013 connection type and it didn't work right? I'm curious since behind the scenes the Access connection (Access 2007/2010/2013) is simply an OLE DB connection, however, there are a couple of subtle differences between the generic OLEDB connection in SCADA Connect and the Access connection. One such difference is how tables are retrieved.

    In the meantime, if things are working using OLEDB then there's no specific reason not to continue to use it. One thing with SCADA Connect is that we provide several different choices for connecting to data sources so as to try to avoid painting users into a corner.

    Regards,
    Wayne.