Topics created by ronnien59

Solved!! it is working Thanks

That has solved the problem. I can now start to calibrate. Thanks so very much for the help. I thought i had changed it and then changed it back for some reason.

that's exactly what I did so that I can just hit the button on the web control rather than using the dropdown, you could of course add the M557 into bed.g and remove from config.g for convenience as well.

The Auto Bed Compensation button on the Control page of DWC 1.15a has a drop down menu next to it that includes the option to display the height map.

Problem solved, reformatting the SD card fixed the problem.
thanks again DC

Well now have my probe running off of 24VDC. R1 15K and R2 2.2K 3VDC out put.

I had similar problems with getting my second SD card to work when I first hooked it up. I do want to say up front that I am not using the SD card socket on the panel due as it was not in a convenient location given the way I ended up designing the enclosure for my Lcd, I have a external SD card slot breakout board. Nevertheless I do think what I did may help. From my looking into this issue this most recent go around and with my last 3d printer where I had similar issues, I found that the problem was ribbon cable length. It wasn't so much that it was too long, its was more about it being the correct length in the range of the length I needed for my application. From what I have read online it's something along the lines of signal reflection or something like that I think is was is happening. Both times I ended up shorting the cable by about 10mm and then it worked properly. If your are able to crimp ribbon cables give it a go and see if it works, you may need to shorten it a couple of times to get it working.
As a side note I saw an app note from a manufacturer, can't remember which one, that said for long length spi communications differental signaling should be used, the same type as rs422. That would require an active converter ic at each end of the cable, maybe some day I will get around to designing a board and try it out.

@dc42:

At the very least you need to change the B vale in the M305 command to suit the Epcos thermistor. Find its datasheet (it may be this one http://media.digikey.com/pdf/Data%20Sheets/Epcos%20PDFs/B57540.pdf)) and use the config tool at https://configurator.reprapfirmware.org/ to work out its B value, and optionally its C value too if you are using firmware 1.17.

Thanks, I will apply the new settings and try that.

Did you get this sorted? I'm having a similar problem on a cartesian and I'm wondering if they are related, perhaps.

https://www.duet3d.com/forum/thread.php?id=4026

Richard

@dc42:

See e.g. http://www.douglaskrantz.com/ElecFlybackDiode.html. Note, the diode will also slow down the action of the relay releasing, which may lead to more arcing of the contacts. The diode rating should be at least as high as the relay coil current. A 1A diode such as 1N4001 should be more than adequate.

It is funny that you pointed to the very website I went to earlier. I have talked with my electrical engineer at work and we have a diode terminal block that will fit the bill. I plan to use it on the positive lead.
Thanks again for all your help

Version 1.15c of PanelDue firmware is current.

@dc42:

The Z probe input of the Duet WiFi is protected against over voltage, but if you are using resistors to reduce the output voltage of the sensor then I recommend you adjust them to limit the voltage to 3.3V or less. See https://duet3d.com/wiki/Connecting_a_Z_probe#PNP_output_normally-open_inductive_or_capacitive_sensor if it is a PNP output sensor.

Thanks , I will adjust my resistors accordingly.

They are moving smooth. Took some calibration to get it right. So far everything i have printed has looked fine, The part I was printing fits quite nice.

@dc42:

Those warning messaged suggest that either you have a bad USB cable or connector, or more likely that the PC or laptop you have connected the Duet to can't supply enough 5V current when you enable WiFi. Try providing external power to the Duet or using a powered USB hub.

It happened while I had power on the DuetWiFi and connected thru the USB cable. This only happens when I am updating the DuetWiFi. Once I get thru the updating, it never happens again.

Let's chat more about this over email.

Thanks for the gcode. I will investigate this later this week.

@Guyaros:

Hi Ron,

I'm also using Cobra metal extruder.

Try these settings:
M906 X1000 Y1000 Z800 E1000 ; Set motor currents (mA)
M201 X800 Y800 Z15 E300 ; Accelerations (mm/s^2)
M203 X15000 Y15000 Z500 E2400 ; Maximum speeds (mm/min)
M566 X600 Y600 Z30 E120 ; Minimum speeds mm/minute

Thanks for the setting, my problem was wiring, most steppers I use it is a simple wire to wire ,however this stepper required a specific order. Once I figured it out it worked fine.
For us newbies it is nice to be able to find help

I put the 1.16 firmware as well as the latest web and server. when I went to run the M997 all went well at least one solved.

Thanks for the help