Ok, well try these settings:
- Sampling Interval 100ms
- Publishing Interval 100ms
- Queue Size 10
If you miss anything with these settings it's because either Kepware isn't sampling fast enough or it occurred in between polls.
Ok, well try these settings:
If you miss anything with these settings it's because either Kepware isn't sampling fast enough or it occurred in between polls.
Also try bypassing Kepware, with a direct Ignition connection to the device (disable Kepware's connection to the device).
Yea it's still missing information. When you mean Kepware isn't sampling fast enough is that a setting within Kepware I would need to change?
Kepware can be configured to ignore or respect the client's requested rate. The Sampling Interval is the rate Ignition is requesting.
Yea I have it set to "Respect Client-Specific Scan Rate" on the Kepware side
Unfortunatley I dont have direct connection to the modbus devices from the Ignition server. So I cannot try this. Although I know the client does not at all want to not use Kepware since they have other things connected to it.
I'm out of ideas, sorry.
Also just to be clear, you can't just watch for updates in the Tag Browser to determine if you're missing values in a sequence, it must be determined from history or logging via tag change scripts or something like that.
Yea I have historian turned on those tags and even in there its missing information
Bust out Wireshark and look at traffic between Kepware and the Modbus devices, and traffic between Ignition and Kepware. You should be able to figure out where the missing values are.
Turns out the issue is related to the Kepware side where it only is allowing me to pull at most 30 tags before it starts causing delays
Try splitting the devices into completely separate channels inside of KepServer.
Kepware will actually recommend that to increase performance.
There should be some settings to change how many it can request per request. At least Ignition's driver does and I thought Kepware did also.
If this is Modbus TCP, definitely make sure each device is on a dedicated channel. If it's Modbus 485, keep all devices on the same wire/cable/daisy chain on a single channel and don't split it up.
This was the exact issue. Don't know how I missed that in the very beginning thanks for confirming