serialport module won't install

[cdsteinkuehler]

On an up-to-date (as of 2016.04.23) Ubuntu 14.04 64-bit x86 system, the serialport module does not install, causing the firenodejs/scripts/install.sh script to fail.

This seems related to the nodejs/node confusion in Debian. When I manually created a symlink from /usr/bin/node to /usr/bin/nodejs, the seriaport package installed and the setup/install.sh completed successfully.

[firepick1]

Charles

How vexing. :(

I abandoned serialport and yet it continues to plague. sigh

Simon ran into this a few weeks ago.

1. double check firenodejs is latest release:
   https://github.com/firepick1/firenodejs/releases
2. I typically expunge all node from my pi then reinstalled node via
   firenodejs install

I am setting up my Pi3 for the first time and you're ahead of me in that.
My 3DP broke down so my hair is currently on fire. As soon as that's fixed,
I'll revisit install instructions.

Thanks,
Karl

On Sat, Apr 23, 2016 at 3:39 PM, cdsteinkuehler notifications@github.com
wrote:

On an up-to-date (as of 2016.04.23) Ubuntu 14.04 64-bit x86 system, the
serialport module does not install, causing the
firenodejs/scripts/install.sh script to fail.

This seems related to the nodejs/node confusion in Debian. When I manually
created a symlink from /usr/bin/node to /usr/bin/nodejs, the seriaport
package installed and the setup/install.sh completed successfully.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#6

Karl Lew
FIREPICK SERVICES LLC
karl@firepick.org
www.firepick.org

[cdsteinkuehler]

Simon ran into this a few weeks ago.

1. double check firenodejs is latest release:
   https://github.com/firepick1/firenodejs/releases

1. I was using master, which based on the commit log looks like it's the
   same as the latest release.

2. I typically expunge all node from my pi then reinstalled node via
   firenodejs install

2. That might be the issue. I didn't manually install anything node
   related, but there might have been something present from the default
   Ubuntu install.

I am setting up my Pi3 for the first time and you're ahead of me in that.
My 3DP broke down so my hair is currently on fire. As soon as that's fixed,
I'll revisit install instructions.

Note I'm on a quad-core x86_64 Ubuntu system, not a RPi. Should I
switch to using a RPi? I only have a 1-B on-hand, and I figured the
memory+CPU on the x86 system would help with the image recognition code.

Charles Steinkuehler
charles@steinkuehler.net

[cdsteinkuehler]

Also, I think this has something to do with node installed on the host system, not the local copy you seem to build in the firenodejs directory. The fix was to create a symlink from node to nodejs in the /usr/bin directory.

[firepick1]

Charles,

The advantage of your quad-core is faster image processing.
The down-side of the quad-core is slower image acquistion via USB vs
RaspberryPi camera.

This is an odd conundrum that will sort itself out as the hardware vendors
wake up and make things better. I'll always support Raspberry Pi as the
baseline, but firenodejs should work on arbitrary Ubuntus. For example, I
run it on my Chromebook Pixel.

Karl

On Sun, Apr 24, 2016 at 6:28 AM, cdsteinkuehler notifications@github.com
wrote:

Simon ran into this a few weeks ago.

1. double check firenodejs is latest release:
   https://github.com/firepick1/firenodejs/releases

I was using master, which based on the commit log looks like it's the
same as the latest release.

2. I typically expunge all node from my pi then reinstalled node via
   firenodejs install

That might be the issue. I didn't manually install anything node
related, but there might have been something present from the default
Ubuntu install.

I am setting up my Pi3 for the first time and you're ahead of me in that.
My 3DP broke down so my hair is currently on fire. As soon as that's
fixed,
I'll revisit install instructions.

Note I'm on a quad-core x86_64 Ubuntu system, not a RPi. Should I
switch to using a RPi? I only have a 1-B on-hand, and I figured the
memory+CPU on the x86 system would help with the image recognition code.

Charles Steinkuehler
charles@steinkuehler.net

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#6 (comment)

Karl Lew
FIREPICK SERVICES LLC
karl@firepick.org
www.firepick.org

[firepick1]

...and by supporting Pi fully, I can sneak around the rather thorny issue of supporting arbitrary Ubuntu machines. My guess is that owners of such Ubuntu machines will be adept at solving issues peculiar to their machines. :D

[cdsteinkuehler]

Understood. I'll get a Pi if I need to, but I think I can get the Ubuntu machine working. Right now I'm doing what I can while waiting for a new Arduino to show up (I gave away all mine when I switched to the BBB) so I can actually start moving some motors.

...and I'm pretty sure there are some pretty advanced vision cards available for x86 machines if the USB camera turns out to be a huge bottleneck. :-)

[firepick1]

Awesome! I'm looking forward to see you post your precision charts to the
group--these visual data points are helping us all understand how FPD
behaves in the wild.

On Sun, Apr 24, 2016 at 6:42 AM, cdsteinkuehler notifications@github.com
wrote:

Understood. I'll get a Pi if I need to, but I think I can get the Ubuntu
machine working. Right now I'm doing what I can while waiting for a new
Arduino to show up (I gave away all mine when I switched to the BBB) so I
can actually start moving some motors.

...and I'm pretty sure there are some pretty advanced vision cards
available for x86 machines if the USB camera turns out to be a huge
bottleneck. :-)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#6 (comment)

Karl Lew
FIREPICK SERVICES LLC
karl@firepick.org
www.firepick.org