Search found 25 matches

Sadly, I'm using the internal oscillator.

This is something I have been wondering. I have a customer who wants tests for every possible thing and I have ISRs for things like oscillator failure. How do you test for something like that? I'll ju ...

I just got an e-mail product brochure on the 16F1613. They say it has fault-detecting features.

It seems to be the best thing since (insert your favorite invention here)

There's also a MISRA rule that you should never use '==' with floats. If you want to check if it's 5.0, use:

if(( voltsPreviousVal > 4.95 ) && (voltsPreviousVal < 5.05 ...

Hamamatsu makes a selection of RGB sensors that I have looked at before. Really, all I have done is read the data sheet and run some quick numbers to see if they would do what I wanted, they seem good ...

I was poked in the ribs by a "real" programmer once to get me to be explicit on every variable type. Since an 'int' could be different on different parts, I now always do full declarations: ...

I recently wrote I2C slave code and added the i2c_read(2) at the same place. I had to do a tech support request to CCS to get it worked out. It isn't in the manual yet, they said it would be in soon.

I found a problem with 4.132 and stepped back to 4.131. CCS told me they have fixed my issue in the next update. It didn't have to do with configuration bits but you need to let them know what you are ...

Where are the defn's for UART_BUFFER_RX2[x]?

The version I used was 1.00.

I will watch for 1.20 and try it again.

Thank you for the comments.

jeremiah, I tried it a few months ago and it couldn't handle paths with spaces. Has that been resolved?

Please see this post first:
http://www.ccsinfo.com/forum/viewtopic.php?t=47549

I tried using MPLabX but, when I found out that it couldn't tolerate spaces in file names or directory paths, I went back to old-fashioned MPLab. This was a shock since spaces have been allowed since ...

Nidal,

When I use MPLab with CCS I still use very old-school methods. My root.c file has this at the top:

#include <18F26K20.h>
#include "C:\_Data\PIC\PIC18F26K20_registers.h&q ...

Did you know there's a web forum for the manufacturer of the module?

http://www.sureelectronics.net/forum/index.php