Incorrect determination of model height
-
@droftarts I changed the card, it did not work.
I did not say that you are obliged to help me, but I hope you will not leave me with a problem!
the problem does not appear every time, try uploading another file and then again my file. -
@Plohish Okay, I see what you mean. For me, it doesn't store the simulation time either. Simulating a different file (which simulates correctly) then going back to this file, it simulates using the previous file's values. I think it's a problem with the file, rather than DWC. I have asked @chrishamm to have a look at the file.
Ian
-
@droftarts
Thank you so much!
I am very glad that you confirmed my situation!
I will be waiting for your reply!
this file is not the only one that causes this problem... i have more!I will send you a file for comparison, this file always works well!
link -
@Plohish @dc42 has corrected a bug in the 3.5beta firmware that meant that sometimes the file info was not read and updated when simulation or print was started. The workaround for older versions of DWC is to reload the DWC tab in your browser. This forces an update of the Object Model, and updates the file info. You can do this while the file is simulating or printing.
However, we haven’t worked out what actually causes this behaviour with the file you posted earlier. It doesn’t seem to be anything in the Gcode file, the file name or file permissions. I notice the Gcode files are made with the current 2.5.0 version of PrusaSlicer; did you have the same problem when using older versions of PrusaSlicer, or other slicers?
Additionally, in the 3.5 beta, we noticed your end Gcode has a G1 H1 … move in it. This wasn’t being ignored in simulation and was causing the simulation to abort with an endstop error, so not saving the simulated time (at least in standalone). @chrishamm has fixed this also, I think. This probably isn’t an issue in 3.4.5.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@droftarts
Thank you for your work!
I made a file in another slicer, Cura 5.2.1 and was surprised to find the same problem.
File link.
You write - you can reload the page in the browser, however, the problem also exists for the PanelDue.Please forgive my bad English, it's Google's fault :)
-
@droftarts
I made a short video for you.
After refreshing the page, I received information about the height of the product, about the height of the layer, and I also saw a working progress bar.
However, as you can see, PanelDue doesn't work correctly!
https://youtu.be/gN9JjY3ChXc -
@Plohish what firmware version is the PanelDue running?
Ian
-
@droftarts
I'm using the latest PanelDue firmware - 3.4.1
With other files PanelDue works fine and shows the progressbar.
This is not a separate problem of the PanelDue or DWC, I think the problem is in the Duet firmware. -
@Plohish I haven't tested PanelDue with your file but the fix I applied to RRF will most likely fix that issue too. The fix is already in both the 3.5-dev and the 3.4-dev RRF source code. It will be included in the 3.5beta2 release.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42
thanks!
I'm not a fan of using beta firmware, but when it comes out, I'll upload it to write you about the results. -
@Plohish said in Incorrect determination of model height:
I made a file in another slicer, Cura 5.2.1 and was surprised to find the same problem.
File link.I tried this file on a Duet 2 WiFi with RRF 3.4.5, but it simulates correctly for me, showing the correct file information without having to do a browser refresh. I had simulated a different file before, but file info was updated when the simulation of this file started. The main difference with this file compared to others is that you are using relative extrusion (which is what RRF generally expects) rather than absolute extrusion. Can you try changing to relative extrusion in PrusaSlicer? Though the short file you sent also uses absolute extrusion, and worked correctly, so this may make no difference.
Ian
-
@droftarts
I made a file with relative extrusion in PruisaSlicer, it didn't change anything.
For the purity of the experiment, first I do an "emergency stop" of the machine and its "reboot", after that I upload the file and see the problem.
link
