Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

IOT2000 Input/Output Module Problem with DI1/DI3/DI4 on Node-RED

Created by: abajolle at: 11/20/2018 10:27 AM (9 Replies)

Rating (1)

Thanks 7

10 Entries

11/20/2018 10:27 AM	Rate (0)
abajolle Advanced Member Joined: 6/25/2018 Last visit: 7/27/2023 Posts: 19 Rating: (2)	Hi guys, I have connected different machine outputs to my IOT2000 Input/Output Module, and on Node-RED, I assigned the ports as per the documentation, so DI0 with D12, DI1 with D11, DI2 with D10. DI3 with D9, and DI4 with D4. Unfortunately I do not get anything on DI1, DI3 and DI4. I have tried that with several IOT2020, with several Input/Output modules, but the problem is still the same. For all those devices the configuration is as follows: mraav1.9.0 node-red-node-intel-gpio v0.0.6 Node-RED v0.19.5 The problem are not coming from the signal, I have inverted the wires, tried several machines, some offline test stations, and consistently those 3 inputs do not work, the 2 others works perfectly. The input signal are nice 24v signals. I also tried the iot2000 specific nodes from bergmanu [Here], but no difference, nothing is detected on those 3 input pins, and they sometims make node red crash, and when I activate the input I get a "lost connection to server reconnecting" and I can't reconnect, I have to restart the IOT2000. What can I try to solve this issue ?

Suggestion To thank Quote Answer

11/22/2018 10:42 AM	Rate (0)
Fe_lipe Silver Member Joined: 12/12/2016 Last visit: 4/8/2024 Posts: 640 Rating: (60)	Hello, Remember that if you are using the intel_gpio package: You will get no reaction from the DIs on the I/O Shield because only GPIO 2 and 3 support interrupts. And GPIO 2 and 3 are not mapped on the I/O Shield. Imho the nodes for the I/O Shield seem a bit buggy and do not work for me on the IOT2020. I will have a look into the nodes to see what's going wrong, but for now please test this nodejs code in the attachment: Copy read-di-test.js to /usr/lib/ Run it with node read-di-test.js This will continuously read all DIs on your I/O-Shield. Make sure M0 is wired to something and your input voltage is >12V. Let me know if this works for you. If it doesn't, try bumping up the Gpio voltage to 5V with the jumper on the arduino shield. Kind regards! Attachment read-di-test.zip (836 Downloads)

Suggestion To thank Quote Answer

11/22/2018 2:03 PM	Rate (0)
iiot2k Silver Member Joined: 9/7/2018 Last visit: 2/16/2021 Posts: 16 Rating: (6)	Hi Fe_lipe, the problem are the intel mraa library. The concept of mraa does'nt work on IOT2000. Therefore any nodes with mraa has problems. We are working on new nodes for IOT2000. Very thanks to Ocean_. He give us her replacement of mraa and we continue this with new features. If the nodes are ready to use, we put in Github and npm. iiot2k group
	Last edited by: iiot2k at: 11/22/2018 2:04:55 PM Last edited by: iiot2k at: 11/22/2018 2:29:55 PM
Suggestion To thank Quote Answer

11/23/2018 2:32 AM	Rate (0)
abajolle Advanced Member Joined: 6/25/2018 Last visit: 7/27/2023 Posts: 19 Rating: (2)	Hi Fe_lipe, Thanks I tried your script and I have no issues reading the status on all the DI. They are functionals. My DI are connected to some machine PLC signals, so for my application I have to use a much slower refresh time than 1000ms. With the other nodes using mraa library at some point in time, within few minutes of reading they would all of a sudden stop getting the status of my pins. For the past few days I have been trying to work around some nodes using mraa library. The main change is that I have added a callback function to the SetInterval function. It seems to be improving things, at least for now I did not get any reading errors since more than 18h, so that's a good point. One drawback is that at the moment I can't deploy again the flow from Node-RED after making some modifications otherwise I get 2 readings at the same time per pin. So I need to restart the IOT2000 device after deploy to fix that bug. It is for sure linked to my callback, but I have not figured out a way to get rid of that yet. I have attached the nodes, feel free to try them and if you have any clue on the bug I mentioned let me know how to solve it. iiot2k, if you have this new library or new nodes available even for debug or test, I am keen to try them. Cheers, Antoine
	Last edited by: abajolle at: 11/25/2018 9:09:20 AM I have most likely found the bug that requires a restart after a new deploy, to be confirmed after test on 26-11-18. Last edited by: abajolle at: 11/26/2018 11:23:32 AM Attachment removed.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users bergmanu

11/26/2018 11:27 AM	Rate (0)
abajolle Advanced Member Joined: 6/25/2018 Last visit: 7/27/2023 Posts: 19 Rating: (2)	Hi, So I confirm the Digital Input node is working fine, it has been connected to my machines for the past 3 days without any problems. I have added the status indicator, which also works fine. On the other hand I still have the annoying bug that require a reboot after deployment, clearly due to a poor management to clear my timeout linked to the callback, but I can't find a workable fix so far ! I am not giving up, but if there are JavaScript experts around I am pretty sure they will be able to spot the issue a lot faster than me. Feel free to test the latest version attached. Cheers, Antoine
	Last edited by: abajolle at: 11/29/2018 8:38:16 AM New version published below, with no more annoying bug.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Fe_lipe

