Looks better now but still is finished with error (actually it's not in terminal, there are only warnings... a bit weird) and `firmware_for_sd_upload.bin` wasn't generated. (see attachment)
Is `firmware.bin` the same as `firmware_for_sd_upload.bin` ?
ok, I'v found already changes in `jgaurora_a5s_a1_with_bootloader.py`, will check this, I'm glad that it's not a problem of compilation, thanks for advise, will keep you updated with my results, and again, thanks for your work, it's amazing!
Excellent! Thanks for sharing your success.I'm thinking I might move the build bin back to that folder, I thought it would make things simpler but apparently not.
First off thank you very much for putting this together. Very impressed with the mimicking of certain features found on Prusa firmware such as moving the nozzle up during filament changes and the autoload features.
Is it safe to say that filament run-out and power outage are still WIP when running community firmware?
I'm also planning to add a precision piezo sensor for auto bed leveling in the near future and my plan is the following:
1. Download source and make edits to account for a nozzle based sensor system. 2. The precision peizo sensor adds length to the hotend so things like unload and autoload would need to be adjusted by 20-50mm where abouts would I find this in source to edit the values used for autoload and unload? 3.
Again thank you everyone for putting work into the firmware and bringing it this point.
Welcome @Msin , glad the firmware is working for you. I haven't had time to work on this for a few months now, and no-one else has jumped onboard yet either unfortunately.
I'm not familiar with piezo levelling, but most of the settings are in configuration.g and configuration_adv.h.
I'm wondering if you have any guidance on purging off the side of the bed. I'm looking to not create a purge line but instead, purge off the side of the bed.
When G28 X occurs the nozzle is placed over the bed however when commands something like G1 X0 the nozzle actually moves onto the bed which is not what im looking todo. Its as if any movement command forces it to get back within range, any thoughts on how I could get around this?
G28;
; Set initial warmup
temps
M104 S160 ; set
extruder no-ooze temp
M140
S[first_layer_bed_temperature] ; set bed final temp
; Final warmup
routine
M104
S[first_layer_temperature] ; set extruder final temp
M109
S[first_layer_temperature] ; wait for extruder final temp
M190
S[first_layer_bed_temperature] ; wait for bed final temp
@Msin in the firmware there is an offset programmed for the printable area relative to the endstop. This results in the behavior you see. Why not just home X each time you want to get off the bed?
That's what I figured. I've been meaning to compile the code from source and I'll put that on my list to change. I wonder if disabling software endstops would allow me to purge off the side of the bed? Could you point me to what variables should be getting changed in the config?
While homing to X gets me off the bed if I try to purge after doing a G28 X it moves back to the print bed which defeats the ability to purge off the side of the bed. It seems any E command returns you to the printable area which makes sense for standard use.
I tried to compile using VScode and your great walkthrough but getting some odd errors. I usually do this through the Arduino IDE but seems like VS code and the workflow you've described is definitely nicer!
Executing task: C:\Users\repto\.platformio\penv\Scripts\platformio.exe run <
Thanks for the help Samuel! Sadly hit another roadblock. After moving the .bin over to the SD card the update swiftly executes but fails to leave the 100% screen. I changed back to the official .bin file for community firmware and it flashes properly. Tried reformating and then placing it and got the same behaviour.
I am recently having the same problem getting stuck at 100% even though it has worked in the past. Please post the solution if you figure it out. I can't even upload my file with the bootloader with the ST link.
Tried the Titan MKII V2 firmware provided on the inventbox website and it flashed fine. I wonder if the gotta build them all version is messing with things.
Can't seem to get any non-factory firmware to load successfully. Hangs at 100% like others have reported above. Cycling power brings up message:
->Fat mount fail
->exacute FW...
And sits there forever. Can load factory firmware to restore operation.
Could the latest factory firmware have killed the ability to load community firmware? Is there older factory firmware stashed somewhere? It doesn't appear to be available on factory site.
I was having the same problem with SD upload but after using st-link and uploading a version with the bootloader I am now able to use the SD card again.
Interesting. Maybe there was an issue with factory installed bootloader? @Earthbound - if you do go the ST-Link route, can you please try and dump a copy of the entire firmware first, before you upload the new one? And no, the firmware with bootloader is safe - the bootloader component is a copy of the factory bootloader from my machine.
Howdy, Stranger! It looks like you've been lurking for a while.
If you register, we will remember what you have read and notify you about new comments. You will also be able to participate in discussions.
So if you'd like to get involved, register for an account, it'll only take you a minute!
Comments
Is `firmware.bin` the same as `firmware_for_sd_upload.bin` ?
Please delete that entire folder, and redownload from github, if that doesnt work we can do a teamviewer session.
to :
and it works now.
Edit: Forgot to mention im using A5S variant
First off thank you very much for putting this together. Very impressed with the mimicking of certain features found on Prusa firmware such as moving the nozzle up during filament changes and the autoload features.
Is it safe to say that filament run-out and power outage are still WIP when running community firmware?
I'm also planning to add a precision piezo sensor for auto bed leveling in the near future and my plan is the following:
1. Download source and make edits to account for a nozzle based sensor system.
2. The precision peizo sensor adds length to the hotend so things like unload and autoload would need to be adjusted by 20-50mm where abouts would I find this in source to edit the values used for autoload and unload?
3.
Again thank you everyone for putting work into the firmware and bringing it this point.
I'm wondering if you have any guidance on purging off the side of the bed. I'm looking to not create a purge line but instead, purge off the side of the bed.
When G28 X occurs the nozzle is placed over the bed however when commands something like G1 X0 the nozzle actually moves onto the bed which is not what im looking todo. Its as if any movement command forces it to get back within range, any thoughts on how I could get around this?
G28;
; Set initial warmup temps
M104 S160 ; set extruder no-ooze temp
M140 S[first_layer_bed_temperature] ; set bed final temp
; Final warmup routine
M104 S[first_layer_temperature] ; set extruder final temp
M109 S[first_layer_temperature] ; wait for extruder final temp
M190 S[first_layer_bed_temperature] ; wait for bed final temp
; Prime line routine
M201 X500 Y500 Z100 E5000
M205 S0.00 T0.00 B20000 X5 Z0.4 E5.00
M420 S1
G1 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X0 E15 F600 ; prime nozzle
G1 X0 Y180 F5000 ; quick wipe
Thanks!
While homing to X gets me off the bed if I try to purge after doing a G28 X it moves back to the print bed which defeats the ability to purge off the side of the bed. It seems any E command returns you to the printable area which makes sense for standard use.
Thanks for your thoughts!
Tried the Titan MKII V2 firmware provided on the inventbox website and it flashed fine. I wonder if the gotta build them all version is messing with things.
And no, the firmware with bootloader is safe - the bootloader component is a copy of the factory bootloader from my machine.
Howdy, Stranger!
RegisterIt looks like you've been lurking for a while.
If you register, we will remember what you have read and notify you about new comments. You will also be able to participate in discussions.
So if you'd like to get involved, register for an account, it'll only take you a minute!