Have a look at a datasheet for the device and the protocol diagrams should help.
Ps. The transaction API works with a predefined device address, the transmit byte is a low level raw byte send.

Sounds like the address of the device is 0x50.
The protocol has this 7 bit address in the highest 7 bits of the first byte, with the read/write flag in bit 0.
Hence the address appears shifted left one bit.

Glad it's working for you now.
Yes, interrupt timing calculations on these ST devices is a known issue.
That Flowcode dialogue doesn't have the information to work out the final clock frequency driving the timers.
So the parameters need to be calculated manually unfortunately. For now.

I'm not near my PC at the moment to check much, but a couple of points that might help...
You need to set the Flowcode Clock speed to the source rate, ie either 16 or 8Mhz.
If you want to double the 96, then change the PLL divider from /8 to /4

Yes, that's it. You need to be aware of the syntax/format of IF expressions. IF something, where something is true or false. In C, false is 0 (zero) and true is non-zero. So sometimes "IF variable" will be a valid statement, assuming variable is an int (not float). And will treat the state...

Well spotted, also it will need to be more explicit..
(Cell_1_Voltage_Float < 3.0) || (Cell_2_Voltage_Float < 3.0)

Your attached msg.txt file seems to end abruptly.
Have you got generic file system issues on your PC?
Full hard drive?
As chipfryer27, please check files exist.

You need to download the STM32F446 Reference Manual from st.com and have a look at page 66.
I don't think that the ART accelerator is enabled by default, but you can enable it with the following C code

Hi Bob,
The first thing to check in your Flowcode project is that the W5500:Initialise is successful.
This does a check of the SPI write and read, and returns 1 for success, 0 for failure.

Hi, I've bought an STM32F303 development board to play with. I've not had any issues with the timer interrupt. However, my testing has thrown up an issue with the 32F303CB FCD, the config section is missing the HSE source divider parameter. This means it would be easy to accidentally overclock the d...