Kissell

Comments

• Yeah, that makes sense.  

  in Using at execute (@execute) commands Comment by Kissell August 2015
• Yeah, that fixed it, thanks!   I didn't realize I had to call it by command name in the extcommands.xml file instead of just passing it the path to the executable.

  in Using at execute (@execute) commands Comment by Kissell August 2015
• Okay, I found information here: http://www.repetier-server.com/manuals/0.50/index.html It says I need to create the file at /var/lib/Repetier-Server/database/extcommands.xml So I'll give that a try, I bet that fixes it

  in Using at execute (@execute) commands Comment by Kissell August 2015
• Okay, that makes sense, I am trying to pass in the path to the executable...  unfortunately I've been doing so through the gcode event dependent event editor inside RepetierServer.  I'm unable to find the extcommands.xml file on the file system.   O…

  in Using at execute (@execute) commands Comment by Kissell August 2015
• @debugcon and @pushmessage work when I type them in the console...  but they don't seem to work when I put them in lines of the gcode.   @execute doesn't seem to work at all...  not sure why.

  in Using at execute (@execute) commands Comment by Kissell August 2015
• +1

  in External Commands at Printer Level Comment by Kissell August 2015
• I haven't been able to get any of the @ commands to work...  I have push messages working, but adding "@pushmessage TEST" to my gcode doesn't send a message.

  in Using at execute (@execute) commands Comment by Kissell July 2015
• Oops, I guess it's version 0.60.4.

  in Using at execute (@execute) commands Comment by Kissell July 2015