ei8htohms

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: struggling with v.6 board – firmware? #6158
    ei8htohms
    Member

    This is a good question. I have no idea if the frame of the PSU is connected to anything. I tried connecting the ground for the shields to the body of the mill also (the bed of the lathe actually in this instance), but I don’t think that’s connected to anything either. I guess I’ll try the DC- on the TinyG next. Thanks!

    in reply to: struggling with v.6 board – firmware? #6154
    ei8htohms
    Member

    OK, I grounded the shielding for the steppers (on the TinyG side only) to the chassis of PSU and disabled all switches (xsm, ysm zsm and asm; they were all set to 1 previously, so I don’t think that should have made a difference). I also took out the transmit delays.

    The spindle I’m using it the Sherline motor with a 10,000 RPM pulley upgrade.

    http://www.sherline.com/33050pg.htm

    Yes, the code runs fine with the spindle off.

    I even tried moving the board a few feet further from the motors and still no luck.

    I’m really starting to suspect the janky wiring in my apartment building may be part of the problem. It’s a pre-war, Art Deco building and almost all of the outlets are only two prong. I’m running both the board and the spindle off of separate extension cords to two of our only outlets that are grounded however and still having the same problem. My next step may be purchase a power conditioner and/or put the board in a metal enclosure in the hopes of getting some Faraday cage protection.

    As a point of interest, when it froze up this time, I uplugged the USB so that CoolTerm would unfreeze and when I plugged the USB back in and told CoolTerm to reconnect (the spindle was off, but I did not reset the TinyG) and sent a G28 command it ran several more lines of the original text file before executing the G28. Weird. Don’t know what to make of that.

    • This reply was modified 10 years, 5 months ago by ei8htohms.
    in reply to: struggling with v.6 board – firmware? #6147
    ei8htohms
    Member

    Yeah, I’ve definitely got an EMI problem. I switched all the stepper wires to shielded cables, put ferrite beads on the power cable and USB cable and it still can’t run the code all the way through with the spindle running and often with some weird anomalous behavior before it just stops.

    I’m not using end stops at all, so I’m thinking my next step may be to ground the shielding on the stepper cables. Can I ground those to the TinyG board or do I need to ground them to the PSU somehow?

    Perhaps I need a metal enclosure for the board to act as a Faraday cage?

    Thanks!

    in reply to: struggling with v.6 board – firmware? #6123
    ei8htohms
    Member

    Well, looks like I spoke too soon. At least with the spindle running, it can still only get through maybe 50 lines of code. The fact that it seems to be able to get farther with the spindle off has me curious if I’m having EMI issues also, so I may try to reduce some of the possible sources of interference before sending the board in. Two steps forward, one step back I reckon.

    in reply to: struggling with v.6 board – firmware? #6111
    ei8htohms
    Member

    OK, this looks promising. When I read the settings from the TinyG, enable_xon_xoff was set to 0, so I set it to 1 and turned it on in Cool Term also. Now my settings report:

    tinyg[mm] ok> [fb]  firmware_build            338.11
    [fv]  firmware_version            0.93
    [si]  status_interval           100 ms [0=off]
    [gpl] gcode_select_plane          0 [0,1,2]
    [gun] gcode_units_mode            1 [0,1]
    [gco] gcode_coord_system          1 [1-6]
    [gpa] gcode_path_control          2 [0,1,2]
    [gdi] gcode_distance_mode         0 [0,1]
    [ea]  enable_acceleration         1 [0,1]
    [ja]  junction_acceleration  100000 mm
    [ml]  min_line_segment            0.080 mm
    [ma]  min_arc_segment             0.100 mm
    [mt]  min_segment_time         5000 uSec
    [ic]  ignore_CR (on RX)           0 [0,1]
    [il]  ignore_LF (on RX)           0 [0,1]
    [ec]  enable_CR (on TX)           0 [0,1]
    [ee]  enable_echo                 0 [0,1]
    [ex]  enable_xon_xoff             1 [0,1]

    Of course I also enabled XON in CoolTerm and it seems to now be able to run the complete code (well, as far as I had the patience to sit through without cutting anything yet, yea!).

    So do I need to do anything with these?

    [ic]  ignore_CR (on RX)           0 [0,1]
    [il]  ignore_LF (on RX)           0 [0,1]
    [ec]  enable_CR (on TX)           0 [0,1]
    [ee]  enable_echo                 0 [0,1]

    I don’t really understand what these are doing exactly and how they will affect either the gcode I write or the commands I’ll send to the TinyG.

    Thanks for the awesome help so far, you guys have made my life vastly better already!

    • This reply was modified 10 years, 5 months ago by ei8htohms.
    • This reply was modified 10 years, 5 months ago by ei8htohms.
    in reply to: struggling with v.6 board – firmware? #6102
    ei8htohms
    Member

    I took a quick look at Putty but have not yet downloaded Plink, I’ll give that a try.

    How can I read the flow control state for the TinyG? Is that something a command through CoolTerm should be able to report back to me?

    Thanks for your help!

Viewing 6 posts - 1 through 6 (of 6 total)