wahran

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • June 2, 2018 at 5:24 pm in reply to: Building g2core for DUE-gshield problems #11006
    wahran
    Member

    I am not a Goko user either, I am not committed to anything yet, I was just getting a feel for different g code senders. I tried both UGS and Goko, and they both worked with the older firmware (I believe 078?), i.e. steppers on axis moved when jogged or gcode file downloaded.
    I have been using the programming port for flashing the firmware and the native USB port for talking to the board.
    I gave up on Windows 7 and the COM driver for now, I have been using a Windows 10 laptop, where the driver loaded without a glitch, I can even connect and “talk” to the board from a terminal session in putty, but no luck with UGS or Goko. Is there a specific version of UGS that works with 100.xx?
    Thanks.

    June 2, 2018 at 11:09 am in reply to: Building g2core for DUE-gshield problems #11004
    wahran
    Member

    Thank you both for the quick replies.

    cmcgrath5035 :
    I started with this whole think a couple days ago, and did as much reading as possible to get me going, some of it, I am sure outdated (I have only seen the mention of 2 COM ports, data and control, must have been reading old stuff…) Thanks for the pointers. I tried the 101.02 firmware and I get the same “TinyG v2” device issue, so I guess that is a driver issue.
    Booted my Win10 laptop, driver loads a generic COM port, Connects with Goko or UGS 2.0 , but can’t get anything to work (mostly jogging…), will have to spend some more time there, now that I know the firmware is good.

    Zootalaws: First day with Git ;-( I cloned the g2.git –recursive, without any other parameters, so I guess the latest, whatever that is, have to read on how to select a specific branch. Sorry, I saw my post going into 3 long paragraphs and didn’t want to make it too painful to read…

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