Search found 190 matches

I have been very happy with Microchip's compilers for our PIC18 and PIC24 projects (and with MPLAB). Of course there is a learning curve, and you lose the peripheral setup features that CCS provides. ...

One thing I have done in the past that works well is to set an unused bit high at the start of the ISR then clear it at the end of the ISR - makes it very easy to see just how much of your total time ...

There are notches in the sides of the case. Using a flat-blade screwdriver, pry the case apart at the seams - it just snaps together.

Ken

Ummm . . .

how about just always

DiffTmr = NewTmr-OldTmr;

This always gives the correct result, even after an overflow.

Ken

Just a little more . . .

Yes, read the encoder as fast as required (sounds like you are).

But, update the display at a rate that is comfortable to the human observer. That is probably no more t ...

Using CCSLoad and ICD-U64, I do one of three things to run:
unplug the ICD
click "Run Target" in CCSLoad
exit CCSLoad

Does this help any?

Ken

I use this macro:

#define nElements(array) (sizeof(array) / sizeof(array[0]))

Ken

Yes, but this is the bit-time, not the character time.

There are 10 bits per character (8 data, 1 start, 1 stop), so the char time is 1.04 msec; X 3.5 is 3.65 msec

Anyway, how is your project co ...

delay_us(3500000/MODBUS_SERIAL_BAUD); //3.5 character delay
This is my longest delay routine in interrupt. it is 364uS (9600baud)

This bothers me . . .
3.5 characters at 9600 baud is 3.64 msec, ...

One more note:

Your "int function" will take the float error, truncate it, and return whatever fits in an "int" - CCS int is an 8-bit unsigned thingy, as I recall

Ken

I scan this forum frequently, both for new ideas and good ol' general education - wish I could contribute more

So, thank you triet, and many many others. Add hope you enjoy your new endeavors !

...

This would have no impact on a "blinking led test", but . . .

Check the timing requirements for the lcd enable or write pulses; at 40 MHz the pulse may be too fast for the lcd ? ? ?

Ke ...

While reading your 1st post, my mind suggested a switch.

Sounds like you've got it!

Ken

Depending on your needs, you may want to round up when doing this, e.g.

myval = (int) (test + 0.5);

But, consider the impact when test is negative!

Ken

Your are right, you must divide (somehow).

However, the compiler will compute (x * y) for you - you don't have to explicitly do that.

Ken