chicken

[POTM] dAISy - A Simple AIS Receiver

267 posts in this topic

Yes of course. For RasPI. When I shall debug a starting script. While it is used gpsd for gps and socat for AIS.

Share this post


Link to post
Share on other sites

Ops. There is not dAISy`s driver for Debian. Ok, without RasPI - only WinXP with OpenCPN. :-) Waiting for driver...

Share this post


Link to post
Share on other sites

Ok, Ok. Thanks gmtii (post 72 I will use...). There are...

.....

pi@raspberrypi ~ $ ls /dev/ttyACM*
/dev/ttyACM0
pi@raspberrypi ~ $ sudo lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 008: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 004: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
Bus 001 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter
Bus 001 Device 006: ID 16d0:0b03 GrauTec
Bus 001 Device 007: ID 2047:0203 Texas Instruments
pi@raspberrypi ~ $ ls /dev/ttyUSB*
/dev/ttyUSB0
pi@raspberrypi ~ $
 

Share this post


Link to post
Share on other sites

Grrr! The VID/PID I bought from MCS Electronics seems to already be taken (GrauTec: 16d0:0b03).

-> Correction, it looks like someone added a GrauTec device with ID 16d0:054b to Linux, and then assumed that GrauTec also owns the VID, which is not the case.

 

In practice that shouldn't be an issue. Just go for the exposed ttyUSB0.

Share this post


Link to post
Share on other sites

It`s right - gpsd /dev/ttyUSB0 /dev/ttyACM0 -G -n  in OpenCPN connection gpsd port 2947

This string is in the start script.

Share this post


Link to post
Share on other sites

Setting up dAISy for use as a shore based AIS station that reports data to MarineTraffic is easy to do with the CC3200 and Energia.  I am still playing with it a bit but have posted working code here

 

daisy-chaining TI LaunchPads so to speak :P

Fmilburn likes this

Share this post


Link to post
Share on other sites

One of the most interesting aspects of selling your widget is seeing how other people use your product and what their requirements are.

 

dAISy was originally built for ship-geeks that are entertained for hours with MarineTraffic (like myself). I also broke out a few pins for tinkerers that want to connect dAISy to other widgets (again, like myself). Turns out, the majority of my customers are boat owners (unlike myself).

 

Boaters use dAISy to keep track of ships around them for navigation purposes, i.e. avoiding collisions. Free software called OpenCPN turns a laptop (or a RaspBerry Pi for the more geeky faction) into a chartplotter, a device that typically costs $500+. dAISy is connected via USB and provides real-time information about nearby ships. However, many boaters already have a traditional chartplotter and want to connect these with dAISy for AIS input.

 

Most chartplotters talk NMEA 0183, a serial standard compatible with RS-422. Unfortunately, that's not the same as the UART serial output of dAISy. Which leads to NMEA output as the 2nd most requested feature for dAISy (right after native WiFi*).

 

Electronic tinkerers can convert dAISy's TX output into a signal that works with some (most?) NMEA 0183 consumers using an NPN transistor and two resistors:

post-9974-0-62940900-1451180467_thumb.png

Exact resistor values don't matter that much, as their purpose is mostly to limit current. Slightly higher values should work as well.

 

Besides not being really NMEA/RS-422 compliant, requiring to solder obviously is a non-starter for the majority of my customers. So I decided to look for an integrated, more polished solution.

 

First step is implementing proper RS-422 driven from dAISy's serial output (TX). Luckily there's a chip for that. Well, there are many, but I settled for the TI UA9638.

post-9974-0-21378300-1451180959_thumb.png

 

As I didn't want to change dAISy's main PCB (NRE, the bane of mass production), I designed a PCB that screws to the backside of the existing enclosure. On the inside of the PCB is the RS-422 driver and a connector for a cable to the main PCB. The cable is soldered to existing breakout pads for TX, 5V and GND. Still on the inside, I also added a DC/DC converter so that dAISy optionally can be powered from the boat's 12V power system instead of USB. On the outside of the PCB is a beefy screw terminal to connect NMEA 0183 and 12V wiring.

 

Here is a picture of the first iteration I built today. The PCB on the left shows the inside, with DC/DC converter and related passives still unpopulated.

post-9974-0-17646200-1451181388_thumb.jpg

 

The NMEA 0183 output works as expected. I'm not sure yet about including the DC/DC converter in the final design. I'm worried that having a switching power supply inside the enclosure will introduce noise and interfere with the radio's performance.

 

I plan to add this or a similar design to my Tindie store early next year. In the meantime, any volunteers that have a chartplotter and dAISy and want to test the add-on should contact me.

 

*Besides being wireless, WiFi is popular because it's the only way to get real-time NMEA data to the iPad. Unfortunately, iOS devices do not support USB or Bluetooth from devices not approved by Apple. Today, dAISy either requires a Raspberry Pi (running Kplex or similar) or some tinkering with an ESP8266. Once it has native NMEA output, dAISy will also work with NMEA routers, some of which include WiFi.

petertux, RobG, tripwire and 2 others like this

Share this post


Link to post
Share on other sites

Now with DC/DC converter and lab tested:

post-9974-0-76752500-1451454009_thumb.jpg

I have a few spares and still look for volunteers for real-world testing.

 

The DC/DC converter didn't noticeably increase  the noise floor, so I think it should be fine. It is a ROF-78E5.0-0.5SMD-R from Recom Power. 9-36V input, 5V output at up to 500mA, and there's also a 3.3V version. Available for about $3.30 in singles at Digi-Key and Mouser.

 

Next: Reducing BOM cost, those connectors are pretty big and cost as much as the DC/DC converter. Does anyone know if terminal blocks are standardized, i.e. whether you can match and mix plug and jack? For some reason Phoenix Contact has really crappy drawings in their datasheets.
 

Share this post


Link to post
Share on other sites

Have you consider using Molex's Eurostyle 39501 and 39502 series connectors? (search on eBay for 3.5mm pluggable screw terminal block connector)

 

What's the status of dAISy BoosterPack?

 

chicken likes this

Share this post


Link to post
Share on other sites

Have you consider using Molex's Eurostyle 39501 and 39502 series connectors? (search on eBay for 3.5mm pluggable screw terminal block connector)

 

What's the status of dAISy BoosterPack?

 

Thanks for the Molex SKUs and Ebay query. 3.5mm terminal blocks look like a very common, standardized format with plenty of cheap options from various vendors.

 

The BoosterPack is a bit on the back burner right now. While it's nice as a breakout for the Si446x family of radio ICs, using it is pretty complex, particularly if you want to do more than just replicate dAISy on a F5529 LaunchPad.

 

I'm thinking about adding a G2553 onto the BoosterPack to abstract away the receiver part. Then an Energia library could receive the AIS messages via serial (or I2C??) and provide more convenient interfaces to build applications on top.

 

Also thinking about more popular form factors, e.g. a RasPi Hat or Arduino Shield.

Share this post


Link to post
Share on other sites

 

I didn't think about using NAND gates as an inverter. Good alternative to the transistor solution above.

 

Re Bluetooth, I guess your idea is to use 2 Bluetooth modules, UART serial on dAISY's side and RS232 on the NMEA device side.

Share this post


Link to post
Share on other sites

Hm, we can install esp2866 board in Arduino IDE and... I shell see. It`s about direct connect dAISy & WiFi.

Share this post


Link to post
Share on other sites

I did it(first step). Example "WiFiTelnetToSerial" is a good platform for this purpose. ESP-01 - 3.3V 50 mA.

PS GPS is connected directly to ESP-01. OpenCPN shows where I am situated by wifi (192.168.1.42:23).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now