Why did we disable the msg to UI?
Was waiting for Behrouz to update UI side to accept payload change (from empty to confirm/cancel byte). Behrouz updated UI this morning so I've un-commented the payload change.
RESOLVED in CODE WALKTHROUGH.
I love this!
RESOLVED IN CODE WALKTHROUGH
that is one operator not two. This has a meaning and cannot be separated ! If you separate them you get compile error ...
How is the message Timeout!!!! related to received_message being equal to None?
Fixed.
Replace with PAYLOAD_LENGTH_FIRST_PACKET setup to 3. Please resolve
Device creation is too generic, make it more specific "Can interface cannot be initialize"
If the send method returns None, that means it sent the message and waited 1 second and got no response.
RESOLVED.
Done
Missing channel for CAN ID 0x200 (UI sync broadcast).
Its place should be reserved then and must not be used for data. So when it has been implemented only a simple change will be required.
Please Change the Cargo variable name to payload...
I think you should add the HD Alarm channel (as an "IN") so you get the system alarm status.
Leo, please make spacing consistent throughout the entire DG code base, this is a must because of our updated C coding standard. Thanks!
Extra line
Done!
Will add later if needed. RESOLVED IN CODE WALKTHROUGH
Added #defines for the years
Changed it to isBufferOk.
Use #defines for 2000 and 1970.
I have a toggle macro in use on my branch.
RESOLVED IN CODE WALKTHROUGH.
When will this reflect the DG modes from DG SRS?
Define constants for 2000, 1970, etc.
It doesn't look like the transfer failed here. Should this be set to zero?
bufferLength should be range checked. Or does setMibSPIBufferLength() range check it?
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.
