Open RomanDmowski opened 4 years ago
After a few tests, I found that If I added a log pointed at the driver port manually, the information (dual_antenna_heading) was published to the topic. So this is only partially a solution to that problem.
Interesting -- when you say you pointed at the driver port manually, do you mean you used a serial connection instead of TCP? It'd be pretty strange for one to work but not the other; does the issue still happen if you set use_binary_messages
to true
? Also, would it be possible for you to record a pcap capture file of the network traffic and a log of the serial traffic so that I can compare them?
I used Web UI to add log 'dualantennaheading' to the virtual port ICOM1 with the binary format. I changed use_binary_messages to 'true' in the launch file.
I have the latest version of novatel_gps_driver (Latest commit 3005b80 on Dec 5, 2019) compiled from source. I am running it on ROS Kinetic on Ubuntu 16.04. I have the Novatel PwrPak7D with Dual Antennas. When I run the node, no information is being published to the DualAntennaHeading topic even though the DualAntennaHeading topic is listed. At the same moment, the log DUALANTENNAHEADINGA contains the right information with a heading value.
I use the lunch file:
I know there was similar issues in the past:
It seems it still doesn't work.