I'm having similar difficulties to the gentleman in this post:
ublox GPS strange characters interspersed with NMEA output
I am using u-blox on a Dell Rugged 7212 tablet to output NMEA to a virtual com port. I am getting GPS coordinates but I'm also getting a strange line of characters in the middle of the output. Any ideas on what could be causing this?
https://i.stack.imgur.com/IKOAb.jpg
You can try replacing the installed driver with the u-blox VCP device driver for Windows Download from here. Driver binaries are at the bottom of the page.
This driver creates 2 VCP Virtual COM Ports and publishes the NMEA strings. Beware, this VCP driver does not emulate/work as a Hardware Serialport. So the asynchronous callbacks etc. do not work. You need to busy poll to read the port. After installation of the driver, you can test the driver using Putty or an application like VisualGps to make sure the driver is working the way you expect it to work.
Related
Working with the STM32L062 Cortex-M0 and CubeMX the generated USB CDC-ACM code works fine in Windows. With loopback code running on the STM32 and TerraTerm running on Windows characters typed in the terminal window correctly echo back. However, when this same system is then plugged into a laptop running Ubuntu, the device fails to enumerate. Even worse, the system doesn't appear to respond to the connection whatsoever- no new messages appear via dmesg that even a failed enumeration is going on. Given that the code used is generated by CubeMX wizards it is difficult to know what to start to troubleshoot. Any suggestions?
As an aside, this isn't the first issue presented by CDC-ACM drivers. Implementing a USB CDC-ACM stack for a PIC32MM processor, data can be sent to the host but not received from the host, however, if the driver is switched to plain vanilla CDC then data can be sent both ways no problem. So it seems maybe Ubuntu has some issues with the default USB drivers, but either way, it's very odd that the ST driver gets zero response at all from the system.
I am using a ublox GPS for a data acquisition application. The device is outputting NMEA on a virtual COM port.
The NMEA output works just fine. But between the NMEA messages strange characters are interspersed. See screenshot below from Realterm with setting "Ascii".
Can somebody tell me what this is? And ideally what commands I would need to send to the device to disable this output?
You should disable the UBX binary protocol. The NMEA and UBX messages are interleaved on the same port. This can be done by sending UBX-CFG-PRT message disabling the UBX output protocol on your port. You can use the handy u-center application avaiable from u-blox website to perfrom this task.
An alternative is to reflash the device or remove the backup battery. It should default back to NMEA only.
We're trying to read data from a digital yacht AISnet base station on a linux box. From what I've read, Digital Yacht has drivers for both osx and windows (but not linux for this unit) and their job is to create a virtual com port so that the device can send an NMEA 1083 stream as if it's doing RS-232 serial communication. We are OK with parsing the NMEA data ourselves, but I don't know much about drivers. Wondering if anyone has any experience getting NMEA data from a digital yacht or similar device in to linux? Is the USB to virtual RS-232 something common for other devices or something that would be practical to make ourselves? Any pointers much appreciated.
Answering myself: use the GPSD gps daemon, as GPS uses the same protocol as AIS (something I didn't know when I posted the initial question and was first dipping into AIS). GPSD handles listening to the stream of raw NMEA data on the device and provides a high level interface to get the data already parsed to JSON. It was very easy to get going on linux and supposedly also runs on OSX though I haven't tried it.
If using Python, there is also a client library for working with the GPSD stream to making AIS listening applications.
GPSD: http://www.catb.org/gpsd/
https://github.com/wadda/gps3/blob/master/examples/agegps3.py
First of all, there's a similar thread on OpenQNX posted years ago but the solutions don't really apply for me.
Having said that, I want to create an OS image of QNX 6.6.0 to put on a Compact Flash card. This card is plugged in an USB adapter which is connected to my host pc. I'm running Neutrino in a VM (VMware/VirtualBox) for which I enabled USB support. Generally, the adapter works fine under Win (current host) and Linux.
The (apparently out-dated) tutorial I was following stated to search for devices named umass* or hd* after connecting the USB adapter. But there aren't any (except for hd0).
See also "ls /dev" screenshot.
The processes devb-umass and io-usb are running. So I expect that the adapter is detected automatically.
Any suggestions what went wrong?
OK, it seems that I had to restart the usb driver 'devb-umass' (several times). When the card reader is already plugged-in during the booting the driver will not detect it autoamtically. Thus one has to unplug and plug it in again after the devb-umass was getting re-started. It also might have been that the Host Controller Driver (HCD) was set to 'ohci' instead of 'ehci'.
Everything is working now as expected.
(Thanks Tim from the OpenQNX forum! ;) )
Quite a while I am struggling with a problem regarding the installation of certain USB device driver in Windows CE 6.0.
The device is some kind of Digital and Analog IO device that connects to the USB port.
It is the LabJack U3.
I followed all instruction and put the driver (labjackusb.dll) and coresponding registry entries into the Windows CE image but the device is not detected correctly.
On every boot up a small Message box came up with the Title "Unidentified USB Device"
and the message "Enter the name of the driver for this USB device:"
Whatever name I put into it want work. I tried the name of the dll. Some title in from the registry and so on but never succedes.
The driver does not work nor the device.
The customer support can not help me so I am asking here somebody to help me at least
with a steps to follow to try to find a solution.
Why the OS does not matches the USB device with the corresponding driver?
I checked everything one million times and everything is in place.
There are a load of reasons this might fail. First:
Is the driver definitely a Windows CE driver?
Is it built for CE 6.0 (not 5.0 or something else)?
Is it built for the same processor architecture you have?
The way to really debug this is to hook up KITL, put in a debug version of device.exe and see what the device managet is actually doing when you plug in the device. A way better and way more reliable mechanism than just trying to guess.