coolterm not sending all gcode

Home › Forums › TinyG › TinyG Support › coolterm not sending all gcode

Viewing 15 posts - 16 through 30 (of 46 total)
1 2 3 4
  • Author
    Posts
  • July 21, 2012 at 9:29 pm #3365
    alden
    Member

    I just ran Coolterm build 162 at the high feed rate. Ran through OK. So that’s not it. I will now try your really really really really slow feed rate, so don’t expect a post back for a while.

    Yes, I have run jobs that have taken a long time, but I don’t think an hour. Let’s also be sure it’s not the stepper driver chips going into thermal shutdown. It doesn’t sound like it, but let’s rule that out. At slow speeds the chips take maximum current (and deliver maximum torque)

    July 21, 2012 at 9:33 pm #3366
    nmanousos
    Member

    I did install the FTDI drivers, and I am using USB. Unsure why bluetooth is in there. Do you have a coolterm .stc config file that I could try? I will look for the 1.4.0b2 build 142 of coolterm now.

    July 21, 2012 at 9:35 pm #3367
    nmanousos
    Member

    Ah ok, build 162 works for you so I won’t look for the old build. Looking forward to seeing how the 1mm/min feed rate works for you!

    July 21, 2012 at 10:00 pm #3368
    alden
    Member

    Seems to have gotten almost 1/2 of the way around. Currently processing line 746

    July 21, 2012 at 10:18 pm #3369
    alden
    Member

    Out of curiosity, what version of MacOS are you running? I’m on 10.7.4  I think you mentioned it also failed on a PC for you.

    July 21, 2012 at 10:24 pm #3370
    nmanousos
    Member

    10.7.4, I also use vmware to run windows 7

    July 21, 2012 at 10:31 pm #3371
    nmanousos
    Member

    what about not being able to do feedholds? is that an indication of a flow control issue?

    update: just edited the gcode to increase the speeds to 100mm/min. Feedhold works but is very delayed. At the slow 0.1 feedrate feedholds dont work at all… or maybe they are working but would take a couple minutes to happen?

    July 21, 2012 at 10:33 pm #3372
    alden
    Member

    Almost all the way through. SO the basics work. We should be looking for something in your setup. It;s also possible that it’s something in 338.11 that’s not in 338.12, but I’m not aware of any bug I fixed between the two of this type. I’ve been meaning to get 339.2 out of dev and tested and into master. This fixed a short arc problem. Do you have the ability to flash new firmware? (BTW – just finished).

    July 21, 2012 at 10:35 pm #3373
    alden
    Member

    Feedhold is problematic with XON/XOFF, as you have to get it through the serial interface, which is blocked during XOFF. ALso, Coolterm is unpredictable as to when you can get a console charater into a file download. Feedhold is more something we need to work into tgFX.

    July 21, 2012 at 10:52 pm #3374
    nmanousos
    Member

    I dont have ability to flash new firmware. I just tried a new experiment – I updated the gcode with faster feedrates, (100mm/min) to see how far it would get. It looks like it gets about a 1/4 through. Here is a screenshot of what happens when it stops:
    http://argonrecords.com/stopped.png

    July 21, 2012 at 10:54 pm #3375
    nmanousos
    Member

    When sending gcode should I see both the d3 and d4 leds light up? is one for tx and the other for rx? d3 is the only one that lights up for me. it turns on and stays on constantly until everything stops.

    July 21, 2012 at 11:15 pm #3376
    nmanousos
    Member

    just tried with my wife’s macbook. Mac OS 10.6.8, ftdi 2.2.17. no dice, it stops at the same place.

    July 22, 2012 at 7:26 am #3377
    alden
    Member

    I flashed a board with 338.11 and am ran it to completion, so it doesn’t look like that’s the problem, but can you please dump your TinyG settings with a $$ and post them?

    D4 is the RX and D3 is the TX. I think both are working or you wouldn’t have any echo at all. The symptom you describe sounds like the XOFF is being sent by TinyG to the host and the host honors it, but the subsequent XON is either never sent or is not honored. If you look at the echo in Coolterm the periods (.) in the text are the XON or XOFF characters.

    Separately, I don’t know why your Gcode has periods at the end of integer numbers, but this should not affect anything and indeed doesn’t give my setup any problem.

    • This reply was modified 12 years, 5 months ago by alden.
    July 22, 2012 at 1:37 pm #3379
    nmanousos
    Member

    [fb] firmware_build 338.11
    [fv] firmware_version 0.93
    [si] status_interval 50 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]
    [g54x] g54_x_offset 0.000 mm
    [g54y] g54_y_offset 0.000 mm
    [g54z] g54_z_offset 0.000 mm
    [g54a] g54_a_offset 0.000 mm
    [g54b] g54_b_offset 0.000 mm
    [g54c] g54_c_offset 0.000 mm
    [g55x] g55_x_offset 0.000 mm
    [g55y] g55_y_offset 0.000 mm
    [g55z] g55_z_offset 0.000 mm
    [g55a] g55_a_offset 0.000 mm
    [g55b] g55_b_offset 0.000 mm
    [g55c] g55_c_offset 0.000 mm
    [g56x] g56_x_offset 0.000 mm
    [g56y] g56_y_offset 0.000 mm
    [g56z] g56_z_offset 0.000 mm
    [g56a] g56_a_offset 0.000 mm
    [g56b] g56_b_offset 0.000 mm
    [g56c] g56_c_offset 0.000 mm
    [g57x] g57_x_offset 0.000 mm
    [g57y] g57_y_offset 0.000 mm
    [g57z] g57_z_offset 0.000 mm
    [g57a] g57_a_offset 0.000 mm
    [g57b] g57_b_offset 0.000 mm
    [g57c] g57_c_offset 0.000 mm
    [g58x] g58_x_offset 0.000 mm
    [g58y] g58_y_offset 0.000 mm
    [g58z] g58_z_offset 0.000 mm
    [g58a] g58_a_offset 0.000 mm
    [g58b] g58_b_offset 0.000 mm
    [g58c] g58_c_offset 0.000 mm
    [g59x] g59_x_offset 0.000 mm
    [g59y] g59_y_offset 0.000 mm
    [g59z] g59_z_offset 0.000 mm
    [g59a] g59_a_offset 0.000 mm
    [g59b] g59_b_offset 0.000 mm
    [g59c] g59_c_offset 0.000 mm
    X origin offset: 0.000 mm
    Y origin offset: 0.000 mm
    Z origin offset: 0.000 mm
    A origin offset: 0.000 deg
    B origin offset: 0.000 deg
    C origin offset: 0.000 deg
    [1ma] m1_map_to_axis 0 [0=X, 1=Y…]
    [1sa] m1_step_angle 1.800 deg
    [1tr] m1_travel_per_revolution 1.000 mm
    [1mi] m1_microsteps 8 [1,2,4,8]
    [1po] m1_polarity 1 [0,1]
    [1pm] m1_power_management 1 [0,1]
    [2ma] m2_map_to_axis 1 [0=X, 1=Y…]
    [2sa] m2_step_angle 1.800 deg
    [2tr] m2_travel_per_revolution 1.000 mm
    [2mi] m2_microsteps 8 [1,2,4,8]
    [2po] m2_polarity 0 [0,1]
    [2pm] m2_power_management 1 [0,1]
    [3ma] m3_map_to_axis 2 [0=X, 1=Y…]
    [3sa] m3_step_angle 1.800 deg
    [3tr] m3_travel_per_revolution 1.000 mm
    [3mi] m3_microsteps 8 [1,2,4,8]
    [3po] m3_polarity 0 [0,1]
    [3pm] m3_power_management 1 [0,1]
    [4ma] m4_map_to_axis 3 [0=X, 1=Y…]
    [4sa] m4_step_angle 1.800 deg
    [4tr] m4_travel_per_revolution 360.000 mm
    [4mi] m4_microsteps 8 [1,2,4,8]
    [4po] m4_polarity 0 [0,1]
    [4pm] m4_power_management 0 [0,1]
    [xam] x_axis_mode 1 [standard]
    [xvm] x_velocity_maximum 200.000 mm/min
    [xfr] x_feedrate_maximum 100.000 mm/min
    [xtm] x_travel_maximum 475.000 mm
    [xjm] x_jerk_maximum 20000000 mm/min^3
    [xjd] x_junction_deviation 0.0500 mm (larger is faster)
    [xsm] x_switch_mode 1 [0,1,2]
    [xsv] x_search_velocity -500.000 mm/min
    [xlv] x_latch_velocity 100.000 mm/min
    [xlb] x_latch_backoff 2.000 mm
    [xzb] x_zero_backoff 1.000 mm
    [yam] y_axis_mode 1 [standard]
    [yvm] y_velocity_maximum 200.000 mm/min
    [yfr] y_feedrate_maximum 100.000 mm/min
    [ytm] y_travel_maximum 200.000 mm
    [yjm] y_jerk_maximum 20000000 mm/min^3
    [yjd] y_junction_deviation 0.0500 mm (larger is faster)
    [ysm] y_switch_mode 1 [0,1,2]
    [ysv] y_search_velocity -500.000 mm/min
    [ylv] y_latch_velocity 100.000 mm/min
    [ylb] y_latch_backoff 2.000 mm
    [yzb] y_zero_backoff 1.000 mm
    [zam] z_axis_mode 1 [standard]
    [zvm] z_velocity_maximum 200.000 mm/min
    [zfr] z_feedrate_maximum 100.000 mm/min
    [ztm] z_travel_maximum 75.000 mm
    [zjm] z_jerk_maximum 20000000 mm/min^3
    [zjd] z_junction_deviation 0.0500 mm (larger is faster)
    [zsm] z_switch_mode 1 [0,1,2]
    [zsv] z_search_velocity -400.000 mm/min
    [zlv] z_latch_velocity 100.000 mm/min
    [zlb] z_latch_backoff 2.000 mm
    [zzb] z_zero_backoff 1.000 mm
    [aam] a_axis_mode 1 [standard]
    [avm] a_velocity_maximum 3600.000 deg/min
    [afr] a_feedrate_maximum 3600.000 deg/min
    [atm] a_travel_maximum -1.000 deg
    [ajm] a_jerk_maximum 20000000 deg/min^3
    [ajd] a_junction_deviation 0.0500 deg
    [ara] a_radius_value 1.0000 deg
    [asm] a_switch_mode 1 [0,1,2]
    [asv] a_search_velocity -600.000 deg/min
    [alv] a_latch_velocity 100.000 deg/min
    [alb] a_latch_backoff -5.000 deg
    [azb] a_zero_backoff 2.000 deg
    [bam] b_axis_mode 0 [disabled]
    [bvm] b_velocity_maximum 3600.000 deg/min
    [bfr] b_feedrate_maximum 3600.000 deg/min
    [btm] b_travel_maximum -1.000 deg
    [bjm] b_jerk_maximum 20000000 deg/min^3
    [bjd] b_junction_deviation 0.0500 deg
    [bra] b_radius_value 1.0000 deg
    [bsm] b_switch_mode 1 [0,1,2]
    [bsv] b_search_velocity -600.000 deg/min
    [blv] b_latch_velocity 100.000 deg/min
    [blb] b_latch_backoff -5.000 deg
    [bzb] b_zero_backoff 2.000 deg
    [cam] c_axis_mode 0 [disabled]
    [cvm] c_velocity_maximum 3600.000 deg/min
    [cfr] c_feedrate_maximum 3600.000 deg/min
    [ctm] c_travel_maximum -1.000 deg
    [cjm] c_jerk_maximum 20000000 deg/min^3
    [cjd] c_junction_deviation 0.0500 deg
    [cra] c_radius_value 1.0000 deg
    [csm] c_switch_mode 1 [0,1,2]
    [csv] c_search_velocity -600.000 deg/min
    [clv] c_latch_velocity 100.000 deg/min
    [clb] c_latch_backoff -5.000 deg
    [czb] c_zero_backoff 2.000 deg
    tinyg[mm] ok>

    July 22, 2012 at 5:23 pm #3381
    alden
    Member

    Interesting machine. You have 25.4 thread per inch screws? Try turning off the status reports and see if that helps. 50 ms is very fast. I’m thinking of making something like 200ms the minimum.

  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 46 total)
1 2 3 4
  • You must be logged in to reply to this topic.