alden

Forum Replies Created

Viewing 15 posts - 316 through 330 (of 702 total)
1 2 3 … 21 22 23 … 45 46 47
  • Author
    Posts
  • September 9, 2013 at 8:39 am in reply to: Modification for cooling grblshield v2 #4487
    alden
    Member

    The board is double sided so there are no interior traces. Everything you are going to cut through you can see on the top and bottom. Both top and bottom cooling planes are ground, so they can touch electrically. It goes without saying – be careful.

    September 9, 2013 at 6:49 am in reply to: Board won't execute GCode #4486
    alden
    Member

    Not sure what’s going on here. Your command response (“r”) returns with status code 0 (OK). The status report (?) indicates that machine is still running, which is weird. WHat settings did you change? Can you please post a complete $$ dump?

    Thanks

    –Alden

    September 7, 2013 at 8:57 pm in reply to: Board Lock and Motors Occasionally Reverse #4478
    alden
    Member

    One other thing to note: We just discovered that if you set the motor timeout to zero – and the power management mode to 0 the axis will not move. It will only make some noise. We’ll fix this quickly.

    September 7, 2013 at 1:03 pm in reply to: TinyG Heatsink Question #4465
    alden
    Member

    Yes, that is correct. If you do this be sure you do not bridge out of the ground “lanes” under the chip. This probably means milling your heatsink.

    Another way to do this without drilling the holes is to use a Berquist (or similar) double-sided sticky, electrically insulating, thermally conductive pad. Something like this:
    http://www.digikey.com/product-detail/en/BP100-0.008-00-1010/BER159-ND/307781

    I’ve had good luck with this. You can just cover the entire back of the board and pop a surplus Duron or other heatsink on that’s the approximate size you need.

    September 7, 2013 at 7:36 am in reply to: Board Lock and Motors Occasionally Reverse #4464
    alden
    Member

    Can you tell me what axis is doing this and post your settings? Usually this means that one of the phases is not powered. Often this is wiring, sometimes the motor itself, and could indicate a fault int he board. (These boards have been tested pretty well and are new).

    You can check this by moving the motor to another port, swapping things around, trying different motors on the faulty port, etc.

    If it is a board fault it’s a DOA and we’ll replace the board.

    September 4, 2013 at 8:42 am in reply to: gShield as vanilla 2.5A driver shield? #4450
    alden
    Member

    Nope. It’s just a general shield. The only thing you need to pay attention to is the pinout, and perhaps the fact that grbl uses a common enable for all motors instead of separate enables per motor – mostly due to Arduino pin limitations.

    The other thing to note about the gSheild versus the Pololu drivers is (1) gShield uses TI stepper drivers that are much more blow-out proof than the Allegros (although the new Pololus have changed over (so if you do use Pololus be sure to get the ones with the TI’s and not the Allegros), and (2) the gShield by design has a LOT more copper for cooling so you can get the advertised amperage.

    — Alden

    September 2, 2013 at 6:52 am in reply to: Board on with no motor #4447
    alden
    Member

    No, it’s fine to run the board with no motors attached. I usually find that it’s more interesting to attach a motor anyway – usually with a flag made of tape – but it’s OK to run it either way.

    As is always the case, you want to make sure that you have your current tuned so the motors don’t overheat when sitting idle and powered, and don’t just walk away and leave the motors energized / pulling power. It’s still a machine tool, even if the motors are just sitting on a test bench.

    August 30, 2013 at 6:53 am in reply to: Message on limit switches #4440
    alden
    Member

    You should be able to do this now by adding homing values to status reports. You cannot add the “hom” group – you will need to add the individual “home”, “homx”, “homy”… etc values. (Status reports are flat and do not return group objects)

    • This reply was modified 11 years, 2 months ago by alden.
    August 29, 2013 at 10:17 am in reply to: TinyG v8 schematics #4431
    alden
    Member

    Posted: https://github.com/synthetos/TinyG/tree/master/hardware/v8schematics

    August 29, 2013 at 9:05 am in reply to: Flashing + Fuses Frustrations #4430
    alden
    Member

    Here’s the link, BTW:
    https://github.com/synthetos/TinyG/wiki/Programming-TinyG-with-the-Atmel-AVRISP-Mkii-Programmer

    August 29, 2013 at 8:43 am in reply to: TinyG v8 schematics #4427
    alden
    Member

    Sorry, we are behind in getting the v8 documentation up to date. Will post these to github shortly.

    August 29, 2013 at 8:31 am in reply to: Message on limit switches #4425
    alden
    Member

    I wonder what the best way to do this is? Add it to status reports?

    August 29, 2013 at 8:23 am in reply to: Flashing + Fuses Frustrations #4423
    alden
    Member

    Sorry you had a problem and thanks for posting this. I’ll use it to update the wiki.

    –Alden

    July 31, 2013 at 7:11 am in reply to: interrupted/corrupt status reports #4396
    alden
    Member

    That’s a bug. Thanks for pointing it out.

    –Alden

    July 29, 2013 at 4:46 am in reply to: Flashing Spindle Direction LED does not cease #4356
    alden
    Member

    Thanks for the update and sorry for the hassle you had to go through. We have discovered that to avoid flash corruption the fuses need to be set to handle brownouts – particularly if you are running a belt-driven machine like the Shapeoko. Please see the writeup here. Again, sorry for the issue:

    https://github.com/synthetos/TinyG/wiki/Programming-TinyG-with-the-Atmel-AVRISP-Mkii-Programmer#fuses

  • Author
    Posts
Viewing 15 posts - 316 through 330 (of 702 total)
1 2 3 … 21 22 23 … 45 46 47