Hi,
I'm an old-time PLC guy and I'm trying to set up the 8 channel RTD module for 9600 baud, 8 data bits, 1 stop bit, and even parity. The module works find at 9600/8/1/NONE but not when parity is set to Odd or Even (I need Even.)
The command line argument I am using is rtc 0 rs485wr 1 9600 1 1 1. If I set the Modscan parity to NONE and change the parity at the command line I see that communications fails if I change it to something other than NONE and returns when I return the parity to NONE. I've tried all of the options available and always get invalid responses from Modscan when I set up the communications for anything but NONE.
My project requires a bunch of these modules to monitor temperatures in electrical rooms and they are going to be monitored by a 3rd party device and not connected to a Raspberry Pi.
Please let me know what I'm doing wrong. I'm using version 7.0 of the module.
Yosi
Hi,
It looks like a bug in firmware. I will check and resolve it by the end of next week.
For the local processor we use, when you choose parity different than none you have to change number of bits. I am traveling and can not check now but , I think this is the problem.
Alex.
Hi Yosi,
I managed to check the firmware, and my assumption was right: there is a bug in the current firmware. A new firmware version was released, and you need to connect the card to a Raspberry Pi in order to update its firmware. Please follow the instructions from here
Alex.
Wow! What terrific support!
@alexburcea When I run the first command the Raspbery PI responds fatal: destination path 'rtd-rpi' already exists and is not an empty directory. I'm assuming this is normal.
The command cd rtd-rpi/update finds the directory and a dir verifies what I'm expecting to see.
The problem starts when I run ./update 0
I get the following response to that "bash: ./update cannot execute: required file not found.
As I said, I'm an old PLC guy and my experience with Linux is decades old. What am I doing wrong?
Thanks in advance.
Yosi
Hi,
It looks like your Raspberry runs a 64-bit Linux, and you need to go to the "debian64" folder (cd debian64/) and run the update from there.
That did the trick! Thanks for the great support!
Thank you for reporting the bug.
@alexburcea Thank you for the products. It's great to know that there are low-cost alternatives for things that I can use for industrial monitoring. It's especially great to experience outstanding support. Kudos!
