la connexion USB du laser ne fonctionne plus avec la version 1.92 de octoprint

[DU4FDR]

The problem

Suite à la mise à jour de la version 1.92 la connexion des laser ne fonctionne plus !
Le port USB donne des erreurs 09 ou 0.20.
à priori je pense rétrograder vers la version 1.87.
Comment faire cette rétroaction, merci d'avance de votre aide !
à priori c'est un problème connu mais pas de correctif pour le plugin GRBL...

Did the issue persist even in safe mode?

Yes, it did persist

If you could not test in safe mode, please state why ("currently printing" is NOT an excuse!)

No response

Version of OctoPrint

1.92

Operating system running OctoPrint

OctoPrint 1.9.2 Python 3.9.2 OctoPi* 1.0.0 (build 2023.07.18.111854)

Printer model & used firmware incl. version

laser TWO TREES

Browser and version of browser, operating system running browser

edge

Checklist of files to include below

• Systeminfo Bundle (always include!)
• Contents of the JavaScript browser console (always include in cases of issues with the user interface)
• Screenshots and/or videos showing the problem (always include in case of issues with the user interface)
• GCODE file with which to reproduce (always include in case of issues with GCODE analysis or printing behaviour)

Additional information & file uploads

J'ai réalisé la connexion sur le port USB avec une imprimante çà fonctionne normalement !

Si je connecte le laser le système me renvoie une erreur sur le firmware du laser ?
je ne sais plus quoi faire ?

[github-actions]

Hi @DU4FDR!

It looks like you didn't upload a system info bundle as requested by the template. A bundle is required to further process your issue. It contains important logs and system information to be able to put your issue into context and give pointers as to what has happened.

Please edit your original post above and upload a bundle zip file. Actually upload the file please and do not paste some link to a cloud provider, we want to have everything in one place here. Also do not unpack, repack or otherwise modify the bundle or its name, share it exactly like you get it from OctoPrint.

Without the availability of a bundle, your issue will have to be closed.

Thank you for your collaboration.

[cp2004]

This is a known issue with the Better GRBL plugin - it's not compatible with OctoPrint 1.9.0 yet. See here synman/Octoprint-Bettergrblsupport#118

[synman]

I know this is closed but the issue in the plugin does suggest regression within 1.9 tied to profile management. There were some big changes in 1.9 that broke backwards compatibility related to profiles.

I didn't bother doing anything about it because I felt like I was kinda misusing them anyway to get around a tool count check... Which could've been suppressed but I didn't know about it at the time.

[DU4FDR]

Good morning, Do you plan to correct the problem of using lasers with OCTOPRINT which do not currently work with version 1.9xx? we are forced to use version 1.87 with a minimum of options for GRBL commands. please inform us because we use the enclosure module. Octoprint allows you to safely control a laser and protect yourself from radiation and dust. ! a+ Francis

…

----- Mail original ----- De: "Shell M. Shrader" ***@***.***> À: "OctoPrint/OctoPrint" ***@***.***> Cc: "DU4FDR" ***@***.***>, "Mention" ***@***.***> Envoyé: Jeudi 12 Octobre 2023 00:40:37 Objet: Re: [OctoPrint/OctoPrint] la connexion USB du laser ne fonctionne plus avec la version 1.92 de octoprint (Issue #4872) I know this is closed but the issue in the plugin does suggest regression within 1.9 tied to profile management. There were some big changes in 1.9 that broke backwards compatibility related to profiles. — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you were mentioned. Message ID: <OctoPrint/OctoPrint/issues/4872/1758644422 @ github . com>

[foosel]

The problem lies with a 3rd party plugin that is not maintained by me. As far as I understand, the problem stems from profile validation introduced in 1.9.x that fixed existing bugs and has already been fixed in the source of the plugin, it only needs to be turned into a new release.

If there are further issues, I'm happy to help the maintainer in solving them, and if it turns out to be due to a regression, I'm also happy to fix stuff on my end.