Register on Extended Data, limit on Modbus RTU Master

Frank · Post by **Frank** » 16 Jun 2020, 13:29

Hello Chris,

please ignore the last problems my colleague Amar encountered yesterday. This was due to something I didn't inform him about - it was totally my fault.
We found out what prevented him to correctly load your _config.rsc

Regards,
Frank

Post by **Amar** » 16 Jun 2020, 16:21

Hi Chris,
Please check For piModbusMaster logs in file var/log/daemon.log

You may get certain errors.
Jun 16 15:19:41 RevPi17643 piModbusMaster[2109]: modbus rtu action device: /dev/ttyRS485, slave address: 14 function: 0x05, address: 1 failed -1/110/-112345568

If there is a timeout on any action ID the following actions will not be executed.If your all action ids are error free then you could read variables even for more than 32 actions.
Regards,
Amar

ChrisDeveloper · Post by **ChrisDeveloper** » 18 Jun 2020, 06:59

Hi Amar,

`tail -f /var/log/daemon.log` was a really useful command, it helped me fix a few unrelated issues.

Unfortunately this didn't show any errors coming from the extra registers beyond row 32 (I have no time out errors now ).

Is there anything else I can do?

Kind regards,
Chris

Post by **Amar** » 22 Jun 2020, 09:54

Hi Chris,
You can test the Pictory config.rsc with ModRSsim2 and look out for possible errors from any action IDs by checking out the logs.
Regards,
Amar

ChrisDeveloper · Post by **ChrisDeveloper** » 24 Jun 2020, 02:57

Hi Amar,

I have already tested using a real modbus network, the logs (tail -f /var/log/daemon.log) show no timeout errors.

Would it be possible to setup a team viewer to investigate?

Kind regards,
Chris

Post by **dirk** » 25 Jun 2020, 11:25

Hi would you be so kind to give us the following infomation:

the compressed "/var/www" folder
output of "uname -a" which is the kernel version

Yes, we can organize a remote meeting with TeamViewer or with MS-Teams.
How about Monday at 13:30 CEST?

ChrisDeveloper · Post by **ChrisDeveloper** » 26 Jun 2020, 02:43

Hi Dirk,

Thank you for your response.

Sure, Monday 13:30 CEST / Sunday 21:30 AEST works for me.

Output of uname -a is:
Linux RevPi37288 4.9.76-rt60-v7+ #1 SMP PREEMPT RT Fri, 28 Feb 2020 15:17:03 +0100 armv7l GNU/Linux

Where do I send the www files?

Kind Regards,
Chris

Post by **dirk** » 26 Jun 2020, 13:41

Hi this sounds good. You can send the files to support@kunbus.com.
See you moday.

Post by **Amar** » 30 Jun 2020, 12:40

Hi Chris,
Thank you for your previous telephone call and for sending www directory.I could reproduce the problem for more than 32 actions at your side.An new ModbusRTUMaster_20180406_1_2.rap for maximum 64 actions and a new _config.rsc for that is attached in zip file ModbusActionsMax64.zip.I could work with more than 32 action with these files.

Steps:
1) backup files
/var/www/pictory/resources/data/rap/ModbusRTUMaster_20180406_1_2.rap
/var/www/pictory/projects/_config.rsc

2) Replace ModbusRTUMaster_20180406_1_2.rap and _config.rsc with the one in ModbusActionsMax64.zip archive

3) Make sure that your browser cache has been cleared!

4) Reload pictory configuration and the new extended data would look as following:

: config.png (71.62 KiB) Viewed 11570 times

5) Modify Modbus comm settings if you have other setting: Kept at default 19200 8 E 1

6) Test the modbus actions.Correct any action id errors if occured with your actual setup.

7) Once it works at your side you can rename the default name registers according to your project.

Attachment:

ModbusActionsMax64.zip: (9.39 KiB) Downloaded 907 times

Please leave a short feedback if it works on step 6.
Regards,
Amar

Post by **dirk** » 08 Jul 2020, 08:54

Hi Chris, how is it going? We would like to hear your precious feedback.

Register on Extended Data, limit on Modbus RTU Master

Products

Ordering

Support

Company