Address displayed as 0 on a hedge mini-rx IA

[viveka]

Hello Marvelmind!



I've been using Marvelmind for about a year and have used it for prototyping.



However, due to low update rate in NIA, we decided to switch to IA. Our setup has the following -

• 4 stationary beacons (19, 25,31 and 45 KHz super beacons ) Addresses 1,2,3,4

• 2 mini rx on the robot. Addresses 11,12

• Raspberry Pi 4 on the robot running Ubuntu 20.04

• SW pack 6.24 on all the beacons + modem + dashboard

• Using Marvelmind's ROS package.

I have connected hedge 11 to the Raspberry Pi on the robot. When I run the /hedge_rcv_bin and execute /subscriber_test, the address of the other hedge on the robot is printed as 0, it should be 12 (although the xyz coordinates are correct). The maps are frozen

[ INFO] [1608057701.391559592]: Hedgehog data: Address= 0, timestamp= 1930617, X=3.388 Y= 4.020 Z=-2.384 Angle: 0.0 flags=0
[ INFO] [1608057701.491073093]: Hedgehog data: Address= 11, timestamp= 1930721, X=2.700 Y= 4.097 Z=-2.217 Angle: 180.0 flags=0

When I disconnect 11 and connect the Pi to hedge 12, the output is reversed -
Hedgehog data: Address= 0, timestamp= 1930617, X=3.388 Y= 4.020 Z=-2.384 Angle: 0.0 flags=0
Hedgehog data: Address= 12, timestamp= 1930721, X=2.700 Y= 4.097 Z=-2.217 Angle: 180.0 flags=0

My question is - only the address of the hedge connected to the computer seems to display the correct address. The other hedge on the robot that is not connected seems to print the address as 0. My intention is to pair the beacons but the address label is incorrect. The address of the other hedge is still 0 when the hedges are paired. I had not seen this issue in SW pack 6.21.

Most of the settings are default on the dashboard except "Location of other hedgehogs"set to enable and pairing settings.

Thanks for your help!

[smoker77]

Hello,

Just to inform other users.
We continued the discussion in email and found that it was really software issue in version 6.240.
In attachment is the updated version of mini-Rx firmware, which fixes the issue.
This fix will be also included into next software release.