Could not configure serial baud rate #32
Comments
|
Hi! I get the same error with this configuration parameters: PARAMETERS
I'm using http://ardupilot.org/copter/docs/common-installing-3dr-ublox-gps-compass-module.html connected via USB to Raspberry PI; the u-blox model is: LEA 6H. |
|
Can you put some debug messages before the line Line 157 in 694268c if statement is failing?
|
|
Hello, I am stuck with the exact same issue unfortunately. I put some debug messages in gps.cpp to indicate which condition may be failing, here are the results: NODES auto-starting new master setting /run_id to 310c1418-6e52-11e8-9ef4-00044b8d23cf Where, |
|
I'd like to note that I was able to fix this issue by using /dev/ttyACM1 (I forgot that I had another sensor attached to /dev/ttyACM0) and most importantly I am using the M8T timing device which is not currently supported by this repo. I was able to find and successfully use this user's repo: |
|
I'm also facing this issue: SUMMARYCLEAR PARAMETERS
PARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 process[drotek_ublox_m8n_and_compass-1]: started with pid [5866] |
|
I can workaround this issue with a powercycle and a very minimalistic config file. The node respawns a couple of times but then comes into a running state: https://pastebin.com/DthC6tvL neo_m8p_base.yaml debug: 3
device: /dev/ttyUSB0
tmode3: 0 |
|
Totally agree with you, this has been my solution as well: And the behavior is the same, a few unhandled |
|
Did you also find a way to set UART1 settings? I need the chip to report RTCM messages. So uart1:
out: 32 # RTCM 3But every uart1 setting fails on setting baudrate. (Which I am not trying to change actually) |
|
Actually no, and I also made a few modifications to make it "more tolerant" with the hardware (or itself, I don't know precisely who is the culprit of all these errors). So I don't know if UART1 is actually configured with 7/1 In/Out (what are these, bits?) and used at all. My output is currently this one: BTW, my Drotek GPS should also have a compass in it and it would be nice to find it and use it, but I think I have no chance to complete this task with the limited amount of time I have to work on this now. |
|
Hello, I am having the same problem after killing my node and then re-launching it again. It seems like the device isn't properly released by the node because I don't see a "Closed connection to " ROS_INFO that's supposed to be logged after calling EDIT: I have the ublox m8n running on ROS Kinetic/Ubuntu 16.04 |
|
There is also param |
|
Solved it by changing the baud rate in the yaml file to 115200. It means something like instead of trying all the baud rate which the launch automatically does we have to put the right baud rate which was set before using U center. So basically I set a baud rate on the m8t using u center and then put that particular baud rate into the yaml file. |
|
I have also same an issue with a Ublox m8n gps on ros. It always gives me error: what(): Could not configure serial baud. I double checked port and baud rate. Did you guys find out a solution to this problem? If so, can you share config file? EDIT: just use http://wiki.ros.org/nmea_navsat_driver. It works with ublox m8n |
|
Changing the baud rate in yaml file is not helping. Has anyone found any solution? |
|
I would get similar behaviour with this package, a Ublox ZED F9R for the simplest case that the USB cable was connected on the POWER+XBEE interface instead of the POWER+GPS. By the way the interface for GPS should be /dev/ttyACM0 and not /dev/ttyUSB0 as in my case was for Xbee. This can vary depending on the Ublox module of course. |
I set it to 38400 using u center and also in the .yaml. My device is ZED F9P. It still doesn't work. |
|
I am facing the same |
|
I have two ublox devices one is working and the other not .(C100 F9K) WORKING ON LOG NON-WORKING ONE |
|
Use U-Center app and see what baud rate is being used. In my case: debug: 1 device: /dev/ttyUSB0 uart1: publish: |
|
Did someone solve it? I'm facing this problem with zed-f9p |
Hello,
sometimes I get an error, if I want to connect the rover with my Rasperry Pi. The base and the rover are connected to difference Raspberry Pi. I can start the base without an error. But if I start the rover launch file, it works just every third time.
robot@igel01:~/catkin_ws/src/ublox/ublox_gps/config$ roslaunch ublox_gps ublox_device.launch node_name:=rover param_file_name:=c94_m8p_rover
... logging to /home/robot/.ros/log/bb634996-58d2-11e8-a299-b827eb0b48c0/roslaunch-igel01-5419.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://igel01:35856/
SUMMARY
CLEAR PARAMETERS
PARAMETERS
NODES
/
rover (ublox_gps/ublox_gps)
ROS_MASTER_URI=http://localhost:11311
process[rover-1]: started with pid [5438]
[ INFO] [1526454535.202589825]: U-Blox: Opened serial port /dev/ttyACM0
[DEBUG] [1526454535.203817069]: Configuring UART1 baud rate: 19200, In/Out Protocol: 32 / 0
terminate called after throwing an instance of 'std::runtime_error'
what(): Could not configure serial baud rate
[rover-1] process has died [pid 5438, exit code -6, cmd /home/robot/catkin_ws/devel/lib/ublox_gps/ublox_gps __name:=rover __log:=/home/robot/.ros/log/bb634996-58d2-11e8-a299-b827eb0b48c0/rover-1.log].
log file: /home/robot/.ros/log/bb634996-58d2-11e8-a299-b827eb0b48c0/rover-1*.log
The text was updated successfully, but these errors were encountered: