Torchmate 4x4 freezes after G Code line

Discussion in 'CNC Cutting' started by MLR_WeldShop, Jun 16, 2017.

  1. MLR_WeldShop

    MLR_WeldShop New Member

    Joined:
    Jun 16, 2017
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    So I've got a Torchmate 4x4 plasma table. Running the latest VMD. Yesterday about midway through the day, the table ceased to function properly.

    It seems that every time the VMD reads the line "M65" (torch shut off), the program stops. What I mean by that is, if I'm running a job that's a square piece with a circular hole in it, the torch will move to position, sense the material, fire torch, move through the shape, shut torch off......and then nothing. It doesn't retract, it doesn't move. I can reset the job and run from the next cut, but again, when the G-code encounters another M65, the same problem occurs.

    I'm not sure what is causing this. Nothing about the machine has changed except the plasma unit, which was changed from a Tomahawk 1000 to a Powermax 125. This error is stopping every job I do, regardless of whether it was designed in Torchmate CAD or pulled from the shape library in VMD.

    I'm losing time right now. I've called customer service and I'm waiting on a call today from whoever I was speaking to yesterday's supervisor. I was wondering if anyone here understands what exactly is going on with my machine.
     
  2. Dnmeistr-LECS

    Dnmeistr-LECS Well-Known Member Staff Member

    Joined:
    Dec 22, 2015
    Messages:
    371
    Likes Received:
    87
    Trophy Points:
    58
    You can check your Input Line, Aux 1 under Machine Settings if it is set to Cut Sense change it to User, that is a possibility.
     
  3. MLR_WeldShop

    MLR_WeldShop New Member

    Joined:
    Jun 16, 2017
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Thank you for the response, I just checked the Inputs tab under Machine Settings. Everything is set to "User". Any other suggestions?
     
  4. inkognito

    inkognito Member

    Joined:
    May 17, 2016
    Messages:
    20
    Likes Received:
    2
    Trophy Points:
    18
    symptoms indicate input 1 is permanently asserted resulting in the controller believing the arc is transferred on M64 but not detecting it's deasserted when the arc is turned off with M65
    does the start of cut look poor due to the system not waiting for the arc to transfer? if true then this confirms the input isn't working.
    call tech support who'll walk you through identifying root cause
     

Share This Page