#[solved] mcu 'Turtle_1': Unable to connect

1 messages · Page 1 of 1 (latest)

sly lance
#

just started testing my box turtle and get this error:

MCU 'nhk' config: ADC_MAX=4095 BUS_PINS_i2c0a=gpio0,gpio1 BUS_PINS_i2c0b=gpio4,gpio5 BUS_PINS_i2c0c=gpio8,gpio9 BUS_PINS_i2c0d=gpio12,gpio13 BUS_PINS_i2c0e=gpio16,gpio17 BUS_PINS_i2c0f=gpio20,gpio21 BUS_PINS_i2c0g=gpio24,gpio25 BUS_PINS_i2c0h=gpio28,gpio29 BUS_PINS_i2c1a=gpio2,gpio3 BUS_PINS_i2c1b=gpio6,gpio7 BUS_PINS_i2c1c=gpio10,gpio11 BUS_PINS_i2c1d=gpio14,gpio15 BUS_PINS_i2c1e=gpio18,gpio19 BUS_PINS_i2c1f=gpio22,gpio23 BUS_PINS_i2c1g=gpio26,gpio27 BUS_PINS_spi0a=gpio0,gpio3,gpio2 BUS_PINS_spi0b=gpio4,gpio7,gpio6 BUS_PINS_spi0c=gpio16,gpio19,gpio18 BUS_PINS_spi0d=gpio20,gpio23,gpio22 BUS_PINS_spi1a=gpio8,gpio11,gpio10 BUS_PINS_spi1b=gpio12,gpio15,gpio14 BUS_PINS_spi1c=gpio24,gpio27,gpio26 CLOCK_FREQ=12000000 INITIAL_PINS=!gpio8 MCU=rp2040 PWM_MAX=255 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1
mcu 'Turtle_1': Starting CAN connect
Created a socket
mcu 'Turtle_1': Timeout on connect
Created a socket
mcu 'Turtle_1': Wait for identify_response
Traceback (most recent call last):
  File "/home/biqu/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
    params = self.send_with_response(msg, 'identify_response')
  File "/home/biqu/klipper/klippy/serialhdl.py", line 262, in send_with_response
    return src.get_response([cmd], self.default_cmd_queue)
  File "/home/biqu/klipper/klippy/serialhdl.py", line 319, in get_response
    self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
  File "/home/biqu/klipper/klippy/serialhdl.py", line 254, in raw_send_wait_ack
    self._error("Serial connection closed")
  File "/home/biqu/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'Turtle_1': Serial connection closed
tribal saffronBOT
#

<@&1304550334839918672>

sly lance
#

I have it connected with can bus following the correct pinout.

I do get a uuid when i check devices in klipper

tribal saffronBOT
sly lance
modern shore
#

have you flashed klipper on to the board? looks like it's application is set to CanBoot and not klipper.
Found canbus_uuid=444cb9bb5867, Application: CanBoot

sly lance
#

i did, think i might have found the issue though forgot to put the jumper on

#

if that doesnt fix it i will retry flashing

modern shore
#

let me know how that goes

sly lance
#

nevermind the jumper is on there, im connecting it to the can port on my btt-pad7 could that cause any issues?

modern shore
#

you confirmed that it is flashed with klipper?

sly lance
#

ill try flashing it again

modern shore
#

run this command and paste back what is returned

sudo service klipper stop
~/klippy-env/bin/python ~/klipper/scripts/canbus_query.py can0
sly lance
#
Total 1 uuids found
modern shore
#

I'm not familiar with how old CanBoot runs compared to Katapult now but try running this then run the query again
python3 ~/katapult/scripts/flashtool.py -i can0 -f ~/klipper/out/klipper.bin -u 444cb9bb5867

sly lance
#
Sending bootloader jump command...
Resetting all bootloader node IDs...
Detected Klipper binary version v0.13.0-120-gb1011e3fb, MCU: stm32h723xx
Attempting to connect to bootloader
Katapult Connected
Software Version: v0.0.1-104-gfcb2f84
Protocol Version: 1.1.0
Block Size: 64 bytes
Application Start: 0x8020000
MCU type: stm32h723xx
Verifying canbus connection
Flashing '/home/biqu/klipper/out/klipper.bin'...

