FW 3.0.5 RC  

Re: FW 3.0.5 RC

Does this statement from the previous version still apply to this version?

DO NOT run calibration routine when any USB program connected ( Pronterface etc )

Re: FW 3.0.5 RC

Notes:
The new calibration process takes about 10 minutes.
There is a new settings menue item "Show end stops" where you can see the state of the end stops (0=anywhere, 1=at end position)

Should the printer be factory reset for calibration?
Does the value of the live adjust Z matter?
What's the meaning of "Check for a new FW update"

X/Y compensation if axes are not perpendicular: Would it be possible to show the compensation results/values?

Re: FW 3.0.5 RC

I am trying this firmware. Settings has "Calibrate Z" and "Calibrate X/Y". Both seem to do exactly the same thing.

I got this message, "X/Y skewed severely. Skew will be corrected automatically".

Re: FW 3.0.5 RC

Seems pretty fine! My X/Y calibration was perpendicular!
The calibrate Z only does the assumed Z-calibration for me, while the X/Y take a couple of minutes to scan the points.
I could also remove my added "x-stop-enhancer" now that the points are located better.

I found one problem, not sure if it's just me but, when I print (from SD this time) and stop the print, it just skips a few lines and then proceeds but with an offset, causing it to try to print outside of the bed.

Re: FW 3.0.5 RC

Should the printer be factory reset for calibration?
Does the value of the live adjust Z matter?
What's the meaning of "Check for a new FW update"

X/Y compensation if axes are not perpendicular: Would it be possible to show the compensation results/values?

Factory reset won't hurt anything, but it should not cause any problems.
Live Z adjustment is disabled for the calibration.
It means that, with new release of drivers, there will be a special command in start gcode with the latest firmware number. When running the gcode on printer, it will compare the versions and notify the user about the new version.

I am trying this firmware. Settings has "Calibrate Z" and "Calibrate X/Y". Both seem to do exactly the same thing.

I got this message, "X/Y skewed severely. Skew will be corrected automatically".

Calibrate Z is the mesh calibration you see before every print. Calibrate X/Y runs longer and finds the point position for later calibrations.
The message measn exactly what is says. Angle between X and Y axes is not 90° and the printer will automatically compensate for it when you print, so 90° angle in gcode corner will print 90° on the printer 🙂

I found one problem, not sure if it's just me but, when I print (from SD this time) and stop the print, it just skips a few lines and then proceeds but with an offset, causing it to try to print outside of the bed.

Can you be more specific? This seems like regular buffer behaviour from Marlin FW :-/ We plan to work on the buffer in the next releases.

Re: FW 3.0.5 RC

I found one problem, not sure if it's just me but, when I print (from SD this time) and stop the print, it just skips a few lines and then proceeds but with an offset, causing it to try to print outside of the bed.

Can you be more specific? This seems like regular buffer behaviour from Marlin FW :-/ We plan to work on the buffer in the next releases.

It's hard to describe, but I was doing a regular rectilinear infill. When I stopped it (using the lcd panel) I'd say it skipped 3 lines of code and just started the next line from a relative position (moved a bit x axis then keps going downleft) but since it was going to be a long line it exited the print bed and probably wanted to keep going but I aborted it.

Re: FW 3.0.5 RC

Hi, back from travel I wanted to give a go to this Firmware, so I started the printer, plugged the USB on the computer, launched Firmware updater and choose the 1_75mm_MK2-RAMBo13a-E3Dv6full.hex file.

Once the update started, the LCD screen showed the 4 lines of squares, but stalled on this stage and never went out of this state.

I even tried to redo the update but got the error:

avrdude.exe: ser_open(): can't open device "\\.\COM4": Acc�s refus�.

What may I do ? Should I restart the printer ? (I do not dare at this stage).

Help !

Re: FW 3.0.5 RC

I was unable to upload this FW via FirmwareUpdater too (4 lines on LCD and never ending update progress). I restarted the printer (with 2 lines on LCD - FW on rambo obviously corrupted) and tried it again with same result. So I tried older (last stable) 3.0.3 - uploaded without problem.

I still wanted 3.0.5. so I used Arduino to compile and upload.

Re: FW 3.0.5 RC

