Hello. This needs looking into since the maximum number of DAC's is currently 4 so even if all the pins are correct, only the first 4 will work. This device has a funny register for CCP as that's what we currently use for PWM. it goes CCP1, CCP2, CCP7 & CCP8 The way Flowcode address the CCP regi...

Brilliant, yep, you got it.
I'm glad you found it very simple.
Those API's come in very handy, especially for component creation.
Thanks for letting me know

Hi Stefan,
Attached is one way.
I then added a text component:

Hi Dirk.
Flowcode isn’t currently compatible with XC8 v3.0.
It’s on our to-do list and we will fix it as soon as we can.
Apologies for any inconvenience.
I will make an announcement when it's sorted.

You're welcome.
I have added the path for FC9 as well

Hello.
You can see them within internals.c
Which can be found at the following for Flowcode10:: FlowcodeV9: Since the directory is hidden, just copy and paste the above path in windows explorer.

Hello.
Yes there is.
If you run Library updates and change Files in use to full database, the latest ADC CAL should resolve your issues.
You should now be able to used ADC2 instead of being restricted to ADC1.
You will still need be wary of sone pins:

Hi Abhi I have looked at the files you sent. The are way to large for me to track down the issue. My guess it could be a recursive function or manual macro linking created a circular reference. Whatever it is the compiler does not like it at all. Looking at the .as file the issues is within Set_Para...

Hello.
Just the words syntax error showing for error is normally unconnected pins.
If you can post your .fcfx, .c and .msg.txt files, then we can help you further.
The bold number you have shown, will refer to a line number within a file ,the error could be found.

Hello. The compiler is warning you because it sees the same piece of code (the one that reads or writes the whole port) being used both in your main program and inside an interrupt. It does this to make sure you don’t ever run that code in both places at once, which could corrupt data. In your IOC_P...