Quotetim_h I found I was able to snap off the clips quite cleanly. Just bend them in and out a few times and they will break at the corner. Yes, I did that too, then I gently filed off the sharp edges where the clips broke off, taking care that the filings fell away from the board. The back cover just fits now. QuoteThe thick white power cable with the 4 crimps on them will not fit through theby dc42 - Ormerod
Mark, have you checked that your x-plate is flat? If you are using the original x-rib and x-plate supplied in the early kits, I found that I had to file down one of the tabs in the x-rib, otherwise the x-plate was forced to bend. The rod is clamped against the acrylic at both ends, so the horizontal spacing between the ground rod and the x-plats bearing surface should surely be constant along itsby dc42 - Ormerod
Radian, the damping factor is still much greater in my scope trace than in your simulation. I think the ringing frequency is similar, although it's a it hard to tell the frequency on your simulation trace because of the horizontal scale. So I think the inductance of my bed + cable is much less than in your model, and the capacitance much greater. I don't think the ribbon cable has anything like 1by dc42 - Ormerod
If you have a DMM, you can check the voltage across the sensor pins at the bottom of the board. There should be nearly 3.3V between the leftmost pair of pins, falling to 1V or even less when the sensor is close to a reflecting surface. There should be a constant voltage of about 1.2V between the rightmost pair of pins.by dc42 - Ormerod
I'm now using Simon's nozzle mount design too. I also reprinted my x-carriage, as I was never happy with the original one. I had to enlarge out the 3/4-holes so that I could feed the countersunk screw heads through them, and also the slot for the brass Bowden end (I had to do that on the original part too). I forgot to print it almost solid, so it has a fill factor of 0.5. Nevertheless, it isby dc42 - Ormerod
I printed markbee's design and fitted it: I had originally planned to so a similar design which uses countersunk screws to hold it on the fan, but the clips on markbee's design are adequate. The two holes fit over the heads of the cap screws just fine. I can feel that the backwash is being diverted upwards. Thanks, markbee!by dc42 - Ormerod
Hi Chris, thanks for the feedback. I'm glad to hear that the change has helped someone else. That gives me more confidence to submit the changes via github. I find that following a reset with both Ethernet and USB connected, I can connect to the Duet via the Arduino serial monitor first, and then Ethernet, without difficulty (or vice versa). That's how I debugged the network issue. However, seveby dc42 - Ormerod
Radian, thanks for doing those. They are interesting, but the one with 100 ohm gate resistor is very different from the trace I captured here (4th photo down). Even though LTspice isn't modelling avalanching, the ringing that I observe is much more heavily damped than in your simulation. Some possible contributions to the difference are: - From the first of my traces, I calculate the inductanceby dc42 - Ormerod
Can you run a simulation with just the gate resistor too? Preferably with 100 ohms (which is what I used) and also with 200 ohms. PS - it would also be good to get the mosfet drain current from the simulation. I estimate that the capacitor discharge current is about 6A peak, using 1uF.by dc42 - Ormerod
The bed plane compensation seems to work reasonably well if there is very little backlash in the z-axis system. If there is significant backlash, it makes things worse, as I found out when my z-system had extra backlash of about 1/10 rotation, or about 0.08mm. I agree that it is best to mechanically adjust the bed to be reasonably flat in the first instance.by dc42 - Ormerod
Somewhat less expensive is this range. I've recently ordered the 25A version.by dc42 - Ormerod
Radian, thanks for separating this topic out, it needed doing. My main comment on that is that there are actually two potential problems caused by the rapid mosfet turn-off: 1. Back emf as you describe, possibly leading to interference with other signals on or reaching the Duet board, by capacitance, induction, or radiation. 2. A spike on the +12V line due to the sudden reduction in current draby dc42 - Ormerod
That's a solution very much in the spirit of Reprap! I found there were 2 causes of hotend sag: 1. Initial sag was caused by too much play between the x-runner bearing and the x-plate. Fixed by fettling out the slot and nut trap, and then installing a 10mm bearing. I bought a cheap pack of ten 623zz bearings via eBay UK for £2.98 inc carriage and the bearing is working fine so far. 2. Later onby dc42 - Ormerod
OK, your laptop IP address is 192.168.1.66 and your gateway (router address) is 192.168.1.254. First, pick an IP address on the same subnet for the Ormerod, one that is unlikely to be already in use. I suggest 192.168.1.150. Second, edit config.sys on the sd card to set the IP address of the Ormerod to that, and also set the gateway address to the address of your router. Third, by "direct connby dc42 - Ormerod
Thanks for trying! I guess the problem you are experiencing is not the same as the one I was.by dc42 - Ormerod
Sure! Please tell us how will you be connecting the printer: direct to your router, or to a computer that is wirelessly connected to your router, or some other way? Also go to a command shell, run ipconfig, and post the results.by dc42 - Ormerod
Have you tried changing the "Extrusion factor" in slic3r? I find that even at 0.24mm, a value of 0.95 gives me better prints than the default 1.0.by dc42 - Ormerod
Hi Dennis, QuoteDennisCowdery I have seen values of 1uF mentioned. If people are putting this across their FET then they will put a big transient load on the FET on turn on (I have popped them in the past this way), they will also inject current into the PCB I was initially horrified when I heard of a 1uF capacitor being connected across the FET. However, the turn on time of the FET is quite slby dc42 - Ormerod
While on the subject of securing the looms, here is a suggestion - not for the product documentation but for the wiring looms themselves. I was unhappy with the connections to the Duet being pulled in different directions when the x-carriage rises and falls. So I was delighted to find that the printed part at the base of the z-axis has holes for a cable tie. Unfortunately, when I tied the loom atby dc42 - Ormerod
Hi Ian, I'd be happy to submit my changes via github (that would be easier than posting diffs). But I'm not comfortable with submitting changes to the code that interacts with the network interface when I know that the network interface code (LWIP library) in the RRP firmware releases is not the same as found here. My changes might be incompatible with your changes to LWIP. It may be that Adrianby dc42 - Ormerod
I've rebuilt the firmware starting from the 0.50 source, and further amended the error recovery. The pointer mismatch messages are gone and it works reliably for me. This is when using a machine that previously would connect only 1 time in about 30, and if it failed the first time, required a reset of the Duet board before it would give any sort of response to further connection attempts. Afterby dc42 - Ormerod
What happened is that my z-driven gear was off-centre, so I printed a new part. The new part was a tighter fit with the z-gear than the old, but I thought it was OK and would loosen up. In fact it became tighter, to the extent that at one point in its rotation, it was quite stiff to rotate. I think that is what caused the wear on the flat on the z-gear, leading to the backlash. I reinstated theby dc42 - Ormerod
Hi Treth, which spike are you talking about? If you mean the spike on the mosfet drain, I really don't think it's a problem as regards reliability and operation of the board. If you mean the spike on the +12V rail, then I agree that this is a problem. Some possible fixes are: 1. Add capacitors on the +12V input, as close to the Duet board as possible. This is my least-preferred solution, and onby dc42 - Ormerod
Ash, it sounds like you may need to turn the washer next to the bearing around. The face with sharp edges should be away from the bearing. If that doesn't work and there is room, substitute a 623ZZ bearing for the existing 9mm one.by dc42 - Ormerod
If it's not reading network config from SD card, change the SD card for a better one - it's a known problem that I and several others have had. I haven't touched that area of the code, and the firmware I built is working for me, using the address I have configured in config.g. I have now found that I can still get into the state of the card being stuck at the password screen if I try disconnectiby dc42 - Ormerod
What happens if you press the Submit button again, or close that browser tab and open another - do you see any further network traffic?by dc42 - Ormerod
Quotedsred294 I normally had debug switched off on the standard firmware. But I presume you were not able to connect, otherwise you wouldn't have tried my modified firmware? And by "stuck at login screen", you mean at the password prompt?by dc42 - Ormerod
I get the pointer mismatch messages too. They are from some existing code that I don't understand yet. After the 'password right' message, you should get the main screen and can click on the Control tab. I am using the SD card files from the Duet branch of the github repository. Were you already getting the 'password right' messages with the standard firmware?by dc42 - Ormerod
Ian, I think we have established fairly definitively that his IR sensor is not emitting light even though power is reaching the board. He's getting 3.2V across the sensor receiver pins (correct), and 0V across the transmit pins (should be 1.2V).by dc42 - Ormerod
I've been looking at the unreliable Ethernet connection. The main problem I found is that after a network error occurs, it doesn't attempt any sort of recovery. As a result, it won't accept a new connection attempt. On the first connection attempt, a network error often occurs (I haven't found out why yet). The attached firmware file contains a fix that works for me. I can close the browser andby dc42 - Ormerod