Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 16 22:40

    monteslu on master

    Added support for odroid-io Merge pull request #36 from rac… (compare)

  • Sep 16 22:40
    monteslu closed #36
  • Sep 16 22:40

    monteslu on master

    Update gpio.js Update gpio.html Update gpio.js and 1 more (compare)

  • Sep 16 22:40
    monteslu closed #38
  • Apr 15 14:54
    monteslu commented #37
  • Apr 15 14:54
    monteslu commented #37
  • Apr 15 10:00
    Laca81 commented #37
  • Apr 15 09:59
    Laca81 commented #37
  • Mar 24 20:55
    Petapton opened #38
  • Mar 21 23:05
    T3rorx commented #37
  • Mar 21 15:10
    monteslu commented #37
  • Mar 21 14:55
    T3rorx commented #37
  • Mar 21 00:16
    monteslu commented #37
  • Mar 20 23:05
    T3rorx commented #37
  • Mar 07 08:29
    pleemans67 commented #37
  • Mar 07 08:26
    pleemans67 opened #37
  • Feb 16 12:38
    Ib2cool commented #20
  • Dec 20 2018 21:36
    PiroozMB commented #2
  • Nov 29 2018 03:05
    racerxdl opened #36
  • Oct 07 2018 10:02
    Ch3fk0ch88 commented #35
nicnet
@nicnet

Johnny-five node in node-red, using TCP socket.
I can't get it to work - just stays with yellow "connecting" status.

The config for node-red J5 node is:
Connection: TCP socket
TCP host: 192.168.100.212
TCP port: 23

Transparent bridge on .212, is provided by ESP8266 running the superb esp-link.
It's connected serially (115200) to arduino pro-mini running latest Standardfirmata.

The bridge works fine - works nicely with node itself, rather than node-red.

Luis Montes
@monteslu
cool
anything showing in the console?
nicnet
@nicnet

These only:

node-red-0 27 Apr 22:02:47 - [info] Starting flows
node-red-0 27 Apr 22:02:47 - [info] [inject:35c6bd75.a7e49a] repeat = 100
node-red-0 27 Apr 22:02:47 - [info] Started flows
node-red-0 1461783767390 Device(s) Firmata

Here's the node itself:
"id":"a58aecce.d7db78",
"type":"nodebot",
"z":"3596b182.73a88e",
"name":"",
"username":"",
"password":"",
"boardType":"firmata",
"serialportName":"",
"connectionType":"tcp",
"mqttServer":"",
"socketServer":"",
"pubTopic":"",
"subTopic":"",
"tcpHost":"192.168.100.212",
"tcpPort":"23",
"sparkId":"",
"sparkToken":"",
"beanId":"",
"impId":"",
"meshbluServer":"https://meshblu.octoblu.com",
"uuid":"",
"token":"",
"sendUuid":""
And:
"id":"5783dffc.c585d8",
"type":"gpio out",
"z":"3596b182.73a88e",
"name":"",
"state":"OUTPUT",
"pin":"13",
"i2cDelay":"0",
"i2cAddress":"",
"i2cRegister":"",
"outputs":0,
"board":"a58aecce.d7db78",
"x":303.1666564941406,
"y":757.066650390625,
Luis Montes
@monteslu
ok, figured out how to test this locally without my esp here
trying something now...
Luis Montes
@monteslu
@nicnet found a bug. published a new node-red-contrib-gpio
firmata over tcp should work now
nicnet
@nicnet

@monteslu TCP connection confirmed working. Much more stable than using virtual serial port as well of course.
Many thanks!!!!!!!

I'll keep on testing ...

Luis Montes
@monteslu
cool!
nicnet
@nicnet
@monteslu Having some stability problems - I can't maintain a connection for very long, before it craps out, and I have to reset everything.
I was reading this old thread rwaldron/johnny-five#627 and it mentioned "TCP ... however it is also quite problematic under reasonable message load because of the FIFO implementation on the bridge. This is a known problem"
I wonder if this is the problem I'm running in to.
So there is also this UDP transparent bridge https://gist.github.com/ajfisher/5fe60fe7d8c49b3223f0
Will this work with node-red-contrib-gpio, using the UDP broadcast settings of the nodebot config?
Luis Montes
@monteslu
definitely worth giving udp a shot
ajfisher seems to like it a lot more than tcp
nicnet
@nicnet

