What is have stated is too vague. We won't be able to help you until you at least upload the fcfx .msg.txt and .c files What can you see on the display e.g 1 or more rows of square, no squares etc. What version of flowcode are you using as it would help if you selected the correct version from the P...

MJU20 wrote: ↑

Thu Oct 23, 2025 5:34 pm

Hey, congratulations on the release of Flowcode 11!
I’m currently taking a look at it and I’m curious to see what’s new (or missing) compared to FC10.

Hello.
The new features of Flowcode 11 are detailed here

Hello.
Many thanks for the report.
I will look into the template and post an updated version.

No problem.
You can purchase by clicking on Buy Flowcode near the top right right of this page
Then you need to select Upgrade User

Hi Jorgen.
If you purchased Flowcode chip packs before the 1st September than you will get a 40% discount, so Its then not free.
Flowcode v11 is only free if purchased Flowcode v10 chip packs or upgraded to professional version on or after September 1st 2025.

You're welcome you can use the built in potentiometers if you now have them. The reason 0 is shown would be down to typecasting. If res variable is a float Try res = ((330.0 * volt) / (5.0 - volt)) If you have an int or byte variable first, then an explicit Type cast is required before the variable....

Hi Jorgen
Yes that helps.
The Flowcode component is only set to work with 0x0D, so any other ID will not work at all.
Hopefully I will have the 0x1E version by this weekend.

Hello.
Can you try with RCC_SYSCLK_SRC changed to HSI instead of PLL
With RCC_SYSCLK_SRC set to PLL the clock frequency is being multiplied.
Therefore there is a mismatch between clock frequency on hardware and on Flowcode clock speed.

What I have noticed is you have 2 x UART components that are set to the same channel, that will take up more memory. Also you have 2 x EB013 components which are specifically for that Eblocks module. Have you got 2 x EB013 hardware? If not just use the standard SPI master components. You will need t...

Did you try and compile to hex with a 64K version? Code grows bigger because people request more feature within components which come at a price of using more memory. By trying with a larger device to compile to hex that will prove or disprove my theory. You don't need to have the microcontroller to...