512 is wrong, which is your main issue. I'm assuming you just thought because you are using 10bit PWM then 50% of 1023 You only need to pay attention to Period Overflow as explained in my previous post. If you look at the image below: 10bit PWM.png You can see the Period Overflow is 124. In the calc...

If you are correctly getting 1second then internal osc and clock settings match. Does the simulation match the hardware? With PWM the period value represents 100%. For 8bit, 100% PWM Duty = Period Overflow. For 10bit, 100% PWM Duty = Period Overflow * 4 124 * 4 = 496. 50% = 496 * 50 / 100 = 248 Try ...

i set the chip at 10Mhz from the config page so im guessing it doesnt slways mean a chip can run at that frequency ?. That is correct. You have two options. 1. use the internal osccon component. On the components ribbon use the magnifying glass and search for intosc Or use the values within the ima...

Hi Bob The first thing you do is make sure your hardware is setup to rub at the correct clock speed. Always flash a LED for 1 sec or use a logic analyser or scope Within projet options you have set the clock at a frequency which does not exist - 10MHz. The would cause issues with your PWM. The only ...

Hi Dirk.
it looks like you have not attached requested .fcfx project file.
If what you posted is not the full msg.txt file then you will need to attach that as well.

From Ben's post, Please pay attention to this: It looks like the specific error being generated it due to the 7 segment quad component pin connections, something there is referring to PortA which doesn't exist on the device you're using. Select the 7seg Quad component on the 2D Legacy panel then rig...

Hi Jorgen. With the display: You will need to set the Orientation within display properties to either 1 or 3. That will set display simulation orientation. For hardware orientation, you will need to drag display SetDisplayOrientation function to match the properties value either 1 or 3 As for the XP...

Hi Bob. No , should not require duty or period as it should be all set automatically by the SetFequency function. Before going any further, have you tried the one second flasher to make sure micro is running at the correct speed? If you have then I will check the SetFrequency on a different target d...

Hi Bob. The C code that was being used is only for AVR(as you correctly stated) as it's much more precise that current AVR PWM. You will need to use the SetFrequency function of Flowcode's PWM component. I have attached an untested example. Note the SetFequency function should automatically set the ...

Hi John. When Ben asks for program, he will be referring to project name.fcfx file. What would also help is .msg.txt and .fcxlog.txt files. The reason could be not set properties correctly, some other component interfering, component not up to-date etc. You can add the files by selecting Full Editor...