I've done my bearing up tight - I wanted to make sure it wouldn't slip, as I had it right at the end of the slot - and the bearing rotates freely. I did make sure to put the washer the right way round (the side that bulges in the middle towards the bearing), and I also added a shakeproof washer between the plain washer and the printed part, to make sure it didn't slip against the plastic. But I'vby dc42 - Ormerod
I thnk that makes three of us - trevor51 has just reported what sounds like the same problem. Ian, I think you need to either supply faster SD cards, or change the firmware to allow the SD card more startup time.by dc42 - Ormerod
Looks like you have the same problem I had, which is that config.g is not running at startup. Workaround: press the Reset button on the Duet before trying to connect Pronterface. Fix: ditch the SD card that came with the kit and substitute a decent one (I used a Maplin own-brand 4Gb class 10 card).by dc42 - Ormerod
Sounds like your config.g file may not be running at startup. I had the same problem. If I pressed the Reset button on the Duet, config.g did get run. I fixed the problem by ditching the SD card that came with the kit and substituting a Maplin 4Gb Class 10 SD card. However, without config.g running, Pronterface didn't regard the printer as online and so couldn't connect (the precompiled Windows vby dc42 - Ormerod
Is the Z sensor turned on? This is normally done by the M558 P1 command in config.g.by dc42 - Ormerod
Success! I changed those resistors, and the sensor is much less sensitive to ambient light. I even reinstated the 50W halogen bulb in the ceiling above the Ormerod, and it only increases the reading by about 15. The highest reading I get is now about 770 at 0mm and it drops to 448 at 1mm. So it's just about clear of the saturation region. I'll calibrate at 1mm or just a little higher. I had to aby dc42 - Ormerod
I'm finding that my proximity sensor is VERY sensitive to ambient light. I already mentioned in another post that when I had a 50W halogen bulb in the ceiling above, I couldn't make it work at all. Now I'm finding that I can't set up parameters that will reliably do the z-homing, because even the sunlight coming through the window is giving quite high readings. What I really want to do is modulaby dc42 - Ormerod
Out of curiosity, what is the change to the z-nut trap? I'm using the new x-rib and x-plate with the old trap adjusted to fit.by dc42 - Ormerod
I haven't done any prints yet, but there is a huge amount of backwash from the fan on my Omerod, so much so that I thought I must have connected it the wrong way round. But I checked and it is rotating the right way to blow air through the heatsink. So I can quite believe that backwash from the fan is cooling the print too much.by dc42 - Ormerod
I agree, a 10mm bearing would have been better - I wouldn't have had to elongate the slot and the nut trap as much.by dc42 - Ormerod
Hi tru168, Thanks, however that doesn't address the problem. I already have the Ethernet and SD libraries. The SD header file you linked to on github looks the same as the one I already have, and has the same references to sam.h and undefined types U8, S8 etc. The Ethernet library you linked to still doesn't have the file Ethernet_sam.h. I found there is a file called sam.h in the Arduino core,by dc42 - Ormerod
Ian, thanks for your feedback. I've ordered some 250x250x1.5mm alu sheet from eBay, and I'll visit my local glazier tomorrow. In the meantime I'll commission my printer by taping the print surface down as you suggest.by dc42 - Ormerod
Hi Treth, I'm not trying to update my firmware to latest (I've already done that), I'm interested in modifying it so that I can solve the problem that I (and others) have of the IR sensor being too sensitive to ambient lighting conditions.by dc42 - Ormerod
I agree, moving the Z axis and setting it up at a right angle is a pain. However, another benefit for me of moving it was that the print head range is now exactly from one end of the glass plate to the other.by dc42 - Ormerod
I've now managed to stop the print head sagging. The main problem was that the nut trap in the X runner wasn't flat, so when the bearing screw was tightened, the screw tended to move towards the outside of the runner. In the end I had to use a 3mm drill to elongate the slot, and a 2.5mm drill and knife to rework the nut trap. With the screw up against the end of the newly-elongated slot, and afteby dc42 - Ormerod
Thanks, Treth! Either I missed the bit about the slot, or it wasn't in the documentation a week ago when I assembled the runner. I'll take it apart and elongate the slot if necessary.by dc42 - Ormerod
Further to my earlier message: - When I said "X idler bearing" in my previous post, I should have said "X runner bearing". - Looking at it closely, I can see that only the very top of the runner bearing makes contact with the X-plate, confirming my suspicion that the main problem is that the runner bearing is mounted too far away from the X-plate. - If I insert a 1mm thick steel rule between tby dc42 - Ormerod
I'm finding that the bottom of the fan assembly is fouling on the foldback clips that hold the glass plate on the heated bed. So I dare not try printing anything, or testing the automatic bed compensation, because any attempt to home the head or move it between the compensation points when it is lowered will result in a crash. It looks to me that the problem stems from two causes: 1. The X-idleby dc42 - Ormerod
My SD card problem (failing to run config.g at power on) did not appear to be related to low voltage either. I measured 4.97V on the 5V rail.by dc42 - Ormerod
I'm trying to rebuild the Duet firmware so that I can sort out the problem with the IR sensor. I've downloaded the firmware source from and also installed all the libraries at as mentioned in the README file. But when I try to built it under Arduino 1.5.5 I get a lot of errors, starting with:: In file included from /Platform.h:2, from /RepRapFirmware.h:52, froby dc42 - Ormerod
I bought a Maplin 4Gb Class 10 SDHC card today to use in place of the one supplied, and that has fixed the problem of the Duet not executing config.g on power up. In summary, the problems I had commissioning were due to two issues: 1. The SD card supplied takes longer to be ready after power up than the firmware allows for. 2. Too much ambient light (especially incandescent light) prevents thby dc42 - Ormerod
OK, thanks for that. I don't have any other issues with the board. USB is working, and Ethernet works provided that I don't connect with Pronterface over USB first - but I guess that is a software issue. So I might fix it myself, depending on how annoying the need for USB power gets.by dc42 - Ormerod
I'm aware that as the owner of an early Duet board with two resistors incorrectly mounted, I can return the board for a replacement. But RepRapPro is now closed until next year. What is the policy on owners who have previous experience of SMD soldering attempting to desolder and resolder the resistors themselves?by dc42 - Ormerod
I came across this too. The instructions originally said 205mm/125mm and that is what I used. When I came to commission the unit, I found that the hot end fan did not clear the main electronics box when the carriage was lowered, even with the electronics box positioned as close to the Y motor as possible. Part of the problem is that the fan supplied to me does not have the recesses for the screwsby dc42 - Ormerod
Hi tru168, I don't think a Hall sensor would work well here. The point of the IR sensor is to allow bed plane compensation to be done by probing the 4 corners of the bed. If you used a Hall sensor, you would need to use 4 magnets under the corners of the bed, and you would have to set the coordinates it uses to place the head very accurately over them. I think the solution is to modulate the IR Lby dc42 - Ormerod
Hi Treth, I'm running my Ormerod connected to my laptop, which is wirelessly connected to my router. To get the laptop talking to the Ormerod via Ethernet, I had to bridge the wired and wireless network adapters, so that both can use the same subnet i.e. 192.168.1.x. Bridging the network adapters under Windows is very easy, you just open the network adapters page in Control Panel, highlight bothby dc42 - Ormerod
I just found why the proximity sensor wasn't working. I sent G31 commands to get the proximity sensor readings. With the head in the middle of the bed and a long way from it, I was getting a reading of 844, and it was very sensitive to anything (e.g. my hand) that I placed under it, even if not very close to the sensor. The Ormerod is on a table with a 50W halogen bulb in the ceiling above. I turby dc42 - Ormerod
I've just bench-tested the proximity sensor, applying +5V to the leftmost pin (the one with the pink wire on the photo), ground to the centre pin, and looking at the voltage on the 3rd pin on a scope. It seems to be working fine. Output is close to ground initially, rising to beyond 4V when I hold a reflective foil surface close enough to the sensor.by dc42 - Ormerod
Hi Markus, thanks for your response. I don't think the X-axis homing problem is down to lack of reflective tape. When I try to home the X axis, it doesn't move at all. When I try to home the Z axis, it drops the head a few mm and stops. I think the problem is that I had the sensor board connections the wrong way round. I've just traced the circuit, and the only component I found on the proximityby dc42 - Ormerod
I got exactly the same thing. I think the commissioning instructions are wrong and you should only get the temperature error messages if the thermistors are not connected. A little later on the commissioning instructions tell you to connect to the Duet using Pronterface, and to expect *correct* temperature readings.by dc42 - Ormerod