Ender3 Max 1st gen
STM32f1 4.2.2
RPI4b klippy.log (156.4 KB)
I’m sorry to even ask, I hate asking for even more so on the internet and would not be doing it if I havent tried for 2 days now to get this right. Ive tried octoprint, mainsail, and now fluidd and get the same exact errors everytime. If I use the example for my printer I immediately get a hotend error and a bed temp error with values hotter than the sun on the nozzle and colder than deep space on the bed. These are always the exact same temps everytime every try, I copy and paste the ender3 v2 or max NEO either one into my printer.cfg and change the x.y.z accordingly and get rid of them, I dont have my BL touch hooked up right now but for my sanity I get past them, then I get an error ‘unable to parse position max’ I look in the log and it reads the 340 followed by ,n,n,n which Im guessing is nil. It almost looks like its not recognizing the end of one line of script and the beginning of the next. So for sanity reasons, I uncommit for the BLtouch then the error changes to unrecognized pin. Ive read other similiar issues and tried changing the 2nd letter on the pins temp pins, no dice. I know its gotta be something stupid simple but I cant see it and to top it off Im not 100% that its flashing correctly, it reads and recognizes that its hooked up to the pi but the time ive spent I have my doubts. I think it was one of the first stm32 boards and have read it needs a bootloader and it doesnt. I have arduinos, an ftdi chip and esp32’s sitting around and thought about trying to burn one but the way this has been going its 50/50 I brick it. I can load Marlin back onto it and it works just fine, but after the time ive put into trying to get it working Ill brick it intentionally before I put marlin back on it. Any help would be greatly appreciated, FYI this klippy.log is from this newest attempt with fluidd I can find one of the mainsail ones if needed.
ValueError: could not convert string to float: '340\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n[gcode_macro G29]\ngcode:\nBED_MESH_CALIBRATE\nG1 X0 Y0 Z10 F4000'
Doesnt matter what I do, Ive tried every creality cfg that has the STM32103RET6 chip, they all have the same firmware instructions. The max is the only one with that large of a max value but other cfgs was copied with the value changed to insure that there werent any extra spaces or anything else.
I deleted the empty lines, it makes no difference, I set it up as if it had a BLtouch, still doesnt work. I have a strong feeling that even if I was to get past this error, there would be another right behind it. But that stock E3 Max .bin still works when loaded. I have a FT232 usb to ttl board from a espCam board. Im going to try and use canBoot with it. After that its getting an AR-12.
That was the error I was talking about in the original post. Its like its trying to constantly monitor that value. After it reads the initial 340 it should go to the next field/value that it needs to confirm. It literally throws an error on everything from the bl’s probe:virtual-Z pin forward. Doesnt matter if I falsify a value, it errors on the next field. Ive not seen any other issues like this. X and Y no issues at all.
If you look at the E3 Max cfg, it seems like its fine until it gets to where the bl touch is first commented on stating to comment out 2 fields and delete the # in the next 2. if I use another printers stepper_Z field, it goes to the crazy temps and it doesnt matter if the thermistors are plugged in or not.
klippy(1).log (130.0 KB)
Klippy(1).log is the stock ender3pro, same temp error on both bed and nozzle. Load Marlin and temps are fine no thermal runaway errors or anything
this dont make any kind of sense, let it sit with the klipper firmware installed. I hear the fans kick on, the bed was at max temp like the pin should be pulled high but the nozzles fine. no prints loaded not even an option to preheat the bed due to the errors. I give
Under the assumption that you are using a Creality 4.2.2 board, and just going by the last provided log:
You config seems correct
The bed’s temperature sensor reports a temperature of 17332.8 °C
This is usually a clear indication of a defect sensor. Either the sensor itself or the wiring towards it. Connect any other 100K NTC sensor to the respective port. If the error goes away, you know for sure, and then you can work on replacing the sensor on the bed.
I’ll give it a shot, I have a few extras laying around but I recall getting past this error once and getting a similar error for the nozzle. The only way I was able to get to this error to begin with was to manipulate the z_stepper max value which should be 340 but only proceeds with the v2s value entered and I can’t figure that out. It’s like klipper is saying the value can’t be that high and stops and throws errors there.
With that being said, I can’t see where anyone has had these issues concurrently. One offs here and there with logical solutions buy not all of them together which leads be to believe its something with the way the board is flashing since it corrects with default marlin firmware. Also anytime any command is sent it disconnects and throws a ‘mcu’ mcu error like the path isn’t correct in the printer.cfg file.
I’ve even entered both path and I’d both as if they was both used. It says connected but as soon as the commands sent it says it’s not. So some sort of communication issue, and thats using multiple usb cords. It even said during a completely different attempt that it was authorized or something of the sort. I’m about to try and manually set the boot mode and flash the firmware via uart and see what transpires because I can’t stop from thinking that that’s the issue.
I don’t know what drivers are on the v2s and pros for all of the components but I have read that the early 4.2.2 especially on the max has randomly different drivers only identified by the writing on the sd card slot. There’s a post about on here showing what some of the letters mean relating to the drivers. So roll the dice…
The more I think about it, in that post one of the biggest variations was on the z stepper. Where all of this boards issues begin, throw in the option for bl touch but not being shipped with it and it only working with stock firmware, that would explain alot as I’m sure that all of the different build options was probably built into the stock firmware whereas on all of the other 4.2.2 boards on other machines are used with all of the same components. If the firmware for the max by klipper was just ported from another machine using that board which is probable due to not nearly as many max machines out there. That would explain all of the issues. Maybe I’ll have to configure firmware based on confirmation of each individual component like it’s a custom built from scratch printer.
Okay, @justj, you came here looking for advice and support. This place has knowledgeable supporters with years of experience in 3D printing, Klipper, and troubleshooting.
What we can offer is a systematic approach to solving your issues:
You provide a concise description of the unexpected behavior.
You provide a klippy.log.
We will provide advice.
You follow the advice.
If unsuccessful, we start over at step 1.
Alternatively, you can choose to chase your own ghosts. Unfortunately, we cannot do both because it will waste your time and ours with no result.
Some general remarks:
Klipper is not Marlin. Marlin accepts many more hardware errors and still does something. Klipper does not. It will error out until you fix your setup.
Klipper is unaware of the type or brand of your printer, nor does it care. You configure the firmware and printer.cfg for specific hardware components. If you do this correctly and your hardware is working, then your entire setup will work.
Your printer and hardware are ordinary and well-supported.