Help diagnose erratic machine control

Home › Forums › TinyG › TinyG Support › Help diagnose erratic machine control

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • August 20, 2016 at 10:17 am #9884
    matt_o_70
    Member

    Hi
    I have had a tinyG purchased 1/21/2014 – That I struggle with a bit. Here is what happens currently.

    At first power up I can consistently hit the Home function and machine will find min limits and home correctly. Getting the machine to run and complete G code sometimes results in a hung system. machine stuck/stopped no response to browser input. When this happens The SpOn LED on the board is now illuminated (PWM is also illuminated but that appears to be normal). This happens with spindle off – testing just the motors without any additional possible noise from running the router motor.

    hitting the reset button will usually fix the hung state. Software reset will not work.

    What date range applies to the “fuses” problem? How do I verify if fuses setting is a problem?

    Matt

    August 20, 2016 at 10:55 am #9885
    matt_o_70
    Member

    Performing the squares $test=3 – I just replicated the Hang condition and get the err: Machine is alarmed – Command not processed when trying to rerun.

    Off to find out how to read or error codes?

    from wiki: “When a limit is hit the machine enters an alarm state and signals this by shutting down all movement and flashing the Spindle Direction LED rapidly.” Since I don’t have a flashing Spindle Dir LED. So I am working on the premise that this is not a falsely triggered limit switch.

    • This reply was modified 8 years, 3 months ago by matt_o_70.
    • This reply was modified 8 years, 3 months ago by matt_o_70.
    August 20, 2016 at 1:29 pm #9888
    cmcgrath5035
    Moderator

    We need to know a bit more about your setup.

    Do you run from Chilipeppr, Coolterm or ___ ?
    Form what OS?

    Create a listing of your machine parameters ($$command), copy them and paste into a text file, post that to a Cloud drive and provide a URL for it.

    Your reported behavior – limit alarm but no flashing spindir. is odd.
    However, when limit is hit, firmware shuts down, so no response to commands is normal. the hard reset restarts firmware with the current location set to 0,0,0

    August 20, 2016 at 8:15 pm #9889
    matt_o_70
    Member

    I have been using XP, chilipeppr, Chrome. I just tried using coolterm today to run through the steps on the wiki to try to gain a better understanding of error / reveal any error codes once triggered to help diagnose.

    This same machine (Openbuilds OX) works 100% under parallel port and Mach3 control no errors – but I am trying to move to x64 Win7/10 environment and so trying this TinyG via USB still on the old XP box.

    Still need to set up the Win10 PC – with TinyG/Chilipeppr to see if that changes anything.

    $$ dump as text file:
    https://drive.google.com/open?id=0BxnzhuMpoz3BR2JUM01kYWczak0

    • This reply was modified 8 years, 2 months ago by matt_o_70.
    August 25, 2016 at 6:01 am #9894
    cmcgrath5035
    Moderator

    Params look OK, with these suggestions:
    Set
    $p1pof = 0.0 (That will shut off pwmled when spindle should be off)
    $xvm, $xfr, $yvm and $yfr are normally suggested at 16000, where you have 2500. That will simply make you machine run a bit slower, should not be an issue
    Set $ex=2 when running Coolterm (RTS/CTS works better). The $ex setting when running Chilipeppr/SPJS does not matter; SPJS uses buffer fill flow control.

    What version of SPJS are you running?
    Is you XP machine 32bit? I don’t see a lot of folks running on XP anymore.
    Is the XP machine sort of “brain dead”?

    Open Windows task manager and look at CPU utilization.

    I have no Mach3 experience, but since it was born and matured on what we today would call brain dead hardware, it is likely more tolerant of the typical legacy XP machine performance.
    Chilipeppr and SPJS are both aggressively multithreaded and use the latest in javascript,

    You could try shutting Limits and homing to OFF ($xsn=0, etc) to see if that performs better with $test=3 or other simple test code.If it does, that might point to noise issues.

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.