Hi
I have a Pi 3B running with node-red and with an OLED display on the i2c bus.
If I send messages to the OLED too quickly, node-red itself stops, then some time later restarts.
I am assuming that normally, incoming messages are somehow 'queued' when destined for different devices, but that although the OLED has received the instruction (and 'releases the bus'?) it has not finished processing it and drawing the display. Then another instruction comes in and it stops all of node-red
The rate of incoming draw instructions seems to be about 8-10 per second. Below this it seems fine, above it then node-red restarts...
Can anyone shed light on the general dynamics of the way the i2c interface handles mutliple incoming messages?
Thanks
I have a Pi 3B running with node-red and with an OLED display on the i2c bus.
If I send messages to the OLED too quickly, node-red itself stops, then some time later restarts.
I am assuming that normally, incoming messages are somehow 'queued' when destined for different devices, but that although the OLED has received the instruction (and 'releases the bus'?) it has not finished processing it and drawing the display. Then another instruction comes in and it stops all of node-red
The rate of incoming draw instructions seems to be about 8-10 per second. Below this it seems fine, above it then node-red restarts...
Can anyone shed light on the general dynamics of the way the i2c interface handles mutliple incoming messages?
Thanks
Statistics: Posted by nicknack23 — Mon Mar 04, 2024 7:17 pm