Author |
Message |
Topic: dsPIC33 only sends ID of 0x00 on CAN2 when using ext frame |
labviewman
Replies: 3
Views: 11063
|
Forum: General CCS C Discussion Posted: Tue Aug 12, 2014 9:39 am Subject: dsPIC33 only sends ID of 0x00 on CAN2 when using ext frame |
Must have been a problem with the CANoe configuration I was using....tested again with CANalyzer and it worked perfectly....weird |
Topic: dsPIC33 only sends ID of 0x00 on CAN2 when using ext frame |
labviewman
Replies: 3
Views: 11063
|
Forum: General CCS C Discussion Posted: Tue Aug 05, 2014 6:06 pm Subject: dsPIC33 only sends ID of 0x00 on CAN2 when using ext frame |
Interesting posts...pretty frustrating MicroChip has so many issues, but I read the errata for this micro (33FJ64GP706A) but didn't see anything on ECAN that applied to my observation.
CCS tried th ... |
Topic: dsPIC33 only sends ID of 0x00 on CAN2 when using ext frame |
labviewman
Replies: 3
Views: 11063
|
Forum: General CCS C Discussion Posted: Tue Aug 05, 2014 8:00 am Subject: dsPIC33 only sends ID of 0x00 on CAN2 when using ext frame |
Is there an issue with the CCS compiler being able to correctly compile code to send CAN messages on CAN2 ? I have code that is pretty simple and uses both CAN ports and has identical function calls ... |
Topic: CAN bit timing with a dsPIC33 |
labviewman
Replies: 10
Views: 12910
|
Forum: General CCS C Discussion Posted: Sun Jul 27, 2014 6:08 am Subject: CAN bit timing with a dsPIC33 |
Thank you RF_Developer for testing on your equipment and telling me the bit rate and thank you Ttelmah for explaining why this is happening.
I said I would reward who ever helped so I'd like to mai ... |
Topic: CAN bit timing with a dsPIC33 |
labviewman
Replies: 10
Views: 12910
|
Forum: General CCS C Discussion Posted: Mon Jul 21, 2014 3:56 am Subject: CAN bit timing with a dsPIC33 |
Ha, I submitted that and didn't realize you had responded.
I will try changing the clock speed and baud rate when I get home to verify it's always 1/2 (we don't have the same compiler version at wo ... |
Topic: CAN bit timing with a dsPIC33 |
labviewman
Replies: 10
Views: 12910
|
Forum: General CCS C Discussion Posted: Mon Jul 21, 2014 3:51 am Subject: CAN bit timing with a dsPIC33 |
It has been a while since I have looked at a CAN waveform, but when I send 0xAA (no bit stuffing will occur), I get a period of 16 usec between rising edges, which if I'm thinking correctly would be 2 ... |
Topic: CAN bit timing with a dsPIC33 |
labviewman
Replies: 10
Views: 12910
|
Forum: General CCS C Discussion Posted: Mon Jul 21, 2014 2:01 am Subject: CAN bit timing with a dsPIC33 |
Duh, sorry I didn't include that!
I have a 10 MHz crystal (#use delay(crystal=10MHz)) and am trying to get HS CAN at 250 Kbps.
I'm taking the board to work today to see what bit rate I actuall ... |
Topic: CAN bit timing with a dsPIC33 |
labviewman
Replies: 10
Views: 12910
|
Forum: General CCS C Discussion Posted: Mon Jul 21, 2014 1:10 am Subject: CAN bit timing with a dsPIC33 |
I am absolutely 100% sure the code is executing at the expected clock frequency by:
a) verifying the blink frequency of a LED driven by the uC is almost exactly as calculated (2 methods: via simple ... |
Topic: CAN bit timing with a dsPIC33 |
labviewman
Replies: 10
Views: 12910
|
Forum: General CCS C Discussion Posted: Sun Jul 20, 2014 4:47 pm Subject: CAN bit timing with a dsPIC33 |
I have struggled with CAN on a dsPIC33 for about 8 hours today and have been able to determine it does attempt to send a msg on the bus (by stepping thru the code I can see it reaches the point of req ... |
Topic: Printf problem |
labviewman
Replies: 7
Views: 9126
|
Forum: General CCS C Discussion Posted: Mon Dec 05, 2011 8:48 pm Subject: Printf problem |
Pretty simple:
int16 data;
Printf("%lx\r",data);
There were other issues with 4.127 which caused me to burn an entire day (Sunday) trying to make my code work with 4.127 which worke ... |
Topic: Printf problem |
labviewman
Replies: 7
Views: 9126
|
Forum: General CCS C Discussion Posted: Mon Dec 05, 2011 9:19 am Subject: Printf problem |
I had the same problem...printf code that worked fine in 4.125 didn't in 4.127 (didn't like %lX but was OK with %ld). I reverted back to 4.125 |
|