Synthetos Shop

Getting really F'n frustrated

From the original Synthetos forum (2011–2025)

Started by Juwalla on in TinyG Support. 19 replies, last activity Oct 5, 2014.

Juwalla #

Hello,

If you cannot tell I am just about ready to send this back to you in melted pieces. Not only is your WIKI convoluted and confusing with your links that send you in circles, but the instructions are half ass in the more important areas like JSON(doesn't work and I wouldn't know if it did anyway because THERE ARE NO INSTRUCTIONS other than..... use it.),any kind of update(I need to update to FW 438.02 but cannot find instructions and TGfx is no help either), zeroing the machine with settings(ie....$tr), and most importantly POST PROCESSORS (I am using CAMBAM but I have no idea what to set as the post processor because I cannot find it on your WIKI or forum). Trying to find troubleshooting guides or useful information on ANY of your sites is damn near impossible for me.

Now that being said. I am VERY new to this world and could be a complete idiot (most likely). When you add stupid with confusing instructions you get a GIANT waste of money. By the way, TGfx has broken about 5 or 6 bits because when you try to zero your machine with the arrows and the + & - it never goes the same distance twice. Hell, sometimes it just keeps going until you unplug it and other times it doesn't move at all. Who knows if it is the current version because I cannot find clear information on which version is most current or where to get it from. There are like 20 different references to different links. The Gshied is great and easy to use for dummies like myself, but the TinyG is almost labeled as garbage in my book.

Here is my problem. I can hook it up, power it up, adjust the settings that NEVER save, and send gcode files that never come out the size of my drawing. TGfx reverts $ex to $ex=2 every time I connect it. I have to change it back in Coolterm before running a job. Hell, sometimes the X-axis just quits working all together until it messes my project up, then it starts working great. (Did you program it to do that?) I have no idea on how to adjust it from here because there are no instructions!!!!!!

