Hi Mike,
not sure if I understand correctly what is the issue. Can you provide more information?
Can you share screenshot of the project part and a sketch of desired behaviour?
Is the issue about setting binary inputs sequentially which produces more logs to be written?
Thanks.
Cheers, Tomas
Hi Sid,
thank you for your question. Custom made solution is far beyond our "free of charge" support. However here are some function blocks which might help you achieve your goal:
TIMER_ - Multipurpose timer
BINS – Controlled binary sequence generator
EDGE_ - Falling/rising edge detection in a binary signal
If there is anything unclear, let us know.
Regards, Tomas
Hi Richard,
sorry, my mistake. You are right - both arrays have 11 items.
But still the size need to comply with parameter n. Once you change it to 11 it should do the trick.
Please, let me know.
Cheers, Tomas
Hi Richard,
thanks for reporting the issue. The problem is that up and yp arrays should have n items but your up array has only 11 items, yp 12 items. Please, fix it so they all have same length and it will work well.
We have already implemented array length checking for those parameters and it won't compile unless all lengths are correct. The fix will be part of new release.
Thank you for understanding.
Cheers, Tomas
Hi Mike,
see the modified project attached. In such a case I recommend to use two different items - one for reading and one for writing. Therefore there won't be any naming collision. Keep us updated about your progress.
PS: I also modified Modbus Port settings to meet requirements for Modbus RTU usage via Monarco - there should be "/dev/ttyAMA0" - for more details see following topic at our Knowledge Base - https://support.rexygen.com/help/modbus-rtu-with-the-monarco-hat-on-raspberry-pi
Cheers, Tomas
Hi Mike,
exec file is not enough - Modbus configuration is hidden in *.rio file. Can you share whole your project? You can send it via e-mail if there is some know-how you wouldn't share with others.
Can you describe your setup more to the details? What devices are "talking"? I was probably misunderstanding that you are trying to implement Modbus Slave in REXYGEN because you have some device acting like Modbus Master. That is wrong, right? 
Cheers, Tomas
Hi Karel,
the COUNT function block is definitely a good choice, however you should be aware of project timing because of quite high input frequency. I recommend you to have a look at example "0120-23 Frequency of Pulses". Change the project timing so the "tick" parameter is 0.001 s (within the EXEC function block) and "ntick0" according to your needs.
It means that Quick Task will be executed every 1 ms and task on Level0 every 0.001*ntick0 [s].
Note that the period of 1ms is quite challenging for Raspberry Pi. I would recommend to use Raspberry Pi 3B+ and watch diagnostics.
Hope it helps.
Regards, Tomas
IMPORTANT - Speaking about Modbus Slave implemented in REXYGEN:
There should be no need for having input and output flags for the same item (same name).
If you want to observe it's state (i.e. changes made by writing from Master), you can add to your REXYGEN project input flags ("From" function block).
Output flags ("GoTo" function block) within Modbus Slave context are valid only for registers meant to be READ ONLY for Master.
If you want to store some initial values within Modbus Slave, use "Init Values" box in Item configuration dialog.
If you can share a test Modbus mapping table suitable for you project I can prepare Modbus Slave implementation example for you.
Hope it helps.
Cheers, Tomas
Hi Mike,
in order to configure REXYGEN Modbus Slave register as read/write, just tick "Readable" and "Writable" options together in Item configuration dialog.
Note: be sure not to use write flag (GoTo flag) within REXYGEN Modbus Slave - it can lead to unexpected behaviour because of multiple sources for one register.
If you need any further assistance, let me know.
Cheers, Tomas
Hi Peter,
thank you for reporting this and also sorry for difficulties. They made some major changes between version 5 and 6 of ArduinoJson library.
I upgraded the Arduino sketch - see attached one. It can be compiled now however I don't have any ESP8266 around so didn't make any further tests.
Let me know about your progress.
Regards, Tomas