breiler / ugs_candy_mechanics Goto Github PK

Is it possible to have the 'localhost-4200/#' text removed at the bottom left? We couldn't figure out how to stop this from coming up.

@breiler another thought - It would be good to figure out how to build in commands to make the motors power off when idle so they are not staying really hot and using power.
In normal UGS (with the command line) this can be achieved by setting $1=100 (power off when idle) Then, before a cut, it can be set to $1=255.

However, we have the 'loading' state where the fixture is in position to be loaded with chocolate. If there is no power to the Y motor, the force of the user pushing the chocolate into the fixture actually pushes the whole fixture away. If the motors have power, this effectively brakes the motor and provides resistance to the user putting the chocolate in.

So, is there a way of adding $1=255 when the sequence is at "load your chocolate" then it goes $1=100 after the cut and move to eject.

I tried to insert these commands directly into the environment file but as they aren't gcode commands it didn't work.
Any help appreciated!

Staff page: Our developer couldn't get the back button from this page to go to the last page the user was on. Instead it goes back to the very start.

Hi @breiler - I think it's at a point now that's really solid, thanks for all the help!
I'm having trouble packaging it through into a single application (i.e. an executable that will startup ugs as well as the pendant UX).
Is there a simple process for building a production ready package?

Is it possible for the machine to populate a txt file with the number of jobs it does every day? Just a time/date stamp and the name of the file?

Also, we have a little cancel switch when someone opens the machine to stop the job, which turns off the spindle and displays an error message. At the moment the error message doesn't make sense for a novice, so where could we find the source file for that to change it to something a bit more understandable to a new user?

Is it possible to have a button which refreshes the page? Like F5? Once in a while the machine might lose connection to the program and it needs to be refreshed.

When it starts cutting, the progress bar immediately goes to 100%, then almost instantly back to 0, then continues to 100. Any ideas? Also, is there any way to make the progress go along accurately? Ideally it'd go steadily 0-100 instead of 0...1... 1.... 2..4....4.....4.......20.....21..22... etc. If not, no biggie, just wondering!

Can this auto-refresh to show new files? At the moment I have to hit F5 to refresh the page

Where is the source file for the 'homing machine' and 'moving to origin' text? It would be nice to be able to change these to something more fun and maybe style them a bit.

Is it possible to have a tabbed bit here? This was in the original doc I sent over but I forgot to follow up on it. - i.e. new and redo files - see below image. Ideally, when a file has been created, it goes to the gcode folder, then when it is finished being done on the machine, it gets put into an oldgcode folder. This way, in a busy scenario the new folder doesn't get clogged up, but still if someone wanted to re-do they could access the file.

Unload: this sends a gcode command that can be in the environment file. It would home, then move the y axis to unload, then to load

Force unload: this sends a gcode command that can be in the environment file. It would home, then move the y axis to unload and keep it there in case the chocolate didn't eject automatically.

Change milling bit: this sends a gcode command that can be in the environment file. In case someone replaces the milling bit, it would move the machine to a point where the user could remove the milling bit, insert a new one, and use a billet of plastic at the exact right height to insert a new bit the right height.

Return to start button: this sends a gcode command that can be in the environment file. This would home, and then move to origin. At the moment it moves using the relative gcode command so if you are already at the origin, it moves it across to a new origin. It needs to home first.