How to view messages during operation

Home › Forums › TinyG › TinyG Support › How to view messages during operation

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • July 8, 2013 at 4:11 pm #4282
    mcgyvr
    Member

    When running TgFX how do you view system/ER messages from TinyG (for example the system shut down ER message).
    Can you have coolterm running at the same time as TgFX or is there somewhere in Tgfx to view those messages?
    Or do I just need to stream the gcode through coolterm and not use TgFX,etc..
    Or do I need to configure tinyG to send them somewhere or what?

    I’ve been having TONS of what I believe are noise related issues/shutdowns/resets,etc.. and I wanted to see if any messages I’m currently not seeing are indicating some problem or might help narrow down a solution.

    I’d like to see a log of the gcode buffer too or something.. I’ve been having issues where whole lines of Gcode are missed or skipped right over occasionally too..

    • This topic was modified 11 years, 4 months ago by mcgyvr.
    July 9, 2013 at 10:22 pm #4288
    Riley
    Keymaster

    I had lots of noise problems with my Panther PCB mill. Specifically the spindle. I solved it by getting an UPS and moving the power for the spindle to that and the computer to a different circuit. I would also make sure you have your homing switches set to disabled (if you are not using them) and if you are using them make sure you are using normally closed switches.

    That being said getting message from tgFX on err I can do. I will open and issue with this and get it coded up.

    If you think you are having noise issues I would see what it says via coolterm + xon for now for sending files.

    If your board starts blinking (red light flashing like reset) mid job then this sounds like it could be noise related.

    I had the option for a log on the gcode buffer but the way it was coded was to log to memory then write it out later. Needless to say it was a huge memory leak so I pulled it. I can open an debug mode as well that will write out a debug file of all tinyg responses process.

    Riley

    July 10, 2013 at 11:09 am #4295
    mcgyvr
    Member

    FYI..
    I am using NC limit/homing switches..
    My issues so far have been
    #1-blinking board mid job
    #2-“supposed” tripped limit switch mid job but not even close to the switches.
    When #2 has happened TgFx has popped up the “a limit switch has been triggered click here to reset.blah blah dialog.
    BUT at that time it also went “crazy” in that the steppers went FULL speed (as in WAY faster than my max velocity is set for) and “sounded” like it was stripping all the threads in my leadscrews. The axis doesn’t move as speeds that fast cause my leadscrews to bind (for lack of a better term) but I just don’t know why it would go into that “crazy..way over max velocity speed cycle”

    I don’t have a spindle to attribute noise too but rather a pneumatic cylinder that is triggered with the coolant pin.. But its running to a SSR and I have flyback diodes across the solenoid valves. I am powering the solenoids from the same 24V supply as TinyG uses though and am going to try to separate it on its own 24V supply.. However seeing as the gcode runs perfectly with coolterm Xon and I’m not seeing those issues I suspect its more of a bug somewhere vs a noise issue.

    I do have shielded limit switch wiring (grounded shield at tinyG) and NC switches and have placed a .1uF cap across each switch line. But the problems still occur.. But only when running TgFx or Matt Stocks android app
    And I did notice $ex was set to 0 in the tinyG config by default.. I now have it at 1 and will try again..
    I assume that its ok to have $ex=1 when using TgFx or the android app??? right?

    • This reply was modified 11 years, 4 months ago by mcgyvr.
    July 10, 2013 at 5:06 pm #4300
    Riley
    Keymaster

    Interesting. Matt and I use a different flow control mechanism than XON. I would say that running tgFX or matt’s code causes this to trigger as “coincident” however if you continue to see it work in coolterm perhaps not. Does this happen on all gcode files? Or specific ones? If its on specific ones I will need to gcode files to replicate this.

    tgFX will turn $ex=0 on connect btw.

    I looked up why the limit switch message would be presented. Its due to an “er” message from TinyG. This perhaps is not the best single identifier for this case.

    In ResponseParser.java insert this line to line #435
    <br>
    Main.postConsoleMessage(“ERROR: ” + message);
    <br>
    And try your whole setup again. This should post a message to the console telling you the whole json message that TinyG sent. It should start with “er”.

    I would like to know the rest of it.

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