Signal-K node server up and running on Raspberry Pi 3 and accessible via built in wireless LAN

306 views
Skip to first unread message

JRT78

unread,
Mar 7, 2016, 8:00:31 PM3/7/16
to Signal K
Have just received my RPI 3 and have got the Signal K node server up and running and now the in built wlan on the rpi board is also running.
So many options now...

Used the following instructions on getting the wlan to be an access point if anyone is interested:

 

JRT78

unread,
Mar 7, 2016, 8:01:38 PM3/7/16
to Signal K
Forgot to mention, the wireless range seems very good for a antenna on chip setup.

Johan Barne

unread,
Apr 23, 2016, 1:32:14 PM4/23/16
to Signal K
Good to hear you got it running. I have recently worked with the nodejs server on a Raspberry Pi 2 with success. In order to reproduce my successful implementation, I wrote up all steps in a file.

However, when I got my Raspberry Pi 3, I used the notes and failed installing the nodejs server. It failed on the serialport part.

You did not have that problem?

Teppo Kurki

unread,
Apr 24, 2016, 10:27:19 AM4/24/16
to signalk
On Sat, Apr 23, 2016 at 8:32 PM, Johan Barne <johan...@gmail.com> wrote:
In order to reproduce my successful implementation, I wrote up all steps in a file.

However, when I got my Raspberry Pi 3, I used the notes and failed installing the nodejs server. It failed on the serialport part.

This is somewhat the reason why I started the Ansible effort at https://github.com/tkurki/marinepi-provisioning - instead of handwritten notes the Ansible playbooks have instructions that can install all the relevant software on a fresh installation.

The playbooks' signalk role installs the latest SK Node server without problems on RPi3. Underneath the hood it just git clones the SK node server and runs npm install on it. I can't recall any special steps needed for serialport to work and I just activated it myself yesterday.

What problems are you running into?

PS. troubleshooting is sometimes more straightforward in Slack on #support channel. The problem there is that the resolution is not googlable, so summarising to the list is good practice/citizenship.


JRT78

unread,
Apr 24, 2016, 9:30:08 PM4/24/16
to Signal K
Yes, I did have a problem with the serial port not working.  Check my other post just recently about a solution to fix it.

Johan Barne

unread,
Apr 25, 2016, 12:30:57 PM4/25/16
to Signal K
Hi Justin!

Thanks for the pointer. I think I found the post you refer to. There you state that:

"then modified the code as per the workaround mentioned and then was able to install the serial port correctly and the server runs from the serial port."

Which modification do you refer to?

Do you have a link to it?

Cheers!

Teppo Kurki

unread,
Apr 25, 2016, 3:23:00 PM4/25/16
to signalk
Since the problem is related to a really old version of node that is bundled with Raspbian Jessie if I were you I would just uninstall that version of node and reinstall node 5 with the instructions at https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions






--
You received this message because you are subscribed to the Google Groups "Signal K" group.
To unsubscribe from this group and stop receiving emails from it, send an email to signalk+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages