Closed thanarnop closed 2 years ago
Hi,
this looks like an issue with your upstart settings. My best guess is that your startup does not wait for all network interfaces to be ready. So that the driver does not find a connection to the sensor on boot-up. If its a systemd service, try to change the after target to something which indicates that the network is ready.
OK I get it , I will try so
Hi, I had the same problem as you. I tried the following step:
If the program reads data from sensor, chmod by custom udev rules by port or by group, or node and topic shows up but can't echo topics.
$ ll /dev/ttyS0 # this is what your sensor connected to
crw-rw-rw- 1 root dialout 4, 64 Jan 7 13:04 /dev/ttyS0 # the result should be 0666
I have the problem when I manually run command roslaunch the output data is appears my system run perfectly no problem, but when let the robot auto run on startup by the robot upstart start system ,It has no output data appear but the rosnode and the topic is appear like no problem seem like running has complete but no output data