Hello,

I just started playing with this plugin and am having an issue where the Gcode state does not seem to work in my programs. I have a program that tests for Gcode state is RUNNING The status on the device shows RUNNING in the admin console but the program shows FALSE. I can see activity from the plugin in the event log as the Gcode state changes and the status is updated on the device in the admin console. Any idea why the program won't show TRUE when the status matches?

Also it appears that I'm unable to control the printer via the plugin. Pause, Resume, Chamber light on/off etc. Via program or directly in the admin console. My printer is an H2D if that matters.

Thanks in advance.

-Xathros

Edited April 18Apr 18 by Xathros

Hello @bpwwer,

Wondering if you have any thoughts about the above? I've found a workaround of job finished using percent complete but am unable to act upon any of the error conditions as they all appear in Gcode state.

The behavior of Gcode State is very odd in the console. I can't get an IF to evaluate TRUE no matter if I test = or NOT= for any of Gcode State's values. Also as stated above, there is no control from the admin console to the printer.

This is obviously not a life threatening situation here but I would like to implement some of my ideas if possible.

Thanks again!

-Xathros

Edited April 24Apr 24 by Xathros

@bpwwer,

Just a bump. Any thoughts about the above?

Thanks.

-Xathros

Sorry, I saw your post show up initially but the title didn't register that this was for the Bambu plug-in.

I just did some testing with my A1 Mini and the plug-in is working correctly. However, the programs on the isy don't seem to register that change.

You can check that the plug-in is changing the state by going into the nodes tab for plug-in in PG3x and watch the gcode state/GV10 value. The number should change as the state changes. I simply started printing a file and it switched to state 2 (RUNNING) almost immediately. I then stopped the print and it switched to state 5 (FAILED).

I also checked the program status on the admin console and it is running the program on a state change (I see the last run time changing), but as you observed, the status never changes to TRUE.

This may be a bug in the isy software or it may be the way it is designed to work with this type of value. Since PG3x is sending the updated values to the isy, it seems like a program should be able to detect those changes.

Stop, Pause, Resume all are working with my A1 mini.

After researching it, the chamber light command I send may be wrong. I can change that, but I don't think I can test it as it doesn't seem to apply to the A1 series. I haven't been able to find a command that turns on the camera light for my mini.

There also could be some issues depending on the firmware version. I stopped updating the firmware on my A1's after they announced some changes that I wan't happy with.