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.

Thanks @bpwwer,

I can see the values change in the admin console and in the plugin as you describe. I will check last run time to verify program run. It is odd that I can't get the program to evaluate true when testing "IS" or "IS NOT" for any value. I'm testing with ver 1.0.3 of the plugin as of today with no discernible changes from my previous observations.

@Michel Kohanim ,

Any thoughts on this matter? Is this a bug in IoX?

Thanks in advance.

-Xathros

The only change I made was to the command sent for turning the chamber light on/off. Since none of my printers have a chamber, I can't test it.

The run/pause/stop commands are all working for my printer. The docs I have indicate that the same commands should work for all models. But as I said, I'm running older an firmware version and given some of Bambu's recent changes, I can't guarantee that they work with the latest firmware.

For the gcode state, it does not appear to be a problem in the plug-in. I see the plug-in get the proper state from the printer, I see it send the proper state to the IoX and I see the IoX respond by changing that state. Why programs aren't detecting the change in state is not something I can answer. It seems like an IoX bug to me, but it could be just the way IoX was designed to work with that type of value.

@bpwwer,

Chamber light on/off nor any of the other printer commands are working with my H2D. Maybe I need to be in LAN only mode for them to work but all of the status stuff is working without.

I agree that IoX is seeing the correct status for Gcode state. I think printer state could use a look over however. After a print completes, Gcode state says FINISH but printer state remains at PRINTING even after the printer has gone to sleep long after a completed print. I do see other printer states during print start such as homing toolhead, changing filament, calibrating extrusion, cleaning nozzle tip etc. I have had to use some of the other values like percent complete, time remaining, bed target temp and bed current temp to work out the actual state of affairs (finished / idle) at the end of a print. All of these work in the programs unlike Gcode state. I'm hoping @Michel Kohanim can shed some light on why programs are triggering on but not evaluating gcode state properly.

Anyway, thanks for looking into this and for your time and effort in developing this plugin.

-Xathros

Edited 8 hours ago8 hr by Xathros