Posts made by ockray83

@fred-y
It looks like the m950 command isn't supported by my board's current firmware (2.05.1). I haven't updated this thing in a long time. I'll have to go through the update and see how it does with the commands you've provided.

@uk25

Its been a while since I've been able to mess with my printers, sorry for the delay. I got the new switch from MakerHive installed and my control has not really improved. I get a small 'controllable window' within the S0-S255 range which I can shift with frequency changes, but nothing I've done has widened the span of that window. Anything below the controllable range results in the offensive buzzing sound with little to no output of air from the pump. Anything above the controllable range results in no change in output (S200-S255 may output the same amount of air, for example). I also installed a diode across the terminals as recommended in other forum posts, with no change in performance. If you figured your issue out, please let me know as I am out of ideas to make this work.

@o_lampe The jumper is in the Vin position.
The MOSFet is identified as F5305S
The coupler appears to be an EL817
I'm not certain if that helps at all.

It looks like makerhive sells all their berd air kits with these switch boards now. If this were a common issue I think I would find it in forum posts somewhere. Maybe I have a defective board/pump?

Side note, I did try running a print at 100% speed, just to see what happened and I noticed that while the heated bed output light was illuminated, I got a slight change in pitch from the pump and checking with a meter, the power going to the pump was dropping off by .08vdc and rising back again once the light was out. At the moment the two are sharing the same PSU.

Update: makerhive got back to me and are sending me a new switch, they believe mine is defective. I should get it in a few days.

It's meant to protect the control board by isolating the fan pwm cconnection from the pump circuit. The ez switch has connections from the psu to the pump on one side and on the other side it takes in a 2 pin 12-24v fan signal from the controller

I recently bought a berd air kit from makerhive to install on my delta printer with a duet 2 wifi. I bought the extra "ez switch" they sell as well, to isolate & protect the duet from the pump. I have everything wired and plumbed and at 100% I'm blown away (no pun intended) at the amount of air this thing pushes through that little cooling ring.

The problem is, I can't seem to control the speeds in between 0 and 100% very well.
Initially I had an awful noise from the pump at anything below about 80%.
After researching this on the forum a bit, I saw people had to change their frequency to the 25k range to get better performance and reduced noise, so I tried that. Now the awful noise is gone, but I don't seem to get a change in the pumps output unless I make a drastic change (more than 50% shift). I've also tried various other frequencies with varying thresholds of poor response and awful noise.

I saw a bunch of berd air posts while researching this, but none that involved the e-z switch I'm using. I'm wondering if the switch is expecting a fan input with switching occurring on the positive lead, while I believe the duet switches the negative pin. Would m106 i1 switch pwm to the positive pin?

For reference, this is an example of the switch, makerhives web page seems broken right now
https://www.kis3d.de/en/products/mosfet-modul-berd-air-e-z-switch-pwm-controller

It has been a couple of weeks since I moved the router closer to my printer. I am happy to say that after moving the router to within about a 6ft line of sight with my printer, I have been enjoying DWC undisturbed by constant dropouts, save for one instance today, which I believe I can attribute to mistakenly trying to upload a g-code file into the job list via Slicer while another print was in progress.

I had enough confidence in the system's stability now that I invested in a smart effector & rods for the printer as well and I couldn't be happier with the result.

Thank you to everyone that replied and helped out a new user struggling. When I get around to building a second printer, I know what board I'm putting in it.

Most of the time it seems to be in the mid to high 60's. Moving the printer upstairs to get it closer to the router really isn't an option (cats like the printer too much), but I should be able to move the router downstairs closer to the printer. I'll try that next.

I haven't been able to update the homing files yet, as I have not been able to successfully connect to DWC today. It looks like the issue is still going on after the firmware update.

That applies to delta printers as well?

I am still experiencing disconnects (just had one). I also have network errors when trying to upload g-code files or update my config file, which causes it to disappear from the system and needs to be manually uploaded via sd card. I'm also getting several new errors in the lower right hand corner of the screen when I start up the printer and press home:

I've just updated the duet, I will see how stable the connection remains and report back.

Sorry for the delay, i've been sick the past couple days and hadn't made it back into the workshop.

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 2.02(RTOS) (2018-12-24b1)
WiFi Server Version: 1.23
Web Interface Version: 1.22.6