[ERROR:root:Flash Tool Error
Traceback (most recent call last):
  File "/home/biqu/katapult/scripts/flashtool.py", line 1096, in main
    await sock.run()
  File "/home/biqu/katapult/scripts/flashtool.py", line 835, in run
    await flasher.send_file()
  File "/home/biqu/katapult/scripts/flashtool.py", line 427, in send_file
    resp = await self.send_command('SEND_BLOCK', prefix + buf)
  File "/home/biqu/katapult/scripts/flashtool.py", line 406, in send_command
    raise FlashError("Error sending command [%s] to Device" % (cmdname))
FlashError: Error sending command [SEND_BLOCK] to Device```
modern shore
#

what commands have you been using before to flash klipper?

sly lance
#

i followed the esoterical guide

#

might have made a mistake somewhere along the way

modern shore
sly lance
#

ill re flash it then

tribal saffronBOT
modern shore
#

<@&1304550334839918672> please correct me if I'm wrong

ionic remnant
#

check the troubleshooting section of docs as well, there are some issues currently with Katapult

modern shore
#

oh yeah I forgot about that, thanks!

sly lance
#

quick question, when flashing i can leave the can-bus/power cable connected right?

ionic remnant
#

for AFC-lite? yeah just don't switch the power select while its on

#

we have seen some cases where the board didn't really want to flash when USB powered anyways

sly lance
#

alright

#

ill try flashing it again with katapult now

sly lance
#

I flashed it again

#
Found canbus_uuid=444cb9bb5867, Application: CanBoot
Total 1 uuids found
#

bitrate was different in /etc/network/interfaces.d/can0 updated that to be this now:

iface can0 can static
  bitrate 1000000
  up ifconfig $IFACE txqueuelen 1024```
drowsy dune
#

canboot is basically teh same thing as katapult just renaemd

sly lance
#

flashing log:


Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash   "
Performing mass erase, this can take a moment
Downloading to address = 0x08000000, size = 5156
Download    [=========================] 100%         5156 bytes
Download done.
File downloaded successfully```
drowsy dune
#

which file are you flashing there

sly lance
#

sudo dfu-util -R -a 0 -s 0x08000000:mass-erase:force:leave -D ~/katapult/out/katapult.bin -d 0483:df11

drowsy dune
#

ok so it has katapult now.

Flash klipper now.

sly lance
#

alright

drowsy dune
#

using flashtool.py -i can0 -f ~/klipper/out/klipper.bin -u 444cb9bb5867

sly lance
ionic remnant
sly lance
#

ah in katapult got it

ionic remnant
#

you need to be in klipper directory to make and flash klipper firmware

sly lance
#

yes

#

~/katapult/scripts/flashtool.py -i can0 -q
Resetting all bootloader node IDs...
Checking for Katapult nodes...
Detected UUID: 444cb9bb5867, Application: Katapult
CANBus UUID Query Complete

#

now to flash it

#
Connecting to CAN UUID 444cb9bb5867 on interface can0
Sending bootloader jump command...
Resetting all bootloader node IDs...
Detected Klipper binary version v0.13.0-120-gb1011e3fb, MCU: stm32h723xx
Attempting to connect to bootloader
Katapult Connected
Software Version: v0.0.1-104-gfcb2f84
Protocol Version: 1.1.0
Block Size: 64 bytes
Application Start: 0x8020000
MCU type: stm32h723xx
Verifying canbus connection
Flashing '/home/biqu/klipper/out/klipper.bin'...

[ERROR:root:Flash Tool Error
Traceback (most recent call last):
  File "/home/biqu/katapult/scripts/flashtool.py", line 1096, in main
    await sock.run()
  File "/home/biqu/katapult/scripts/flashtool.py", line 835, in run
    await flasher.send_file()
  File "/home/biqu/katapult/scripts/flashtool.py", line 427, in send_file
    resp = await self.send_command('SEND_BLOCK', prefix + buf)
  File "/home/biqu/katapult/scripts/flashtool.py", line 406, in send_command
    raise FlashError("Error sending command [%s] to Device" % (cmdname))
FlashError: Error sending command [SEND_BLOCK] to Device```
#

same error :(

#

at least it shows as katapult now

ionic remnant
#

as I meantioned before check the troubleshooting in AFC docs site.

#

I can't get to it from work or I would be more accurate

sly lance
#

no worries ill go down the list

#

remaking katapult with a known commit version

#

its doing something!

#
Sending bootloader jump command...
Resetting all bootloader node IDs...
Detected Klipper binary version v0.13.0-120-gb1011e3fb, MCU: stm32h723xx
Attempting to connect to bootloader
Katapult Connected
Software Version: v0.0.1-89-ge171665
Protocol Version: 1.1.0
Block Size: 64 bytes
Application Start: 0x8020000
MCU type: stm32h723xx
Verifying canbus connection
Flashing '/home/biqu/klipper/out/klipper.bin'...

[##################################################]

Write complete: 1 pages
Verifying (block count = 492)...

[#ERROR:root:Flash Tool Error
Traceback (most recent call last):
  File "/home/biqu/katapult/scripts/flashtool.py", line 1060, in main
    await sock.run()
  File "/home/biqu/katapult/scripts/flashtool.py", line 816, in run
    await flasher.verify_file()
  File "/home/biqu/katapult/scripts/flashtool.py", line 457, in verify_file
    resp = await self.send_command("REQUEST_BLOCK", payload)
  File "/home/biqu/katapult/scripts/flashtool.py", line 403, in send_command
    raise FlashError("Error sending command [%s] to Device" % (cmdname))
FlashError: Error sending command [REQUEST_BLOCK] to Device```
#

Resetting all bootloader node IDs...
Checking for Katapult nodes...
Detected UUID: 444cb9bb5867, Application: Klipper
CANBus UUID Query Complete

#

It works!

#

E _ _ _ _
R ||||||
R | _
__
O | \
R | |\ X |
! ______/ ||
Turtle_1
8:26 PM
lane4 tool cmd: T3 EMPTY READY FOR SPOOL
8:26 PM
lane3 tool cmd: T2 EMPTY READY FOR SPOOL
8:26 PM
lane2 tool cmd: T1 LOCKED NOT LOADED
8:26 PM
lane1 tool cmd: T0 EMPTY READY FOR SPOOL
8:26 PM
Box_Turtle Turtle_1 Prepping lanes
8:26 PM
Error: /home/biqu/printer_data/config/AFC/AFC.var.unit file not found. Please check the path in theAFC.cfg file and make sure the file and path exists.
8:26 PM
AFC Version: v1.0.20-1484-34f3be0

turbid steeple
#

That error should not display on your next reboot since AFC will create it

sly lance
#

alright

#

rebooting now

turbid steeple
#

Do you have anything in lane 2 because you prep sensor is triggered

sly lance
#

error is gone

#

nothing in lane 2 its now red

turbid steeple
#

So do you have a non error turtle now when klipper first starts up?

sly lance
#

yes sir

turbid steeple
#

Nice

sly lance
#

nevermind lane 2 still reports this after klipper restart: lane2 tool cmd: T1 LOCKED NOT LOADED

ionic remnant
#

check your sensors are connected correctly

sly lance
#

yes wasnt mounted properly. 3 of the respoolers are just a bit too tight so will need to adjust that

#

cant spin freely

#

lane 1 can

sly lance
#

fixed the tightness will continue testing tomorrow.

Thanks for the great help everyone!

#

really appreciate it

sly lance
#

it is now up and running and starts up properly and loads filament.

#

I have a question regarding bed size, im adding a purge bucket and brush but needed to move my bed forward to do that how do i properly adjust my bed size? is it just adjusting the position min and position max on x and y?

#

also do i manually need to add a deadzone for the filamatrix cutter?

#

<@&1304550334839918672>

sly lance
turbid steeple
sly lance
#

good to know, thanks

turbid steeple
#

np, I don't brush or poop and solely use the tower.

sly lance
#

I've measured the pins with my multimeter and it does work

#

do i need to include the nitehawk in the AFC config maybe?

#

fixed it

#

had to put a ^ before nhk:gpio3

sly lance
#

found it in the docs!

#

should read better before i ask question ;)

sly lance
#

I get this error when it swaps filament and tries to continue the print:
Move exceeds maximum extrusion (2.607mm^2 vs 1.440mm^2)

couldnt find anything in the troubleshooting section. I manually set the max_extrude_cross_section to 3.0 in the toolhead extruder hope that fixes it

#

<@&1304550334839918672>

drowsy dune
#

you probably have ramming enabled

#

but yes, bumping that up a bit can help

#

(i have mine to set to 5)

sly lance
sly lance
drowsy dune
#

printer settings /multimaterial tab / make sure enable filament ramming is NOT checked

sly lance
#

adjusting that allowed the color swap to work!

am now following all the settings from the linked video for prusaslicer

#

really enjoying the box turtle so far, was a fun build!

ionic remnant
#

can we call this one solved @sly lance ?

sly lance
#

Yes we can! Just have to tweak some of the filament path lengths, thanks for all the help!

sly lance
ionic remnant
#

[solved] mcu 'Turtle_1': Unable to connect