Hello, I have a question regarding how to flash firmware to my ATmega2560 / RAMPS 1.4 I'm building a voron 1.6. I have Octoprint and Klipper installed on my R PI 4. I know this is an old combo but its the parts I bought when I started and its taken a while to get everything together. ALso there was a voron 1.6 config in the the machine files so I though that would make things easier. when I try make menuconfig and then use the make command to the usb port it fails to program the board. does the RAMPS need to be programmed with Klipper from the ardrino IDE somehow or do I need to burn the bootloader? MY assumption was that it would have with thr bootloader preinstalled. Any help would be appreciated. Thank you
#Trouble installing klipper on RAMPS 1.4 for Voron 1.6 Build
50 messages Β· Page 1 of 1 (latest)
If its an actual ramps 1.4, it should have an actual arduino mega. And being an arduino product, it should have the bootloader already installed. And thus, klipper's flashing tool should just work
Clearly, something in my long list of "should"s there isn't going quite according to plan
Can you show us exactly what happens when you attempt the flash?
@sonic quartz
Thanks for the reply. I got the RAMPS and the Arduino from ZYLTech per the sourcing guide. I actually have another update I got it flashed. I found an older config file in the Voron 1.6 firmware files I had that indicated that the RAMPS / ATmege combo need to be updated with the following command "make flash FLASH_DEVICE=/dev/ttyACM0" instead of actually specifying the serial port. I do however have a new problem. when I try to connect to the printer I get the error: "Your printer's firmware reported an error:
Option 'mesh_min' in section 'bed_mesh' must be specified
Due to this error, OctoPrint was not able to continue to communicate with your printer and sent an emergency stop command M112 to ensure all heaters are turned off, then disconnected." Any insight would be appreciated.
Well, as step 1, I would strongly encourage using mainsail or fluidd over octoprint. Much nicer integration with klipper. But that's mostly an aside. Can you post your [bed_mesh] section as it stands now?
I'm with you on the mainsail π but octoprint is what I know so I was trying minimize variables here is my bed mesh section: [bed_mesh]
speed: 150
samples: 2
horizontal_move_z: 4
sample_retract_dist: 2.0
min_point: 25,5
max_point: 203,153
fade_start: 0.6
fade_end: 5.0
probe_count: 4,4
algorithm: bicubic thanks !
Min_point and max_point should be mesh_min & mesh_max
My guess is they changed at some point, but nobody has updated that...err....rather old config file...
I try it. Thank you !
Update: I tied replace Min_point and max_point and mesh_min & mesh_max. I'm still seeing the same error when I try to connect to the printer in Octoprint. I'm looking through the klepper github for answers. any additional insight would be appreciated. Thank you.
The whole same error? With "mesh_min must be specified" ?
Protip: post the whole config (in a sensible format) and the error message in its entirety.
Trying to upload the config now. I should note that the config is the one that was bundled with the original Voron 1.6 STLs / documentation. Alsop of note is the LCD for the control board will power on but it hasn't displayed anything before or after flashing. Thanks,
Display can't show anything when klipper isn't even starting
My first reaction is that the config you uploaded can't possibly be the one you printer is actually using
The klipper log may offer some kind of insight
I uploaded the config myself and hand copied that from the editor in octoprint
the klipper log will show not just error messages, but also the entire config as it is used (with any included files), not just the file you think is the config which may or may not actually be the case.
That editor is a notorious source of weird problems
Stop using it immediately
If you insist on using octoprint, you should do your config editing via some other channel. I suggest something like vscode 's ssh functionality
mainsail or fluidd are much more sane choices for a klipper web ui. They're actually made to work with klipper and has much fewer weird quirks compared to octoprint. Even if you're used to octoprint, it's not a huge barrier to swap and it'll very quickly be worth it. It's also what basically everyone else uses (mostly mainsail, though there's not a huge difference between them) so support for it in places like this is going to be much better.
I don't have a problem with trying Mainsail or Fluidd. what no one has actually told me is why they are better. I'll take a look at the logs. Thanks.
- Their editors work
- They are properly integrated with klipper, giving you full access to klipper's macros and sensors and other things without manual tinkering
- They have better performance.
- Access to high level klipper features like cancel object
Fair enough. I'm still not even to the point to where the printer is even talking with the web UI. Maybe I'll try swapping later today. Thanks.
it should be fine to run both octoprint and mainsail in parallel on the same rpi4. especially if you have kiauh on there already.
Right now I'm just trying to the the control board to talk to the R-PI. π I can try mainsail but I find it highly unlikely that the error I'm getting has anything to do with Octoprint.
If the editor is flaky maybe it isn't commiting my changes or something IDK.
sigh Octoprint's broken config editor means there's probably a difference between the config your printer is actually using, and the conrig you think it's using
that might make sense
Which is why you're getting an error complaining about a setting you appear to have fixed
Which is why were asking for the klipper log
It would tell us what the config ACTUALLY looks like
As opposed to what you think it looks like
There is no need to be rude just because I don't know what you do. π Your explanation is sound. I appreciate the help.
I don't think I'm being rude. The error message you're getting strongly suggests a ...mismatch between what klipper thinks is happening and what you think is happening. That's not a criticism of you. It's just the situation as it stands
Or I guess it would be more accurate to say, I don't mean it as a criticism of you
(Maybe of your chosen software platform, if I'm right about why it's happening)
Point taken. no big
No worries man. I work with some engineers I'm no sure qualify as organic life forms. π I wanted to use Octoprint because its been running my other printer rock solid for years but I also understand your reasoning as to why Mainsail or Fluidd would work better with Klipper. I'll post a follow up once I get my RPI setup again. Thank you kindly.
Ya I mean, octoprint and marlin work together very well. Klipper just approaches things enough differently that it doesn't work out as well.