The esp32 does offer a remarkable amount of 'bang' for the buck.... The programming paradigm ( :-) ) - is slightly different to most MCUs - for the most part because of the (co-operative) multi-tasking system used. It's worth playing along though - because the performance for such a low-price device...

Hi Bob, I did a quick demo program - and the UARTs seem to work okay. I use two UARTs one (connected to UART1 - and thus to USB) and one to UART2 (I connected an FTDI convertor). Note that I also connected the Tx pin - and output a message here - as a sanity check. It looks for data at UART2 (I used...

I have used a second UART successfully - for example viewtopic.php?t=3542&hilit=LiDAR - however i did this in C...

Can you upload a code snippet and a bit more detail what's going wrong...

Martin

To use the spi - probably use spi master. To compile you will need to specify a DOUT (MOSI)- it won't be connected to any thing - but this is okay (toggling the clock pin transfers the data). If using transactions - the dataout will be just be dummy data which will be ignored. Note that some MCUs on...

Yes - the SPI does just send and receive bytes (8 bits) - however characters are also just bytes too... Strings - 0 is treated as the end of the string - so receiving a string will 'stop' at this point. You could use Transaction to receive a byte at a time - just send 0 if no data to send (SPI is bi...

Thanks Steve,

Sorry - I hadn't noticed that the file extensions had changed in v11 - I can re-do in v10 if changing the file extension doesn't do the trick....

Martin

Looking at the datasheet - this is indeed the case - so as the SPI component reads the data in bytes (8 bits) there will be 4 bits to remove. There are ways around this: 1) Mask/shift the appropriate bits in the bytes received before conversion to a word. 2) Convert to 16 bit word then mask and shif...

I changed tack slightly and used GetLastChar - looking for '\n' - here I just display the value (using a numeric indicator) - and clear the current entry on 'enter'.

Not very elegant - left all my 'working' in (although disabled) - to show how I looked at the returned data.

Martin

It's less easy than it should be.... One way - get the string input (GetInputString) - 'pressing' Enter on the keypad is returned as character '\n' (0x0a) - if this is received then set the display and 'clear' the input buffer. In a similar vein - the 'EditBox' - doesn't seem to have any way to read...

Looks good....

Easy to add other 'options' if needed too...

Still faffing with the circular includes I couldn't get a 'new' program (with tinyusb) to compile yesterday - but old stuff was okay. Something odd going on. It will sort!

Martin