I've been able to connect via YAT when i lose DWC connection. The connection seems stable so far this morning, I haven't been disconnected yet and I've been on for about 30 minutes so far.

I'm reaching a peak of frustration with the disconnecting issue. It seems like its happening more frequently. I'm trying to change some settings to improve the printer's accuracy and I cannot stay connected to DWC for more than five seconds at a time before getting an error message that says request time out.

I cannot keep my printer going with an interface that behaves like this. Can anyone please help me?

Wi-fi. My printer is in my shop in the basement, my router is on the 1st floor, maybe 10ft away from the printer's location.

EDIT: So much for my theory on long prints being related to disconnects. I'm in the middle of a 2 hour print and I've lost DWC again.

I've had a couple of short prints in which I can maintain DWC access, but anything longer than about 4 hours ends up disconnecting.

With the short prints, the head retracts to the home position as it should at the end of a print.

Any time a print results in a disconnect from DWC, it will still freeze at the end of the print. This is very irritating as I'm usually left with a blob of drool on the top of my print if I'm not there to intervene right when the print finishes.

I'm really at a loss as to why loss of DWC access would result in the printer freezing up at the completion of a job.

Any input or assistance is greatly appreciated.

M122 report:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6J9FA-3S86J-TARZG
Used output buffers: 3 of 20 (10 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98620 of which 0 recycled
Exception stack ram used: 432
Never used ram: 6496
Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3788) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 02:29:51 ago, cause: software
Last software reset at 2020-05-09 10:59, reason: Stuck in spin loop, spinning module GCodes, available RAM 6268 bytes (slot 2)
Software reset code 0x4043 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20001efc Task 0x5754454e
Stack: 00443523 00446ee6 21000000 dc000000 4153df1c 00000000 00000000 434b3217 436a1fe6 bdb81c00 4893afd1 cb295ff9 422b1a1b 00000000 476c1e00 37d33333 3f800000 60000000 411fcb61 20000010 00000004 00000000 00000004
Error status: 8
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 39.6, current 42.9, max 44.6
Supply voltage: min 12.6, current 12.9, max 13.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/1023
Driver 1: ok, SG min/max 0/1023
Driver 2: ok, SG min/max 0/608
Driver 3: ok, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Date/time: 2020-05-09 13:30:07
Cache data hit count 4294967295
Slowest loop: 342.01ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 121, MinFreeDm: 120, MaxWait: 509865ms, Underruns: 0, 0
Scheduled moves: 105415, completed moves: 105385
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Stack records: 1 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is doing "G1 X13.922 Y-3.572 E25.24059" in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.61ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8

• WiFi -
  Network state is running
  WiFi module is connected to access point
  Failed messages: pending 0, notready 0, noresp 0
  WiFi firmware version 1.23
  WiFi MAC address 60:01:94:73:5b:e9
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 25240
  WiFi IP address 10.0.0.17
  WiFi signal strength -71dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0

EDIT: The router isn't responding to the duet again. Same as before, started a print, able to use DWC for a while, then the same error connection reset page as before.

Upon print finish (different file this time) the printer froze again and I could not command it to do anything until I pressed the red stop button. it then reset and would go to home.

M552 shows it is connected to the network. Cycling S0, S1 doesn't seem to do anything as it still shows connected to the network after sending S0 and after sending S1. I'm still unable to connect to DWC.

The duet now seems to freeze up after every completed print and will not move until it reboots. What should I try next?

I was waiting for my print to finish before trying anything. I just watched it finish and for some reason instead of the head moving upwards to the home position, it just stopped slightly above the end point and all function froze. (I printed a copy of this same G-code file before and it finished with a return to home as intended.) The system reset itself and I was able to connect to DWC again. I'm guessing this is because the connection was re-established upon reboot. Still leaves the question as to why it stopped like it did.

I love this board, but I'm not sure whats going on with all these little oddities lately.

The blue LED is lit, M552 shows it is connected to my network.

I seem to have developed another problem. I started a print after I was able to use DWC again. The print has been running overnight and I used DWC several times to check the progress throughout the evening. Now when I try to connect to DWC again, I am getting another error "this site can't be reached. The connection was reset". My printer is still running the same job, nothing changed but the time of day, but I'm back in the boat I was before, unable to use DWC.

Any ideas on what to try next?

That worked! Thank you for your help. My delta is back up and running.