kkannan

Agreed, let me try to update one of the board to build 440.20 and see if the connectivity issue goes away, or I can query the internals of Tinyg and send gcodes accordingly.

BTW Goko.com seems to have been hijacked.

Thanks
Kannan

• This reply was modified 8 years, 6 months ago by kkannan.

Hi vex & cmcgrath,

Thanks for the replies, originally the machine was running RepRap which I use it to cut low density foam, plotter style using hot needle. I’ve written a java program using rx/tx lib which looks for ok> before sending the next gcode. This setup worked so well that I didn’t bother to change the boards which was Duemilanova with 3 separate stepper drivers.

The reason I want to change it to Tinyg was speed and microstepping. I’ve two v6 boards which I want to use it. Setup went really smooth and looked a lot neater with less wiring. This time, my program started looking for tinyg [mm] ok> for end of execution of the previous cmd. But, I discovered that due the planner and everything, the response is not one to one. After few gcodes, the response comes in bulk or not at all. The machine stuck with the last cmd and does crazy things when it eventually receives a new gcode. That is the reason why it is going diagonally instead of straight line pattern in the gcode list, it simply missed the corner.

After many experiments later, gave up on CP trying tinyg, old, tingygg2, line mode, idmode. The working setup in coolterm is 1000 ms for files with large line segments and 100 ms for short segments. My program breaks circles, arcs into small line segments. Though it works now, as you can see , a new program may still wreck havoc with the job. Foam material so cheap I can afford to waste it. Here’s my $sys params,

[fb] firmware_build 338.02
[fv] firmware_version 0.93
[si] status_interval 0 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 1 [0,1]
[ex] enable_xon_xoff 1 [0,1]

Any documentation to query the planner buffer and status could be helpful. IMHO, tinyg should not rely on third party for basic operations, there should be a basic Gcode sender however small and featureless it is.

Thanks
Kannan

PS: Chrome on Vista Home premium

• This reply was modified 8 years, 6 months ago by kkannan.

Looking forward to v8, this will make small CNCs with the sophistication of tinyg and the power of servos possible.

-Kannan