roslaunch service inactive

[GavinGaoYan]

[GavinGaoYan]

it seems that the service auto stopped?

[GavinGaoYan]

I can start it by run systemctl start. but it cant auto start when boot.

[GavinGaoYan]

And I also can boot it successfully by adding "Restart=always" to the [Service] block. But I want to find the core problem.

[cwbollinger]

Given that "Restart=always" works, my first guess is this has something to do with when the module lookup is happening. If the lookup happens too early, it will fail to find the modules, and exit.

This would happen if the onboard PC boots up before all the modules have an IP. The proper startup sequence is:
Batteries on (wait a little bit for the onboard router to boot up) -> Actuators power on (wait for slow green blink to indicate IP acquired) -> PC power on.

If you are following that sequence and still seeing this issue, I'd need to see more info on why the tready node process is dying. Can you take a screenshot with a wider terminal, so the full text on those two lines is visible?

[GavinGaoYan]

Complete screenshot.
My startup sequence is right. I want to confirm if there is any problem with the operation of your Tready?

[GavinGaoYan]

Another little problem can also be seen from the screenshot. When the service is stopped, the topics still exists.