VzBot 330

[Penatr8tor]

8 hours ago, TitusADuxass said:

The motors were not out of sync, but there is a problem.

When I home all everything is fine.

When I home X and then Y (or just X or just Y) and then try and move the toolhead along in 10mm steps I get a Must home axis first error (for X it occurs after 30mm, and for Y it occurs after 50mm of movement).

The error is consistent, but only happens when I individually home either X or Y.

Software or hardware... That strikes me as the burning question.

I'm guessing it might be software related.

How exactly are you homing just X or just Y? With klipperscreen? From the console? From a Mainsail button?

Since it's possible to redefine G38 every method could be the same or different.

The answer might be buried in a macro.

And what does home-all do differently than just homing axis individually? Hmmm

Just thinking out loud here.

[TitusADuxass]

@Penatr8tor I'm thinking it's software, hardware wise these things are built like tank. Mechanically everything is in order.

I home it via the individual homing buttons on mainsail.

And now it takes three power on cycles before I can get mainsail up in a browser.

At the first cycle the CPAP Fan runs continuously and the printer is not shown on the router network.

2nd cycle, the CPAP switches off, and the printer is visible in the router network. But, it doesn't load in a browser.

3rd cycle and everything is as it should be.

There's a klipper update available, but it fails every time I try it.

I've not changed any macros, the only thing that is different is the mainboard.

A simple print of 9 1st layer test patches gives this.

It starts from centre and goes left one, down one, right three, up one, up one and left three.

The layer shift can be seen on the right hand patch centre row and all three of the top row.

And, the normally super reliable bed levelling  is all over the place.

I wonder if when the USB socket detached itself from the board it corrupted the PI image (me thinking out loud as well).

I'll make a new image for the PI and try that.

[TitusADuxass]

So I downloaded all the config files from the printer, then took another 16gb shdc card and, with PI image, put a new image on the card and put it in the PI.

Then it was:

sudo apt update && sudo apt upgrade -y

Then installed Kiauh and updated everything installed.

Then installed the Beacon klipper module

Then followed this - https://www.klipper3d.org/RPi_microcontroller.html apart from the final stage - sudo usermod -a -G tty pi which I changed to my login as I do not have the user PI on my system.

Now it boots up on the first power cycle.

Now the single axis homing works but I no longer have the must home error when stepping the toolhead.

But I still have the layer shift on Y and a terrible first layer.

I'm stuck now, I do not know where to go from here.

There is one option - start from scratch - i.e. prebeacon, get the printer behaving as ist should and then add beacon. 

 

[TitusADuxass]

Swapping the PI for another didn't make a difference.

So the only thing that is new is the mainboard - mmmh.

[atrushing]

2 hours ago, TitusADuxass said:

Swapping the PI for another didn't make a difference.

So the only thing that is new is the mainboard - mmmh.

It might be worth checking the connections and the jumpers for the stepper drivers. Then I would double check the current settings in your config (especially for the X axis). It also couldn't hurt to try changing between 0 and 999999 to see if stealthchop is giving you troubles. I tend to have better luck with it set at 0 for spreadcycle.

[TitusADuxass]

31 minutes ago, atrushing said:

It might be worth checking the connections and the jumpers for the stepper drivers. Then I would double check the current settings in your config (especially for the X axis). It also couldn't hurt to try changing between 0 and 999999 to see if stealthchop is giving you troubles. I tend to have better luck with it set at 0 for spreadcycle.

Thank you,  I'll look at those and play with the stealthchop.

[TitusADuxass]

Fixed that problem!

I reinstalled the original board and double checked everything - it worked.

Now I've totally screwed up my print start.

In orca I have:

M104 S0 ; Stops OrcaSlicer from sending temp waits separately M140 S0 print_start EXTRUDER=[first_layer_temperature] BED=[first_layer_bed_temperature] CHAMBER=[chamber_temperature]

In the Start_Stop macro I have:

 

gcode_macro PRINT_START]
gcode:

    ## Beacon contact print start
     BED_MESH_CLEAR
    SET_GCODE_OFFSET Z=0

    G28     ; home axes
    G0 Z2   ; position beacon at 2mm for heat soak

    M140 S{BED}     ; start bed heater
    M109 S150       ; preheat nozzle to probing temp
    M190 S{BED}     ; wait on bed temperature
    G4 P60000       ; optional, let temps settle for 1 min

    #WIPE_NOZZLE     ; call another macro to wipe nozzle if available

    G28 Z METHOD=CONTACT CALIBRATE=1    ; calibrate z offset and beacon model hot
    Z_TILT_ADJUST                       ; or QGL to balance towers
    BED_MESH_CALIBRATE RUNS=2           ; bed mesh in scan mode

    WIPE_NOZZLE
    G28 Z METHOD=CONTACT CALIBRATE=0    ; calibrate z offset only after tilt/mesh

    M104 S{EXTRUDER}                    ; set extruder to print temp
    M109 S{EXTRUDER}                    ; wait for extruder temp

    SET_GCODE_OFFSET Z=0.06     ; add a little offset for hotend thermal expansion
                            ; needs fine tuning, long meltzones require more
    SET_GCODE_OFFSET Z_ADJUST={OFFSET}  ; apply optional material squish via slicer

    PRIME_BLOB   ; call another macro to purge or prime nozzle
    ; start printing

But it errors out after homing with Error on 'M140 S': unable to parse

Can another Beacon Contact user please give me some pointers.

Much appreciated.

 

