alden

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 702 total)
1 2 3 4 … 45 46 47
  • Author
    Posts
  • May 24, 2015 at 4:59 pm in reply to: Communication issue with TinyG #7741
    alden
    Member

    Eduardo,

    Thanks for posting your experience. I have some questions to diagnose this.

    – Are you using the JSON protocol? It appears so, but I want to confirm.

    – Which parameters time out? None of them should. Could it be that you are writing parameters when the queue is full? You can determine how many of the 254 bytes in the receive queue are available by requesting (rx:n}. It returns the number of available bytes.

    As for SR’s, you should set up a listener for them and handle them when they come in. They are not synchronous commands such as request/response pairs. The normal communications is:
    – Send request, get response almost immediately. Listen for SRs. Most people look for the stat:3, which means the machine has stopped.

    • This reply was modified 9 years, 7 months ago by alden.
    May 18, 2015 at 6:49 am in reply to: Vref adjustment for parallel stepper motor in Y axis #7714
    alden
    Member

    Putting 2 NEMA17’s (or NEMA23’s) in parallel will not damage the driver. Adjust the Vref until the driver runs smoothly. If the drivers take too much current – as might be the case with very large NEMA23s – the driver may go into thermal shutdown but should not be damaged. In that case we recommend fan cooling.

    May 17, 2015 at 1:16 pm in reply to: M53 Gcode Implementation? #7713
    alden
    Member

    Thanks for the note. We have been refactoring the digital IO system and will include M53 as an option.

    May 14, 2015 at 10:24 pm in reply to: Incorrect Arc Movement #7710
    alden
    Member

    Thank you for the report. We are still doing some work on arcs. Thank you for your patience – we should have this resolved soon.

    March 15, 2015 at 5:54 am in reply to: Y axis motors stopped working #7543
    alden
    Member

    It sounds like the motor / wiring. Stuttering may be an indication of thermal shutdown of the chip (see if the chip is hot to the touch), but more likely one of the motor phases is not connected or is intermittently connected.

    March 13, 2015 at 6:48 pm in reply to: What is going wrong? Machine not following g code #7534
    alden
    Member

    Finally back to my shop. I’ve just run part1.nc on build 440.14 – our current edge build. It’s working well – other than I don’t have quite enough table for it and it crashes into the edge on my Shapeoko2. 440.14 is what Chilipeppr is running these days so I’d recommend updating to that build.

    March 7, 2015 at 11:37 am in reply to: What is going wrong? Machine not following g code #7513
    alden
    Member

    Can you post the makercam file somewhere where we could try it out?

    –thanks

    March 7, 2015 at 5:39 am in reply to: trimming motor current #7510
    alden
    Member

    Try a series of moves going back and forth, like
    g1 f1000 x1000
    g1 f1000 x0

    Or simply
    g1 f1000 x1000
    x0
    y1000
    y0
    z1000
    z0

    …etc

    You can enter them individually or in the Coolterm “Send String” dialog in the Communications menu item. Do you get any movement?

    March 7, 2015 at 5:35 am in reply to: What is going wrong? Machine not following g code #7509
    alden
    Member

    Can you please post what build number you are on? That’s the $fb value in the $ display — Thanks

    March 4, 2015 at 9:05 am in reply to: Y axis motors stopped working #7502
    alden
    Member

    Have you checked your stepper wiring? If the problem moved from the Y axis to motor 4 that’s in indication that something’s wrong in the motor, or often the wiring itself. Your symptoms sound like 1 of the 2 motor phases is not energizing.

    If you have a spare motor lying around try attaching that to the Y axis (Motor 2, I assume) and see if that works – or just re-arrange your profile to map the X axis to motor 2 and see if that works. This would be useful to isolate the problem between the motor driver and the the wiring/motor/mechanical system.

    February 26, 2015 at 7:16 am in reply to: Finding hex file for new edge build #7465
    alden
    Member

    We’ll get that posted to the download page shortly. Sorry for the delay.

    February 14, 2015 at 6:51 am in reply to: Connection arduino to tinyg through a serial port #7364
    alden
    Member

    The RX and TX lines on the v7 and v8 are set up to be 5v tolerant specifically so you can connect one up to an Arduino.

    Realize that you cannot use the USB and the RX/TX connection at the same time, but you may be able to “snoop” on the RX/TX with the USB. But it’s probably best to unplug the USB.

    • This reply was modified 9 years, 10 months ago by alden.
    November 29, 2014 at 7:38 am in reply to: On the edge? #7046
    alden
    Member

    It’s past time to move the edge branch to Master. Edge is fine and recommended at this point. At that point edge will become more “edgy” as we introduce new functionality.

    November 2, 2014 at 2:36 pm in reply to: JSON level 5 responses are hard to check for correctness #6963
    alden
    Member

    How are you parsing? Most UI’s using JSON are using the native JSON capabilities in JavaScript, Python or whatever. Floats are floats, so it doesn’t matter.

    There is a list of precisions in the config_app.c file. The table sets what precision the results are returned. There may be a few special cases where the answer may be different in mm mode or inches.

    November 2, 2014 at 2:33 pm in reply to: gshield v5 and Seeduino v3 issues #6962
    alden
    Member

    I think I cross posted to the wrong thread. The seeeduino is not an Arduino R3 pinout and the power connector is different. See here for guidance.

    https://github.com/synthetos/grblShield/wiki/gShield-v5-Notes#5-volt-power-right-position

  • Author
    Posts
Viewing 15 posts - 31 through 45 (of 702 total)
1 2 3 4 … 45 46 47