Search found 55 matches

Well, the results are in. As Ttelmah suggests, there is not discernible jitter when the NCO increment (count) is a binary multiple. Otherwise, the NCO will automatically adjust a separate count (accum ...

Thanks, I've seen that link and several others.

Jay,

Apparently some PICs do have an external input to the NCO. I may keep looking to try and find one that does as well as meets my other criteria.

As far a the jitter rewquirement goes, I'm no ...

Hello all,

I'm working with a PIC16F18426 and am planning on using the Fixed Duty Mode (50% square wave) of the NCO to provide a precise, jitter-free output with an external clock as the NCO clock ...

asmboy,

I see your point. Didn't study the sort closely enough before making the assumption that the loop limit was incorrect. I revised your comment on that line to read "i 0-14" instead ...

Great routine asmboy!

I think there may be a typo in the sort loop upper limit. Orig code shows <15, but it should probably be <16. Corrected code below.

Thanks for the great job. It was j ...

Just received an email from CCS. They do not support what I am attempting to do.

Thanks for all the replies.

I guess it's just the way that CCS compilers treat the ?: operation. I've verified my test code works with two other non-CCS 'C' compilers as well as the Arduino compiler.

To your point, I changed the code to fill a variable array rather than a constant array. The results are the same.

#include "16F18323.h"

void main()
{

int x;

x=5; ...

In this example, the intent is to fill one element of the array with a constant (either 6 or 7) based on the conditional expression of whether x=5 or not.

This type of conditional fill works with o ...

Hello all,

Trying to fill a const array using a conditional expression and am getting an error 27 "Expression must evaluate to a constant". Have tried several things, but no joy.

The c ...

Thanks Ttelmah. I see where ALL of the individual port pin pull-up bits are set to '1' by default so ANY change to the pull-ups will result in all others being turned on.

Cheers

I just discovered a possible issue with the programmable weak pull-ups. I've only tested this on the PIC16LF1579, but I suspect it might also pertain to other similar parts.

The problem was found w ...

This device only has PWM5 and PWM6. The compiler will reject the setup_pwm1() statement, but will allow setup_pwm1_duty(). Not sure why Microchip doesn't use PWM1 and PWM2 instead.

I have submitted ...

You can still use the setup_pwm5_duty() routine. You just have to be aware that the duty cycle period value is 4x what you might think.