@Phaedrux Thanks for the support.
The below issue came up repeatedly.
'M997: File DuetWiFiServer.bin not found'
Then we read another topic in which it is suggested to use 'M21 to remount the SD card'.
After that, it updated the firmware. Now it is connected to the Wifi
@jay_s_uk That's great. Thanks for the links. Will try it.
If any queries will get back to you.
@jay_s_uk ok. Finally got the solution. The wire was the problem. After changing the wires the issue was solved.
Is there any link which will show all the errors and solutions?
These words 'phase B short to Vin' just threatened me.
Thanks for your support.
@jay_s_uk Sorry, its a surprise to see this message of 'ok'.
For this reply, I didn't write this much detailed query..
I know that you have assisted us in some other queries. But this reply is not acceptable. Thanks anyway.
Hi all,
We are using Duet 6 XD boards.
For Y axis, we are using Leadshine Closed Loop Nema 23 stepper with driver. (Other axis with Open Loop Nema 23 only)
We are unable to get the closed-loop tuning.
All the documents are pointing to the 1HCL board only.
How can we tune the above motor?
In the below thread, @dc42 has mentioned the closed-loop steppers motor possibilities:
https://forum.duet3d.com/topic/31328/getting-stared-with-closed-loop/2
'Use external closed loop motors or motors+drivers with step/dir inputs and drive them from a Duet 3 MB6XD board'
Any clear guide on the above?
Thanks
@jay_s_uk oh..k. Thanks for the update. Will wait for beta2 then
Hi,
I have updated the latest firmware to 3.5beta1
We are having IDEX machine. I wanted to ensure that X and U (RIght hotend) do not collide with each other when manually moving (After homing).
I found this M597 and tried using it in config.g. M597 X0 U120 (Nozzle to nozzle offset is 120mm). But I didn't find any change.
When I tried to move U closer to X, it crossed the 120mm limit and it is getting closer to X-axis and started colliding. I tried this command in the console by changing the values also, but no result
Is it the right way I am using this command?
@Phaedrux Thanks, but how to sense the failure of BL touch? Because the Z can be moved from the bottom to top. Any time based failure detection or any other way?
Hi all,
When we use BL touch or Clone, sometimes there are chances that the BL touch will crash with the bed. This may happen if the Z height is not tuned properly or if there is a big blob at the nozzle.
With this, the Bl touch will try to move the bed, but the nozzle is already crashing with the bed. This gives a bad moment.
Due to this, the BL touch probe may break and the glass bed may also damage.
Is there any bltouch crash detection available?
I found this on Modix website:
https://www.modix3d.com/tech-specs/
'Crash Detector
Previously an optional add-on and now default with every printer is an additional layer of safety in rare cases where the BL-Touch bed leveling probe fails and this failure is not being detected by the printer controller. In this case, the detector will prevent the print head from crashing into the bed plate.'
This will be of great help to avoid the failures
@jay_s_uk I always respect your support. As mentioned that you have supported me lot of times. I know that.
Sorry, that my words have hurt you. My apologies for that.
I know that you are supporting from outside, not from Duet Team.
@jay_s_uk Sorry, its a surprise to see this message of 'ok'.
For this reply, I didn't write this much detailed query..
I know that you have assisted us in some other queries. But this reply is not acceptable. Thanks anyway.
@jay_s_uk But i hope i have explained it clearly.
'Frequenty the driver Warning is coming and either CoreXY is skipping or the Z axis is skipping. We thought that the driver warning is due to wire issues.
If driver warning is due to wire issues, then practically no print should come properly. Some prints are fine, then suddenly Driver warning comes'
Either it should be a complete Flop or it should be a complete success.
@jay_s_uk @Phaedrux @dc42 @T3P3Tony
Thank you. I have changed all the above as suggested.
But the thing is getting worsened.
Now we are getting the following error:
Warning: Driver 0.2 warning: Phase B may be disconnected.
Actually we are FFF machine makers. We used to build custom machines to the needful customers.
4 months back we made the following machines - 02 nos (Installed at our customer location). It is targeted as High speed machine with 3000mm/s2 acceleration
CoreXY with CF tube gantry.
Rapido hotend with Orbiter 2 extruder.
E3d High speed motor for X&Y and E3D Super whopper motor for Z.
Duet3 Mini + Wifi board + 4.3 Panel Due. (Board is cooled by 50x15 blower fan across the board). Purchased from E3D.
Gates GT2 9mm belt + 20teeth GT2 pulley.
X+Y is Hiwing MGN 12 guide Rails
Dual Ball screws in Z axis.
3D printed EVA hot end parts.
It was tested at our premised for 2-3 months and installed at the customers location.
We are now facing multiple issues.
Frequently the Wifi is getting disconnected. If this afternoon gets disconnected, then the whole day it wont connect back. The customer tried a lot. Switched off the network, restarted the machine and whatever he does the Wifi doesn't connect. The next day it will connect automatically.
It happened multiple times. We asked him to recheck the Wifi Antenna, interchange Wifi antenna from another machine, recheck their network connectivity, but nothing was useful.
4 days back I raised the query in this forum and someone asked to install the updated Board and Wifi firmware. We tried today and now it is working.
But we are not sure when this Wifi issue is going to come.
Frequenty the driver Warning is coming and either CoreXY is skipping or the Z axis is skipping. We thought that the driver warning is due to wire issues.
If driver warning is due to wire issues, then practically no print should come properly. Some prints are fine, then suddenly Driver warning comes.
We have set the acceleration to 3000mm/s2, but the customer is printing with 60-80mm/s speed only. So he is not trying with high speeds also.
Previously we have used Multiple boards:
Starting from Ramps 1.4, MKS Gen L, MKS Gen V 1,.4, MKS Rumba, MKS E3d, MKS Robin Nano, to the recent BTT Octopus, Octopus Pro. Zero issues due to board after the proper tuning.
None of these boards are having this kind of major issues.
Particularly this Wifi issue and Driver warning issue is killing.
Recently we have build some machines with 500x500 CoreXY with Octopus Pro running with Marlin. Some machines we have used MKS Robin Nano V3. Never we faced these issues. Once tuned it will be like a workhorse.
Now these two machines are customized with Duet boards. This is totally damaging our reputation. The customer is totally angry with us.
I am not sure whether we are doing the wrong things or the board is having these many issues.
Kindly provide us some solution, If we are wrong, guide us in the proper way.
@Phaedrux Thanks for the support.
The below issue came up repeatedly.
'M997: File DuetWiFiServer.bin not found'
Then we read another topic in which it is suggested to use 'M21 to remount the SD card'.
After that, it updated the firmware. Now it is connected to the Wifi
