U2C v2.1 was found a lots of error issue
- Dominant language
- No language data
- Stars
- 153
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
hi there
i was flashed can-fd firmware from U2C_V2_STM32G0B1.bin.
but it's found bytes_retransmit=20 and bytes_invalid=10~90 on klippy.log a lots of lines over 1,000 lines.
also that value was affected same even small or bigger(10 to 5,000) txquelen value(as i think shouldn't happen will be better to use.
at this moment i couldn't fixed up and rebuild or modifying by myself without candleLight source for U2C_V2_STM32G0B1.
how'd you think about to share that self build sources of candleLight_fw for STM32G0B1 on github?
this issue gotta Stop and Shutdown MCU or EBB36 if found that bytes_retransmit and bytes_invaild values.
* Octopus 446 (set by can pd0/pd1 via canboot bootloader)
* Ebb36 (set by can pb8/pb9 via canboot bootloader)
! when using U2C v2.1(STM32G0B1) - a lots of timeout error when g28 and stuck & must be reboot at 2~3 layers when printing

! when using U2C v1.1(STM32F072) - nothing on problem

Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported U2C_V2_STM32G0B1.bin firmware and the bytes_retransmit and bytes_invalid entries in klippy.log. Compare the U2C v2.1 setup using the Octopus 446 and EBB36 with the stated U2C v1.1 behavior. Done means identifying the cause of the CAN errors or documenting the needed candleLight_fw source and a reproducible fix.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100