Topics created by Quadcells

@cosmowave thanks again.
I did implement R-1 and that seemed to work just fine.
Once I did that I disassembled the filament sensor and added just a very small drop of med thick ca on the TAC switch to add a little height to help remove some space between the TAC switch and the 6mm bb that pushes on the switch when filament goes thru the tube.

@quadcells followed the instructions for motion. I now have live video working and on the DWC .
Thanks

@phaedrux thank you for the reply.

Yup it will contain the most recent stable release, whatever that is at the time.

@oliof thanks, that will work.

I swapped Y and E1 to help with the heat, I redesigned my Duet Wifi and Duex5 mounting brackets so that a 40mm x 40mm x 10mm fan mounting at one end of the control boards so that the fan is half below and half above the Duet boards and air flows across the drivers per dc42's suggestion. I also added heatsinks on the drivers and align them so the fins of the heatsinks allow air to flow unrestricted.
I have completed 4 30 hour prints without any over heat warnings.
Thanks for your help and saving me $$.
Some day I'll switch to Duet 3.

@Quadcells it’s possible this is related to other reports of connection failures due to a bug in the ESP SDK. It's on @dc42’s list to do a new wifi server using the newer expressiv SDK, but it's not a quick job. You’ve found the workaround already!

I liked @bondus reply here for why these things happen: https://forum.duet3d.com/post/139288

Ian

User error.
Not to make excuses, but my eye sight close up is not what it used to be. Thinking that E6 is Thermistor 6 , after looking at the board layout online I notice that E6 is Thermistor 7 not 6.
So now I have the coolant thermistor plugged into E(5) Thermistor(6) and my code is:

M305 P106 X6 T10000 B3950 R4700 H0 L0 S"Coolent Temperature"

@t3p3tony thanks for the extra info. I found my error:

I was using M106 P2 S50 T40 H2, The H2 was wrong, since my sensor was number 5.
I changed that before reading your message and it works. I will add the temperature range, but I have to say that using the S parameter to control the speed works too despite it is a thermostatic fan.

just completed a 12 hr print no heat faults. Thanks again.

Bit late, but it was mechanical. Didn't see that my Y tower Idler pulley mount had a lose screw.
Fixed.

All the code is in the github repo in the last post in that thread. The Wemos D1 mini and shields are simple to solder together, and you flash the Wemos D1 mini from arduino just like any other arduino after installing the ESP8266 board package. Easy peasy!

@dc42 Thanks for the info. Didn't know that .

Not sure what it was, but since I updated the firmware all is good.

@phaedrux said in Viewing .csv file without DWC:

It's pretty easy to view it in Excel if you have one of the modern versions of Excel.

Open the CSV, highlight all the grid data points (starting at the 4th row), then go to Insert, and on the ribbon there are some chart buttons, find the one that has bar graphs going above and below, in there will be a 3D surface map. Choose that option and it should drop in a little graph window showing your heightmap in 3D. You can right click on it, and choose 3D rotation, which opens a control panel that gives some rudimentary scale and rotation functions to view the map from different angles.

Here's a picture that kind of shows everything.

0_1553184774397_Screenshot 2019-03-21 10.12.07.png

Very cool. Thanks for the detailed instructions.
/quadcells

@Hergonoway
I did not as I saw that the 3 jams I experienced were caused by a faulty heat sink fan. I replaced the fan and no jams.

Perfect.
Thanks.
That did it.

/quadcells

Awesome, thanks again.

LOL. Can't believe that I neglected to count the zeroes.

@deckingman said in X end stop not switching Yes to No on DWC:

@quadcells There you go then.

BTW, if you use the probe for homing Z, then you need that second line with the S2 (but without the X1 obviously). So M574 X1 Y1 Z0 S1 followed by M574 Z1 S2.

Actually you don't, assuming you use a G30 command to home Z in homez.g and homeall.g. It's only when you use a G1 S1 Z command to home Z that you need to define the Z probe type.