OpenPlotter project

[zugol]

hey there,

first, Id like to thank you for developing a great piece of software.

Im running OpenPlotter 0.6 on a Raspberry 1 Rev.B.

I have a Terratec Cynergy T-StickRC Rev3 with the Realtek 2838U chipset, which I believe is similar to the 2832U and should work with open plotter.

The stick is recognized by the raspberry, lsusb -v gives me:

iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDIR

But the AIS button in open plotter is greyed out.

Any hints?

Regards,

[petter5]

Originally Posted by zugol

hey there,

first, Id like to thank you for developing a great piece of software.

Im running OpenPlotter 0.6 on a Raspberry 1 Rev.B.

I have a Terratec Cynergy T-StickRC Rev3 with the Realtek 2838U chipset, which I believe is similar to the 2832U and should work with open plotter.

The stick is recognized by the raspberry, lsusb -v gives me:

iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDIR

But the AIS button in open plotter is greyed out.

Any hints?

Regards,

First of all, I would recommend to upgrade to the latest release:
Test OpenPlotter v0.8.0beta | Sailoog

If still problems after that, It will be easier to support you.

[zugol]

Hey,
thx for the response.
I updated to 0.8, but still no luck. It is still greyed out.

Any further advices?

regards,

[Alekoy]

Have you set it up under the SDR-AIS-tab in openplotter?

Have a look in the documentation

[Sailoog]

Originally Posted by zugol

hey there,

first, Id like to thank you for developing a great piece of software.

Im running OpenPlotter 0.6 on a Raspberry 1 Rev.B.

I have a Terratec Cynergy T-StickRC Rev3 with the Realtek 2838U chipset, which I believe is similar to the 2832U and should work with open plotter.

The stick is recognized by the raspberry, lsusb -v gives me:

iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDIR

But the AIS button in open plotter is greyed out.

Any hints?

Regards,

Although it says 2838 chipset, it has a 2832 and should work. Never saw one of them but I think I know what is the problem.

Open the file /home/pi/.config/openplotter/openplotter.py

and change the line 699:

if 'DVB-T' in output:

by:

if 'DVB-T' in output or 'RTL2838' in output or 'RTL2832' in output:

If it works I will change the master branch. Thanks!

[Sailoog]

Originally Posted by zugol

hey there,

first, Id like to thank you for developing a great piece of software.

Im running OpenPlotter 0.6 on a Raspberry 1 Rev.B.

I have a Terratec Cynergy T-StickRC Rev3 with the Realtek 2838U chipset, which I believe is similar to the 2832U and should work with open plotter.

The stick is recognized by the raspberry, lsusb -v gives me:

iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDIR

But the AIS button in open plotter is greyed out.

Any hints?

Regards,

Forgot my last post, it will work but I am not including some others "not conventional" dongles. Could you copy paste the complete line when you do lsusb?

[zugol]

hey,

thx for the response.
Should I update the openplotter.py? I think i didn't quite get your last post.

This is the complete lsusb:

Bus 001 Device 005: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 008: ID 0ccd:00d3 TerraTec Electronic GmbH
Bus 001 Device 007: ID 1546:01a7 U-Blox AG
Bus 001 Device 006: ID 2101:8501 ActionStar
Bus 001 Device 004: ID 2101:8500 ActionStar
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Lsusb -v


Bus 001 Device 008: ID 0ccd:00d3 TerraTec Electronic GmbH
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0ccd TerraTec Electronic GmbH
idProduct 0x00d3
bcdDevice 1.00
iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDIR
iSerial 3 00000001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4 USB2.0-Bulk&Iso
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 Bulk-In, Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 Bulk-In, Interface
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 2
Device Status: 0x0000
(Bus Powered)

[Alekoy]

Originally Posted by zugol

hey,

thx for the response.
Should I update the openplotter.py? I think i didn't quite get your last post.

No, open a terminal window, write
"sudo nano /home/pi/.config/openplotter/openplotter.py"

Find the mentioned line, edit as described

Ctrl+x to exit, y to save etc and test

And please tell sailoog if it worked, so he can update the file for future versions

[zugol]

i did, it doesn't change anything, neither in lsusb nor in the open plotter settings...

[Sailoog]

Originally Posted by zugol

hey,

thx for the response.
Should I update the openplotter.py? I think i didn't quite get your last post.

This is the complete lsusb:

Bus 001 Device 005: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 008: ID 0ccd:00d3 TerraTec Electronic GmbH
Bus 001 Device 007: ID 1546:01a7 U-Blox AG
Bus 001 Device 006: ID 2101:8501 ActionStar
Bus 001 Device 004: ID 2101:8500 ActionStar
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Ok.

