Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I get info from instrument's stored REG into LOOKOUT

I have a DATA-logger (SCADAPACK-LP) that stores information into a registry every 15 minutes.

How do I get LOOKOUT to retrieve that information, so I can save it to a file for EXCEL. I also want to purge the registry after the information is recieved.
0 Kudos
Message 1 of 8
(3,968 Views)


Hi,

SCADAPack-LP supports Modbus protocol. Using the Modbus Object in Lookout, you can communicate with the SCADAPack-LP and read the data.

You'll need to find out the exact registers where the data is being saved (from the SCADAPack manufacturer). You then would read these registers in Lookout. And to flush them, you can write zeros.

Hope this helps.

Regards,

Khalid


0 Kudos
Message 2 of 8
(3,967 Views)
I am using the ModBus Protocol. I can see information that the SCADAPACK logger is putting out. (more information than I need).

I am trying to figure out how to get that stored information in Lookout. I have a feeling that, for example if I have 30 pieces of information in that register, in LOOKOUT, I'll have to repeat some sort of retrieval method 30 times.



The register that the stored information resides in is 41100


Their are 2 fields:
It contains the 4-20MA information.
It also contains a time stamp.


Also, register 10200 will allow me to clear the register 41100. I assume that I need to send a 0 or 1 to clear it. How can I do that?


Thank You!
0 Kudos
Message 3 of 8
(3,967 Views)


To simply display the value from 41100 you would insert an expression like say, Modbus1.41100 on the panel (where Modbus1 is your Object). You can write this value to the spreadsheet using the Spreadsheet object. You can have the value sent to excel on a regular interval (using a Timer), or on demand (using a trigger).

Are you saying the value in register 41100 keeps changing? How often? If you poll fast enough you should be able to get the new value each time.

Is the 4-20mA info' and timestamp bundled together in some form? I.e., can you parse these back? Or are they stored in adjacent rgisters? In which case you may have to either read 41101 as well. Or read F41100.

To write to 10200, you would connect a Pot (or a
PushButton if it's a logical). To do this you can right-click on 10200 in the Object Explorer and select Edit Connections. Then connect the Pot/PB to it.

Sorry if I am not understanding your questions .. please write back with more details. And some examples of the data format, etc.

Regards,

Khalid


0 Kudos
Message 4 of 8
(3,967 Views)
Thanks.

To make things simple I have a web page that explains what I am doing...

Click here for details.

Thanks again.
0 Kudos
Message 5 of 8
(3,967 Views)


Sorry for the delay in getting back -- had a pretty hectic day today!

From the info' you provided, it's clear that 41100 is where the data is stored (at least the first of it). However, this may just be the beginning of the series of consecutive 799 more registers. The description of the Field Register Address says "A Field Register Address is the address of a Modbus register or the address of the first Modbus register of a small block of consecutive registers. So, I am wondering if the rest of the 799 data is in the consecutive registers, 41101, 41102, and so on.

And this makes sense because 41100 is just a single 16-bit register. There's no way it can "store" 800 data.

What do you see in Lookout
when you try to read 41101, 41102, and so on?

Another alternative (if you cannot get to the stored registers) is to read, or rather sample, the 41100 every 15 minutes and store that in Lookout/Excel.

Not sure if this is of much help. Do let me know how it turns out.

Regards,

Khalid


0 Kudos
Message 6 of 8
(3,967 Views)
I have to agree with you, 41100 is where the information is.

Here's what I found out. The information "IS" in 41100, but immediately sent to the "onboard memory" of the SCADAPACK logger (via timer). This "onboard memory" is SCADAPACK's own design (their secret to storing a lot of DATA), and does not use standard modbus address ports. The support tech told me that the only way to access that stored information, is to use their "crappy" software. He didn't say the "crappy part", but you know what I mean. Their software is a Windows 3.0 16-bit program that requires accessing a DATA logger one at a time. I have 9 DATA loggers to access, most are expensive toll calls. To use their software, you have to go to the configuration pan
el and manually type the telephone number each time you want to call a different number to a different DATA logger.

I find it hard to believe that there is no other way to access that stored information, when NI, and a few other competitors, sell similar DATA loggers at the same price.

A tech from NI told me that he believes there might be a way to get the stored information, or even program the DATA logger to store information in a block associated with a unique modbus addresses, and skip the storage part all together. This is still pending.
0 Kudos
Message 7 of 8
(3,967 Views)
@ Khalid

Thank you for your help! Couldn't solve the problem without you!
0 Kudos
Message 8 of 8
(3,968 Views)