Topics created by smoki3

@Phaedrux

This is my controller:
Screenshot_20210126-230351.jpg

I use RRF3 and no special config applied. You control the GPIO pins

@Phaedrux
No I use it for almost 2 years.
I am pretty sure that the CPU is gone

@chrishamm

Sure:

https://drive.google.com/file/d/12BHjItNynpZUoFNisMo6L-Hr6kTsQpC1/view?usp=sharing

Just for confirmation:
It's fixed!👍

@jpomo10 you are able to control the pin with M42 and M280.

But I will go for CNC Mode that I am able to set directly the turns per minute instead of the PWM signal

then you could go with using a variable for now; altough you'd need to do something like create a dummy tool and store the acceleration value as f.ex. tool offsets, or dummy fans/heaters etc.

not sure if you can set tools[n].offsets[0] .. tools[n].offsets[2] or if you need to use G10 to set the offset, but you can test that easily enough. If you have more axes than xyz, you can probably set more than 3 offets pr tool as well.

I'm still hopeful someone will post instructions I can follow for converting a Duet2Ethernet to d2+SBC as I'd like to have the extra processing ability for some of the hoped to have plugins.

It's fixed now with RC12

@Danal said in Tool Calibration Station E3D Toolchanger:

What is the 44.23 constant?

Or, same question phrased another way: Is it possible to have the station calibrate itself?

The offset between the Z Probe and the Tool Probe.

I think think this is not possible duet to both micro switches and to the fact that the my V Axis is too short

@smoki3 said in XY Motors on Duex5:

@dc42 said in XY Motors on Duex5:

It makes no difference whether you use the Duet or DueX motor connections.

Ok cool. Does it matter if I connect the Z probe to Duex5?

Yes. The endstop inputs on DueX5 have higher latency. So I recommend that you connect the output from the Z probe to the Duet.

@Damien said in Panel Due with RRF 3.0 issue:

Any suggestions?

read the https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-310 before upgrading.

All PanelDue users: the PanelDue connector (or IO_0 on Duet 3) is no longer dedicated to PanelDue, therefore if you connect a PanelDue to this port you must use the following command in config.g to enable it: M575 P1 S1 B57600. You can use baud rates other than 57600, however the IAP files all assume 57600 baud; therefore if you use another baud rate then PanelDue will not display firmware update progress.

@dc42 said in Fourth Extruder not working on latest RRF3:

I've just fixed this - new binary in same place as before.

Tested with the dropbox binary. Now it's working. Thanks

@dc42 said in Tool Change: Moving in axis without calling them:

@smoki3, I have fixed this in the 3.0 stable release.

I am not planning to do any further 2.x releases, but you have an easy workaround (M400 at the start of the tpre and/or tpost file).

I see. Its working fine now.

For 2.x I don't use it. I just thought about all the tool changer users....

@dc42

I am using the latest v3-dev branch

This is the response:

M408 S2 {"status":"I","coords":{"axesHomed":[0,0,0,0],"wpl":1,"xyz":[0.000,0.000,0.000,0.000],"machine":[0.000,0.000,0.000,0.000],"extr":[0.0,0.0,0.0,0.0]},"speeds":{"requested":0.0,"top":0.0},"currentTool":-1,"params":{"atxPower":-1,"fanPercent":[0,100,0,0,100,0,100,0,100],"speedFactor":100.0,"extrFactors":[100.0,100.0,100.0,100.0],"babystep":0.000},"sensors":{"probeValue":0,"fanRPM":[-1,-1,-1,-1,-1,-1,-1,-1,-1]},"temps":{"bed":{"current":23.0,"active":0.0,"standby":0.0,"state":0,"heater":0},"current":[23.0,22.2,21.6,22.1,22.4],"state":[0,0,0,0,0],"tools":{"active":[[0.0],[0.0],[0.0],[0.0]],"standby":[[0.0],[0.0],[0.0],[0.0]]},"extra":[]},"time":126.0}

My config;

