Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exposure Setting to Zero Seconds on Anycubic M5s Pro #941

Open
Jewce86 opened this issue Nov 19, 2024 · 2 comments
Open

Exposure Setting to Zero Seconds on Anycubic M5s Pro #941

Jewce86 opened this issue Nov 19, 2024 · 2 comments
Assignees

Comments

@Jewce86
Copy link

Jewce86 commented Nov 19, 2024

System

UVtools v4.4.2 X64 and 4.4.3 X64
Operative system: Microsoft Windows 10.0.22631 X64
Processor: 12th Gen Intel(R) Core(TM) i9-12900K
Processor cores: 24
Memory RAM: 27.75 / 63.75 GB
Runtime: win10-x64
Framework: .NET 6.0.33
AvaloniaUI: 11.1.3
OpenCV: 4.9.0

Path:       C:\Program Files\UVtools\
Executable: C:\Program Files\UVtools\UVtools.exe
Loaded file: 15Boyz()_03h21m_73ml_copy.m5sp [Version: 518] [Class: PhotonWorkshopFile]

Printer and Slicer

  • Printer: Anycubic M5s Pro v1.0.5.4
  • Slicer: Anycubic Photon Workshop 3.4.2 & Chitubox V2.1

Description of the bug

Exposure setting itself to 0s on printer for all layers following Bottom and Transition (including delay UV light activation during transition). When printing a file, the Bottom 5 layers work properly. When the transition layers start, there is a delay in activating the UV light. When the normal layers begin to print, rather than the UV light staying on for 3.6s, it flickers quickly. This can also be noticed in the slicer when the estimated time of the file drops significantly, in the linked file, original file time from slicer is 4h26m, in the UVTools processed file, with the issues of the exposure resetting to 0s, time is now 3h21m. Attempts to manually change exposure on the printer via the settings fail as it reverts back to 0s for the following layer. Attempts to print without processing in UVTools works successfully. Prints immediately fail after processing through UVTools as there is no signficant exposure.

This was tested and confirmed by turning off all AI settings such as Resin Detect and Intellegent Release, covering the screen with a sheet of paper to protect it from the build plate, and watching the UVLight activating via a side hole where the Vat would sit.

Another issue i had noticed in UV Tools 4.4.3; files would take upwards of 15 minutes to Detect Issues. When i downgraded to UVTools 4.4.2, files returned to the normal approximately 3 minutes. When printing with my previous Mono 2; these issues were not happening, as well as the Computing Issues were only taking 3 minutes.

How to reproduce

Slice File in Anycubic Slicer
Save File to Disk
Open file in UVTools
Compute Issues
Fix Resin Traps
Save File
Load file on printer via either USB or Cloud (tested both)
Print file.

This was tested and confirmed by turning off all AI settings such as Resin Detect and Intellegent Release, covering the screen with a sheet of paper to protect it from the build plate, and watching the UVLight activating via a side hole where the Vat would sit.

Files

https://1drv.ms/u/c/d9d92a66e33001da/EUyDkmGFYeZGlKS0E3R2wroBB7wVBva_RF_PC9WfV6MKIg?e=cgA1CD

Copy link

This is your first time submitting an issue with UVtools 🥳Please review your issue and ensure that the submit template was followed, the information is complete, and not related to any other open issue. It will be reviewed shortly. Debugging is very important and make the program better. Thanks for contributing and making the software better! 🙌

@sn4k3
Copy link
Owner

sn4k3 commented Dec 3, 2024

Looks like PerLayerOverride is activated which cause problem in recent models.
In same file you can try to: File - Reset layer properties, Save and try to print again. My bet is that will work as that reset all properties and set flag to off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants