Posts made by massynrt

Thank you for the reply- I tried it - Sort Of.

Maybe you can provide some ideas (or the math)..

Bascily I put a 1.3k ohm resistor (dont have 1kohm) between the FAN_Vin and the VAN_pwm(-). I then only connect the pwm signal. No ground to the PWM converter as the Duet and the PWM converter are powered by the same PSU, I suspect the grounds will technically be the same.

Results.. It works - Half way.

My FAN Vin is set to 24v (Input of the duet). And my pwm input is also set to 24v also on the PWM signal. If I measure the DC voltage over the PWM and ground (when at full speed) I get only 14v and not 24. The resulting Voltage after PWM conversion is only 5.5 or something, and not closer to 10.

Does the resistor cause a voltage drop or something? At least I'm starting to get some movement.

Hi guys - I think I've read every comment and doc on this topic and I still feel stupid. I'm building a new CNC machine with a Duet 2 Ethernet I have. The only PWM to 10V converter I can get in South Africa is the blue one that is not recommended to be used. As a side no I'm a noob. I learn by blowing stuff up. hehe.. Not reallly. Please forgive my ignorance. I'm just trying to understand and work with what I can get.

Few questions -

1. The posts says that it is not recommended to use the small blue PWM converter board, because 1. It is difficult to drive from some duet boards and the 2. the shared ground issue. My question is then if it is possible to use it, although difficult, how would i go about it?

2. Lets say I use FAN2 as the PWM output. On the duet board - If I look on the schematic, one pin is FAN_Vin and the other pin, normally the ground pin, is the PWM pin. Does this mean the pwm signal is pulsed on the ground pin. One pin is always 5v (if Vin is set to int 5v) , the other pin (ground/pwm) pulses from 0 to 5v and thus create the voltage difference for the PWM signal with Vin as the reference. Like an inverter PWM signal. If that is the case then I will understand why the blue board wont work.. the pulsed 5v (Pwm/Ground) pin from the duet will always be pulled to ground through the converter board.

Any help in understanding is appreciated.

Im building a new CNC machine and would like to use NPN proximity sensors for homing/endstops.

24v supply for the NPN Sensor. Will a simple voltage divider (10k and 68k) with resistors be ok on the output of the sensor. Feeding the divided voltage to the STP pin?

I think this was also on the documentation for the probe input. Will this also work for the endstops?

Rudi

Hi Guys - I have 2x Duet 2 Ethernet Versions available for sale - The one was in a 3d printer with not a lot of running time - The 2nd was part of a Ooznest Workbee CNC that I bought. I've went over to resin printing, and the workbee is now a plazma cutter running Mach4. Thus - If anyone are interested - Not sure how the shipping will work etc, (I'm in South Africa) but You can have both for the price of 1.
The Ooznest one will just need to be configured with the standard interface, as it has the workbee control screen.

This offer excludes shipping - And if shipped international there might be duties and taxes payable.

I also have 1 sealed connecter kit that was with the Duet 2. Still in the box with the cables. PM me if you would like some images

Hi. Im busy building a 100w co2 laser cutter. I need to be sure that Duet3 will be able to work as a controller as this machine will be used commercially in our shop.

I dont need all the detail at this point, i just need to make sure that the laser psu can be controlled. If possible the water cooler, air assist and extraction. Z level etc etc. then also software support like lightburn..

I use a duet2 in a 3dprinter and workbee and i love them. Would like to stay with Duet..

Please help/advise..

I have a 3d printer and a CNC router that uses a Duet 2 Ethernet Controller. I want to build an joystick input to move the the router. Basically to setup the job. This is not a problem for 3d printing, but CNC does require this ability. Typing in gcode to move around is way to time consuming.

So - I've read that a 2nd rasp-pi (or in my case I will use pic controller or Arduino) to interface the joystick to the panel due port of the duet. But..

I have a few questions. I'm no gcode expert so please help..

1. What I know from the basic G0 is that I set a WCS location. What Gcode can be used, if possible, to keep on moving until some other gcode is send. At a feed rate that is send as part of the gcode. Is there gode like that? I've scanned the doc but do not remember about something like that.. Is this something that can be added if it does not exist.

2. Is it possible to send the gcode from a PC - via ethernet - to the Deut. it would be much easier to program an application.. And plugin a game console.

3. Is anyone keen on assisting with developing something like this.. I would be a great addition to any Duet based CNC.

It has been fixed. Thanx a mil.

You need to configure the Z Endstop to use the Z-probe. You only configured the Probe.