; Configuration file for Duet WiFi (firmware version 1.21) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool on Wed Sep 19 2018 21:12:53 GMT+0200 (Mitteleuropäische Sommerzeit) ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Network M550 PCoreXY ; Set machine name M552 S1 ; Enable network M587 S"FRITZ!LES WLAN" P"69713510671866861951" ; Configure access point. You can delete this line once connected M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; Drives M584 X0 Y1 Z2 E3:4:5:6 U7 ; Map Drives to Axis M669 K1 ; Select CoreXY mode M569 P0 S0 ; Drive 0 goes forwards M569 P1 S0 ; Drive 1 goes forwards M569 P2 S1 ; Drive 2 goes forwards M569 P3 S0 ; Drive 3 goes forwards M569 P4 S0 ; Drive 4 goes forwards M569 P5 S0 ; Drive 5 goes forwards M569 P6 S0 ; Drive 6 goes forwards M569 P7 S0 ; Drive 7 goes forwards M350 X16 Y16 Z16 E16:16:16:16 I1 ; Configure microstepping with interpolation M350 U8 I0 ; Configure microstepping without interpolation M92 X100 Y100 Z1600 U100 E460:460:460:460 ; Set steps per mm M566 X600 Y600 Z18 U2 E100:100:100:100 ; Set maximum instantaneous speed changes (mm/min) M203 X35000 Y35000 Z1200 U25000 E5000:5000:5000:5000 ; Set maximum speeds (mm/min) M201 X6000 Y6000 Z400 U500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2) M906 X1650 Y1650 Z1100 U200 E1450:1450:1450:1450 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S120 ; Set idle timeout ; Axis Limits M208 X-13.5 Y-56 Z0 U0 S1 ; Set axis minima M208 X316 Y202 Z270.20 U500 S0 ; Set axis maxima ; Thermal Sensors M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; Set thermistor + ADC parameters for heater 0 M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.060000e-8 ; Set thermistor + ADC parameters for heater 1 M308 S2 P"e1temp" Y"thermistor" T100000 B4725 C7.060000e-8 ; Set thermistor + ADC parameters for heater 2 M308 S3 P"e2temp" Y"thermistor" T100000 B4725 C7.060000e-8 ; Set thermistor + ADC parameters for heater 3 M308 S4 P"e3temp" Y"thermistor" T100000 B4725 C7.060000e-8 ; Set thermistor + ADC parameters for heater 4 ; Hardware M950 H0 C"bedheat" T0 M950 H1 C"e0heat" T1 M950 H2 C"e1heat" T2 M950 H3 C"!exp.heater3" T3 M950 H4 C"!exp.heater4" T4 M950 F3 C"duex.fan3" M950 F4 C"duex.fan4" M950 F5 C"duex.fan5" M950 F6 C"duex.fan6" M950 F7 C"duex.fan7" M950 F8 C"duex.fan8" ; Max Temp Protection M143 H0 S140 ; Set temperature limit for heater 0 to 140C M143 H1 S270 ; Set temperature limit for heater 1 to 270C M143 H2 S270 ; Set temperature limit for heater 2 to 270C M143 H3 S270 ; Set temperature limit for heater 3 to 270C M143 H4 S270 ; Set temperature limit for heater 4 to 270C ; Fanmapping M106 P0 S0 I0 F500 H-1 C"Tool 0" ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P3 S0 I0 F500 H-1 C"Tool 1" ; Set fan 3 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P7 S0 I0 F500 H-1 C"Tool 2" ; Set fan 7 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P5 S0 I0 F500 H-1 C"Tool 3" ; Set fan 5 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H1 T55 ; Set fan 1 value for Tool 0, PWM signal inversion and frequency. Thermostatic control is turned on M106 P4 S1 I0 F500 H2 T55 ; Set fan 2 value for Tool 1, PWM signal inversion and frequency. Thermostatic control is turned on M106 P6 S1 I0 F500 H3 T55 ; Set fan 6 value for Tool 2, PWM signal inversion and frequency. Thermostatic control is turned on M106 P8 S1 I0 F500 H4 T55 ; Set fan 8 value for Tool 4, PWM signal inversion and frequency. Thermostatic control is turned on ; Endstops M915 X Y S5 H350 F0 R0 ; Set Stall detection sensitivity M915 U S5 H200 F0 R0 ; Coupler M574 X1 Y1 S3 ; Set endstops controlled by motor load detection ; Z-Probe M574 Z0 C"nil" ; no Z endstop switch, free up Z endstop input M558 P5 C"!zstop" H3 F180 T25000 ; Z probe connected to Z endstop input G31 X0 Y0 Z0.00 P500 ; Set Z probe offset + naher ran - weiter weg M557 X0:300 Y0:190 S50:47.5 ; Define mesh grid ; Tools M563 P0 D0 H1 F0 ; Define tool 0, Fan 0 M563 P1 D1 H2 F3 ; Define tool 1, Fan 3 M563 P2 D2 H3 F7 ; Define tool 2, Fan 7 M563 P3 D3 H4 F5 ; Define tool 3, Fan 5 ; PID Settings Tools M307 H1 A595.9 C199.5 D4.5 S1.00 V24.1 B0 ; Set PID settings tool 0 M307 H2 A775.0 C252.4 D8.2 S1.00 V24.1 B0 ; Set PID settings tool 1 M307 H3 A716.5 C237.1 D8.7 S1.00 V24.1 B0 ; Set PID settings tool 2 M307 H4 A567.7 C241.0 D6.7 S0.80 V24.1 B0 ; Set PID settings tool 3 M307 H0 A181.4 C631.5 D4.9 S1.00 V24.1 B0 ; Bed PID Settings ; Tooloffset ;G10 P0 X0.00 Y34.50 Z-15.84 ; Set tool 0 axis offsets ;G10 P1 X0.55 Y34.50 Z-15.83 ; Set tool 1 axis offsets ;G10 P2 X0.16 Y34.50 Z-15.85 ; Set tool 2 axis offsets ;G10 P3 X0.25 Y34.50 Z-15.70 ; Set tool 3 axis offsets M98 Ptooloffset.g ; Tools Temperatures G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C G10 P1 R0 S0 ; Set initial tool 1 active and standby temperatures to 0C G10 P2 R0 S0 ; Set initial tool 2 active and standby temperatures to 0C G10 P3 R0 S0 ; Set initial tool 3 active and standby temperatures to 0C ; LED Strip M950 F2 C"nil" ; Free fan 2 pin M950 P2 C"fan2" ; create GPIO pin 2 attached to fan 2 M42 P2 S30 ; Turn LEDs on 30% PWM ; Calibrate MCU Temperature M912 P0 S-8 ; DAA M593 F80 ; Load config override M501

