search

node-red / node-red-nodes

Extra nodes for Node-RED
Other
988 stars 593 forks source link

PiLCD: Startup warning "Raspberry Pi specific node set inactive" #1073

Closed Kristian-240623 closed 3 months ago

Kristian-240623 commented 3 months ago

about project: node-red-node-pilcd https://flows.nodered.org/node/node-red-node-pilcd

I am using a Raspberry Pi. When i use the node rpi-lcd, it has a gray rectangle and the text "not available". Sending text has no effect. I verified the hardware function with a Python script. (See details in discussion: https://discourse.nodered.org/t/problem-how-to-debug-pi-lcd/88886) A catch node in node-red doesn't report an error. A normal GPIO read node seems to work.

The startup log says: 23 Jun 20:14:19 - [info] Node-RED version: v3.1.9 23 Jun 20:14:19 - [info] Node.js version: v18.19.0 23 Jun 20:14:19 - [info] Linux 6.6.28+rpt-rpi-v8 arm64 LE 23 Jun 20:14:21 - [info] Loading palette nodes 23 Jun 20:14:21 - [debug] Module: node-red-node-pi-gpio 2.0.6 /home/ks/.node-red/node_modules/node-red-node-pi-gpio 23 Jun 20:14:21 - [debug] Module: node-red-node-pilcd 0.3.1 /home/ks/.node-red/node_modules/node-red-node-pilcd 23 Jun 20:14:21 - [debug] Module: nrlint 1.2.0 /home/ks/.node-red/node_modules/nrlint 23 Jun 20:14:23 - [warn] rpi-lcd : Raspberry Pi specific node set inactive 23 Jun 20:14:23 - [info] Settings file : /home/ks/.node-red/settings.js 23 Jun 20:14:23 - [info] Context store : 'default' [module=memory] 23 Jun 20:14:23 - [info] User directory : /home/ks/.node-red 23 Jun 20:14:23 - [warn] Projects disabled : editorTheme.projects.enabled=false 23 Jun 20:14:23 - [info] Flows file : /home/ks/.node-red/flows.json 23 Jun 20:14:23 - [info] Creating new flow file 23 Jun 20:14:23 - [debug] loaded flow revision: 4f53cda18c2baa0c0354bb5f9a3ecbe5ed12ab4d8e11ba873c2f11161202b945 (...)

My environment:

hardillb commented 3 months ago

What version of python is installed on the machine?

Also please provide the output of cat /proc/cpuinfo (I think this is something we have fixed for other pi based nodes.)

Kristian-240623 commented 3 months ago

Hi, Python Version: 3.11.2

cat /proc/cpuinfo
processor   : 0
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

processor   : 1
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

processor   : 2
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

processor   : 3
BogoMIPS    : 108.00
Features    : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd08
CPU revision    : 3

Revision    : c03114
Serial      : 100000005c35cc5a
Model       : Raspberry Pi 4 Model B Rev 1.4

thanks, Kristian

Kristian-240623 commented 3 months ago

I tested different Raspbians. As you said (in the forum thread/ see first post), it is a matter of 64 or 32 bit. Raspberry Pi 4 users seem to need attention, because not every "32 bit" is really 32 bit. I read somthing about this, but i lost it (and it is very late). What works for me, is the "legacy 32 bit" version. Not the other two versions. See Screenshot.

grafik

hardillb commented 3 months ago

OK, the test that is failing is this line

https://github.com/node-red/node-red-nodes/blob/305327faaa650c2cee9e428ecf4e45d972de7d7b/hardware/PiLcd/pilcd.js#L13

Which just checks for BCM being somewhere in the /proc/cpuinfo output and if it's not there then it says you are not running on a Pi.

It may also need another update like https://github.com/node-red/node-red-nodes/pull/1024