-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues getting node to work #1
Comments
Hey Sam, Let's figure out what's happening. Could you please take the following steps:
Otherwise we should setup a screen sharing call, so I can look with you. |
Hi Melvin, Firstly thank you for your offer to help. I can certainly do that. I am not sure what the bus digits I should be using are. I have them current set at 0 and 0. Also how do I account for the fact my cs is connected to gpio 19 and my miso, mosi and clk are as per my first message. |
Regarding the wiring, let's start with connecting board CS to Pi SPI0 CE0 (BCM 8): https://pinout.xyz/pinout/pin24_gpio8 Once we got the basics working, we'll play around with different setups to achieve your final goal. |
Hi Melvin, Sorry it has taken a while to get back to you. I have been a bit busy. I have changed everything as per the layout above and I am getting "TypeError [ERR_INVALID_ARG_TYPE]: The "value" argument must not be of type number. Received type number" I am also getting a temp however that is -242.02. Any ideas? It is working through craftbeerpi and reading correctly. Regards |
Make sure craftbeerpi isn't running at the moment you are running the node. A reading of |
That worked thanks. I did a complete reinstall of raspbian. Now do you think there is anyway I can have 4 pt100’s working? There is a python script to do it for craftbeerpi but I have no idea program. Kind Regards |
I believe we can get it working. Key is to achieve that step-by-step. Let's add the second board. Have them share the SPI0 MOSI, MISO and SCLK pins. Then assign the first board the SPI0 CE0 pin and the second board the SPI0 CE1 pin.
If that works continue step-by-step with the 3rd board: Note that these boards will be connected to SPI1 instead of SPI0.
And repeat all the checks to get it working in Node-RED. Adding the 4th: Have them share the SPI1 MOSI, MISO and SCLK pins. Then assign the third board the SPI1 CE0 pin and the fourth board the SPI1 CE1 pin. Hope this works! :-) |
Thanks for your reply Melvin. I can certainly get the second one going on CE1 of the SPI0 bus, however I am unable to use the SPI1 bus. This is because it is running quiet a complicated brewery with valve and pump control and I am using all of the IO on the Pi, so I am unable to use those pins as they are assigned to other devices and I have no room to shift them. With Craftbeerpi, the guy who wrote the plugin, managed to get flexible cs pin assignment meaning you could have more that 2 Max31685 boards on the SPI0 bus. Regards, |
good afternoon, I have this code in python that runs Simple demo of the MAX31865 thermocouple amplifier. import time import board import adafruit_max31865
however the node-red node returns me a value -212.02 |
@yurilq Let's figure out what's happening. Could you please try the following: Create a workflow in Node-RED with an input trigger connected to the MAX31865 and a debug output to see if anything happens when you trigger. Also, please let me know the settings of your MAX31865 node. |
@slogan87 Sorry, missed this comment. Will check if I can implement flexible CS pin assignment on the SPI0 bus (or any bus). |
node on the noder-red server node configuration |
to be able to use I'm using the example in python and saving to a CSV, so I read this file but I would like to use only node-red resources |
Hi there,
I have just downloaded you Node to run on my Raspberry Pi. I am currently trying to create my own brewery controller. I have been using another program on the Pi and have everything wired. My MOSI, MISO and CLK are connected to 10, 9 and 11. I also have 4 PT100's with 4 board that I have currently working but am struggling to get it working with your node. Are you able to help?
Kind Regards,
Sam
The text was updated successfully, but these errors were encountered: