I am logging bag weights coming from a check weighter using the TCP driver. Works fine with the only exception that some bags going across it are not getting captured. I am pretty sure its from the bags going across too fast to get processed. As long as the bags stay within a bag every 5 seconds it’ll capture, any faster and they don’t get captured. I have the scanclass of the driver at 1 second and the transaction group logging the weights set at 1 second.
I’ve tried the IA module for the IND560 but it doesn’t capture the “printed” weight.
Anyway around this problem?
We capture IND560 s through the UCON driver in Kepware.
1 Like
Hi Chris! How are you?
Can you share your capture using UCON driver in Kepware?
Thanks!
I’ve used direct socket connections (java networking in jython) to monitor an IND570 scale via its ethernet shared data server. You end up with weight status reports streamed from the unit multiple times per second. The IND560 appears to have the same ethernet capability. You want the unit’s “Shared Data Reference” manual to guide your coding effort. Found on the CD that comes with the unit.
We are using a opc server “kepserverex” with driver u-con to get the weight.
We configured the module IND560 with especific layout and tcp/ip continuos output.
On telnet is possible to get the weight.
You don’t want continuous mode (unless your process requires it), it constantly talks to the scale.
I do not have the UCON driver handy, but basically what you are doing is issuing telnet commands and parsing responses, based on the scale’s manual (Technical Manual Appendix D).
/c
The OP says they aren't closing the loop fast enough with the query-response approach. Continuous output gives 10 or more updates per second, which should suit their application just fine.
Ah, yes I see. My request-response with demand polling through Kepware was sub-second, with thousands of daily transactions. I always had an issue with continuous output because which measurement do you accept without having a ‘stable’ bit and which weight is the next thing being measured?
Continuous output includes the stable status, among other things. For weigh-in-motion you basically have to use peaks between low-weight thresholds. Extra resolution on the time axis helps.