![]() In order to better structure these steps, we create functions. Here you can use them to define more complex g-code sequences. The two typical places are in Printer Configuration -> G-Code -> Quick Commands or Wizards. If a button has no g-code like the “Cancel” button in this example only the dialog gets closed. Any selection of a button closes the dialog for all users and executes the g-code associated with that button. The user can now move the dialog around dragging it at the header (except on the touch interface) and select one of the buttons. In Repetier-Server Monitor dashboard you will see a warning icon when dialogs from printer are available. If they are in a global window they won’t see the dialog until they switch to printer. Last step is calling which finally shows the dialog to all users that are on the printer interface. Put it in quotes and split commands with \n. The first is the button text and the second one is the g-code to execute. There is no limit but too many might look not so nice. If the text contains spaces, put it in double quotes like shown in the example. The first parameter is the messege in the dialog and the second one the header text. So how does it work? With you initiate the creation of a dialog box. Now save the new settings and try to trigger it. Here we enter our warning: Filament is low. If you are unfamiliar with regular expressions, there are many tutorials or just ask wikipedia. If you are unsure I advise to pretest your expression in an online tool like. If you omit these chars any line containing the text “filament_low” anywhere would match. So only lines that exactly contain that term are matched. The ^ means the line must start with this. In our case the expression is “^filament_low$”. Next is the regular expression that should match the output. So you add a event – the event name must not contain spaces! It is a message send to all connected interfaces so you can also use this to trigger some other functions. We want to get a warning when this happens without watching the console constantly. When that is reached the firmware writes “filament_low” once. Lets assume you have added a trigger to your printer that detects when the spool has only 90% capacity. There is a sub tab called Response to Event which you will need. So it is now time to learn the more advanced settings in the Printer Settings->G-Code tab. More likely is that you want some printer action trigger a message. ![]() a warning that you need to do xy soon or before a command to inform the user why you are going to pause. ![]() In the generated g-code you might want to add a info at some special places, e.g. While you can add them anywhere they should of course only appear when there is a reason. Now that you know how to show them the big question is where to add them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |