#Internal error on command:"PREP"

1 messages · Page 1 of 1 (latest)

warm storm
#

Basically fresh install... this was all working prior on older btt pi v1.2. But i swapped to a pi 5 today and have been having issues lol hopefully someone has some insight... I tried checking prior posts and wasn't to much there to help me :/

warm storm
#

<@&1304550334839918672>

pale copper
#

hello ! can you please run the following command :

cd ~/AFC-Klipper-Add-On/troubleshooting
./afc-debug.sh

#

it can be copied from the AT docs under the AFC debug script section

#

and share the links to the different log files to see what is actually happening on that "internal error" many thanks !

warm storm
#

sounds good... i have figure out why my pi isn't connecting all of a sudden :/ just one thing after antohter lmao

#

i'll hit you back when i get in

pale copper
#

sounds good ! let me know

warm storm
#

As soon as I get the can network set my pi ip changes....and I don't get why

#

Flashing it witb esso reg method didn't work I had to do tell the pi the bitrates and went through the "getting started " section

languid storm
#

Small tip, Set your pi to a static IP on your router, that way if it does release/renew while working with interfaces it will receive the same IP again.

warm storm
#

6it was the esso steps that made it change... it's never done this

#

this is the steps i had to take to get the 1m bitrate and qlen to 128

#

but once i did sudo reboot at the end... ip changes

languid storm
#

Yes you are making changes to the network service to create can0

warm storm
#

i'm not proficient enough in this stuff to get it lol

#

well when i flash the board with mainboard flashing method of esso's... my bitrate is nonexistant, and i get a qlen of 10

#

so I had no choice but to go to that page ?

#

at a bit of a loss as to what to do now tho

#

oh also my router has yet to see the pi ... i had to plug it into a monitor to get the IP

languid storm
#

Give me a few minutes to get to a PC and we'll see if we can get you sorted

warm storm
#

i'm reflashing the PI sd to start from scratch there

#

and thank u

#

seems i'm back in for now on the pi... jhust need see if the can network shows up now after it updates

bleak jay
#

If you do this command it will not wait for the can network
sudo systemctl disable systemd-networkd-wait-online.service

#

This is also found in the guide

warm storm
#

ya so as soon as i sudo reboot... i can no longer SSH into the pi at all

#

i can log in on the screen... but ssh is done. I"'m so done with this pi omg

languid storm
#

So it sounds like your host wasnt using networkd before, so you'll have to set networkd to start at boot

#

Which would also explain why it changed IP

warm storm
#

i got no clue how or where to start on that end

#

sorry this part is new... i kinda jumped into this to soon i think

#

but it changes to the same number every time i've tried this... 127.0.1.1 every time

#

not sure if that matters

languid storm
#

Thats loopback.

#

Every network interface sees itself as 127.0.0.1

#

or 1.1

warm storm
#

ah, good to know

#

how do i set the ntworkd ?

languid storm
#

sudo systemctl start systemd-networkd

#

and see if that gets you online

warm storm
#

i have reflasht he pi again

#

it wont let me ssh in lolol

#

i'm going to smoke ... i'll be back in a bit ... silly pi is pissing me off today LOL

languid storm
#

Throw a keyboard and display on the pi if possible.

warm storm
#

been sharing my pc keyboard on it lol

#

and it has a monitor plugged in to it atm

#

that's how i know i can log into it but not ssh

languid storm
#

right so networkd is likely offline.

warm storm
#

but i'll start from begininnng and try that networkd first ...

languid storm
#

once we start that you should get ssh access back.

warm storm
#

kk i'll be back in 5

#

workin on kiauh now then i'll see what happens lol

#

appreciate the help by the way

#

when i do the getting started part should i run that command just before i reboot the pi then?

languid storm
#

What are you doing with kiauh?

warm storm
#