11/29/2018 8:37 AM	Rate (1)
abajolle Advanced Member Joined: 6/25/2018 Last visit: 7/27/2023 Posts: 19 Rating: (2)	Hi dear community, Good news, I have it solved, and now it's working perfectly, no reading issues, you can redeploy as many times as you want without needing to restart the IOT2000... Here is the modified code: var sys = require('util') var exec = require('child_process').exec; module.exports = function(RED) { var mraa = require('mraa'); /***************************************************/ / New functions / /*************************************************/ function newSetInterval(func, interval) { newSetInterval.Ids = newSetInterval.Ids \|\| {}; newSetInterval.IdCount = newSetInterval.IdCount \|\| 0; var That = this; var Id = newSetInterval.IdCount++; var FFBug = arguments.length - 2;//To prevent Firefox bug that adds an extra element to the arguments ( function Fn() { var args = [].slice.call(arguments, 0, FFBug);//To prevent Firefox bug that adds an extra element to the arguments func.apply(this, args); newSetInterval.Ids[Id] = setTimeout.apply(this, [Fn, interval].concat(args)); } ).apply(That, [].slice.call(arguments, 2, arguments.length)); return Id; } function clearInterval(Id) { if(!newSetInterval.Ids \|\| !newSetInterval.Ids[Id]) { return false; } clearTimeout(newSetInterval.Ids[Id]); return true; } /**************************************************/ exec("echo 63 > /sys/class/gpio/export"); function gpioDin(n) { RED.nodes.createNode(this,n); var node = this; node.pin = n.pin; node.updateInterval = n.updateInterval; node.mGpio = new mraa.Gpio(parseInt(node.pin)); node.mGpio.mode(mraa.PIN_GPIO); node.mGpio.dir(mraa.DIR_IN); var lastPinState = 0; var currentPinState = node.mGpio.read(); var timerId = newSetInterval(function() { if(node.pin != "ub") { currentPinState = node.mGpio.read(); } else { exec("cat /sys/class/gpio/gpio63/value", function(error, stdout, stderr) { currentPinState = parseInt(stdout)}); } if(currentPinState === 0 \|\| currentPinState === 1) { if (currentPinState != lastPinState) { if(currentPinState === 0) node.status({fill:"grey",shape:"ring",text:"Low"}); else if(currentPinState === 1) node.status({fill:"grey",shape:"dot",text:"High"}); var msg = { payload:currentPinState, topic:"D"+node.pin }; node.send(msg); } lastPinState = currentPinState; } },parseInt(node.updateInterval)); this.on('close', function() { clearInterval(timerId); }); } RED.nodes.registerType("IoT2000-gpio-din", gpioDin); } I put the new archive, here, the LED works fine as well, in the coming weeks I will work on the other nodes, but I don't really need them for my project at the moment so I will treat that with a low priority. After unarchived, copy the folder in '/usr/lib/node_modules/node-red/nodes' and restart node-red or your IOT2000. One comment regarding the UserLed, on the IOT2040 there are indeed 3 colors for the LED, but on the IOT2020 we only have green. Cheers, Antoine Attachment node-red-contrib-IoT2000-gpio.zip (1065 Downloads)
	Last edited by: abajolle at: 11/29/2018 10:37:32 AM Install Instructions Added
Suggestion To thank Quote Answer
This contribution was helpful to 5 thankful Users Fe_lipe bergmanu steph129 Hollowwood maabril

2/1/2019 4:58 PM	Rate (0)
Stan_707 Regular Member Joined: 12/13/2018 Last visit: 10/25/2024 Posts: 2 Rating: (0)	Hi, I'm new with programming IOT2000, I have similar issue, my DIs are not working, M is connected to 0VDC and then I'm connecting 24VDC to DI0 but nothing happening, I have simple program which display notification at UI (see attached), its working when i use button but not working based on DIs. I was trying both libraries at node-red: 1. node-red-contrib-IoT2000-gpiov2 2. node-red-contrib-IoT2000 But no success, not sure what I'm doing wrong, DOs are working fine instead, Could anyone of you send me some simple program to test those inputs, please. Regards Stan Attachment test DIs.JPG (1062 Downloads)

Suggestion To thank Quote Answer

1/6/2020 9:52 AM	Rate (0)
ziml Posts: 9 Rating: (0)	I installed the unzip file to the following path /usr/lib/node_modules and it appeared in my node-red pallet/menu. Works just fine too... Is there a difference between the path you recommended vs the one I used?
ziml Posts: 9 Rating: (0)
Suggestion To thank Quote Answer

1/15/2020 11:23 PM	Rate (0)
Hollowwood Member Joined: 3/25/2018 Last visit: 11/6/2024 Posts: 2 Rating: (0)	abajolle's node works really well. I can now get all five digital inputs captured. Is there a node for Analog Input?

Suggestion To thank Quote Answer

1/16/2020 9:05 AM	Rate (0)
bergmanu Platinum Member Joined: 4/28/2015 Last visit: 11/12/2024 Posts: 3345 Rating: (379)	Hi, I am not quite sure, but as I remember the preinstalled "intel-gpio" work fine for the Analog inputs. The mapping from shield to the gpios is as follows. U0 - A0 I0 - A1 U1 - A2 I1 - A3 Best regards!
	Not working for IOT2050 support anymore from March 1st, 2024. I really enjoyed the time supporting you! :)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on