Closed yucedagonurcan closed 4 years ago
@yucedagonurcan, thank you for reaching out.
Based on what I see here, I think that the driver cannot connect to your receiver. It maybe that your port 3001 is already in use by something else.
You could try updating your "oem7_port" in your launch file to be another value between 3001 and 3007. These are TCP ports (unless reconfigured on your receiver). These ports can only service one connection at a time. This approach could let whatever else is connected to your receiver continue, but presumably allow the ROS driver to use an unused port.
If that doesn't work, please next confirm that you can at least ping your receiver, for that you could use the command:
ping 192.168.1.112
Hello,
Changing port to 3002
from 3001
resolved the issue.
Thank you for your help.
UPDATE: This comment is captured by Issue #10
Hi
I'm experiencing a similar issue when using usb operation method. There were 3 error messages reported as follows:
[ERROR] [1598343835.180147191]: Attempt 0: timed out waiting for response.
[ERROR] [1598343835.196250946]: AACmd 'LOG INSCONFIGB ONTIME 300' : 'ERROR:Trigger ONTIME not valid for this log'
[ERROR] [1598343835.260403646]: AACmd 'LOG CORRIMUSB ONTIME 0.01' : 'ERROR:Invalid Message. Field = 2'
Additionally, although the /gps/imu and /corrimu/ topics are published, there isn't any imu data under these topics.
Hello,
We are experiencing timeout errors while using the oem7 ros driver.
Here is our oem7_net.launch file:
Launching the launch file gives timeout errors:
$ roslaunch launch/oem7_net.launch
Here is our logging window:
Here is our position window:
What do you think is the reason for getting such an error?
Have a great day.