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.

Mango uses Modbus4J in 1000's of applications around the world. It is a well used and full-featured library. You won't see much development activity on it since it has been very stable for a long time.

Hi vijay,

There may be more than one solution, but we have solved this on our MangoES product for instance by using udev rules to create a symlink with a consistent name. In our case, we used the attributes identifying which USB port the device was connected to. You may find this stack exchange thread helpful: https://unix.stackexchange.com/questions/66901/how-to-bind-usb-device-under-a-static-name

You'll need to use udevadm to find the attributes to identify the port by, and then a /etc/udev/rules.d/ rule to SYMLINK+="ttyNewSymlinkName"

Hi,Dan! Have you maked the application ? I have the same problem. I am trying to use modbus4j but without success. Sorry for your worrying. Alexander.

Modbus does not provide a built-in way of detecting slaves. So to do what you want to do would need to be a hack or workaround...Such as polling each slave, if there is a response from that slaveId even if it is an error code such as "illegal address", then there is probably a slave of that ID ??

The most proactive thing you could do for the issue of the null pointer is perhaps to fork the repository, implement some tests that use input and output streams, finish the TestSerialPortWrapper class, and submit a pull request.

But, if you're trying to talk to an actual device and not simply playing with the test code, then perhaps you are wanting to use your own implementing class of SerialPortWrapper which presents the input and output streams of your serial port in the methods that return null in the test class.

In Mango, our Modbus module makes a call to the SerialPortManager to get a proxy, and then returns the input stream and output stream from the proxy.

https://github.com/infiniteautomation/ma-core-public/blob/main/Core/src/com/infiniteautomation/mango/io/serial/SerialPortManagerImpl.java#L205
returns
https://github.com/infiniteautomation/ma-core-public/blob/main/Core/src/com/infiniteautomation/mango/io/serial/JsscSerialPortProxy.java
for non-virtual serial ports in Mango, which uses Jssc to actually handle the serial nitty-gritty.

@phildunlap thanks a lot.

I'm sorry for posting without any specific content but i didn't know what will be best.

Understandable, and it can lead people down the wrong paths to focus on the
wrong thing. But assuredly we need something to even stand a chance of offering something back.

I imagine you're adding a BasicProcessImage to a TcpSlave via the addProcessImage function. You should be able to instantiate a com.serotonin.modbus4j.BasicProcessImage with a slave ID of 255.

We have added Mod10k data types into the next release of the Modbus module, 3.4.1, which should be released sometime next week, most likely. It's currently in the store in the development channel.

Seems like a path issue. Is modbus4j on your classpath?

Hi mischaivchenko,

Three things I would consider trying are,

What happens if you use Mango's tools on the Modbus Data Source page to read these registers? Do you get better feedback, or output to the log file? The point locator test tool uses the same method you are using. Can you attach a debugger? Modbus4J is open source and as far as gaining knowledge in Java goes, you should be able to attach a debugger in your IDE and step into the code. Get a log4j configuration that will output the various log statements from TcpMaster and pass that into your program as a command line argument.

Hi Sagarsama,

So, you're requesting the same register over some period of time, and it never errors but the value is usually what you would expect for the kWh and occasionally what you expect for the instantaneous voltage? That's bizarre. I would set up a Mango reading that register for a while to be sure that is what is going on (you make it sounds as though you are using Modbus4J in your own application), but that sounds like an issue with the PLC. If you're requesting the same range of values and it is spontaneously changing those values, that is its issue.

It should be the same process as any other Java project or regular JAR. I've never used Android studio personally though, so i can't give you specific instruction. I bet "import jar android studio" gets usable search results from elsewhere on the web. The github project is here: https://github.com/infiniteautomation/modbus4j

@nikorun
where this master.setValue
(...) line should be added ?

You can review our main site, then download the Mango files. Here is an article about exploring the API once you have Mango running on your machine: https://help.infiniteautomation.com/explore-the-api/

We need to update the document on API authentication which you'll need before you integrate your application but you can use Swagger to test all the end points and see the JSON formats

Looks like you and I are trying to do the same thing.

It seems that your simply looking to poll modbus registers, and write them.

Here's what I found.

There are two types of groups.

Group one are experts at doing just this.
Group two are experts at taking the data and putting it on a slick graph.

I spent 6 months on this same project last year, only to get frustrated and quit.

I think we should collaborate.

Drop me an email response.

Thanks.

Greg

check out the modbus data source in the old mango source code for an example on how to use the modbus4j library

https://sourceforge.net/projects/scadabr/files/Software/mango-src/

Hi libu7alex,

ReadSerialTest throws a null pointer because TestSerialPortWrapper returns nulls for its input and output streams. That looks like a bug in the test, and shouldn't affect the larger issue you seem to be asking about, so,

I believe you're writing code to use Modbus4J? We offer limited free support for this.

You are providing the SerialPortWrapper to the Modbus master you're creating an instance of, correct? If so you should set a breakpoint in your serial port wrapper and see what happens in the serial library you're wrapping for the 232 setup you're testing when it tries to get the input or output stream from your wrapper.