Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
BARIX R6 Configuration
-
Hi Chromeaccent,
My first step was googling for a manual. I found this: http://www.barix.com/fileadmin/data/Manuals/barixr6_manual_V0200.pdf so I will be presuming you're talking about that device.
The "Supported standard commands" indicates that only read requests on holding registers are supported, so I am guessing those values in your post are holding register offsets. The bit about "please not the protocol address in..." is informing us that it is a 0 offset implementation, but that it's presenting information with a 1 offset. So, in using the test tools, I would assume reading Holding Register 256 should give you the Device Type
I do not see the slave ID for the device described in the document, but they say that there is a jumper that can force it into default settings (although it appears from the document that the default modbus address is 255, which is frowned upon in the Modbus spec and you may have issues. I may be able to supply you with a sly workaround to set a better slave ID if this is an issue, but perhaps you have the tools to set the PLC's slave ID or you know it has one that is lower than 247, and this won't be an issue)
A request that i think should get the Device Type
Settings in document: 19200 baud (bit rate), even parity, 1 stop bit. This would be a Modbus Serial data source.
-
It looks like for Write commands you will be writing to Coil Status registers 1-6 (0-5?), once you have communication going.
-
Thanks for your quick response. I have been trying to use Modbus poll from Modbus tools as a master in order to change the R6 address, however, I have been having communication issues with it. I will try the setting listed above and let you know.
-
When I attempt to write to the device I keep getting:
There was a problem testing the locator. (com.infiniteautomation.mango.io.serial.SerialPortException: Port /dev/rs485-1 in use by Mango Modbus Data Source DS_451699)
Any ideas? -
You need to disable any data sources using that port before using the test tools. I'm guessing that is the issue.
-
Hi Chromeaccent,
It is possible the parity is "None" instead of "Even" as the manual is not clear. "Even" is the default but "None" is also listed as a supported possibility. From the document:
Supported interface configurations are 19200 baud, 8bit, even parity, 1 stop bit (**default**) 19200 baud, 8bit, no parity, 1 stop bit 9600 baud, 8bit, even parity, 1 stop bit 9600 baud, 8bit, no parity, 1 stop bit -
Hi Phildunlap,
I was able to get another Modbus device display, this device has two data points, temperature and relative humidity, however, I am at a loss as the Barix R6's configuration. Strangely it responds to Modbus poll.
By the way, I have not seen Relative Humidity(RH) in the point properties drop down menu. -
I don't know what you mean, "Strangely it responds to Modbus poll" You are not using Slave Id 255 are you? I would not expect that to work. It must have a slave ID <= 247
If you are not seeing the Units (I assume you are referring to units) you need, you can set a custom suffix in the text renderer section of the data point.
-
I did change the address to 200 for the R6, I also had to change the address for the other device, this I changed to 230. One thing I did notice was that at first, I would get the result for temperature in Hexidecimal but after a while it changed to decimal values.
-
Can I use a crossover cable to connect my mango ES to my laptop?
-
Ethernet? I suspect so, but I've only used a standard ethernet cable for that purpose (haven't ports been self detecting and switching for a half decade or so? https://en.wikipedia.org/wiki/Medium-dependent_interface#Auto_MDI-X ). Then you'll probably have to give your ethernet interface a static ip on the same network or listen for its IPv6 address and use that.