I thought that the output of your normal lsusb was

iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDI

but it is just

Bus 001 Device 008: ID 0ccd:00d3 TerraTec Electronic GmbH

so the best solution to apply here is comparing the idVendor:idProduct (in your case 0ccd:00d3) with the list of all supported devices. I was assuming that all the compatible devices contain 'DVB-T' or 'RTL283x' in the lsusb output but this is not true. Let me some time, I will fix this on github master branch. Thanks.

[Sailoog]

Originally Posted by Sailoog

Ok.

I thought that the output of your normal lsusb was

iManufacturer 1 Realtek
iProduct 2 RTL2838UHIDI

but it is just

Bus 001 Device 008: ID 0ccd:00d3 TerraTec Electronic GmbH

so the best solution to apply here is comparing the idVendor:idProduct (in your case 0ccd:00d3) with the list of all supported devices. I was assuming that all the compatible devices contain 'DVB-T' or 'RTL283x' in the lsusb output but this is not true. Let me some time, I will fix this on github master branch. Thanks.

Done, please download from github master branch, test and confirm.

These are all the supported devices now:

Generic RTL2832U (e.g. hama nano)
ezcap USB 2.0 DVB-T/DAB/FM dongle
Terratec Cinergy T Stick Black (rev 1)
Terratec NOXON DAB/DAB+ USB dongle (rev 1)
Terratec Cinergy T Stick RC (Rev.3)
Terratec NOXON DAB/DAB+ USB dongle (rev 2)
Compro Videomate U620F
Compro Videomate U650F
GTek T803
Lifeview LV5TDeluxe
Twintech UT-40
Dexatek DK DVB-T Dongle (Logilink VG0002A)
Dexatek DK DVB-T Dongle (MSI DigiVox? mini II V3.0)
Dexatek Technology Ltd. DK 5217 DVB-T Dongle
Genius TVGo DVB-T03 USB dongle (Ver. B)
GIGABYTE GT-U7300
DIKOM USB-DVBT HD
Peak 102569AGPK
SVEON STV20 DVB-T USB & FM

[Nick_Currawong]

Hello All,

I have got my IMU sensor working and producing XDR sentences (from Inpector).

I am trying to see/use them in Opencpn 's dashboard, I can see that openplotter produces 2 XDR sentences , 1 for pressure/temp and then a 2nd for pitch/heel.

Is it possible to get it to produce only one or how can I filter/modify or combine these sentences? Either in openplotter or via opencpn NMEA converter or some other means?

Also Has anyone got the dashboard to display the pressure reading, I have used the NMEA converter plugin to create a $wimda, sentence , using
$WIMDA,,I,$OSXDR2,$OSXDR3,,,,,,,,,,,,,,,

If someone could provide me with their conversion statement that would be great.

Thanks for any ideas and assistance as always

[Nick_Currawong]

Hi

A quick update I changed the talker ID in ~/.config/openplotter/i2c.py for the heel/pitch sentences, which helped with one issue, but still can't get them to display in the opencpn dashboard.

Any idea which NMEA sentence the dashboard uses?

Thanks

[Sailoog]

Originally Posted by Nick_Currawong

Hi

A quick update I changed the talker ID in ~/.config/openplotter/i2c.py for the heel/pitch sentences, which helped with one issue, but still can't get them to display in the opencpn dashboard.

Any idea which NMEA sentence the dashboard uses?

Thanks

Hi Nick
I have never been able to find out what sentences opencpn needs for heel and pitch, neither on code nor here:
NMEA Sentences | Official OpenCPN Homepage
There you can see sentences for pressure and temp but they are obsolete and I remember doing test long time ago and some of them even didn't work.

XDR sentences are divided in OP due to limitations in UDP message sizes.

I think Dashboard plugin is not a good idea as a instrument panel at this moment, actually NMEA 0183 is not a good idea for this because it has limited standard sentences. It seems that opencpn is doing some work to implement signal k and that could be the solution.

I think that is not worth working in OpenPlotter to be opencpn/dashboard compatible because we should focus in the future but if you get something with NMEA converter or modifying the code I could merge it.

[Sailoog]

Well, we have the first version of our low-cost USB-N2K converter ready!

https://sailoog.gitbooks.io/openplotter-documentation/content/en/can-usb.html

CAN-USB Stick is able to read and write on the CAN bus but for safety you have to select what data you want to transmit before writing and we are working in a software to do this. Reception is working right

Does work with OpenPlotter, Signal K, CANBoat and Open Skipper.