It does work - so I guess the 'hint' hasn't been updated. (As mentioned the component used to work with bytes) Note - Use the Rx interrupt - data has been received (so it should never timeout?) I don't know what timeout would return in this case (but if you only receive single character in the inter...

The display does use a D/C pin (to select data or command)
They have maybe missed it from the diagram?

Sorry - missed a '.' - I meant 0..511 (or 0 to 511) Which version of Flowcode are you using - the components used to only return a byte (8bit) - in version 10 (free !) - the Send/Receive Char take an int (16bit) of which they send/receive the appropriate number of bits... Did you manage to get my de...

Note - could possibly have done the send and receive on the same Mega. I didn't think of it beforehand... I powered the second board from the first as I couldn't lay my hand on 2 of the Type A USB cables (though they are surely hiding somewhere) Windows terminal programs don't support 9 bit data (th...

A quick demo of 9 bit comms using 2 Arduino Megas. One is the 'sender' (S) and one a 'receiver' (R) (I called it UART) (that echoes the received data to a PC via the USB comms UART) I connected RX1 to TX1 and TX1 to RX1 on boards 'S' and 'R' - also GND (essential) and 5v as I have the sender powered...

... There is an issue - send and receive take a byte which is 8 bits, so some extra work needed..

- I might be wrong on this - looks like the functions now return an int.

A little tip to make life easier. The output from the esp32 compiler is a 'little' verbose. It is possible to turn off some of the warnings. In your project directory/main Edit CMakeLists.txt At the end of the file add: target_compile_options(${COMPONENT_LIB} PRIVATE -Wno-unused-variable) target_com...

This is some alternative code for WS2812 LEDs running on the esp32. Rather than the RMT based component (I get issues with this being deprecated...) I tried two alternatives - using the i2s hardware where I got 'reasonable' results. LEDs would set but occasional glitches ( I think the T1L time I got...

Please post your code - or a snippet showing the problem. SPI sends overwrite the sent data with values received by the sender (or 0 if there is no reply) - so you might need to just update the array values each time.. loop (forever) loop (i = 0.. 7) array[i] = val[i] send (array) delay(1s)

is the display component connected correctly?

I'm going to say 'maybe' - or I think/hope so...


Will play some more....