dswillows

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • January 12, 2020 at 12:59 pm in reply to: tinyg odd communication #11756
    dswillows
    Member

    I see you have previous posts that mentions this- unfortunately the same error/behaviour after the factory default 🙁
    You mention in forums about corrupted EEPROM, and the steps for FW re-install …I will try those instructions next

    January 11, 2020 at 5:13 pm in reply to: tinyg odd communication #11754
    dswillows
    Member

    On an aside, sending any gcode returns an error- such as:

    tinyg [mm] err: Invalid or malformed command: G0X100

    January 4, 2020 at 11:29 am in reply to: tinyg odd communication #11743
    dswillows
    Member

    Info was provided as I was asked to elaborate on the descriptor, “lost control”

    -no, the pi and the limits are not a concern, I have stripped back to starting from scratch, just coolterm (direct USB from win10). Limits are disabled.

    Back to the setup problem at hand,
    I’m trying to diagnose tinyg communications. So if test isn’t functioning, what process would one follow to test communication/operation of the board?

    January 3, 2020 at 11:07 am in reply to: tinyg odd communication #11740
    dswillows
    Member

    Thanks for the knowledge on $ej.

    Defining lost control:
    Had a functioning machine using chilipeppr, cutting 3D paths with what seemed like random kills during larger gcode files.
    The suspects at that time were the limits with false triggers or maybe com errors due to using a piZeroW for JSON server. I left this unresolved for a time, and looking at resolving this recently I peeled everything back to the beginning (hence the $test) due to strange behaviour, such as:
    Strange things in chilipeppr, like energize motors cmd seems to work(motor LEDs emit green & test motor resists). However I have no manual jog or any gcode spits out a quick LED pulse of tx & rx without performing motion.
    And the strange thing in coolterm as mentioned is the $test cmd failing.

    So currently I’m back to the board’s setup instructions,start fresh… just coolterm and one small test motor driven with tinyg internal driver.

    January 2, 2020 at 10:02 am in reply to: tinyg odd communication #11738
    dswillows
    Member

    Thanks for the inquiry- I did try setting/aligning both values, no dice. I thought maybe setting the json tag ($ej) to 1, however it seems the variable can’t be changed(?)

    Some background: This tinyg board was functioning in the past, I tried starting from the beginning to find out why I’ve lost control. The troubleshooting section doesn’t seem to have a similar experience to relate to 🙁

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)