I have the V8 board. It is on the standard Shapeoko with Nema 23 motors on the X and Y axis. Here are my current settings.Actually I just tried loading the ril3ys shapeoko dual Y config in TGfx but I have not ran a job with it yet(that is the settings listed below.) Before that, I used the Shapeoko settings for dual Y that is posted on your Wiki. I know the FW is out of date but I cannot find instructions on how to update it.(I'm sure it will require that I install 12 more programs to do one simple task.)

I am thinking that my post processor may be the issue. I read on your wiki that you tried to stick to Linux Gcode when you programmed TinyG so I chose Linux CNC as the post processor in CamBam. Please tell what post processor works best with TinyG and I will ask the CamBam folks to help me write one. My problem is that the X-axis just does its own thing, works perfect one second and just stops the next. Nothing comes out the correct size.
Before typing this I ran a project that should have been 6" for the outside diameter with a 1/4" off set to the inside and the rest of the circle is a pocket operation. I kinda got a circle that was 6 1/2" in diameter with a offset that varies depending on where you look and a sloppy pocket. I have ran successful jobs with the TinyG even though they were not the correct size the machine still ran, but now I cannot run a successful job at all. Help me out here please. I want to like your product but I am not happy with it at this point.

There is a fan attached to keep the drivers cool.

[fb] firmware build 435.10
[fv] firmware version 0.97
[hp] hardware platform 1.00
[hv] hardware version 8.00
[id] TinyG ID 2X2660-KKP
[ja] junction acceleration 2000000 mm
[ct] chordal tolerance 0.010 mm
[sl] soft limit enable 0
[st] switch type 1 [0=NO,1=NC]
[mt] motor idle timeout 10.00 Sec
[ej] enable json mode 0 [0=text,1=JSON]
[jv] json verbosity 3 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
[js] json serialize style 1 [0=relaxed,1=strict]
[tv] text verbosity 0 [0=silent,1=verbose]
[qv] queue report verbosity 0 [0=off,1=single,2=triple]
[sv] status report verbosity 1 [0=off,1=filtered,2=verbose]
[si] status interval 100 ms
[ec] expand LF to CRLF on TX 0 [0=off,1=on]
[ee] enable echo 0 [0=off,1=on]
[ex] enable flow control 2 [0=off,1=XON/XOFF, 2=RTS/CTS]
[baud] USB baud rate 5 [1=9600,2=19200,3=38400,4=57600,5=115200,6=230400]
[net] network mode 0 [0=master]
[gpl] default gcode plane 0 [0=G17,1=G18,2=G19]
[gun] default gcode units mode 1 [0=G20,1=G21]
[gco] default gcode coord system 1 [1-6 (G54-G59)]
[gpa] default gcode path control 2 [0=G61,1=G61.1,2=G64]
[gdi] default gcode distance mode 0 [0=G90,1=G91]
[1ma] m1 map to axis 0 [0=X,1=Y,2=Z...]
[1sa] m1 step angle 1.800 deg
[1tr] m1 travel per revolution 36.5400 mm
[1mi] m1 microsteps 8 [1,2,4,8]
[1po] m1 polarity 0 [0=normal,1=reverse]
[1pm] m1 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[2ma] m2 map to axis 1 [0=X,1=Y,2=Z...]
[2sa] m2 step angle 1.800 deg
[2tr] m2 travel per revolution 36.5400 mm
[2mi] m2 microsteps 8 [1,2,4,8]
[2po] m2 polarity 0 [0=normal,1=reverse]
[2pm] m2 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[3ma] m3 map to axis 1 [0=X,1=Y,2=Z...]
[3sa] m3 step angle 1.800 deg
[3tr] m3 travel per revolution 36.5400 mm
[3mi] m3 microsteps 8 [1,2,4,8]
[3po] m3 polarity 0 [0=normal,1=reverse]
[3pm] m3 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
[4ma] m4 map to axis 2 [0=X,1=Y,2=Z...]
[4sa] m4 step angle 1.800 deg
[4tr] m4 travel per revolution 1.2500 mm
[4mi] m4 microsteps 8 [1,2,4,8]
[4po] m4 polarity 1 [0=normal,1=reverse]
[4pm] m4 power management 1 [0=disabled,1=always on,2=in cycle,3=when moving]
[xam] x axis mode 1 [standard]
[xvm] x velocity maximum 16000 mm/min
[xfr] x feedrate maximum 16000 mm/min
[xtn] x travel minimum 0.000 mm
[xtm] x travel maximum 298.000 mm
[xjm] x jerk maximum 5000 mm/min^3 * 1 million
[xjh] x jerk homing 20 mm/min^3 * 1 million
[xjd] x junction deviation 0.0500 mm (larger is faster)
[xsn] x switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
[xsx] x switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[xsv] x search velocity -1000 mm/min
[xlv] x latch velocity 100 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 16000 mm/min
[yfr] y feedrate maximum 16000 mm/min
[ytn] y travel minimum 0.000 mm
[ytm] y travel maximum 301.000 mm
[yjm] y jerk maximum 5000 mm/min^3 * 1 million
[yjh] y jerk homing 20 mm/min^3 * 1 million
[yjd] y junction deviation 0.0500 mm (larger is faster)
[ysn] y switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
[ysx] y switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[ysv] y search velocity -1000 mm/min
[ylv] y latch velocity 100 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 1200 mm/min
[zfr] z feedrate maximum 1200 mm/min
[ztn] z travel minimum 0.000 mm
[ztm] z travel maximum 54.000 mm
[zjm] z jerk maximum 50 mm/min^3 * 1 million
[zjh] z jerk homing 20 mm/min^3 * 1 million
[zjd] z junction deviation 0.0500 mm (larger is faster)
[zsn] z switch min 0 [0=off,1=homing,2=limit,3=limit+homing]
[zsx] z switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[zsv] z search velocity 400 mm/min
[zlv] z latch velocity 100 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 16000 deg/min
[afr] a feedrate maximum 3600 deg/min
[atn] a travel minimum 400.000 deg
[atm] a travel maximum -1.000 deg
[ajm] a jerk maximum 20 deg/min^3 * 1 million
[ajh] a jerk homing 24000 deg/min^3 * 1 million
[ajd] a junction deviation 0.0500 deg (larger is faster)
[ara] a radius value 1.0000 deg
[asn] a switch min 1 [0=off,1=homing,2=limit,3=limit+homing]
[asx] a switch max 0 [0=off,1=homing,2=limit,3=limit+homing]
[asv] a search velocity 6000 deg/min
[alv] a latch velocity 1000 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 deg/min
[bfr] b feedrate maximum 3600 deg/min
[btn] b travel minimum -1.000 deg
[btm] b travel maximum -1.000 deg
[bjm] b jerk maximum 20 deg/min^3 * 1 million
[bjd] b junction deviation 0.0500 deg (larger is faster)
[bra] b radius value 1.0000 deg
[cam] c axis mode 0 [disabled]
[cvm] c velocity maximum 3600 deg/min
[cfr] c feedrate maximum 3600 deg/min
[ctn] c travel minimum -1.000 deg
[ctm] c travel maximum -1.000 deg
[cjm] c jerk maximum 20 deg/min^3 * 1 million
[cjd] c junction deviation 0.0500 deg (larger is faster)
[cra] c radius value 1.0000 deg
[p1frq] pwm frequency 100 Hz
[p1csl] pwm cw speed lo 1000 RPM
[p1csh] pwm cw speed hi 2000 RPM
[p1cpl] pwm cw phase lo 0.125 [0..1]
[p1cph] pwm cw phase hi 0.200 [0..1]
[p1wsl] pwm ccw speed lo 1000 RPM
[p1wsh] pwm ccw speed hi 2000 RPM
[p1wpl] pwm ccw phase lo 0.125 [0..1]
[p1wph] pwm ccw phase hi 0.200 [0..1]
[p1pof] pwm phase off 0.100 [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 deg
[g54b] g54 b offset 0.000 deg
[g54c] g54 c offset 0.000 deg
[g55x] g55 x offset 110.000 mm
[g55y] g55 y offset 110.000 mm
[g55z] g55 z offset 0.000 mm
[g55a] g55 a offset 0.000 deg
[g55b] g55 b offset 0.000 deg
[g55c] g55 c offset 0.000 deg
[g56x] g56 x offset 110.000 mm
[g56y] g56 y offset 20.000 mm
[g56z] g56 z offset -10.000 mm
[g56a] g56 a offset 0.000 deg
[g56b] g56 b offset 0.000 deg
[g56c] g56 c offset 0.000 deg
[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 deg
[g57b] g57 b offset 0.000 deg
[g57c] g57 c offset 0.000 deg
[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 deg
[g58b] g58 b offset 0.000 deg
[g58c] g58 c offset 0.000 deg
[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 deg
[g59b] g59 b offset 0.000 deg
[g59c] g59 c offset 0.000 deg
[g92x] g92 x offset 0.000 mm
[g92y] g92 y offset 0.000 mm
[g92z] g92 z offset 0.000 mm
[g92a] g92 a offset 0.000 deg
[g92b] g92 b offset 0.000 deg
[g92c] g92 c offset 0.000 deg
[g28x] g28 x position 0.000 mm
[g28y] g28 y position 0.000 mm
[g28z] g28 z position 0.000 mm
[g28a] g28 a position 0.000 deg
[g28b] g28 b position 0.000 deg
[g28c] g28 c position 0.000 deg
[g30x] g30 x position 0.000 mm
[g30y] g30 y position 0.000 mm
[g30z] g30 z position 0.000 mm
[g30a] g30 a position 0.000 deg
[g30b] g30 b position 0.000 deg
[g30c] g30 c position 0.000 deg

cmcgrath5035Staff #

Sort of hard to tell where to start here.

What OS environment are you working in (Win, Linux, OSX)? Each has different tools available. Since you mention Coolterm, I'm sort of thinking Win_64....

A quick look says your Motor parameters are probably wrong, unless you have a very unique set of steppers and pulleys. 36.54 mm/rev is the typical NEMA 17 setting. That by itself will distort sizes.

If you want to update your FW, follow this wiki item

https://github.com/synthetos/TinyG/wiki/TinyG-Updating-Firmware

My suggestion - forget CAMBAM for a while and start with experimenting with moves from the command line in Coolterm, text mode. Draw in air (leave Z above the board, spindle off,
Try drawing a square, with something like
g0X10
g0Y10
g0X0
g0Y0.

The Shapeoko wiki has some good start up procedures and tuning suggestions, as well as some simple G code files for the next step.

chmr #

I can see your frustration, and I try to answer your questions in sequence:

Json: Forget it for now, it is very useful for people developing programs that talk to tinyg, but nor for the average user. That said, it's documented at https://github.com/synthetos/TinyG/wiki/JSON-Operation and https://github.com/synthetos/TinyG/wiki/JSON-Details , linked from the tinyg start page.

Firmware update: Carl already linked the page, but you probably don't need it anyway. The easiest way to update the firmware is with tgfx.
Note: Firmware updates reset the configuration to default.

tgfx: Make sure you have the newest version, older versions don't work properly with the recent firmware versions. You can get it from https://github.com/synthetos/tgFX#binary-downloads if you don't have version 3625 already.

Cambam: I second Carls' suggestion to postpone it until you have tinyg itself configured and running. I think most people run the generic gcode backend with tinyg (not using Cambam myself).

Flow control: Yes, tgfx sets $ex=2. Rightfully so, because RTS/CTS is the easiest and most effective type of flow control to use. Just set Coolterm options to also use CTS, save settings, and be done with it.

Axis configuration: I found https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97 to be very useful for basic configuration. My suggestion is to work with 1 axis at a time, start with X (the easiest), and when that works move on to the next. The settings above are already a good starting point, I noted the following settings need verification:
$1tr=40 (is 36.54 above, but 40 should be correct if you have the Nema23 upgrade from Inventables: pulley with 20 teeth, belt pich 2mm)
$xvm=4000 (start with a low value for max velocity, then tune it later when the rest is working)
$xfr=4000 (same)
$xjm=200 (max jerk: start low, tune it later)
Test it like Carl suggested.

When you're happy with X, continue with Y (motors 2 and 3) and finally Z (reduce $4vm and $4fr; $4tr above seems to be correct for stock machine, but not if you have an acme screw upgrade; might also want to experiment with different $4mi values).

I really hope that gets your Shapeoko going, feel free to post more detailed questions if you still have problems.
And a slight warning for the Shapeoko wiki: Some of the pages describe the procedures for GRBL without telling so, and the procedure for tiny might be different. This bit me when I started with CNC. If in doubt, ask here or in the tinyg section of the Shapeoko forum.

Juwalla #

cmcgrath5035,

The OS is Windows 7 64-bit. The settings I posted were setting that I just tried through TGfx. It was "ril3ys Shapeoko dual Y config". Before I tried "RIL3YS" settings I had the standard or default Shapeoko settings and experienced the same problem. Meaning, I had the X and Y axis settings at $tr=36.54. The X and Y motors are Nema 23 from Inventables. I will update the FW this afternoon and try to download the newest TGfx.I will try your G commands as well, but I am not very familiar with doing it that way. Thank you for the help.

CHMR,

Thank you for the response as well. I have read both of the JSON pages that you referenced. For me, it might as well be a different language because I don't get it. But,I do get that I don't need it now. The Wiki is highly suggestive that you need to use JSON for TinyG to work properly.

Why do I not need the most recent FW update?

I have tried updating the FW with TGFX. I doesn't work. TGfx doesn't even know that there is a new FW version. I will double check to see if I have version 3625.
Speaking of FW updates and losing configuration settings...... Is there a way to export or save your settings before and a way to import them after? There was a forum post where someone said they wrote a script for that but I don't know how to apply it.

I will forget CamBam for now as you suggest. The problem is I have no clue how to operate the machine with "G" commands and TGfx has cost me too much in broken bits for me to trust it. I have been moving the machine manually to move it into position. I know that ChiliPeppr is another option but it is way over my head, and there are no instructions for dummies either.Yes, I watched the youtube videos.

"Flow control: Yes, tgfx sets $ex=2. Rightfully so, because RTS/CTS is the easiest and most effective type of flow control to use. Just set Coolterm options to also use CTS, save settings, and be done with it."

This is confusing to me because the Wiki instructs you to ALWAYS make sure you are using XON/XOFF.

That link tells me what you said about flow control. But later you are told differently. Of course I cannot find it now. I rarely get to the same page twice without hours of searching and reading. I know you guys are working on it but Holy Hell i'm ready for it to be finished.

Your link for basic configuration does a good job of defining commands but not a configuration process or methodology. Or I need to send TinyG back because it is way above my understanding.

I do have the Acme screw upgrade but I have not installed it yet because I have orders for jobs that I need to run. I had no idea it would take this long to get it to work. I refuse to hook the Gshield back up again until I know if I can get TinyG to work or not. Do you suggest installing the Acme screw upgrade first or wait until everything is configured? I'm sure upgrading after will mean that I have to reconfigure the Z axis again.

Thanks for the tip about the Shapeoko wiki. I remembered reading somewhere that the TinyG is completely different from Gshield in regards to GRBL. I have been trying to stick to your wiki as best I can.

Will the configuration settings be the same for TinyG as the were for my Gshield?
Meaning will the number for Travel per revolution work the same on both. I know that they are called different things depending on which board you are configuring but the math should be the same correct?

cmcgrath5035Staff #

Juwalla
Additional suggestions

tgFX - the currently available version, build 3525, has issues with its download/update functionality. I suggest you try FW update using avrdude instead, or just stick with what you have. The changes implemented in the latest tinyG edge version, 438.02, are minor and will not affect your getting the basic functionality up and running.

GUI - if you really miss GUI functionality, you can start to read up on Chilipeppr at

https://github.com/synthetos/TinyG/wiki/Chilipeppr

But Chilipeppr at the moment lacks GUI support for parameter setup/configuration, so I highly recommend you get comfortable with Coolterm and text mode setup. JSON works too, but the syntax is a bit fussy unless you are fluent.

Flow Control - tinyG will work with Xon/Xoff or RTS/CTS. I'd suggest stick with Xon/Xoff as long as tgFX is out of the picture.

Shapeoko - Until very recently, Shapeoko was synonymous with NEMA 17s. I believe they have recently formalized a version with NEMA 23s. When you see reference to ShapeOko in Synthetos documentation, think NEMA 17. NEMA 23s are used by lots of folks, but the end user (you) has to make the necessary configuration modifications. Similarly, ACME Z axis is a popular upgrade, but you must adjust the configuration accordingly.

Juwalla #

Ok, I am in coolterm typing the commands you guys suggested but when I type the command (i double check) nothing happens so I type again (double checking) and it moves. Sometimes it moves sometimes it doesn't. I even tried copying and pasting the same command with the same results. I double checked my settings in coolterm to ensure they match your Wiki. What am I doing wrong? The lights on TinyG insinuate that it is receiving the command each time but it doesn't move each time.

Juwalla #

I get it. You have to press the reset button each time. This will take ages!

Juwalla #

Reading through the posts again taking notes I realized that cmcgrath5035 says...
"Flow Control – tinyG will work with Xon/Xoff or RTS/CTS. I’d suggest stick with Xon/Xoff as long as tgFX is out of the picture."

But before that chmr says....
Flow control: Yes, tgfx sets $ex=2. Rightfully so, because RTS/CTS is the easiest and most effective type of flow control to use. Just set Coolterm options to also use CTS, save settings, and be done with it.

So which is it?
This is just like reading the wiki! Confusing!!!!!!!!!!!!!!!!

chmr, you said.....
"When you’re happy with X, continue with Y (motors 2 and 3) and finally Z (reduce $4vm and $4fr; $4tr above seems to be correct for stock machine, but not if you have an acme screw upgrade; might also want to experiment with different $4mi values)."

What is $4vm $ $4fr I don't see either of these when I query the settings with $$ or when i look on the Wiki. I am guessing "velocity max" and "feed rate"? I see that for $Z but not $4. Reduce it to what, and why?

cmcgrath5035Staff #

Flow Control - Pick one, both work.

You should not have to reset.

Do you have limit switches enabled?
Disable them for now.

Is $ej still = 0 (text mode) ?

Juwalla #

Limit switches are $xsn and $xsx for each axis correct?
If so then yes they are disabled.

Yes, $ej is 0.

chmr #

Sorry for the confusion with tgfx, I wasn't aware of the problems with it's firmware update procedure.
Also for flow control, both work, but stick with Carl's suggestions. I am just a normal user who pops in occasionally, his answers have definitely more weight.

Yeah, I meant $zvm and $zfr. Just reduce them to something like 400 for now, you can increase it gradually later when the machine works reliably.

When you say that the same command works one time, but not again, can you give an example with the exact commands you are entering? For the move commands (G0 and G1), be aware that the coordinates are usually absolute, so "G0 X10" tells tinyg to move to X coordinate 10 mm. If it thinks it is already there, it just won't do anything. You have to move it back first with "G0 X0". A reset of the controller also resets the current coordinates to X0 Y0 Z0. By entering "?" you will get a status report including the current coordinates.

Juwalla #

No worries. I thought you meant $zvm and $zfr but I wanted to make sure I wasn't over looking something.

It seemed to be correct with a small square so I tried drawing a larger one to see if there was a difference. I followed the commands that were suggested except I changed the numbers. G0x100, g0y100, g0x0, g0y0.

To be fair, I did notice that I hit the letter "o" instead of the number "0" at times. I did confirm that I was entering the correct command when it didn't move at times. I also tried g0x-10, g0z10, and g0z-10 just trying to familiarize myself with commands. The Z-axis commands seem to fail more than the X and Y axis commands. I checked the connection to the board to make sure it was not a loose wire or two. Like I said before the Z-axis failed more often than the other two. The board lights up like it is receiving the command but nothing happens.

I think I have some of the settings correct now. Here is what I changed last night.
$1tr=39.5
$2tr=39.75
$3tr=39.75

$zvm=800
$zfr=800

Switched CoolTerm to CTS/RTS
Verified TGfx version is 3625

I did not update the FW since it was suggested that it wouldn't make a difference.

I ran the same job to see the difference in cutting. I have to see how changes affect the operation. I am visually oriented when it comes to understanding mechanical things. I did get a 6" diameter this time but I screwed up something on the CAD/CAM side that caused problems. I'm getting there thanks to your help and recommendations. Thank you

cmcgrath5035Staff #

Sounds like some progress.

First, why is $tr for X different than $tr for Y ? Different drive pulleys?

$1tr=39.5
$2tr=39.75
$3tr=39.75

I would expect these to yield a slightly squashed circle (a.k.a. an oval)

You are not the first to type GOX10 rather than G0X10, I still do it all the time.

I have also noticed that some commands, such as an M30 at the end of a run leaves tinyG in JSON mode. The first text command entered will change tinyG mode but not execute the command.
I have gotten in the habit of just entering G0[return] to make sure tinyG is in text mode, then entering G0X10, etc.

Any chance the Z axis is binding due to alignment or ?? If it is, you will likely hear a buzz or groan from the motor. Perhaps loosen the fasteners a bit.

Juwalla #

I am not sure why the X $tr is different than Y, but it is. I was thinking that they would be the same since they are all Nema 23 with the same pulleys and belts. My only guess is that the belt tension could be different but it doesn't feel different when I tug on the belts a bit. I have everything in my garage that is not climate controlled and the temperature has been fluctuating a bit. I had to tighten them during the middle of summer, but they don't seem to be to tight now that it is cooling down a little. I am going to do the whole thing again just in case I overlooked something.
I have pictures of the process if that would help but I am not sure how to upload them to the post. I see the img button, but it wants a url and I don't have them uploaded anywhere.

I am pretty positive that the Z-axis is not binding. I can run the fast (manual) homing in tgFX with no issues. Doing the normal speed homing doesn't have any issues either.

Juwalla #

OK, I was feeling a little confident and went ahead and ran the same job as before. The 6" diameter circle I mentioned above. I think TinyG just likes to waste my money. =)

So the first pocket was looking good and the second started off good, then towards the end I could tell that it was not cutting the pocket symmetrical to the first. I have no idea if it lost a step or what, but the second circle was offset to the left about 1/8th inch.

If I configure the machine and it comes out correct 5 out of 5 times then run a job and the job goes south, how do you trouble shoot that?

Well lookey there!!!!!!!!! The POS Inventables drive pulley screws (well one of them to be exact) came out at some point. Nothing I like more than making myself look like a JACKASS! I wont make that mistake again. By that mistake I mean the pulley screws, not the making myself look stupid. I do that quite often it seems.

I'll leave everything the way it was in the above post as an example for others and to humble myself. Feel free to share and have a laugh on me.

Here is an addition to the "he's got a screw loose issue." I found the missing pulley screw hidden under the little tab that holds the belt. If anyone else has a screw loose they might find it there as well.

cmcgrath5035Staff #

I'm actually a bit surprised that a set screw being that loose resulted in such a small, therefor hard to detect, error. Perhaps it was on one of the Y motors, leaving the other to do most of the work?
Anyway, good find.

Your use of the term 'pocket' leads me to think you are milling a 2.5D job of some sort.
Perhaps now is the time to upgrade your machine to the latest tinyG FW, 438.02 if not already, I have lost track of where you are at.
While the differences between 435.10 and 438.02 are minor, they were changes to fix machine dynamics when Gcode calls for very short moves. Many 2.5D code generators seem to be outputting code with move increments at or below the minimum capability of the machine. TinyG seeks to accumulate such short moves until a physical move can be made, there were some bugs up thru 438.02.
BEWARE- Loading new FW will reset all your configs, you will have to re-enter. Make sure you have a copy of where you are at.

This forum tool is tough on images and long files. What we suggest is to set up a dropbox or equivalent clould sharing account. put images, configuration files and Gcode examples in files, and post here a URL.

And, very long threads become difficult to look back into as well.
Since you seem to be more or less up and running now , with all your screws tight ( :) ), I suggest start a new topic, with new Subject that refocuses on more specific issues.

And now perhaps an opportunity to address your CAMBAM post processor question. I don't use CAMBAM, so don't have specific suggestions, but here are some fundamentals that the post processor might address.
1. Configure to use arcs - Gcode G2 and G3 commands. Work well with tinyG.
2. Use reasonable precision - tinyG will keep track of line segment requests down to 0.08mm and arc segments down to 0.10mm. not much point in requesting a 1.0001 mm move.
3. Do the math and understand the fundamentals of your setup, specifically the minimum moves that it can make in the X,Y and Z directions. The minimum move a stepper can make is a microstep. The number of steps per revolution is a physical parameter of you motor. The number of microsteps is programmable, [1,2,4,8]. Pulley diameter and belt pitch determine the travel per revolution. From all those parameters, compute travel per microstep in each direction. You will find these to be larger than the tinyG minimums for a typical NEMA23 machine. It is then a personal preference how precise you have your Gcode generated. Maybe 2x, meaning that if a microstep is 0.2 mm, generate Gcode with 0.1mm accuracy. Super accurate Gcode will run, but it will be a much larger file, will take longer for tinyG to interpret (i.e. slow the machine sometimes) and won't deliver any additional accuracy in the final job, because of the machine fundamentals.

Enjoy

This topic is from the original forum (October 2014). Your reply starts a new discussion linked to it.

Reply

Different problem? Ask a new question

Back to TinyG Support or latest activity.