X and Z limit contacts non responsive and no SP control

Home › Forums › TinyG › TinyG Support › X and Z limit contacts non responsive and no SP control

Tagged: 

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • October 2, 2016 at 11:47 pm #9939
    TayTech
    Member

    Hey guys,
    Not sure what is going on but it looks like the board may have an issue. shorting out the ontacts on the board for both X and Z axis does nothing now, no Spdir flash or anything. Also I would use M03 to start up the spindle relay and now M03 does nothing, no light/ output… the Y axis limit still works and the motors outputs are fine but maybe a 3V power line is out or something??

    October 3, 2016 at 6:10 am #9941
    cmcgrath5035
    Moderator

    Can you provide a parameter ist($$); copy to a cloud drive an provide a link.

    When you say ‘shorting out”, you connecting to ground or +3v?

    From you description, you know what to expect. Did your setup work, then stop?

    October 3, 2016 at 7:15 am #9942
    TayTech
    Member

    Sorry, I’m unsure what you mean in regards to the parameter ist etc.. Im just using chillipeppr and type in m03 in the gcode window and it used to turn on the spOn light and drive the spOn terminal high to 3v but now it does nothing. I mean I have my limits set to NO so if I close the contact between Xmin amd ground it should either act as a limit or flash the spdir error but now it doesnt do anything. It has all been working up until recently. I disconnected all cables info the left side of my V8 board and de powered overnight etc. Even flashed firmware to latest stable (.20) but no change.
    Thanks for your quick response!
    Mitch

    October 5, 2016 at 10:00 pm #9952
    TayTech
    Member

    I’m going up to my workshop this weekend (nearly 2 hours away) so any help would be great before I go please 🙂

    October 8, 2016 at 7:12 am #9954
    TayTech
    Member

    Anyone?

    October 9, 2016 at 10:18 pm #9955
    cmcgrath5035
    Moderator

    Sorry, obviously missed your time line.
    Typo on my part, the $$ command entered into the CP Command Window generates a Parameter list.
    Those parameters reveal a lot about various aspects of your machine setup.
    They are easiest to view in a cloud drive file rather than posted directly here in the forum tool.

    I suggest getting your machine up and running, jogging, running known good test Gcode, with limits turned off. Once the basics are well in hand, introduce homing, limits and advanced functionality.

    • This reply was modified 8 years, 2 months ago by cmcgrath5035.
    October 10, 2016 at 8:31 am #9957
    TayTech
    Member

    Thanks for getting back to me 🙂 The machine had been working well finally up until this happening the other day. I will enter CP into the machine and send you a link this weekend Sydney time. I finally got motors running smoothly and limits and jerk pretty stable so was disappointing to have 2/3 limits stop working but this machine is my first and I have learnt a LOT through many problems setting everything up.
    Camming software is where my headache is at and what I am playing with now but don’t really like the idea of playing with it without limits set incase something does go funny…
    Cheers for the help

    October 15, 2016 at 6:00 am #9962
    TayTech
    Member

    Please see below
    https://docs.google.com/document/d/1enferqcmH03hCT11j6H5_Z01NhQMbLQLc_ueUAh9HyI/edit?usp=sharing

    Thanks!!

    October 15, 2016 at 7:42 am #9963
    cmcgrath5035
    Moderator

    My best guess is that something (some electrical event) has resulted in EEPROM corruption.

    The tell tales for me are parameters that has ‘illogical’ values – values I doubt you would intentionally enter that are not part of any default set of values
    Some that catch my eye are:
    [xlv] x latch velocity 102 mm/min
    [xlb] x latch backoff 5.004 mm
    [xzb] x zero backoff 0.991 mm
    [yjd] y junction deviation 0.0508 mm (larger is faster)
    (not a complete list, just a hint as to what look like ‘odd’ values)

    My suggestion would be to reset your tinyG parameters to default, then re-enter values for your OX.

    Steps
    1. Make sure you have a parameter list backup – you will need to reenter most.
    2. Use CP on Chrome or CoolTerm
    3. Send the command $defa=1, which will reset tinyG to factory defaults (FW compiled in parameters)
    3.5 After the $defa=1, have a look at the parameter list ($$), it will look nothing like your Ox setup, it is targeted toward board test.
    4. Restart tinyG (reset button), connect with CP or CoolTerm
    5. Re-enter all your unique parameters, one at a time, from the CoolTerm Command line or the CP Serial Port Console.
    Make sure you are in mm mode (not inch) when entering parameters.
    Avoid the CP parameter widget, enter one parameter at a time from the Command Line Interface (CLI) or Serial Port Console.
    6. When you are done (and hopefully successful), re-create the document you posted above.
    It is an excellent, human readable way to archive your settings should this event happen again.

    Hope that helps

    October 17, 2016 at 8:14 pm #9966
    TayTech
    Member

    Thanks again for getting back to me.
    The strange thing is those parameters were like that from the get go. As in I would put the numbers in and after reseting the board or changing something else it would change them slightly, it has worked fine while they were like that so that is not new to the system… I can wipe it but everything says it should be reading correctly doesn’t it? It’s just frustrating cause I get to go up there once a week (2 hours drive away) and I can try a few things but it might be month before I can use it again if this doesn’t work.
    Cheers for the instructions
    Mitch

    October 18, 2016 at 7:01 am #9968
    cmcgrath5035
    Moderator

    Your reported behavior is very unusual indeed, I’ll go so far as to say “not right”.
    Some ‘distortion’ of parameters is typical if parameters are entered in inch mode then displayed in mm( rounding error).
    Your time to machine situation does makes things difficult, in this worls there is always ‘one more tweak’ to be made.

    October 22, 2016 at 5:09 am #9976
    TayTech
    Member

    Hey again,
    Just got up here. Reset the board then just put in limit settings but no dice. Nothing causing the SpDir to light up at all and the M03 command doesn’t activate the SpOn light either. Think the 3V portion of the board is dead.
    Should I just buy a new one? Don’t really have time to do anymore testing.
    Cheers
    Mitch

    October 23, 2016 at 9:35 pm #9981
    cmcgrath5035
    Moderator

    Unless you are REALLLY GOOD at fine pitch soldering, after debugging, I suggest buy a new board.

    October 23, 2016 at 10:18 pm #9983
    TayTech
    Member

    Dam… just bought another. Not a cheap exercise with $60US shipping but guess I had to!
    Thanks for trying to help.
    Mitch

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