thanks for your reply. To have a feature you mentioned was great! In our project i had to generate several meta points just to be able supply modbus publisher with zeroes.
Concerning the problem mentioned, i have new findings. Initially i did not define the modbus registers linearly corresponding their address. For example i defined
0 lenght 4 ...
64 length 2 ...
4 length 4
8 length 4
60 lentgh 4
Now, they are ordered strictly monotonically increasing corresponding their offset.
Should be documented somewhere maybe?
I recently bought a Publisher for Modbus IP publish-ip-unlimited licence.
Now when trying to feed a third party TCP Modbus Master, I get in trouble.
The master needs to read multiple registers with length 120. That fails. I tried reading multiple registers with length 16, that worked. 32 didn't.
Sadly there is no documentation about a lenght restriction IMHO.
For my project it is really important to be able read 120 registers at once!!! If not implemented in the module, would it be possible getting that included soon?
Anybody who can give advice?
in the mango help http://help.infiniteautomation.com/support/solutions/articles/14000022524-meta-data-source there is written 'see “Script execution” below' when it comes about when a script is executed.
Sadly there is nothing written below...
Can anyone tell me when a metadatasource is updated?
I am about to setup mango to retrieve BACnet data from six JCI DCCs, approximately 200 data points each.
What will be the best approach considering data sources. Should I use one data source for all controllers or better use one data source for each controller?
Especially regarding CPU performance and best Threading behaviour.