Add this to your endstop section.

M574 Z1 S2 ; configure Z-probe endstop for low end on Z

I'm sure my config.g is fine for v3. I did do the changes

I've reconfigured a new Duet 2 Ethernet today. On the previous Maestro I could extrude filament on the web console. I've loaded the new RRF 3 that was release today, as well as the new web console. think it is 2.1?? Any case.. The extrusion control is disable. Normally when temp was reached it went active.. I think im missing something. How does the load filament work - What is the purpose?

Yes we worked out something to get going again.. Must say - I'm impressed with the support.. I know I started off a bit frustrated, but at the end i must admit.. I was wrong.. You guys are amazing.. @dc42 @droftarts Thank you for everything.

I got a test print finished with the new board.. Now to get the printer "perfect".

Thanks for all your help @droftarts. I got the Duet 2 up and running.. Busy with first test print..

2 Observations:

1. The prints are definitely slower. With the same config file, Except for the BL Touch config. The rest seems to stay the same from Maestro to Duet 2 .
2. The motors are quiter. Alot.. Printer just feels better..

Any idea why??

Might be something ooznest did with their config. I turning the white clips around.

Quick question.. the connectors for the motors are upside down vs the meastro. Thus, i have to redo them.. although the red blue green black is still the same.. .

What is the reason? Do i have to redo, or will it still work?

Sorry for my silly question.. I cant find R84. I looked at the whole pcb and could not find any problems. Even did a good old shock test while it was at operating temp. Does not reset. Almost certain it is not the button or a loose component.

I dont have any fancy tools to remove the.button. Only solder sucker and iron. But this will be last resort only after confirmation of warranty replacement as advised.

I will send you a pm with and alternative solution.

Here is an updated image of the CPU..

Sorry guys. That seem to be only jpg compression or Huawei playing tricks on us. None of those bridges on the cpu. Ill use my dslr to supply with better images. Will do it in the morning..

I've updated.. Don't know how I forgot to change that back. I copied/pasted so many times trying to fix this..

; Configuration file for Duet Maestro (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue Mar 31 2020 16:02:15 GMT+0200 (South Africa Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Cooper" ; set printer name

; Network
M552 P192.168.0.9 S1 ; enable network and set IP address
M553 P255.255.255.0 ; set netmask
M554 P192.168.0.1 ; set gateway
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E837.00 ; set steps per mm
M566 X800.00 Y800.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-115 Y-100 Z0 S1 ; set axis minima
M208 X115 Y120 Z300 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X9 Y-65 Z1.65 ; set Z probe trigger value, offset and trigger height
M557 X-100:100 Y-50:50 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M307 H0 A75.4 C81.7 D2.1 S1.00 V24.1 B0
M140 H0
; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0

; Fans

; Tools
M563 P0 S"Titan Aero" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

; Configuration file for Duet Maestro (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue Mar 31 2020 16:02:15 GMT+0200 (South Africa Standard Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Cooper" ; set printer name

; Network
M552 P192.168.0.9 S1 ; enable network and set IP address
M553 P255.255.255.0 ; set netmask
M554 P192.168.0.1 ; set gateway
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E837.00 ; set steps per mm
M566 X800.00 Y800.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-115 Y-100 Z0 S1 ; set axis minima
M208 X115 Y120 Z300 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch
M558 P9 C"zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X9 Y-65 Z1.65 ; set Z probe trigger value, offset and trigger height
M557 X-100:100 Y-50:50 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M307 H0 A75.4 C81.7 D2.1 V24.1 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 A554.4 C258.9 D5.7 V24.0 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

; Fans

; Tools
M563 P0 S"Titan Aero" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Custom settings are not defined

The printer did print a few prints fine. Just randomly started to reset.

Here is what I've done so far today.

1. I've rewired the printer completed. New connectors, new wires - No success.
2. I've moved the location of the board to the bottom frame, as to reduce vibrations - No success.
3. I've reformatted the sdcard - No success.
4. I've created new gcode, Cura, Slic3r, PrusaSlicer. Fast, Slow. High, Low, whatever.. - No success.
5. I've moved the X Limit switch from the gantry. - - No success.
6. I've added a fan on the Duet. - No success.

Observations:

1. Before the printer reset, the is definitely some weird printing going on... As if the g code is corrupt. I've noticed it on most of the fails.

2. I have a good success rate, printing "longer" moves.. Like a base plate. But as soon as the detail start, and "movement - I might go for a while, of crash quick..
   

I'm really tired/frustrated