Just wanted to chime in with my experience.

So before using the firmware updater to update to 3.0.5, I factory reset my printer to be safe. The updating process might have taken a little longer than before or maybe it just seemed that way, but regardless, the firmware was applied successfully.

During the process of the X/Y calibration, my nozzle actually just barely made contact with the bed during the longer part of the calibration process when it hones in on each calibration point. So when I noticed this happening, I canceled the calibration, adjusted my z offset 0.2mm higher and restarted the calibration process and everything went smoothly from there. And the end result of the X/Y calibration process was quite good. Everything is aligned up pretty much perfectly.

James

Re: FW 3.0.5 RC

Ok, a quick update:

Rebooting my computer fix my write denied error, I was able to put back 3.0.3 firmware. I feel better now 🙂

I downloade again and tried to reapply 3..0.5 RC and got this error:

avrdude.exe: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.01s avrdude.exe: Device signature = 0x1e9801 avrdude.exe: reading input file "./fw.hex" avrdude.exe: input file ./fw.hex auto detected as Intel Hex avrdude.exe: writing flash (186448 bytes): Writing | #######################################avrdude.exe: stk500_2_ReceiveMessage(): timeout ########### | 100% 41.00s avrdude.exe: 186448 bytes of flash written avrdude.exe: verifying flash memory against ./fw.hex: avrdude.exe: load data flash data from input file ./fw.hex: avrdude.exe: input file ./fw.hex auto detected as Intel Hex avrdude.exe: input file ./fw.hex contains 186448 bytes avrdude.exe: reading on-chip flash data: Reading | ################################################## | 100% 20.12s avrdude.exe: verifying ... avrdude.exe: verification error, first mismatch at byte 0x0000 0x0c != 0xc1 avrdude.exe: verification error; content mismatch avrdude.exe done. Thank you.


Not sure how to fix that and why do I have this error in my situation.
At least rolling back to 3.0.3 worked like a breeze this time.

Re: FW 3.0.5 RC

So I just upgraded the firmware and ran the x/y calibaration, worked great. However the result came back "x/y skewed severely but will be corrected automatically." but everything looks straight and the prints have been coming out great.

How is that possible?

Re: FW 3.0.5 RC

The skewing is only relevant to the 9 probe positions. You may have to run the V2Calibration code again to reset the Z adjust.

For some reason, your bed is not square to the Z frame (twisted by a degree or two - not sure how that becomes "severe"...).

Peter

Re: FW 3.0.5 RC

one more thing, now the bedleving fails. "Sensors triggerd to high waint for reset" how do i fix that?

Re: FW 3.0.5 RC

Can I suggest a factory reset and retry the calibration?

Also ensure that the probe is positioned as per the manual. I think the probe should be just under 1mm higher than the tip of the nozzle.

Peter

Re: FW 3.0.5 RC

remind me again about the reset precedure, just hold the two buttons down until it beeps?

Re: FW 3.0.5 RC

Press and hold the knob; press and release the reset button; keep holding the knob until it bleeps.

Peter

Re: FW 3.0.5 RC

one more thing, now the bedleving fails. "Sensors triggerd to high waint for reset" how do i fix that?

Was it during the printing?

Re: FW 3.0.5 RC

one more thing, now the bedleving fails. "Sensors triggerd to high waint for reset" how do i fix that?

Was it during the printing?

Thus happens directly after the mesh leveling procedure. The v2 calibration gcode worked though.

I tried a factory reset but my Z offset remains even after the reset. So the problem is still there.

Re: FW 3.0.5 RC

Now I have reset again, i checked the difference between nozzle and probe and the probe is 0,7mm higher then the nozzle.

After I reset I printed V2 calibration and started the batman gcode to further adjust the nozzle. After that I started the whistle gcode just to see it it started, thats the one that failed for me earlier, and it started so I stopped the print.

No I ran the x/y calibration and got a different message. Saying something like "All OK x/y is slight misaligned" I different message then before. It didn't mention anything about it being corrected automatically.

So I started the whistle again and after the bed leveling it just stops and I get the message again "Bed level failed, sensor triggered to high waiting for reset" and nothing happens.

What may be causing this, I'm starting to get a bit frustrerad.

Thanks for the help.