-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hanging and trash data when both driver connection and rtk corrections through serial port #145
Comments
Serial connections can only be used exclusively as far as I know. Can you try to use USB2 for RTK? Is there a reason you do not want to use the TCP connection? |
One of the reasons I cannot use the TCP connection is that the Linux kernel on my Orin Nx doesn't include the rndis_host driver, which results in no virtual ethernet interface. But the other reason is that I have to use the com port on the Orin instead of the usb port. |
Ok, thanks for clarifying. I was not aware that RNDIS is not possible on Orin. I think I have not yet fully understood your setup. Which Septentrio module are you using? Are you connected via USB or a real serial port? What is the source of your RTK corrections? Also it would be helpful to know which driver and ROS version you are using. NTRIP via ROS does not make sense, since it is a TCPIP stream which can be received by the Septentrio directly. Maybe RTCM would be possible but then again this could be sent to the Septentrio directly. |
Unfortunately on our firmware, which is based on kernel 5.15.136, there is no rndis_host, indeed. The Orin Nx is actually a Syslogic RMLA4NX16-M202S-02 computer. The setup as it is now: The source of RTK corrections is RTKLIB's str2str tool, via the usb serial port /dev/ttyACM0 (set up as described here). I'm using ros2 iron (humble/iron/jazzy, not much difference) and septentior_gnss_driver v1.4.1. |
Thanks for the details. As I said before, it is not possible to use one serial port with two programs. Please, try to set the str2str tool to use /dev/ttyACM1 and the driver to use USB2. When the setup changes to RS232 port, you will have to set up a second port. |
Thank you for the support. |
These debug logs signal that some messages were received, which cannot be decoded by the driver. Are you still sending RTK corrections on the same serial port? |
I am not sending rtk corrections, the ntrip client is turned off.
Here are the debug messages when starting the ros driver:
|
Okay, this is strange. Can you please post your config or a minimal example of it. I will try to reproduce it. |
I connected the receiver the a PC where I could see the web interface, and as you said, it was the rtcm messages. They were being sent from the receiver. Here is the config:
|
Ok, thank you for checking again.
|
When using one serial port for both the driver connection and ntrip corrections, the driver regularly hangs for a few seconds and doesn't communicate with the module / doesn't publish messages.
When setup is the same, but device is connected through tcp, no problems occur.
Connection:
Connected to the mosaic-go-heading with a USB cable. Using external client to provide ntrip corrections.
Config file:
Debug output from the septentrio_gnss_driver:
These AsyncManager errors also occur when ntrip client is turned off.
The text was updated successfully, but these errors were encountered: