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

Compatibility with GCode Filename Format #182

Closed
StumbleNOLA opened this issue Jul 21, 2020 · 7 comments
Closed

Compatibility with GCode Filename Format #182

StumbleNOLA opened this issue Jul 21, 2020 · 7 comments

Comments

@StumbleNOLA
Copy link

Would it be possible to have OctoPrint Connection use the file format generated by "GFF"? I need GFF to keep my files organized and properly named, but the two don't play together, so I end up not using OPC for anything but one time print files I plan on deleting.

@fieldOfView
Copy link
Owner

Because of the design of the plugin, unfortunately no. You could use the Custom Printjob Naming plugin instead.

Perhaps a future version of the GCode Filename Format plugin will change this:
rgomezjnr/GcodeFilenameFormat#2

@rgomezjnr
Copy link

Hey guys just saw this and wanted to add. I added compatibility for OcotoPrint Connection in GFF in version 2.0.0-rc2. Because of the significant changes and unfinished testing I haven't integrated this into a release, but other users have reported that it works for them. This version removes the separate Save Gcode button, and actively updates the job name with the specified format, which will then be used by OctoPrint Connection. @StumbleNOLA I can help you install this version if you would like.

@StumbleNOLA
Copy link
Author

@rgomezjnr That would be great, I am happy to beta test it. I hate having to bounce between the two plugins.

@rgomezjnr
Copy link

  1. Download 2.0.0-rc2.
  2. Extract 2.0.0-rc2
  3. Move GcodeFilenameFormat folder to Cura plugins folder
  • Windows: C:\Users\%USERNAME%\AppData\Roaming\cura\4.4\plugins
  • Mac: $User/Library/Application\ Support/Cura/4.4/plugins
  • Linux: $HOME/.local/share/cura/4.4/plugins
  1. Launch Cura
  2. Set filename format
  3. Slice
  4. Select Print with OctoPrint button
  5. Verify the filename format is used In OctoPrint Connection

@StumbleNOLA
Copy link
Author

StumbleNOLA commented Aug 5, 2020 via email

@fieldOfView
Copy link
Owner

Is it perhaps a good idea to move this discussion to rgomezjnr/GcodeFilenameFormat#2 ?

@rgomezjnr
Copy link

Yes @fieldOfView, I agree.

@StumbleNOLA please post further questions on this in rgomezjnr/GcodeFilenameFormat#2 .

I suggest first uninstalling the plugin using the Cura Marketplace:

image

Once that is done, close Cura and verify there is no GcodeFilenameFormat folder in your Cura plugins folder. If there is then delete it.

Then extract and copy the GcodeFilenameFormat folder to the Cura configuration folder. Note there shouldn't be any "-2.0.0-rc2" in the folder name.

You should have the following paths:

cura\4.4\plugins\GcodeFilenameFormat\images
cura\4.4\plugins\GcodeFilenameFormat\test
cura\4.4\plugins\GcodeFilenameFormat\__init__.py
cura\4.4\plugins\GcodeFilenameFormat\Format.qml
cura\4.4\plugins\GcodeFilenameFormat\GcodeFilenameFormat.py
cura\4.4\plugins\GcodeFilenameFormat\Help.qml
cura\4.4\plugins\GcodeFilenameFormat\LICENSE
cura\4.4\plugins\GcodeFilenameFormat\plugin.json
cura\4.4\plugins\GcodeFilenameFormat\README.md

If you are sure the plugins folder is correct, then launch Cura. If it's still not loading the plugin, check the Cura log file in:

cura\4.6\cura.log

If the plugin is loading properly it should report the following:

2020-08-06 21:12:47,282 - INFO - [MainThread] UM.Logger.info [122]: Loaded plugin SimpleView
2020-08-06 21:12:47,312 - INFO - [MainThread] UM.Logger.info [122]: Loaded plugin X3DReader
2020-08-06 21:12:47,352 - INFO - [MainThread] UM.Logger.info [122]: Loaded plugin XmlMaterialProfile
2020-08-06 21:12:47,375 - INFO - [MainThread] UM.Logger.info [122]: Loaded plugin XRayView
2020-08-06 21:12:47,456 - INFO - [MainThread] UM.Logger.info [122]: Loaded plugin GcodeFilenameFormat

If there's an error after it attempts to load GcodeFilenameFormat please paste it in rgomezjnr/GcodeFilenameFormat#2 .

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

No branches or pull requests

3 participants