node red serial port closing issue

513 views
Skip to first unread message

siddharth fultariya

unread,
Feb 10, 2018, 3:12:09 AM2/10/18
to Node-RED

hello, i am using johnny-five and the problem is how to close the serial port which is already opend?now the problem is when i re-deploy the flow in node-red it will generate an error as shown below:


10 Feb 10:38:33 - [info] Stopping flows
10 Feb 10:38:33 - [info] Stopped flows
10 Feb 10:38:33 - [info] Starting flows
1518239313152 Connected COM6
10 Feb 10:38:33 - [info] Started flows
1518239313157 Error Opening COM6: Access denied
(node:12788) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Unhandled "error" event. ([object Object])
(node:12788) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
1518239323160 Device or Firmware Error A timeout occurred while connecting to the Board.

Mark Setrem

unread,
Feb 10, 2018, 4:19:49 AM2/10/18
to Node-RED
there's no need to shout!

What version of node-red?
What operating system?
What version of nodejs?

siddharth fultariya

unread,
Feb 10, 2018, 5:12:47 AM2/10/18
to Node-RED

 Node-red Version : 0.18.2
Operating system : windows 10
Version of Node.js : 8.9.4

Julian Knight

unread,
Feb 10, 2018, 8:59:52 AM2/10/18
to Node-RED
Can you connect to COM6 manually using a terminal emulator or the Arduino monitor?

What makes you think that the serial port is open? The error is a permissions issue.

siddharth fultariya

unread,
Feb 11, 2018, 10:44:24 PM2/11/18
to Node-RED
i thinks that serial port is open, because when i deploy the flow first time in node red it works fine but when  i re-deploy the flow in Node-Red it throws an error "access denied" due to this behavior i thought that serial port might be opened.  

Julian Knight

unread,
Feb 12, 2018, 11:35:38 AM2/12/18
to Node-RED
Ah, so perhaps Johnny 5 or te j5 node isn't releasing the serial port on redeploy. Maybe raise an issue there?
Reply all
Reply to author
Forward
0 new messages