Having similar problem with UDP - nodebot stays on yellow "connecting".
Here's the definition:
"id":"2ccd99cb.043aa6",
"type":"nodebot",
"z":"3596b182.73a88e",
"name":"",
"username":"",
"password":"",
"boardType":"firmata",
"serialportName":"/dev/ttyUSB0",
"connectionType":"udp",
"mqttServer":"",
"socketServer":"",
"pubTopic":"",
"subTopic":"",
"tcpHost":"192.168.4.1",
"tcpPort":"1025",
"sparkId":"",
"sparkToken":"",
"beanId":"",
"impId":"",
"meshbluServer":"https://meshblu.octoblu.com",
"uuid":"",
"token":"",
"sendUuid":""
Probably not a problem, but the definition could be changed so it was UCP host and port, rather than TCP host and port.
Could there be similar bug here as well? At least the symptoms are the same (not getting further than "connecting")?

Thanks for your help!

nicnet
@nicnet

@monteslu Forgot to add, it works perfectly fine with node example script:

https://gist.github.com/ajfisher/5fe60fe7d8c49b3223f0#file-test-js

Luis Montes
@monteslu
@nicnet had to updated udp-serial and node-red-contrib-gpio
works super fast now over udp
nicnet
@nicnet

@monteslu Confirmed - as you say, really quick now. And rock solid stable.
This is now really usable - thanks a lot!

Now I just need to re-configure the UDP bridge with static IP in station mode, rather than softAP. Have you managed this with ajfisher's UDP bridge?
When I try to reconfigure it, it just crashes, and I need to reflash. So currently stuck in softAP mode with only 192.168.4.1 as IP - not very flexible ...

Luis Montes
@monteslu
I haven't used the udp bridge (i fixed node-red-contrib-gpio it with a local upd server relay), but if it's anything like the TCP bridge, you can use AT commands to setup the IP after you connect to it
victorim
@victorim

Hi, I'm wondering if anyone can help me. I'm incredibly new to this stuff so please excuse me if I seem like I've no idea what I'm talking about! I'm using johnny-five with node-red an arduino nano to try to turn pin 9 on when I click an input node.
I entered this into my johnny5 node.

var five = require("johnny-five");
var board = new five.Board();

board.on("ready", function() {
this.pinMode(9, five.Pin.OUTPUT);
this.digitalWrite(9, 1);
});

but when I try to deploy the flow, node red stops working and I get this:

1485359910665 Error Error Resource temporarily unavailable Cannot lock port
25 Jan 15:58:30 - [red] Uncaught Exception:
25 Jan 15:58:30 - TypeError: Uncaught, unspecified "error" event.
at TypeError (<anonymous>)
at Board.EventEmitter.emit (events.js:74:15)
at Board.log (/home/victoria/.node-red/node_modules/johnny-five/lib/board.js:630:8)
at Board.(anonymous function) [as error] (/home/victoria/.node-red/node_modules/johnny-five/lib/board.js:641:14)
at Board.finalizeAndBroadcast (/home/victoria/.node-red/node_modules/johnny-five/lib/board.js:369:12)
at Board.<anonymous> (/home/victoria/.node-red/node_modules/johnny-five/lib/board.js:147:18)
at Board.<anonymous> (/home/victoria/.node-red/node_modules/johnny-five/node_modules/firmata/lib/firmata.js:569:7)
at SerialPort.EventEmitter.emit (events.js:95:17)
at SerialPort._error (/home/victoria/.node-red/node_modules/serialport/lib/serialport.js:150:10)
at SerialPort.<anonymous> (/home/victoria/.node-red/node_modules/serialport/lib/serialport.js:172:19)

The only way to be able to start node red again is by going into my flows file and deleting the johnny5 node.

Anybody know what's going on?

Luis Montes
@monteslu
I can try and reproduce. Can you get me version on node-red you're using and version of node?
also what does your flow look like
there was some recent changes to node-serialport that I think might be causing problems
victorim
@victorim
Sure, one second. My flow is just input -> johnny5 as described above -> debug
Node-RED version: v0.14.6
victoria@victoria-ThinkPad-W540:~/.node-red/node_modules$ node -v
v0.10.25
Luis Montes
@monteslu
cool. give me a few and I can try and reproduce
oh, and which board?
victorim
@victorim
Arduino nano 328
Luis Montes
@monteslu
cool. same as an uno.
one more thing, which OS?
victorim
@victorim
Ubuntu 14.04
Luis Montes
@monteslu
cool
Luis Montes
@monteslu
ok, I think I know what's going on. I should have a fix soon