Posts made by PayTor

I have the following code in a macro called "Start" which runs perfectly fine when I run it on its own. Basically, I just want the printer to pause at a certain location and wait for an external signal to resume.

G1 Y96 X68 F3000
G1 Z5 F500
M581 E5 S1 T2 ;Start the trigger (trigger2 file)
M25 ;Pause and wait for a switch to be pressed to resume
M581 E5 S-1 T2 ;Turn off the trigger

I want to run this macro from a GCode file using this command: "M98 P/Macros/Start". The issue is that all other commands in the Start macro run just fine except for the trigger portion. The trigger doesn't work this way. I have to put the trigger commands inside the GCode file to run them.

This is important for me because I have different machines and the setting is slightly different for each one. I want to have the same line (M98 P/Macros/Start) in all the gcodes and don't deal with creating a new GCode file for each machine.

Is there a way around this?

David, I sent the file to your email.

I uploaded the gcode to the board through the web interface and just clicked on it and started it.

I found an interesting/annoying bug here! I slice my STL models and save each layer into a different gcode file. When I reach the file that has "layer122.gode" in the name this error happens. It seems for some reason the software confuses those layers with M122 command. When I change the file name it solves the issue!

Duet Ethernet: DuetEthernetFirmware-1.19 and DuetWebControl-1.19

No, it doesn't. I reset the board and it didn't help. Also, I upgraded to the newest firmware after I saw that issue, and it's still not solved.

Yes, I'm using the web interface for sending the gcodes. I'm using a separate laptop just for running this machine and I don't remember ever sending the M122 command before.

Hi, I'm using duet ethernet with the latest stable firmware and web interface versions. The problem is whenever I send a GCode to the machine, no matter what the commands are, it just returns a diagnostics message starting with "====Diagnostics===" as if I have sent M122. All the commands in macros work, however. If I copy the same gcode to a macro it works. Does anyone know what is going on?

Works perfectly, Thanks.

I don't have an M563 tool definition command. I put M140 H-1 on top of my config.g, still didn't work.

M140 H-1 removes the Bed Heater temperature control box from the web interface, but still the same issue. The LED flashes for second and turns off.

Hi, I'm trying to use the heat bed output of a DuetEthernet as a regular IO. I've used "M307 H0 A-1 C-1 D-1" command to disable the bed heater first. I can actually confirm that it's disabled with "M307 H0". But then when I use "M42 P0 S255" to turn it on manually, the bed heat LED on the board flashes and turns off quickly. Is there anything I'm missing here? I can control all other heater outputs like this (E0-E6). Bed heater is the only one I can't control.

I think I'll go with the Arduino option for now then. Thank you all for your responses.

I cannot touch the surface and the thermistor doesn't give me the right number with a gap there.

@elmoret:

What are you looking to accomplish with this? There might be an easier way.

That's a good question! I'm not using this for an FDM machine. It's a robotic application. I want to measure the temperature of a surface and wait for it to cool down to a room temperature (20-25 deg C for instance) and then continue the moving operation. I'm looking for an easy solution where I don't need design a board or modify the firmware significantly.

One way I can think of is to attach the sensor to an Arduino and then use trigger macros on the Duet. Any other ideas?

This one for instance:

http://www.robotshop.com/en/ir-temperature-sensor.html?gclid=Cj0KEQjwp83KBRC2kev0tZzExLkBEiQAYxYXOjPr3nDwT9Q8XR45iIP4-Gm1Pzp037zmrYMhpKWB9rIaApLZ8P8HAQ

Do you know of any interface boards that I can purchase for something like this?

I was just wondering if it's possible to connect an IR sensor to Duet Ethernet instead of a thermistor. Is there a daughter board to buy to get this functionality?

I was commanding a lot of numbers and was confused what was going on. I wrote 50 here as an example because I thought there was something wrong with my setup and the number doesn't actually matter. Anyway, thanks for the replies. I think I need to figure out a workaround for what I want to do.

@elmoret:

Maybe as a short term workaround, wait until it gets to 40C and then pause for X seconds?

Thanks, that's what I'm doing now, but that pause doesn't get me back to the same temperature each time. As you said, it's a good short-term workaround.

I found the issue!

M109 RXX works for any number greater than or equal to 40. Any number below 40 doesn't work. In my application, I need to wait for the heater to get to the room temperature. Is there any way I can do that?