maz0r / klipper_canbus Goto Github PK

Can you guide update Mks monster 8 V2 when it flash canboot and klipper firmware?

In description "MKS Monster8 v2 as a Can to USB bridge adapter" is mistake, for entering to DFU mode you have to use BOOT0 instead RESET button.

Clone device, does it "just work" or does it need notes/special attention

Move this info to live with respective boards, as currently it's seperate and people keep missing it

in toolhead/example_configs/toolhead_btt_ebbcan_G0B1_v1.2.cfg the [extruder] section has the following line:

pullup_resistor: 2200 # this is the default for the Revo heater

the pullup_resistor setting is not thermistor specific. its specific to the MCU that's reading the thermistor, and in the case of ebb36 1.2, it should not be defined, the default value is correct, whatever that may be.. setting it to 2200 results in 'room temperature' readings of ~40C

The same entry is in the ebb36 1.1 example config, which I suspect is also wrong, but I don't have that board so I can't confirm, However, the comment is still wrong.

I think that is not an issue, but can you tell me something about this error? thx

`[##################################################]

Write complete: 13 pages
Verifying (block count = 413)...

[#########ERROR:root:Can Read Error
Traceback (most recent call last):
File "/home/pi/CanBoot/scripts/flash_can.py", line 137, in send_command
ret = await self.node.readuntil()
File "/home/pi/CanBoot/scripts/flash_can.py", line 287, in readuntil
return await asyncio.wait_for(self._reader.readuntil(sep), timeout)
File "/usr/lib/python3.7/asyncio/tasks.py", line 423, in wait_for
raise futures.TimeoutError()
concurrent.futures._base.TimeoutError
#########################################]

Verification Complete: SHA = DF9F878419F13509BFA40F1B3D4E919EA5B6DD78
CAN Flash Success

`

Including special caveats around bridge mode

Finally get round to writing this up :/ it's only been on the desk for a few months :/

Add a callout to clarify that

`

Download done.
File downloaded successfully
dfu-util: Error during download get_status
`

Is perfectly normal and expected

Hello,
Thank for the summarization of several pieces together.
I've tried flashing candlelight_fw (using the web updater) and a utoc-1 in DFU mode and it resulted in a non-working board. the status leds don't come up after flash.

Putting the board back into DFU and restoring mellow firmware fixed the board (to the old firmware).

CAN timing issues
Klipper multi mcu timing issues
Microsteps
H/L mixed
Termination

Attempting to flash a BTT ebb36 v1.2 with G0B1 does not work if you select a Bootloader offset of 8 KiB. The device will flash but cause the network to go into an ERROR-PASSIVE state as soon as communication is attempted on the canbus. Compiling the firmware with No bootloader selected works fine and the device can successfully communicate with klipper. Flashing (with full memory erase) was done with STM32 programmer and was attempted at multiple different baud rates (250k, 500k, 750k, 800k, 1M).

Review current info about this board and add warning /notes/ workarounds.

Note: order another 2.1 board biqu tracking update as shows delivered in wrong country:/

250k/500k/1000k and which speed to shoot for and why (1000k)

Current flow requires navigating in a specific order and can be confusing, update so it can be more linear.

Currently have 128 and 256 interchangeably.
Test if if has negative effects on either test case (RS485 vs Canable Pro
Verify which is required/ if it varies per board.

Suggestion from clee instead of a seperate startup script.

Reflash and test required.

How can i connect Mks monster 8 v2 by Can Bus?
Direct to usb on PI or by UTOC?
If direct, i will connect CAN_L and CAN_H to USB on PI or TX and RX to GPIO on PI?
Thanks