Bill

Forum Replies Created

Viewing 3 posts - 16 through 18 (of 18 total)
  • Author
    Posts
  • Bill
    Member

    What you describe does sound strange.
    A: I think the strange is I send one GCode command and a batch of GCode commands, the result is different when I trigger the limit switch. When I send one command, it can act correctly, but a batch of commands, it can’t.

    What steps do you take to bring tinyG back to an operating state?
    A reset?
    A: I will press the reset button

    Are you using tinyGV8 or tinyG2?
    A: I am using TinyG V8, firmware is 0.97, the tool is coolterm

    Bill
    Member

    Thanks for your answer!!

    I am testing the limit switch of Y axis. The configuration are following:
    $YSN=2
    $YSX=2
    the other parameters use the default value.

    When I send single command, for example:
    G1 X100 Z100 A90 F400

    I turned on the Y limit switch(I use a switcher to simulate) during the motors are driving. All the motors can stop and the LED of SpDir on board can flash. It looks like normal. Then I send a text file that contains 25 GCode commands(the samiliar as the above command), I turn on the Y limit switch after around 5 seconds, the SpDir LED is not flashing and the board doesn’t go to the Reset status, the GCode is still executed and the motors is still running.

    I feel very strange, it looks like the firmware doesn’t respond the limit switch during the batch commands executed. Could you please give me any suggestion?

    Thanks!!

    Bill

    Bill
    Member

    Thanks for your answer!!

    When are you going to release the TinyG2 and firmware 0.98?

    If we use LabView as interface developing tool, is it possible?

Viewing 3 posts - 16 through 18 (of 18 total)