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.
Invalid arguments: router address not provided for a remote recipient
-
When trying to discover devices on network we get this exceptions.
I have already opened a thread on something similar where it seems that you have taken out completely the linked service for some reason.BTW:Old stack used to discover properly same network.
Looking on the code I can see that Linked service is not updated upon IM request and all other requests so that later on if we try to access the device we get that exception.java.lang.RuntimeException: Invalid arguments: router address not provided for a remote recipient
at com.serotonin.bacnet4j.npdu.Network.sendAPDU(Network.java:76)
at com.serotonin.bacnet4j.transport.DefaultTransport.sendForResponse(DefaultTransport.java:812)
at com.serotonin.bacnet4j.transport.DefaultTransport$OutgoingConfirmed.sendImpl(DefaultTransport.java:310)
at com.serotonin.bacnet4j.transport.DefaultTransport$Outgoing.send(DefaultTransport.java:246)
at com.serotonin.bacnet4j.transport.DefaultTransport.run(DefaultTransport.java:357)
at java.lang.Thread.run(Unknown Source)Need this to be fixed quite urgent.
Thanks.
-
What BACnet4J are you using? There is an issue in 3.2.2 surrounding binding the sink address 0.0.0.0 during discovery. There may be useful information on getting 3.2.3 from us in this thread; http://infiniteautomation.com/forum/topic/2056/no-datagram-receive-on-unix-based-systems/3
-
Hi
Thanks, I did upgrade to 3.2.3 and things looks much better.
BTW: I have noticed that the stack add network address upon receiving: “IAM router To Network” PDU.
I was wondering why not to add Linked Service when it Get IM PDU?
The reason I 'm asking since when searching device on Network with BBMD I still get some of the devices coming OK but when trying to get some points belonging to them I get same error from stack. Do I need to initiate specific request to get the network address of a specific device or is WHOIS request enough for to satisfy the stack? -
It looks like that old functionality has been taken a way where we used to get the linked service in IM requests.
With 3.2.3 the stack expect IM router to Network or I Coud be Router to Network to come in order to decide about network address (Linked Service) .
Im a bit surprise since we can get the linked service when getting the IAM and make use of it.
I have a temporary fixed but expect it to be fixed officially.
