Home › Forums › TinyG › TinyG Support › Clunk at end of circle
- This topic has 14 replies, 3 voices, and was last updated 10 years, 9 months ago by tomking505.
-
AuthorPosts
-
January 16, 2014 at 3:06 am #5171tomking505Member
Alden and Riley,
I just sent you a video that shows a loud clunk after routing a circle. This is the code that does it.
( Made using CamBam - http://www.cambam.co.uk ) ( FINAL GEAR large 1/11/2014 7:07:36 PM ) ( T7 : 3.18 ) G21 G90 G64 G40 G0 Z1.0 ( T7 : 3.18 ) T7 M6 ( Pocket1 ) G17 M3 S1000 G0 X187.0752 Y183.3798 G1 F2500.0 Z-1.0 G3 F2500.0 X75.956 Y246.1622 I-74.0752 J-1.3798 G3 Y117.8378 I37.044 J-64.1622 G3 X187.0881 Y182.0 I37.044 J64.1622 G3 X187.0752 Y183.3798 I-74.0881 J0.0 G0 Z1.0 G0 Z1.0 M5 M30
There is nothing physically wrong with the machine. It seems to do this as it transitions from one sequence to another, like from curves to straight. I had some gear code where it clunked after each tooth. After seven or eight layers, it was half an inch off, ruining big chunk of nylon.
This is why I was trying to update the firmware. Any ideas? I can’t continue to ruin materials and waste hours of time.
- This topic was modified 10 years, 10 months ago by tomking505.
January 16, 2014 at 9:31 pm #5174aldenMemberCan you please tell us what firmware build you are running and post your settings? Thanks
January 16, 2014 at 9:34 pm #5175tomking505MemberSure. Meant to do that last night.
[fb] firmware build 380.06 [fv] firmware version 0.96 [hv] hardware version 8.00 [id] TinyG ID 1H4973-D2L [ja] junction acceleration 100000 mm [ct] chordal tolerance 0.001 mm [st] switch type 0 [0=NO,1=NC] [mt] motor disble timeout 60 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] [tv] text verbosity 0 [0=silent,1=verbose] [qv] queue report verbosity 0 [0=off,1=filtered,2=verbose] [sv] status report verbosity 1 [0=off,1=filtered,2=verbose] [si] status interval 100 ms [ic] ignore CR or LF on RX 0 [0=off,1=CR,2=LF] [ec] expand LF to CRLF on TX 0 [0=off,1=on] [ee] enable echo 0 [0=off,1=on] [ex] enable flow control 1 [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] [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 2 [0=X,1=Y,2=Z...] [1sa] m1 step angle 1.800 deg [1tr] m1 travel per revolution 4.020 mm [1mi] m1 microsteps 8 [1,2,4,8] [1po] m1 polarity 1 [0=normal,1=reverse] [1pm] m1 power management 0 [0=remain powered,1=shut off when idle] [2ma] m2 map to axis 3 [0=X,1=Y,2=Z...] [2sa] m2 step angle 1.800 deg [2tr] m2 travel per revolution 4.020 mm [2mi] m2 microsteps 8 [1,2,4,8] [2po] m2 polarity 1 [0=normal,1=reverse] [2pm] m2 power management 1 [0=remain powered,1=shut off when idle] [3ma] m3 map to axis 1 [0=X,1=Y,2=Z...] [3sa] m3 step angle 1.800 deg [3tr] m3 travel per revolution 4.020 mm [3mi] m3 microsteps 8 [1,2,4,8] [3po] m3 polarity 0 [0=normal,1=reverse] [3pm] m3 power management 1 [0=remain powered,1=shut off when idle] [4ma] m4 map to axis 0 [0=X,1=Y,2=Z...] [4sa] m4 step angle 1.800 deg [4tr] m4 travel per revolution 4.020 mm [4mi] m4 microsteps 8 [1,2,4,8] [4po] m4 polarity 0 [0=normal,1=reverse] [4pm] m4 power management 1 [0=remain powered,1=shut off when idle] [xam] x axis mode 1 [standard] [xvm] x velocity maximum 2000.000 mm/min [xfr] x feedrate maximum 2500.000 mm/min [xtm] x travel maximum 150.000 mm [xjm] x jerk maximum 10000000 mm/min^3 [xjh] x jerk homing 20000000 mm/min^3 [xjd] x junction deviation 0.0500 mm (larger is faster) [xsn] x switch min 1 [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 800.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 3000.000 mm/min [yfr] y feedrate maximum 3500.000 mm/min [ytm] y travel maximum 150.000 mm [yjm] y jerk maximum 10000000 mm/min^3 [yjh] y jerk homing 20000000 mm/min^3 [yjd] y junction deviation 0.0500 mm (larger is faster) [ysn] y switch min 1 [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 800.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 3000.000 mm/min [zfr] z feedrate maximum 2500.000 mm/min [ztm] z travel maximum 75.000 mm [zjm] z jerk maximum 10000000 mm/min^3 [zjh] z jerk homing 20000000 mm/min^3 [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 1 [0=off,1=homing,2=limit,3=limit+homing] [zsv] z search velocity 800.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 3 [radius] [avm] a velocity maximum 172800.000 deg/min [afr] a feedrate maximum 172800.000 deg/min [atm] a travel maximum -1.000 deg [ajm] a jerk maximum 5760000000 deg/min^3 [ajh] a jerk homing 5760000000 mm/min^3 [ajd] a junction deviation 0.0500 deg (larger is faster) [ara] a radius value 0.1989 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 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 (larger is faster) [bra] b radius value 1.0000 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 (larger is faster) [cra] c radius value 1.0000 deg [p1frq] pwm frequency 100.000 Hz [p1csl] pwm cw speed lo 1000.000 RPM [p1csh] pwm cw speed hi 2000.000 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.000 RPM [p1wsh] pwm ccw speed hi 2000.000 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 75.000 mm [g55y] g55 y offset 75.000 mm [g55z] g55 z offset 0.000 mm
- This reply was modified 10 years, 10 months ago by tomking505.
January 16, 2014 at 10:45 pm #5182aldenMemberThanks. I’ll give this a run, but I’m pretty sure you are going to need to upgrade the firmware from 380.06. We’ve made a lot of progress since then. If you are so inclined you can update from the edge branch.
January 17, 2014 at 1:02 am #5183tomking505MemberI would upgrade the firmware, but my attempts to do so have failed.
I described the problem in detail in another thread. Basically, the installer crashes with no explanation, and no error code.
January 17, 2014 at 1:06 am #5184tomking505MemberHere is what I said in the other thread about my attempts to upgrade the firmware:
The stuttering bug has reared its head again, and TinyG damaged an expensive hunk of nylon. I’ve tried for the past two hours to figure out how to update the firmware, but I hit several roadblocks.
First, you suggest using AVRdude that came with Arduino. I have Arduino, but no AVRdude. I can see the TinyG in the Arduino serial window. I can trigger boot mode by issuing $boot=1 from inside Arduino. But no idea how to use it to update the firmware.
I installed AVRdude. After some path variable issues, and figuring out that I have to issue $boot=1 in CoolTerm, then immediately close it and issue the AVRdude command. But it crashes during the loading process. Ends in Failed, Failed, Failed a thousand times so that any useful info flies off the screen. And the logfile switch doesn’t work. If I redirect the STDERR to a file, it contains nothing. Frustrating.
Which firmware? I went here:
https://github.com/synthetos/TinyG/wiki/TinyG-Boot-Loader
It lists this link:
https://raw.github.com/synthetos/TinyG/master/firmware/tinyg/default/tinyg.hex
If that’s not the right one, which one should I use, and where is it?
January 17, 2014 at 8:27 am #5187tomking505Member>I’m pretty sure you are going to need to upgrade the firmware from 380.06.
And in the most respectful way possible, can I ask where that firmware is located?
January 17, 2014 at 10:38 am #5188aldenMember🙂
The .hex file is on the edge branch in the github:
https://github.com/synthetos/TinyG/tree/edgein the firmware/tinyg/default directory. Don’t worry if you looked for it before and didn’t find it, I just added it back in. Also, I expect another push to edge in the near future – perhaps as early as this weekend.
January 18, 2014 at 4:58 pm #5191kajukMembertgFX fails to communicate with this version:
>[+]Connected to /dev/tty.usbserial-DA00CB3F Serial Port Successfully.
>
>Getting TinyG Firmware Build Version….And after that nothing happens.
- This reply was modified 10 years, 9 months ago by kajuk.
January 18, 2014 at 5:29 pm #5193kajukMemberSeems like that rather than being an edge version it’s still a test version – $test=? commands only move Motor 4.
January 18, 2014 at 5:52 pm #5194aldenMemberI should probably wait for Riley to get back from a conference as he’s the keeper of tgFX, but let me see if I can answer your question. The edge firmware needs to work with the tgFX edge, which is lagging the firmware by a bit. Please give us a few days to get these lined up and get a version of tgFX out there that works with the edge branch. Sorry for the confusion.
In the mean time you can always drive TinyG directly from Coolterm, albeit without some of the nice features tgFX offers.
January 18, 2014 at 6:03 pm #5195kajukMemberSure, but even from the terminal I can move only Motor 4 so it’s pretty much unusable at the moment.
January 18, 2014 at 6:48 pm #5196tomking505MemberI have already asked multiple times. What is the magic to update the firmware?
The AVRdude instructions in the wiki are either wrong or incomplete. I have done it many times and every time it crashes in an error with no error log.
I have updated firmware on many microcontrollers. It shouldn’t be this hard.
UPDATE: I just added a wiki page that begins to document where to find the firmware, and I added a link to it on the main page. It amazes me that something so pivotal is not documented already.
- This reply was modified 10 years, 9 months ago by tomking505.
January 18, 2014 at 8:00 pm #5200aldenMemberI appreciate your pitching in. You know, we work very hard on this and it’s quite disappointing when people are not satisfied. We are not getting rich off this, and it’s not our regular jobs. Any help we can get is much appreciated.
January 18, 2014 at 9:15 pm #5204tomking505Member>We are not getting rich off this, and it’s not our regular jobs.
Hold it a second.
Your site says very prominently that this is
- “Affordable INDUSTRIAL GRADE Motion Control.”
Industrial grade means I can do meaningful work without destroying something. Industrial grade means fully-functional. You can’t claim TinyG is “industrial grade” and also that it’s okay it doesn’t work because it’s your hobby.
I’d be sympathetic if you didn’t seem to be working on other projects while this one is still broken. If you are going to take money for this project, there should be ONE DAMN SETUP that works. Working firmware. A functional bootloader. Complete basic documentation.
I’d be more thrilled to hear about your arduino-based TinyG, if the original TinyG worked correctly. It seems to me, the guy with three of your boards and a pile of stuff they destroyed, that you are farting around with new stuff while the people who already PAID YOU are dead by the side of the road.
- This reply was modified 10 years, 9 months ago by tomking505.
- This reply was modified 10 years, 9 months ago by tomking505.
- This reply was modified 10 years, 9 months ago by tomking505.
- This reply was modified 10 years, 9 months ago by tomking505.
-
AuthorPosts
- You must be logged in to reply to this topic.