Matrix user forums

Have you got a folder C:\Program Files\Flowcode 7\compilers\pic16?

What device are you using?

Try removing the 0 -> B6
If that does not fix the issue, please could you provide more info on the hardware that you are using?

Reply here ...
https://flowcode.co.uk/forums/viewtopic.php?f=3&t=685

Hi,
No, we don't support the F1 series.
But I think an F4 program could likely run on F2

OK, good, thanks for letting us know.
Also, I have been reminded that historically in Flowcode the operators AND, OR and NOT have always been bitwise operators.
So this confirms that you do need to use D=!D in this scenario.
Thanks
Leigh

Ah, well spotted, this is the issue with your Timer interrupt program. In my test version I used D = !D which does work. (as I've been a C programmer for the last 40 years :lol: Bools are simple in C, in that 0 is false, anything else is true. But this can have complications depending upon how they ...

Hi, I don't have them with me at the moment. But I suggest you use the project that you first posted. That used the internal HSI. (So will eliminate any possible issues with your external crystal) In the project options screen, change the clock speed to 16MHz (from 8MHz) and then in the Timer interr...

I've just run a similar program on a 32F446 and it works fine.

I also just noticed that in your latest Flowcode project that you have not changed the Timer Interrupt properties,
you still have Rollover as 1000, so unless you have an oscilloscope on your LED you might not see the on/off state change.

It looks Ok.
Have you tried a simple 1 second LED flash loop, with LED on/off and 1/2 second delays?
Without the timer interrupt.
Just to check the chip is programming and running OK?

Hi, I've done an example based on your original Flowchart, because on your settings above you have changed to HSE, but I don't know your external crystal frequency. btw. For HSI the clock speed should be set to 16MHz (not 8MHz, I was getting confused with the Nucleo board) clock_speed.jpg Or set thi...

Hi, The timer interrupt is likely working on the target device, but much faster than you expect. Unfortunately, the calculated period in the Flowcode timer interrupt properties dialogue is incorrect. This is because Flowcode is not aware of the PLL multiplier and other clock configuration parameters...

Determine the correct programmer COM port for your Leonardo. Run Windows Device Manager. Press reset on the Leonardo and watch out for the Port (COM & LPT) that appears for a few seconds. Make a note of the COMxx port. Settings for Flowcode project "Project Options" screen. Ensure you...

Flowcode 9 and ESP32: Can I develop programs in flowcode 9 targeting ESP32 as a microcontroller,

Yes

Have you also checked (or tried variations for) Clock Phase, Polarity and Sample point?

Hi Rafael,
Could give more details and post your Flowcode project?
What do you mean by "programming manually"?
What have you got connected to UART1?

Thanks for the reminder Martin

https://docs.espressif.com/projects/esp ... /gpio.html

UART0 is best avoided as this is the debug channel.
Do you have another unit to test?

Each PORT represents 32 pins.
So PORTA 0 to 31 is GPIO0 to GPIO31
PORTB 0 is GPIO32 etc...

Hi Rafael,
Even if the pin mapping on the board is different,
you should still be able to select IO via the GPIO/pin numbers,
e.g. GPIO6 is PORTA6

Hi Andrew,
Sorry for the delay in getting back to you.
Do you have more than one Formula Allcode,
such that we can determine if it is just this one unit that might be at fault?

As you probably realise, the ADC will only be capable of accepting input voltages between its power rails. So you would need to buffer the signal with an Op Amp so as to provide a gain or signal reduction as well as an offset such that 0v at the test point gives mid-rail at the ADC input. Google som...

Here's an update, please try this ...

Thanks for the info. I've made some changes and attached an updated component, if you could please drop this into the following directory on your PC and then retry C:\ProgramData\MatrixTSL\FlowcodeV8\Components As before, GetTouchCoordinates should be called first, this will return non-zero if there...