I actually figured out a solution. I made an additional trigger function and turned off all the tools and rest the machine with the command M999.
Posts made by msugar
-
RE: Emergency Stop
-
RE: Calling Separate Trigger Files
@deckingman Would these pins be the ones labeled E_2stop, E_3stop etc.? If so these are the ones I currently have them wired into. What are the appropriate names of these pins? based on your response it seems as if I have the wrong name for the physical pin.
-
RE: Calling Separate Trigger Files
@deckingman Both of these suggestions are already done. I think my problem is that my expansion Duex5 is not monitoring the inputs or I have a problem with my code monitoring inputs. I am trying to monitor inputs on the expansion board so that if the inputs are not met then the move motors will not be triggered.
-
RE: Emergency Stop
I am not using these outputs for actual fans I am using the fan pins as general outputs for different tools. It is turning on the pins for fans 4-7 on the duex 5 expansion board.
-
Duex5 Pin callout names
Hi,
I have an expansion board Duex5 that I am using with my Duet2 WIFI board and I am not sure if I am calling the pins correctly. On the expansion board I am using pins E2-Stop, E3-stop and E4-stop as general inputs. I am trying to set it up so that if the condition is not met then the program will not run a path. Once the conditions are met the machine can run a path. If at any point a condition changes state during a path I would like the machine to pause or even just have a screen popup. I know to call the message M581 is used. I noticed on your diagram with the pins there are a few different names to call them out. What are the names I should be using? I have used all of the names that I can see but it doesn't seem to be calling them correctly. Is there a way that I can see what I being triggered with the pin names?
Firmware: 3.4.6
Config:
42aa476b-00e0-4dc2-acc8-f7e0ff02e980-config.g -
Emergency Stop
Hi,
I added a physical E-Stop to the system that will cut power to the board and my expansion board. After the power is cut, I want the fans to remain off. Right now they are turning back on when power is restored and the emergency stop is disengaged. Is there a command that will allow me to turn them off and remain off or even reset them to their initial state. I saw the command M911 is to configure auto save on loss of power. Would this be appropriate in this situation?I am using firmware 3.4.6 and here is the config file
f905920d-4d54-4cba-be09-73d3b5addd86-config.g -
Calling Separate Trigger Files
Hi,
I am trying to call a separate trigger file similar to how a pause is called by T1. I made a new trigger g-code file named "TRIGGER2.g" and to call it in the config by the command "M582 T2" but it doesn't seem to be executing. Is this because of the name of the file or should I be calling it differently?
-
RE: Expansion Board
@Herve_Smith
Here is the config file:
config.gI was able to get the fans to trigger by using M950 instead of M42. How would I get the extruder heater to trigger? I have an LED strip connected to e0 so I just need to trigger it.
-
Expansion Board
I recently changed the firmware version from 2.05 to 3.4.6 and I am having a lot of difficulties' getting the same outputs to trigger with the same commands. I am trying to trigger the FAN4 output using M42 P24 S1 and I am getting an error stating that the P value is too high. With firmware 2.05 this command would trigger correctly. I have made a new config file. Could this be because the new expansion board is not being recognized. How would I know if my duet board is recognizing the expansion board? How does the pin callout work with the new firmware? Is it different then what was used in firmware 2.05? I am using the duex5 expansion board and the main board is the duet 2 Wi-Fi.
Is there a number I can call to get support with this problem?
-
Error: Filename too long
I am using the board DUET2 MAIN W07341 and I keep receiving an error message saying that the file name is too long. It seems that this error happens randomly because I uploaded g code files with longer names earlier in the day and did not get the error. The error will also keep notifying me continuously. I am unsure what the error is referring to and what a solution would be. I have attached a picture of the error for reference.
Additional info:
- Firmware: 2.05.1
- Wifi Server: 1.23
- Web Interface Version: 1.22.6
- M122: M122.txt