Hi,
I didn't notice this plugin existed so I wrote my own but didn't get around to publish it yet.
One thing mine does is create a higher resolution PNG image (320x320) - not sure if you are interested in adding it.

The code is at https://github.com/DanielO/GXCodeWriter/blob/main/GXCodeWriter.py if you want to take a look.

(I'm happy to dual license it etc..)

Great work: Extension makes it possible to print using Cura on Raspberry Pi 4.

Only remark: after printing the printhead is brought to the home position and platform does not go back to home position.

For protection of the print nozzle, the platform should first go back to the home position. After that print head can go back to home position.

Is is possible to utilize the usb port and drivers to monitor and print from Cura?

I'm no professional or anything and I'm asking so that other people wondering can see the answer here.

i see that there was a recent change to the gx.py script stating it made the script useable for other applications, im currently trying to use this for post processing gcode made by prusaslicer, but i cant seem to get gx.py to even work, it will not allow me to use the script on my already made gcode, so im wondering, what am i doing wrong? p.s. sorry if i shouldnt have put this in as an issue, but i didnt see anywhere else to put it

Export window of Cura 5.3.0 is like this:

Whereas Cura 5.2.1 has export window like this:

I have GXWriter 2.0.0 installed.
I am not expert but doesn't plugin supporting SDK 8.1.0 supports Cura 5.3.0?

Thanks for producing the plugin! I am sure many people are appreciative.

Long time Finder and FlashPrint boffin. But now I am getting dangerous, as I want to extend my knowledge.

Gist is at here, then here, and then here.

The basic story, I bought a second removable bed for my finder and mounted a hot plate - call me crazy 🤪. Plenty of thought given as to how to insulate, but obviously still needs testing (don't do this at home, yet).

The hot plate (obviously) means the bed is too tall for the finder levelling, and therefore the bed likely requires a reduction in the Z axis of the print volume.

Not sure how to deal with the levelling problem, unless I can drive that with G28 then G29 (Marlinesque), but a print should be doable, using CURA?

Is it as straight forward as dropping the "Gantry Height" in the "Machine Settings" with the "FlashforgeFinderIntegration", or dropping both "Gantry Height" and "Z (Height)"? Or is it going to need a hack of the plugin code please?

I assume, on a normal finder, the "Heate bed" and "Heated build volume" checkboxes are unused in any event? There seems no means to set the "Heated build volume" for example.

Cheers,
A

Hello!
i am very ignorant of codes. Since I am using Prusaslicer on Flashforge Dreamer NX, the idea came to mind. Post-processing scripts can be added in Prusaslicer. Is there any way to customize your Cura plugin so that the script takes the same thumbnail and simply adds Gcode to the beginning when saving? And the .GX end can be added to the "Output fileneame format" line.
Best regards Egon

Good Day;

I was able to get this installed and change the settings to match the Flashforge Creator Max. I have not yet tried using it to print, but ran into an issue where after adding this plugin I am no longer able to connect to the Raspberry Pi with Octoprint on it for online management.

Would you know what I can do to help verify this plugin is not interfering with the Octoprint connection? It was working until this plugin was activated. Could be coincidental, but I want to be sure.

Hello!
Because on dual-nozzle printers, Cura adds the Gcode T0 command before it starts, and the printer recognizes it as an invalid code. Is it possible to make a script that checks before the start of Gcode T0 for existence and if necessary removes it? And would that be possible at all?
Many thanks! Egon

Hello,

I was wondering if there are any specific instruction for Cura 4.9.0. Downloaded from Marketplace seems to do nothing and dropping the packages to Cura also seems to do nothing.

Kind Regards
Ioannis

Do you plan to make this available for Cura 5?

There is a new support for the Finder 3. This issue is to track support for that new model.

Hi, I've just reviewed and tested your plug-in as you submitted it to the Marketplace. And I found a bug.

The printer profiles include some quality profiles (low, standard, high and hyper). However these profiles seem to be made for Cura 4.6. Earlier versions of Cura can't downgrade them. As a result, the profiles aren't available and it loads the default set of profiles or no profiles at all.

The following errors are put in the log:

2021-04-28 11:56:25,454 - WARNING - [MainThread] UM.Settings.ContainerRegistry.loadAllMetadata [324]: Invalid metadata for container finder_standard: {'quality_type': 'normal', 'type': 'quality', 'name': 'Standard Resolution', 'weight': '0', 'version': '4', 'definition': 'finder', 'container_type': <class 'UM.Settings.InstanceContainer.InstanceContainer'>, 'global_quality': 'True', 'setting_version': '13', 'id': 'finder_standard'}
2021-04-28 11:56:26,084 - WARNING - [MainThread] UM.Settings.ContainerRegistry.loadAllMetadata [324]: Invalid metadata for container finder_hyper: {'quality_type': 'hyper', 'type': 'quality', 'name': 'Hyper Resolution (Slower)', 'weight': '0', 'version': '4', 'definition': 'finder', 'container_type': <class 'UM.Settings.InstanceContainer.InstanceContainer'>, 'global_quality': 'True', 'setting_version': '13', 'id': 'finder_hyper'}
2021-04-28 11:56:26,308 - WARNING - [MainThread] UM.Settings.ContainerRegistry.loadAllMetadata [324]: Invalid metadata for container finder_low: {'quality_type': 'low', 'type': 'quality', 'name': 'Low Resolution (Faster)', 'weight': '0', 'version': '4', 'definition': 'finder', 'container_type': <class 'UM.Settings.InstanceContainer.InstanceContainer'>, 'global_quality': 'True', 'setting_version': '13', 'id': 'finder_low'}
2021-04-28 11:56:26,703 - WARNING - [MainThread] UM.Settings.ContainerRegistry.loadAllMetadata [324]: Invalid metadata for container finder_high: {'quality_type': 'high', 'type': 'quality', 'name': 'High Resolution (Slow)', 'weight': '0', 'version': '4', 'definition': 'finder', 'container_type': <class 'UM.Settings.InstanceContainer.InstanceContainer'>, 'global_quality': 'True', 'setting_version': '13', 'id': 'finder_high'}

They are invalid because it expects (in this case) the setting_version metadata to be 11.

Setting the setting_version to 6 should allow the profiles to be loaded in Cura 4.0 and higher, which is what the plug-in is marked to support. You should then be careful not to change any settings that are implemented in those newer Cura versions. I think the best approach would be to just set them to 6 and test it on all supported Cura versions. In Cura 4.0, see if it produces any errors in the log about settings that don't exist, and if so remove those setting overrides.

If you really need to use features of more recent Cura versions, you'd have to modify the installer to install different profiles in modern Cura versions than in the old ones. That would get complex.

No matter what temperature i choose in my Cura profile, it sets to 180°C which is too low (stepper motor starts clicking because the filament is under too much pressure)