Not related to 3D printers but I regularly heat large metal tubes at work and use many heaters. Up to 40 on a system and each one controlled independently. Each heater does have an effect on the others but usually it is minimal.
It might be a good idea to do that but it may also complicate the slicing setup.
I’m not sure if that was helpful or not.
@Phaedrux well I was able to get the bed cleared off and run my G32 (bed.g) which I added a link to my macro and after the macro I added the M500 P31 in the bed.g and that saved the offsets correctly. So that gets me a work around.
Luckily you are using thermocouples. If you wire them all together the actual voltage signal will average out. So if you just take all the +ve leads and connect together on the same +ve terminal and take the -ve leads to the same -terminal it will average out the three sensor readings. Its a pretty old school trick.
good luck.
What about just adding isolation mounts to the Nema23 motors. They are the source of the vibration so if you isolate them it should be greatly reduced.
what you are looking for is not PWM (pulse width modulation) you want FM (Frequency Modulation). I would suspect that the duet is not setup to use FM as it is not mentioned anywhere in the documentation. As Bearer said you can change the base frequency of the PWM and if you set the PWM to 50% and then changed the base frequency it might work to act like frequency modulation, but i doubt it. Give it a try, it can't hurt.
I do believe you can buy conversion hardware that will take a PWM signal and convert it to an FM signal.
It will likely be in this part of your config.g file.
G31 P25 X-31 Y0 Z0.6 ; set Z probe trigger value, offset and trigger height
M557 X20:215 Y20:215 S64 ; define mesh grid
Likely the X-31 is no longer accurate. With the probably area being X20-215 and a -31 offset it could still probe 11mm off the bed (I think). But those are the parameters that you need to adjust to get the probe back on the bed.
@Phaedrux maybe he has the same issue I had and it is interference with his stepper motors. It possible it was working for testing then he tried to print and now it doesn’t work? We can only guess.
@mrenz999 Try sending an M18 E0 command before you attempt to use the probe.
The reason that was happening it is was telling it to go to extruder position 2 from wherever it last was. If it is using absolute moves then that could be position 10000 or some other large number.
Looking at the GCode that S3D generates it seems to use absolute positions but every feature or so it sends an G92 E0 which essentially resets the counter.
Another way to do your end script would be to
G92 E0
G1 E-2
@fcwilt That is good to know. I will grab a meter and check that voltage level of that switch.
@lukas-aurarum try adjusting the H value in you M558 command that sets up the probe. I think default is 5mm. The z axis will travel an equal distance in the negative direction as the H value. So it will move 10mm before it gives up with the default of 5mm.
@fcwilt That is good to know. I will grab a meter and check that voltage level of that switch.
@alankilian But The LED beside the stepper motor jack lights up for either of the E0 or the E1 stops, so even if they are different internally, both still seem to recognize the signal at least via the hardware. it is very strange I think. Thanks though.
Yeah there must be an issue with the board I have because connected to e1stop, the filament sensor works fine. What the heck.
Oddly, I changed the port to use the E1stop and also moved the D0 to the end of the line and it works properly now.
So is there an issue with the board, or is there a resistor issue as stated by @fcwilt .
M591 P2 C"e1stop" S1 D0 ; filament monitor connected to E0 endstop
Hello I'm having some issues trying to get a filament runout sensor working on my duet 2 wifi with RR3.2. I've added the following line into my config.g as it should be a 2=simple sensor (low signal when filament present) but as soon as my start.g finishes running I get a pop up on the DWC that the print has paused because of no filament.
M591 D0 P2 C"e0_stop" S1 ; filament monitor connected to E0 endstop
So I then tried a P1 But that trips the filament sensor before the Start.g even runs or at least at the very same time.
M591 D0 P1 C"e0_stop" S1 ; filament monitor connected to E0 endstop
I'm pretty sure the wiring is correct and when I tested the switch with a piece of filament I see that the E0 stop light on the board is funcitoning when I add or remove filament. When the filament is in the switch the E0 light is illuminated, when I remove the filament it is off. I have also tried the C"e0stop" as well as C"e0_stop" as I have seen documentation for both but there is not change in functionality.
Here is my Config.g
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.10 on Sun Dec 20 2020 17:43:31 GMT-0600 (Central Standard Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Ender 5 Pro" ; set printer name
; Network
M552 S1 ; enable network
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 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X32 Y32 Z32 E32 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z1600.00 E276.00 ; set steps per mm
M566 X900.00 Y900.00 Z300.00 E400.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z1200.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z50.00 E250.00 ; set accelerations (mm/s^2)
M906 X500 Y800 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X-110 Y-110 Z-8 S1 ; set axis minima
M208 X110 Y110 Z506 S0 ; set axis maxima
; Endstops
M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S3 ; configure motor stall for Z max
M915 Z S2 F1 H200 R0 ; configure stall detection
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F300 T9000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-42.5 Y-8.00 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X-105:65 Y-105:65 S34 ; define mesh grid
; Filament sensor
M591 D0 P1 C"e0_stop" S1 ; filament monitor connected to E0 endstop
; 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
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
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
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
;Virtual Heaters
M308 S4 Y"mcu-temp" A"MCU" ; create mcu temperature
M308 S5 Y"drivers" A"Stepper driver" ; create driver temperature
; Fans
M950 F0 C"fan0" Q50 ; create fan 0 on pin fan0 and set its frequency Board cooling fan
M106 P0 L50 T30:45 H4:5 ; set fan 0 value. Thermostatic control is turned on proportional to the mcu temp
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency Part cooling fan
M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency Heat break fan
M106 P2 S0 H1 T45 ; set fan 2 value. Thermostatic control is turned on
; Tools
M563 P0 D0 H1 F1 ; 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
; Miscellaneous
M572 D0 S0.05 ; Set pressure advance
M501 ; load saved parameters from non-volatile memory
M911 S23 R24 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool
@Phaedrux Sorry it has been awhile, I don't think I ever did delete those tool change files, but the second layer jump seems to have been resolved.
I don’t think I can. It’s one of those eeros from Amazon. Not much I can do without the subscription.
So I have a Duet 2 Wifi and it is connected to my home network. It doesn’t have a static ip therefore dynamic and assigned by my router. So I have managed to figure out that I can find my printer (duet) by its name with a / at the end using Chrome as the web browser. I can’t however, seem to use the same method with safari on my phone or chrome.
Am I doing something wrong or does a phone just not naturally look to local resources before looking to the internet?
Thanks for any help. Thanks
@deckingman that’s a good point but for those of us running big printers I’m usually above 1mm/s so it would t be a problem for me and likely others.