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.

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • I have just created a Modbus serial data source using ttyS129, which is a symbolic link pointing to ttyR00.
    I am using Moxa NPort 5150 Ethernet Serial modules and they create virtual devices ttyR00, ttyR01, etc.
    Since RXTX seems not to enumerate them, a symbolic link is a quick workaround.
    When I create a new source the serial port indeed shows up and all is good (I can communicate).

    When I look at the list of data sources it is also all good (data_sources.shtm) and the source shows up wity ttyS129, also when I export I get it right.

    But when I click on edit, I am left with only ttyS0 and ttyS1.

    When I edit the data source, I only get ttyS00 and ttyS01 in the HTML form (data_source_edit.shtm?dsid=31)
    Exporting, deleting and reimporting with the corrected ttyS129 seems to have fixed my problem.


  • Just checking, but did you put the rxtxserial into your mango/overrides folder?


  • Hi Phil, thanks for your help.

    I did not have this, so I did it now. Not sure if I did that right, but I copied /usr/lib/jni/librxtxSerial.so to my mango/overrides folder and restarted mango.

    I also get the following in the logs:

    Stable Library

    Native lib Version = RXTX-2.2pre2
    Java lib Version = RXTX-2.1-7
    WARNING: RXTX Version mismatch
    Jar version = RXTX-2.1-7
    native lib Version = RXTX-2.2pre2

    Serial communication/modbus seems to work though, although I get the error message posted in another thread:

    'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    
    

  • How did you go about installing rxtx?

    I noticed on the rxtx website they mentioned a version mismatch is thrown by the 2.2 prerelease: http://rxtx.qbang.org/wiki/index.php/Download

    I've not experimented with 2.2 yet, as we tend to use the 2.1.7 (it is supported on a great many platforms) for systems we deploy.

    I'm not familiar with that error, but I'm guessing it can be traced to something in the configuration/setup. What are you trying to do?


  • I've installed it using sudo apt-get install librxtx-java on Ubuntu 12.04. I am not familiar with Java unfortunately and it's infrastructure, so consider me a dumb user.

    I have a modbus serial source setup and it seems to work fine (ie. I get he frequency from the inverter).

    But it seems each time it will create the following error in the log:

    Oct 23 23:59: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    UrgentOct 23 23:54: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    UrgentOct 23 23:49: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    UrgentOct 23 23:44: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    UrgentOct 23 23:39: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    UrgentOct 23 23:34: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    UrgentOct 23 23:29: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1
    UrgentOct 23 23:24: 'Modbus': Exception from modbus master: No recipient was found waiting for response for key com.serotonin.modbus4j.serial.SerialWaitingRoomKeyFactory$TransportSyncWaitingRoomKey@1