cmcgrath5035

Forum Replies Created

Viewing 15 posts - 1,201 through 1,215 (of 1,771 total)
1 2 3 … 80 81 82 … 117 118 119
  • Author
    Posts
  • July 13, 2015 at 7:30 am in reply to: TinyG and ChiliPeppr under Windows 10 Insider Preview #7992
    cmcgrath5035
    Moderator

    What browser are you using under Win10?

    Does Win10 support the necessary FTDI device driver?

    July 13, 2015 at 6:25 am in reply to: TinyG Updater App Problems #7989
    cmcgrath5035
    Moderator

    Another thought – are you sure that when you start up Chilipeppr, you are choosing the tinyG buffer manager option in the SPJS widget(lower right) for your connection?

    That of course would have nothing to do with CoolTerm.

    Also, a reminder to be sure SPJS is not still running when you exit CP and try CoolTerm or avrdude from command line.
    You are running Windows – use Alt-Ctl-Del to open the Task Manager to double check. SPJS can be restarted as a background process by a restart of SPJS.

    July 12, 2015 at 10:45 pm in reply to: TinyG Updater App Problems #7988
    cmcgrath5035
    Moderator

    Hmmm, wild ride.
    Particularly strange that not responsive CoolTerm, that is a very basic interface.
    Update to 440.15 was not absolutely necessary, but OK to stay there.

    My current guess is that you have some limit switch issues that stop your machine(maybe).
    So you see fast flashing of Spin/Dir when the machine stops?

    Try to post your parameter set (results of a $$) to a cloud drive so we can have a look. Here is a how to:

    July 11, 2015 at 4:49 pm in reply to: TinyG Updater App Problems #7974
    cmcgrath5035
    Moderator

    I’m a bit confused, the Avrdude method does not use a programmer, it sends the file over USB if initiated correctly while Spin/Dir flashing(accepting connections from Avrdude.

    Are you saying Avrdude method did not work either?

    What OS and what version of avrdude do you have?

    July 10, 2015 at 1:08 pm in reply to: Newbie Help Installing: Motor not moving #7971
    cmcgrath5035
    Moderator

    Go back to 24V 5A. That should be enough current for test motion at least.
    24V at 6-8 A probably better, but for now 5A should work for you.

    MEMA17 motors usually have smaller(#teeth) pulleys. What pulleys and belts are you using?
    My NEMA17 SH2 had $_tr=36.54 (11 teeth, MXL belts)

    In you parameters, all motors are disabled, $_pm=0. Try $_pm=2.

    Motors will hum for 10 seconds after tinyG reboot, locking current position for $mt seconds then release holding current.

    (Gently) turn all 4 current (not voltage) pots to max until you get a bigger PS.

    See if this helps

    July 10, 2015 at 12:48 pm in reply to: TinyG Updater App Problems #7969
    cmcgrath5035
    Moderator

    Do you know what version you were upgrading from?
    When you hit reset on the tinyG, does the Spin/Dir led flash one per second or so For 5 seconds or so(sorry, away from my tinyG, going from memory)?
    That is the bootloader running (good), while the led is flashing, the bootloader will accept a connection from Avrdude.

    You should use the Avrdude method, outlined here:

    Additionally, I use the “-e” option, discussed here:

    You should flash with Edge release 440.14, NOT 380.08.

    • This reply was modified 9 years, 2 months ago by cmcgrath5035.
    July 9, 2015 at 5:53 pm in reply to: TinyG 440.15 #7965
    cmcgrath5035
    Moderator

    Review the Chilipeppr group posting above frequently, Danal added a lot of clarity to what does/does not work well if you stay with 440.14.

    If you are the adventuresome type, the multi-Coordinate system support enabled by 440.15 looks real neat.

    July 9, 2015 at 1:53 pm in reply to: Incorrect Arc Movement #7963
    cmcgrath5035
    Moderator

    djdaudio: First check will be FW version, there have been almost continuous refinements to the handling of arcs and the somewhat strange arcs that are generated by some packages. FW 440.14 is the current best choice, but there are still corner cases being worked.
    These issues are often resolved by tweaking the backends of the Gcode processors, using less aggressive minimal arc lengths, etc.

    • This reply was modified 9 years, 2 months ago by cmcgrath5035.
    July 9, 2015 at 9:34 am in reply to: Incorrect Arc Movement #7960
    cmcgrath5035
    Moderator

    I suggest start a new thread, we have no context for what you issue might be.
    Start with a description of your machine and a parameter list

    July 9, 2015 at 9:30 am in reply to: PWM LED always lighted #7959
    cmcgrath5035
    Moderator

    In CoolTerm, issue an M5 (spindle off) Gcode command.
    Or you may have to issue M3 (Spindle on) then an M5.

    The spindle was off.
    You have to give tinyG a reason to read the new parameter value for off state.

    July 9, 2015 at 9:14 am in reply to: TinyG 440.15 #7957
    cmcgrath5035
    Moderator

    The 440.15 fw supports an updated (new features) Chilipeppr widget which significantly enhances the use of multiple coordinate systems. The creation of this new widget found a bug in 440.14 that is corrected in 440.15.

    440.15 was created and is supported by Danal, has been tested and works for those who have tested it so far. If you upgrade to 440.15 and don’t like it, yes, you could reinstall 440.14 from Synthetos.

    You do have the option to run CP with 440.14. Unfortunately, I can’t be explicit as to the specific case where the bug (fixed in 440.15) will nip you.
    I’ll ask Danal to address that, in this thread:

    July 8, 2015 at 12:38 pm in reply to: Compiling tinyg2 #7953
    cmcgrath5035
    Moderator

    yck011522: What OS are you running.

    I run Linux (openSUSE). I find that some apps don’t play nice with network drives. How Dropbox appears to the OS is likely different across OSs.

    Good to know

    July 8, 2015 at 9:50 am in reply to: X-axis offset #7952
    cmcgrath5035
    Moderator

    Having read this a couple times:

    I am fairly sure this offset you are seeing could be related to the identified bug in fw 440.14.

    After a successful home cycle, my read is that $mpox and $posx should both be 0.0.

    A fix is in-progress, I suggest upgrade to 440.14 and reevaluate.
    Bugfix release will be released soon.

    July 7, 2015 at 10:12 am in reply to: X-axis offset #7950
    cmcgrath5035
    Moderator

    Hmm, after reading this item:

    I come away wondering if your observed offset might be related to this bug or an earlier version of it.

    I would strongly recommend you move to FW 440.14 (or greater, a new build is currently being evaluated) before banging your head against 435.10

    July 7, 2015 at 9:21 am in reply to: X-axis offset #7949
    cmcgrath5035
    Moderator

    Oops, I just realized that I did not scroll down the screen far enough, and that yes, mpox is Machine (G53 coordinate system) x position. See this table:

    So I am sort of guessing that you have $xzb, X zero backoff, set to 5mm and that is what you are seeing.

    For (your) programming, best solution might be to define a SR that provides posx, which would be position in current coordinate system by default G54.
    That should be the 0.00 you think you want.

    As you migrate away from tgFX, give Chilipeppr a look. There is currently a really nice/powerful update being finalized that makes coordinate systems much clearer and easy to use

  • Author
    Posts
Viewing 15 posts - 1,201 through 1,215 (of 1,771 total)
1 2 3 … 80 81 82 … 117 118 119