Creality CR-10 upgrade
-
I suggest you read the commissioning instructions in the fitting instructions page, at https://miscsolutions.wordpress.com/mini-height-sensor-board/.
-
Thank you. I think i have the idea now. Here is the map:
Is this any good or my bed is bad?
I have bought new 8mm precision plate but it does not look that precise.
Before i had Chaina heatbed out of 3mm aluminium and got this:
Can you help interpret the results?
P.S. I have 5V LED bar. Draws little over 1 A
Can i connect it to unused expansion header pins and control it with a macro? Cant seem to find header ratings -
Your first height map looks OK, but the second (mostly red one) looks poor.
If you have a spare controlled fan output on the Duet, you can connect your lighting between +5V on the expansion header and FAN- on your chosen controlled fan output. The control it using M106. Or, if uou are not using the E1 heater output, you can connect the lighting between +5V on the expansion header and E1- on the E1 heater terminal block. Caution! Some versions of the Duet PCB have the E1- and VIN legends for the terminal block the wrong way round. E1- is the end farthest from the corner of the board.
-
Great. Thanks.
-
Agniusm,
I'm about to start my adventure to replace the cr-10 board with the DuetWiFi..
The steppermotor connectors are slightly different, but it's possible to plug it in…Question:
Are the steppermotor connectors of the CR-10 pin-compatible with the connectors of the Duet board?
Can I plug them in the Duet board or do I have to rewire ??
If so, which way should the connector be orientated? -
I think you will need to rewire. I swapped my cables and built them from scratch so i don't really know.
-
I think you will need to rewire. I swapped my cables and built them from scratch so i don't really know.
Not wat I was hoping for, but thanks for letting me know..
I'll go and hunt down the wiring of the cr-10 connectors. -
You can test whether the connectors need to be rewired in either of two ways:
1. Use a multimeter to measure the resistance between pins. If the wiring is correct for the Duet, you should get a few ohms resistance between pins 1 and 2, and a few ohms between pins 3 and 4. There should be no continuity between 1 or 2 and 3 or 4.
2. If you don't have a multimeter, then you can try shorting pins together to see if it makes the motor harder to turn. If it is wired correctly, then if you short pins 1 and 2 together, or pins 3 and 4 together, it will be harder to spin the spindle with your fingers.
-
I think you will need to rewire. I swapped my cables and built them from scratch so i don't really know.
Not wat I was hoping for, but thanks for letting me know..
I'll go and hunt down the wiring of the cr-10 connectors.Rewiring is basically swapping pins. There is not much to it. Like DC42 said or you can simply plug generic LED and spin the motor by hand. If it lights up, you got a pair.
On cr10 i think pairs are layed out as follows on motor connector: 1 and 4 one pair, 3 and 6 the other one. On duet you have 1b1a and 2a2b.
Now just connect you wires so 1 goes to 1a 4 to 1b 3 to 2a 6 to 2b and if its reversed, reverse it back in firmware. It is different for y axis only. -
The AJAX error still does my head in. I pulled out old router to test, where all AP's are stored so i could edit the list? I have ordered new AP so i can dedicate it to the printer
-
The latest (1.20) version of DWC gives a more precise error message instead of "AJAX error".
-
Is there a way to set baby stepping on LCD to be something else than 0.05 or is it precompiled in LCD firmware?
-
I do not think that these AJAX errors are caused by your wifi connection but by the firmware (Firmware 1.9 and up)
I had them all the time after upgrading, im back to the old firmware and dont have them anymore
see also my tread :
https://www.duet3d.com/forum/thread.php?id=3831i hope this will be fixed
-
Is there somewhere i could find how long last print took?
-
Different users find different firmware versions work best for them, so I caution against generalising. The main changes to DuetWiFiServer.bin were:
- Firmware 1.19 moved the web server form the WiFi module to the main processor
- Firmware 1.19.1 tries harder to restore the wifi connection if it is lost than all earlier versions did
- Firmware 1.20 uses the latest SDK from Expressiv to fix the KRACK vulnerability that is present in all earlier versions
- Firmware 1.20+1 uses version 2 of the LWIP TCP/IP stack instead of version 1, and a still-later SDK version
-
Dc42 what do you mean worked best for them? I liked the new version, i hope my problem wil be fixed.
-
I'll get new AP, place it in the same room and then we will see. I have IP wifi camera further away and it works fine. I don't know why this is problematic. Is it poor hardware (wifi module) or something else causing so many people problems?
-
I mean that some users found DWS 1.03 and earlier gave unreliable connections, and the more recent versions more reliable; and a few users such as yourself have the opposite experience.
-
but DC42 to whole point of having the duet wifi for me is that i can control it from a distance and the active development of the firmware to get even better printing results.
i would like to have some help to get things going again with the new firmware.
-
Unfortunately we are dependent on the Expressiv SDK for management of the WiFi connection. It's closed source, and FCC rules prohibit Expressiv from open-sourcing it even if they wanted to. There was some indication on the Arduino github pages that the new SDK version that fixes the KRACK vulnerability doesn't play nice with some brands of WiFi router.
There remains the possibility that some of the connection issues are due to our own firmware. To help identify whether this is the case, recent versions of RRF and DWS have a debug facility whereby any debug messages coming from the wifi module will be echoed to USB if you send M111 S1 P14 first. You must have a USB connection active to use this facility.
There is a 1.21RC1 version of DuetWiFiServer almost ready for release. It fixes a known issue with repeated use of FTP. I suggest you try that along with DuetWiFiFirmware 1.21RC1 when it is released (I hope tomorrow), and enable the debug facility if the disconnections persist.
