Winterhill with Node Red
Winterhill with Node Red
Hi all,
Has anyone installed Node Red onto the same Pi4 that is in the Winterhill receiver?
I used a Pi3 for controlling everything in my DATV transceiver, but with the addition of the Pi4 in Winterhill I am wondering if I can use the Pi4 instead.
What's nice is that there is an I2C breakout pins on the Winterhill board that I can use with my sensors etc.
One last question, does anyone know if the "1-Wire" pin on the Pi4 GPIO is used within Winterhill? I would like to use if for a sensor.
Cheers!
Has anyone installed Node Red onto the same Pi4 that is in the Winterhill receiver?
I used a Pi3 for controlling everything in my DATV transceiver, but with the addition of the Pi4 in Winterhill I am wondering if I can use the Pi4 instead.
What's nice is that there is an I2C breakout pins on the Winterhill board that I can use with my sensors etc.
One last question, does anyone know if the "1-Wire" pin on the Pi4 GPIO is used within Winterhill? I would like to use if for a sensor.
Cheers!
Re: Winterhill with Node Red
Not me but interested if anyone has. I can test it on my spare (the prototype) winterhill and if it works could useful get my operational unit to measure the PA parameters which are currently monitored by an Arduino Nano with ethernet hat.
I can't see why it would not work. My WH is headless. There might be issues with ones using the 4 screens on the PI, but as it has trouble with more than one H265 and doubt it will support more than one H266, perhaps instead of 4 VLCs it could be set up to display all the parameters you like and perhaps one signal locally and the rest remotely.
Mike
I can't see why it would not work. My WH is headless. There might be issues with ones using the 4 screens on the PI, but as it has trouble with more than one H265 and doubt it will support more than one H266, perhaps instead of 4 VLCs it could be set up to display all the parameters you like and perhaps one signal locally and the rest remotely.
Mike
Re: Winterhill with Node Red
GPIO4 is unused by WH and comes out on the Ryde header at the front of the pcb.
WH uses the hardware I2C port, so a software I2C would need to be used by any other application.
Brian
WH uses the hardware I2C port, so a software I2C would need to be used by any other application.
Brian
Re: Winterhill with Node Red
Thanks for the reply guys, much appreciated.
I guess whats the worst that can happen, I have to re-image another sd card! lol.
I thought I2C was stackable? As long as devices dont use the same hardware address?
Cheers
I guess whats the worst that can happen, I have to re-image another sd card! lol.
I thought I2C was stackable? As long as devices dont use the same hardware address?
Cheers
Re: Winterhill with Node Red
I2C is, I am not sure if Brian's implementation is though but in any case it is a bus and taking it off board may result in errors so best to use a different port if you can. For my use it would be great to connect an ADC to the GPIO so I could monitor the Forward and Reflected power pins on the PA and perhaps a current monitor. No point monitoring PA voltage as it is fixed 12V, mind you, as it is class A, so the current is also fixed, 18A regardless. Possibly the most inefficient uplink PA possible for narrowband as only 200mW is required.
Mike
Mike
Re: Winterhill with Node Red
RPi4 (and presumably others) don't support multi-master I2C.
Brian
BCM2711:
3.1. Overview
The Broadcom Serial Control (BSC) controller is a master, fast-mode (400Kb/s) BSC controller. The Broadcom Serial
Control bus is a proprietary bus compliant with the Philips® I2C bus/interface version 2.1 January 2000.
•
I2C single master only operation (supports clock stretching wait states)
•
Both 7-bit and 10-bit addressing is supported
•
Timing completely software controllable via registers
•
The BSC controller in the BCM2711 fixes the clock-strectching bug that was present in BCM283x devices
Brian
BCM2711:
3.1. Overview
The Broadcom Serial Control (BSC) controller is a master, fast-mode (400Kb/s) BSC controller. The Broadcom Serial
Control bus is a proprietary bus compliant with the Philips® I2C bus/interface version 2.1 January 2000.
•
I2C single master only operation (supports clock stretching wait states)
•
Both 7-bit and 10-bit addressing is supported
•
Timing completely software controllable via registers
•
The BSC controller in the BCM2711 fixes the clock-strectching bug that was present in BCM283x devices
Re: Winterhill with Node Red
Is an I2C ADC a bus master then? I thought you could add several such devices, LCDs, ADCs,DACs, MEMs etc.
Re: Winterhill with Node Red
On my pi3 which runs in my box I use 4 I2C devices connected to the one I2C. 3 x voltage sensors and 1 x ADC.
Why is there a I2C breakout on the WH board if its not to be used? Or was it for future development?
Btw, loving the Winterhill! Thank you guys!
Matt
Why is there a I2C breakout on the WH board if its not to be used? Or was it for future development?
Btw, loving the Winterhill! Thank you guys!
Matt
Re: Winterhill with Node Red
The I2C header was just a thought for adding a WH LCD display, as on MiniTiouners.
Brian
Brian
Re: Winterhill with Node Red
Connected my sensor board which contains 4 I2C sensors to the I2C front header on the WH and this is the result, it detected them. I can also confirm that Node Red reads these devices perfectly.
The only thing I did do was to use a 5v line for the INA219 instead of the 3v3 on the WH header.
Now I am trying to figure out which pin on the other header is the 1-Wire connection to the Pi
The only thing I did do was to use a 5v line for the INA219 instead of the 3v3 on the WH header.
Now I am trying to figure out which pin on the other header is the 1-Wire connection to the Pi