[TitusADuxass]

The Vz appears to be ignoring my Start_Stop.cfg and I can't, for the life of me, find it.

I've checked each of the 8 .cfg files and can't find any other PRINT_START, so the only one that is valid is the one in the Start_Stop.cfg.  The Start_Stop.cfg is called up in the printer.cfg. I'm at my wits end with this.

[TitusADuxass]

Ladies & Gentlemne - remember that PRINT_START is different from  START_PRINT, especially when you have one in the Machine code and the other in your Start_Stop.cfg. It's been staring me in the face all this time.

[TitusADuxass]

Finally!

It's printing how it should again.

[PFarm]

1 hour ago, TitusADuxass said:

Ladies & Gentlemne - remember that PRINT_START is different from  START_PRINT, especially when you have one in the Machine code and the other in your Start_Stop.cfg. It's been staring me in the face all this time.

I think we've all been there at one point. I'm glad you figured it out!

[TitusADuxass]

7 minutes ago, PFarm said:

I think we've all been there at one point. I'm glad you figured it out!

You can bet your bottom dollar that I've made back ups of everything in case or should I say when it happens again.

[PFarm]

8 minutes ago, TitusADuxass said:

You can bet your bottom dollar that I've made back ups of everything in case or should I say when it happens again.

That good practice backup has saved my a** a few times!

[claudermilk]

37 minutes ago, PFarm said:

I think we've all been there at one point. I'm glad you figured it out!

Anyone who has dealt with code for any length of time has been there. Once you find it you have a facepalm moment, then relief that is was something stupid and simple. Finding a misplaced period or semicolon is a real bear. Ask me how I know.

[TitusADuxass]

This morning I swapped out the X tmc 5160 as I was getting a constant failure when homing X, buzzing X also gave the same failure.

Then I swapped to a 0.6 nozzle and set up a new profile in Orca.

Now every print attempt results in - Move out of range: 10.002 10.000 -0.310 [0.000] error.

It does everything normally (homes at 150, bed scan, rehomes and waits for 265c. Then it motors to X0, then to Y0 - that's when the error occurs. 

I do not understand what Move out of range: 10.002 10.000 -0.310 [0.000] is telling me here - any pointers good people?

[mvdveer]

7 hours ago, TitusADuxass said:

I do not understand what Move out of range: 10.002 10.000 -0.310 [0.000] is telling me here - any pointers good people?

In the [z_stepper] section, try increasing your pos-min to -5 and see what happens. It sounds like the calibrated Z_offsett is out of range.

[TitusADuxass]

4 minutes ago, mvdveer said:

In the [z_stepper] section, try increasing your pos-min to -5 and see what happens. It sounds like the calibrated Z_offsett is out of range.

Thanks, I'll look at that. 

I think it is down to the Prime_Blob macro in combination with the new nozzle.

I'm going to calibrate the Z_offset with a 0.2 feeler gauge instead of paper. I looked at the sheet of paper that I used for the last Beacon Calibration and it has a rather deep divot in it, almost as if the nozzle is perfectly in line with a depression in the textured PEI sheet.

I'll reposition the sheet and see if that makes any difference.

[TitusADuxass]

12 hours ago, mvdveer said:

In the [z_stepper] section, try increasing your pos-min to -5 and see what happens. It sounds like the calibrated Z_offsett is out of range.

Putting position_min: -5.0 fixed the issue. I just need to fine tune the prime_blob macro now as it no longer builds a blob - the nozzle is to high.

[mvdveer]

7 minutes ago, TitusADuxass said:

Putting position_min: -5.0 fixed the issue. I just need to fine tune the prime_blob macro now as it no longer builds a blob - the nozzle is to high.

Probably a good idea to recalibrate the beacon Probe, or adjust the offset in the PRINT_START macro. (See here)

[TitusADuxass]

11 minutes ago, mvdveer said:

Probably a good idea to recalibrate the beacon Probe, or adjust the offset in the PRINT_START macro. (See here)

I've looked at that and think I understand it. At present my offset is set to 0.0

I'm still fining tuning the Z height.

[mvdveer]

16 minutes ago, TitusADuxass said:

At present my offset is set to 0.0

For the Goliath, I have an offset in the macro set to 0.80 and for the Voron Revo's, just calibrating now and it looks like 0.04

[TitusADuxass]

6 minutes ago, mvdveer said:

For the Goliath, I have an offset in the macro set to 0.80 and for the Voron Revo's, just calibrating now and it looks like 0.04

What is being offset, the Z ?

I've got mine sorted now. 

I didn't realise that changing upto a 0.6 nozzle would involve sort much faffing about. I think I'll run through Orca calibration tests again just to satisfy myself and to build some trust in the new settings.

[mvdveer]

48 minutes ago, TitusADuxass said:

What is being offset, the Z ?

Yes - to compensate for heat expansion as probing is done at nozzle 150Deg.

50 minutes ago, TitusADuxass said:

I didn't realise that changing upto a 0.6 nozzle would involve sort much faffing about

You can copy your 0.4 printer settings to a VZBOT 0.6nozzle as example and then set the Z-Offset in the printer configuration:

[TitusADuxass]

I've got the 0.6 nozzle dialed in nicely for PETG.

The change up to 0.6 makes a huge difference in vase/spiral mode - it's more robust. It's about a 6 hour print. 

 

[Penatr8tor]

Nice looking prints!

PETG is some really pretty material.

I played around with a 0.8mm nozzle and the results were pretty spectacular.