Dual_CAN.ino error? #11
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Created the example for this library, there are drawbacks though. This version of the library does not allow the sketch to see if a received CAN message is standard or extended in length, I suggest using the sub-development branch if you are serious about bridging. UNTESTED! I HAVE NOT TESTED THIS
Excel document that helps determine the configuration register values.
Made serial output more useful as a CAN sniffing tool and to demonstrate using the extra bits of the ID.
Mega2560 bootloaders and can cause timeouts during upload
Triple bang is a special command for the Mega2560 boot loader.
There was an extra sendMsg() in one of the sendMsgBuf() functions.
Loop back example to test a single CAN interface.
…N_loopback.ino ...
Fixed hex char's in array; fixed txBuf0, txBuf1 typo
Added interrupt pin defines and tested locally
Update Dual_CAN.ino
Static emulation of OBD ECM responses.
Missing example copied from forum post https://forum.arduino.cc/index.php?topic=402018.msg3209207#msg3209207
Improved sleep functionality
Guard DEBUG_MODE to allow control from the main program.
Fixed small spelling mistakes.
Allow clkout to be selected in CNF3 register.
Manual spelling fixes.
Guard debug mode definition
The Send timeout was based on an incrementing register and a while loop that ran at system execution speeds with no delays. I have changed it over to use the Arduino micros() function.
The Send timeout was based on an incrementing register and a while loop that ran at system execution speeds with no delays. I have changed it over to use the Arduino micros() function.
Maintain the deterministic timeout for sendMsg().
Fixed typo...
SPI-Bus selectable in constructor
Fixes errors in example.
Fixing issues caused by #27
Fixing issues caused by #27
- fix setMsg to respect the len - try to prevent buffer overflows and always limit to MAX_CHAR_IN_MESSAGE
fix setMsg and clearMsg
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi.
error: 'AA' was not declared in this scope
byte txBuf0[] = {AA,55,AA,55,AA,55,AA,55};
byte txBuf1[] = {55,AA,55,AA,55,AA,55,AA};
changed to:
byte txBuf0[] = {0xAA,0x55,0xAA,0x55,0xAA,0x55,0xAA,0x55};
byte txBuf1[] = {0x55,0xAA,0x55,0xAA,0x55,0xAA,0x55,0xAA};
error: 'tx0Buf' was not declared in this scope
CAN0.sendMsgBuf(0x1000000, 1, 8, tx0Buf);
CAN1.sendMsgBuf(0x1000001, 1, 8, tx1Buf);
changed to:
CAN0.sendMsgBuf(0x1000000, 1, 8, txBuf0);
CAN1.sendMsgBuf(0x1000001, 1, 8, txBuf1);