@Phaedrux I have been pining target and had disconnect - ping had no issues at all.
Best posts made by Aurimas
-
RE: Web Control keeps disconnecting
-
waterjet cutter and duet
Hi,
has anyone used Duet boards to build a waterjet cutter?
Latest posts made by Aurimas
-
RE: G1 H1 for extruder
@Phaedrux sorry I was not clear enough - I need switch activation for detection - stall will not work in my application
but this partially answer my question G1 H1 E is possible. just need endstop definition for this, but it looks like M574 cannot be usedthe other option would be to use Meta commands, something like:
while Alarm is off
G1 Exxxand loop until the alarm activates and exits the loop
any other ideas? -
G1 H1 for extruder
Hi all,
is it possible to have homing for the extruder just like other axis?
need to push the filament until it hits the extruder and then stop
is it possible?
@dc42 -
RE: 6XD+1LC+RC3 Bltouch throws random error mode
@gtrider - no errors. nothing to do with it
-
RE: 6XD+1LC+RC3 Bltouch throws random error mode
@T3P3Tony said in 6XD+1LC+RC3 Bltouch throws random error mode:
Can you confirm that when you say going into error mode, please describe this.
Probes keeps going around and probes the points.
At random stage it would hesitate to respond to the touch and goes into error mode.
starts blinking and duet reports that probe was trigered before probing.
I could not finish single G29 on RC3
back on RC2 didn't have a single issue so far -
RE: issue with 1LC+3.5.0RC2 and magnetic filament sensor V3
@T3P3Tony said in issue with 1LC+3.5.0RC2 and magnetic filament sensor V3:
When you say you are powering up and down to change the filament monitors, is that just the toolboard or the whole system?
the whole system
yes - no changes in the loom or anything else -
RE: 6XD+1LC+RC3 Bltouch throws random error mode
![download (5).jpg](Input file contains unsupported image format) @T3P3Tony said in 6XD+1LC+RC3 Bltouch throws random error mode:
is could be an issue with the probe deploy and retract files
unless it is something different in RC3 from RC2 I cannot see how it could effect anything.
on top of that - it is working, but no the whole way.I have also replaced BLTouch a couple of time just to make sure - nothing changed.
File attached - just rename it to .zip
download.g -
RE: 6XD+1LC+RC3 Bltouch throws random error mode
@Phaedrux said in 6XD+1LC+RC3 Bltouch throws random error mode:
Probing when doing what? You don't specify.
G32 or G29.
it can throw an error after 2, 5 or 10 probed points.
the fact is that it works with RC2 but fails with RC3 -
RE: 6XD+1LC+RC3 Bltouch throws random error mode
@Phaedrux - what does homing file have to do with this?
RC2 - works no issues at all
ungraded to RC3 - probes random amount of points and then throws an error
went back to RC2 - works as expected - not a single errorNO chnages in the config/homing or anything else have been made. ONLY firmware upgraded and downgaded.
Config is below - but you will not find anything in there because it works with RC2
And yes different G31 pxxx values have been tsted. from 200 to 1000 and made no difference on RC3.
On RC2 anything works; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Giga Vega" ; set printer name ; Wait a moment for the CAN expansion boards to start G4 S3 ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet M575 P1 S0 B57600 M669 K1 ; Drives M569 P15.1 S0 ; physical drive 121.0 goes forwards M569 P15.0 S1 ;M569 P122.0 S0 ; physical drive 0.1 goes forwards M569 P0.0 S1 T5:5:7:0 ; physical drive 0.2 goes forwards M569 P0.1 S1 T5:5:7:0 M569 P0.2 S1 T5:5:7:0 M569 P0.3 S1 T5:5:7:0 M569 P121.0 S0 D3 V40 ; physical drive 0.3 goes forwards M584 X15.0 Y15.1 Z0.0:0.1:0.2:0.3 E121.0 ; set drive mapping M671 X-180:-180:1100:1100 Y40:1100:1100:40 S14 M350 X16 Y16:16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80 Y80 Z3000 E400.00 ; set steps per mm M566 X1200.00 Y1200.00 Z7.5 E10000.00 ; set maximum instantaneous speed changes (mm/min) M203 X9000.00 Y9000.00 Z300 E10800.00 ; set maximum speeds (mm/min) M201 X1750.00 Y1750.00 Z35 E2000.00 ; set accelerations (mm/s^2) M906 X2000 Y2000 Z2000 E600 ; Axis Limits M208 X0 Y0 Z-1 S1 ; set axis minima M208 X1000 Y1000 Z1000 S0 ; set axis maxima M564 H0 ; Endstops M574 X2 S1 P"!121.io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin M574 Y1 S1 P"15.!io1.in" M574 Z1 S2 ; Z-Probe M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch M558 P9 C"121.^io0.in" H7.5 F3600 T9000 S0.25 ; set Z probe type to bltouch and the dive height + speeds G31 P300 X-30 Y5 Z2.6 ; set Z probe trigger value, offset and trigger height Increase Z number if the nozzle is too far M557 X50:700 Y70:850 S150 ; Heaters ;M140 H-1 ; disable heated bed (overrides default heater mapping) M308 S1 P"121.temp0" Y"pt1000" R2200 ; configure sensor 1 as PT1000 on pin 121.temp0 M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S350 ; Fans M950 F1 C"out6" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 S1 ; set fan 1 value. Thermostatic control is turned off M950 F1 C"out5" Q500 ; create fan 1 on pin out4 and set its frequency M106 P1 S1 ; set fan 1 value. Thermostatic control is turned off M950 F2 C"121.out2" Q500 M106 P2 T45 H1 M950 F3 C"121.out1" Q500 ; create fan 0 on pin out3 and set its frequency M106 P3 S0 H-1 ; set fan 0 value. Thermostatic control is turned off ; Tools M563 P0 S"Left Extruder" D0 H1 F3 ; define tool 1 M568 P0 S0 R0 A0 ; set initial tool 1 active and standby temperatures to 0C ; Custom settings are not defined T0 M376 H2 M501 M955 P121.0 I52 M593 P"EI3" F60
-
6XD+1LC+RC3 Bltouch throws random error mode
So the system was running no problem at all.
Installed RC3 firmware and it started - the BLTouch would go into error mode randomly while probing the bed.
Tried different probing speed, different height, different sebsitivity - nothing helped.
Finally went back to RC2 and all issues are gone. -
RE: issue with 1LC+3.5.0RC2 and magnetic filament sensor V3
so I did more testing - downgraded versions and the drop out after drop out.
impossible to use.
comes up with non enough movement
somehow it started detecting the sensor from the first boot now.
works sometimes for few cm and sometimes for few meters.
trying to get report from sensor says that it was between 98% to 102%
interupts through the roof as before.
LED is blinking as it supposed to - no issues there.
unpause the print and it goes for a littlewhile with filament counter starting from zero
it is not the first setup that is doing this stupid thing.
almost had enough with the magnetic sensor. just wasting time and I believe I am not the first one