I am not alone:

https://github.com/chrishamm/DuetWebControl/issues/166

Imlbrown created this issue in chrishamm/DuetWebControl closed Alternate axis (U,V & W) show "n/a" for position on dashboard #166

Correct that a Pi cannot attach to a Duet 2 via ribbon cable high speed interface until the Duet2 firmware is updated.

However... There are two ways to use a Pi as a touch screen interface to a D2 that work right now.

Run the DWC interface in a browser on the Pi. The D2 and the Pi must be on the same network. This can be any mix of wired and wireless, as long as their IP addresses can reach each other.

It is literally as simple as building a vanilla Pi, with touchscreen, and launching a browser and entering the Name (or IP) of the printer.

Connect the one of the Pi's UARTS to the same port on the Duet 2 that a PanelDue connects. This is just TTL serial, so PI TX <> Duet RX and vice versa.

Then, write your own touch gui. Have it issue the same commands a Panel would... and display the status of the printer by "polling" for updates, just like a Panel does.

Easy to look at github and see all the commands. Being a Pi, that gui could be Python, NodeJS, or any of a dozen other languages.

Obviously path 2 is more work; it also allows TOTAL custom GUI. BIG BIG buttons for start/stop/home, whatever. Scrolling screen for other buttons. Whatever your heart desires.

@droftarts

I renamed the C axis to U axis.
Now it seems to work. PanelDue only supports U axis as third axis

Just copying the homec to homeu have not worked.

DWC is now on 2.0.2

There is a comment on the change list saying 'print another' has been fixed.

@smoki3 said in Unretract after Tool Change:

@deckingman
yes because you get stringing between the last known position and the next print move

But if the next move is a print move including extrusion, then you need to unretract before making that move, so you won't get stringing. If on the other hand, the next move is simply a change of position without extrusion, then you might get stringing. In that case, the unretract needs to happen after the first non print move and before the next print move.
So the unretract needs to be conditional depending on whether the next move has an "E" element.
I can't off hand think of a way to do that other than a post processing script.

@smoki3 said in tpost.g does not apply tool offset:

@dc42 then we need an option to disable it in tfree. Because a dock and a parking position will never in the tool coordinate system

You will be able to prefix movement lines with G53 to do that.