Closed ghost closed 10 years ago
Hi. I really need more information than this. I guess you mean you have updated to 0.78a? And your proximity probe was working correctly on older firmware? Have you changed any settings in config.g? Check that the probe is working correctly first; see the commissioning and troubleshooting sections of the instructions. We have just noticed that the proximity probe values have been set incorrectly as G31 Z0.8 P600. The default value should be G31 Z2 P300 to leave it high above the bed; this will be changed. The 'P' value is also used in the X axis homing, as the trigger value. If you have not done it already, you need to put a piece of paper/adhesive label, like you use on the bed, on the tab on the X motor mount, so the sensor has a better target. Let me know if that helps.
Ian RepRapPro tech support
Hi Ian! Thanks for the fast reply. Yes, I updated to 0.78a. Yes, the sensor worked with 0.65 or something like this. I don't know which firmware it was because I deleted the files. No I didn't change anything in config.g. I just noticed that the maximum value of the probe is about 388 when I'm about 0.1mm above the bed and when I'm above 4cm above the bed the sensor shows 275. SD-Card is working well. The white piece of paper is already attached on the motor mount. Do you have an Idea why the sensor send such weird values? This wasn't there with the old firmware.
If you have updated from earlier firmware, you need to move the pin the proximity sensor is connected to. It has changed between 0.65 and 0.78. See the 'NOTE' and updated wiring diagram here: https://reprappro.com/documentation/ormerod/wiring/#Wiring_the_Duet We do try and let people know about these kind of changes, via our blog, the forum and notes in the instructions, but perhaps we should have a readme/text document in the firmware folder too.
Ian RepRapPro tech support
That was the solution. I didn't notice that the pin has changed because I only opened github and checked the version. Thank you for your help!
Great! Feel free to close this issue...
Ian RepRapPro tech support
I updated the firmware today and now when I want to home the x-axis the hot end crashes into the threading rod. I updated the firmware on ormerod itself and use the sd-files 1. It looks like if the IR sensor don't switch.