Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

"active" control panel


gogden Mar 20, 2013 07:17 PM

I am very new to the programming aspect of the CR1000 unit. It looks to me like it operates more on a background level. once you get the parameters defined/organized you turn it on and it "goes"---takes data, can control lots of things given inputs or time set points etc.

However, can we configure a computer to "actively run" the system, i.e. where an operator can turn things on/off wihtout going into the program and changing it (and then needing to change it back)

rather something along the lines of a labview control vi?


kirving Mar 20, 2013 07:55 PM

You can set variables to values, e.g., using corascript commands.
Here's a part of a script I use to set a logger variable:

printf "%s;\n" \
'connect localhost' \
"set-variable $site public RadioHold { } True" \
quit | nc loggernet 88088

This runs on linux, but sends the commands to a corascript process on another server running LoggerNet-Linux. On the
LoggerNet host corascript can be used to execute a script passed to it on standard input. This is setting the value of a variable in the public table on the logger, and the program can do whatever you want with the variable.


gogden Mar 20, 2013 08:06 PM

Doesn't this require one to "re-upload" the main program? or does this act kind of like a "new input" feeding into the main data logger program.

if not, then this type of command might do the trick

thanks


kirving Mar 20, 2013 08:35 PM

It's the latter, just poking a new value directly into the running process on the logger, no change to the program required. The variables can be of various types, string, number, boolean, array, etc., so it's pretty flexible.

There's also the 'ConstantTable' feature which allows program constants to be changed without re-uploading the program, but in that case the program is recompiled and restarted, i.e., similar to what would happen after a power outage. This is useful for things which affect the structure of the program or are not intended to change during operation. (And it's also not without some chance of losing data if you're not careful.)


Sam Mar 21, 2013 09:21 PM

You can use LoggerNet, RTMC, and the HTTP/web interface also.
Also there are Modbus aware panels that could be used to "drive" inputs and display outputs; the datalogger can easily made into a Modbus slave or master.

https://www.campbellsci.com/rtmcpro

https://www.campbellsci.com/loggernet

https://www.campbellsci.com/web-api-article

Log in or register to post/reply in the forum.