i reflashed the pi (before reALIZing i probably didn't need to with that command available...)

#

but here we are lol

languid storm
#

Oh, ok

warm storm
#

i'm done now anyway so gonna move over to esso guide and see what happens

languid storm
#

What version of debian are you flashing

warm storm
#

the OS for the pi?

#

that would be the lite os 64bit

languid storm
#

so mainsail OS?

warm storm
#

i was gonna swap to mainsail yes

#

but have used fluidd up til now

#

... i'm at the part i need to go to the getting started, as i g0t no bitrate and qlen 10

languid storm
#

Where did you get the image from you put on the SD card

warm storm
#

rasp imager

#

in the other tab

languid storm
#

ok so just the RaspiOS lite

#

good, thats bookworm.

warm storm
#

ok i'm in .. ish

#

that command worked

#

i have bitrate and qlen now

#

dont see my mcu uuid but that's probably cause the disapearing act

languid storm
#

Did you restore your config files?

warm storm
#

yes trying to

#

upgrading the pi atm with mainsail... then gonna reboot and see what happens

#

i'm in on printer omg

#

now to get afc going again

#

you're amazin bud i appreciate you 😄

languid storm
#

No worries lol

warm storm
#

is hould probably just install afc from kiauh instead of drag dropping files eh?

#

sorry from ssh* derp

languid storm
#

AFC install script.

#

Yeah

warm storm
#

ya figured as much ty

#

Pin 'M1_STEP' is not a valid pin name on mcu 'Turtle_1'

#

this was a working config prior to all of this...

#

oh well it is fresh install to ... so there is that

languid storm
#

Did you do a reboot after install?

warm storm
#

think so .. worth a try tho

#

on it

#

O_o it's not going back into main

#

No ssh either dafuq

#

But can log in on monitor again lol

languid storm
#

So that commmand just starts networkd.

warm storm
#

how do we get it to stay on forever then?

#

cause seems it is resetting?

languid storm
#

As I thought we were just trying to access your existing install again.

#

Yeah we need to enable that service at startup, we;re back to the same point as when you decided to reinstall lol

warm storm
#

but i do not need to reinstall tho

#

lol k so what do i do meow

languid storm
#

So since we know that was the issue

#

sudo systemctl enable systemd-networkd

#

Will enable networkd to run at startup.

warm storm
#

ran it.. rebooted...and i'm in

#

😄

#

now to figure out afc .. again lololol

#

maybe not :/

languid storm
#

Whats going on now

warm storm
#

lolol moonraker isn't connectintg

#

should i uninstall it and reinstall that?

languid storm
#

No

warm storm
#

we good

#

to late

#

lolol

#

it worked tho

#

printer homes. that's good... now back to afc

#

ok i'm back to m1 step

#

after reboots

#

Pin 'M1_STEP' is not a valid pin name on mcu 'Turtle_1'

#

i mean it's the config everyone else uses klipper stfu

#

lolol

#

networkd is not running at start up

#

i have enter that command evry time from the pi itself

#

ok maybe moonraker is still mad at me

#

... it connected wtf is up with this pi ... i hate it

#

still m1 step issue tho

#

one last hurdle and i think we got it dude... seems can network is talking fine now ty

warm storm
languid storm
#

Diagnose why it wasnt working lol

warm storm
#

ok so how do i address the m1 step issue tho :/

languid storm
#

What its telling you is that it doesnt know how to parse that pin alias

warm storm
#

so where do i go to fix it? as this all worked before.. and is a fresh install

#

am doing a confuse lol

languid storm
#

So verify that the AFC Lite file is present under MCU folder inside the AFC Klipper Add-On folder

warm storm
#

it all worked first time is et it all up

languid storm
#

Something may have gone wronr during the install

languid storm
warm storm
#

It was a fresh install at that point basically as well :/

#

Nit sure I wiped anything th3n lol it may just come back for all e know now :/

#

Looks good to me no?

#

i mean it's all fresh installation... not sure why it can't parse that when i havn't changed anything when it comes to the AFC yet

languid storm
#

OK so is klipper still displaying that error?

warm storm
#

Yessir

languid storm
#

show me the Turtle_1.cfg

warm storm
#

that work?

languid storm
#

Run the install script again

#

I think the symlink may be broken.

warm storm
#

do u want me to remove afc and install it again

#

or update it

bleak jay
#

Looks you are missing this at the top of your AFC_turtle_1.cfg file
[include mcu/AFC_Lite.cfg]

warm storm
#

oh wow... if that's all it is

#

omg

#

Omg

#

Back to prep

#

It boots up now

#

Back to the point of why I made this thread lmao

bleak jay
#

Upload your klippy log

warm storm
#

working on the logs now

#

i did a troubleshooting afc debug

#

did that work? lol

#

let me know if you need anyting else ... really appareciate all the helps guys

#

why didn't it see my uuids? it should have 4 in total

#

not that that is relivant... it connects lol

bleak jay
#

Upload your klippy log here as it's too big for termbin and does not show everything

warm storm
#

Gotcha gimme 5 smoking atm lol

#

i'm running CAN... why' is it trying to open serial ports?

#

Gonna be something silly to I bet ugh

#

that should not even attempt to try serial... dafuq?

#

everything in my config has it pointing at canbus

#

Apologize for potato phone :/ I broke my good one

#

i dont get why it sees it on can network... the just drops it?

bleak jay
#

once klipper is running you cant see your uuid anymore

warm storm
#

i'm not lookin for it. i know to stop klipper to see id's and even then the main board mcu may not show up (can click the reset button once to get it to)

it sees can network.. then drops it

#

after the prep

bleak jay
#

because you restored your files you need to fix this path

warm storm
#

i can pull all my uuids in ssh no problem. the can network seems to be working now

bleak jay
#

its not a uuid problem, klipper would not get to PREP if your uuids were a problem

#

your VarFile variable in AFC.cfg file should be updated to VarFile: /home/dizzy/printer_data/config/AFC/AFC.var

warm storm
#

i was lookin at that just now... just have to ad that .var at the end is all it is?

#

wild

bleak jay
#

well it was right until your restored your previous config

warm storm
#

nope was the afc lol i see it

bleak jay
#

its the user biqu thats messing it up

warm storm
#

you sir

#

are fricken amazin

#

both of you

#

i can't thank you both enough 😄

languid storm
#

Sorry, got pulled away by a call. Glad you guys got it figured out.

warm storm
#

No you helped as well no nees to apologize. She is back on and imma toss my turtle on it him after I do a fat dab

#

🤣