problems with communicating kvh gyro
I am working with ubuntu 14.04 and indigo, and I am trying to communicate with the kvh dsp3000 gyro. Downloaded the packages from the github source. compiles and builds successfully. Now, after I plugged in the gyro to the robot computer, I checked that there is a /dev/clearpath/fog path in my system. Then, I ran roslaunch kvh dsp3000.launch and it gave me the following error.
~/catkin_ws$ roslaunch kvh dsp3000.launch
... logging to /home/administrator/.ros/log/3a32e428-5579-11e8-b31d-c986401ef8c9/roslaunch-dhcp-59-208-2780.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://dhcp-59-208:55395/
SUMMARY
========
PARAMETERS
* /dsp3000/port: /dev/clearpath/fog
* /rosdistro: indigo
* /rosversion: 1.11.13
NODES
/
dsp3000 (kvh/dsp3000)
ROS_MASTER_URI=http://localhost:11311
core service [/rosout] found
process[dsp3000-1]: started with pid [2798]
[ERROR] [1526084024.469802151]: buffer filled without end of line being found (in SerialPort::readLine)
Does anyone know what this means and how I can resolve this?
Please don't use an image to display text. Images are not searchable and people cannot copy and paste the text from the image. Please update your question with a copy and paste of the error instead. Please see http://wiki.ros.org/Support#Do
Got it!!!!!
Just to exclude a problem with the actual hw: can you communicate with the device with any of the mfg's software (if they provide you with anyhing, of course)?
I will look more into if they have mfg software. I also opened an issue on the kvh github site.
I'm assuming that the manufacturer of your device (ie: dsp-3000) provides you with a manual and some software to configure the device (a Windows program typically). At least, that is what I typically get when I buy some hw from a manufacturer. Using that software is always a good first check ..
.. to make sure your hardware is at least functioning. If the mfg's software also cannot communicate with your device, then you might have other problems (ie: broken device, cable, connector or port). It's just a way to move forward with your diagnosis.
how do you determine to what port the device is connected?
this is called cross-posting, and is not too nice: at best it leads to split discussions, but typically leads to duplication (and thus waste) of effort.