I am trying to make a skin that can monitor Bambu lab 3D printer telemetries.
It will be relying on a command line program called bambu-lab-observer.
That program will do all the heavy lifting, communicating over the network using MQTT protocols.
What i need help with here is the Runcommand plugin not playing nice with that software.
This is what happens when I run the program outside of Rainmeter:It updates live, maybe every second ish.
But if i run it through Runcommand, the CMD window is blacked out, no output:That is, until I manually close the CMD window, and only THEN does the measure output data, and produces an output file (readout.txt).
I then naively made a automated close command fire every second, and it worked. But, i celebrated too early.
that of cause will just make the program reconnect constantly, taxing the network, and make it harder later to parse out the relevant information i am interested in.
Do you think the program is just made in a unusual way and impossible to get around? or am i using RunCommand wrong here?
On another note:
I am aware of the MQTT plugin that would make my life so much easier.
But after a lot of struggle with that, I decided to explore this other avenue to the end first.
I could upload the skin if you own a Bambu printer and want to test.
You will have to input your printer info and credentials into the JSON file.
It will be relying on a command line program called bambu-lab-observer.
That program will do all the heavy lifting, communicating over the network using MQTT protocols.
What i need help with here is the Runcommand plugin not playing nice with that software.
This is what happens when I run the program outside of Rainmeter:It updates live, maybe every second ish.
But if i run it through Runcommand, the CMD window is blacked out, no output:
Code:
[MeasureRun]Measure=PluginPlugin=RunCommandStartInFolder=#@#exe\Bambu\Parameter="bambu-lab-observer.exe"OutputType=ANSIOutputFile=#@#exe\Bambu\readout.txtState=ShowI then naively made a automated close command fire every second, and it worked. But, i celebrated too early.
that of cause will just make the program reconnect constantly, taxing the network, and make it harder later to parse out the relevant information i am interested in.
Do you think the program is just made in a unusual way and impossible to get around? or am i using RunCommand wrong here?
On another note:
I am aware of the MQTT plugin that would make my life so much easier.
But after a lot of struggle with that, I decided to explore this other avenue to the end first.
I could upload the skin if you own a Bambu printer and want to test.
You will have to input your printer info and credentials into the JSON file.
Statistics: Posted by StArL0rd84 — Yesterday, 7:37 pm — Replies 1 — Views 87