absolute newbe

Home › Forums › TinyG › TinyG Support › absolute newbe

Tagged: ,

Viewing 15 posts - 1 through 15 (of 34 total)
1 2 3
  • Author
    Posts
  • May 26, 2015 at 4:36 pm #7748
    snooperace
    Member

    Hi
    I am completely new at this and need help configuring my newly built OXbuild cnc. What I have is the z motor is a nema 17 and is drive by 8mm lead screw with 2 pitch, the X axis is a nema 23 and belt driven and the y axes has two nema 23 motors both belt driven.

    what I need now is how do I configure my tinyg to understand my machine and its limits , distance. for arguments sake my first attempt to drive just the X drive from one side to the next using chilipepper to jog it chilipepper reports that the x axis travel is 9cm when in fact it is 60cm.

    I also need to know if the wiki can be downloaded in a more flowing format so that I can start on page one and work my way through it to learn get my machine to the point where I can actually start to us it.

    And lastly what has been really doing me some mental damage is what spindle to choose as I wish to work with both wood and aluminum sheet. So if anyone could guide me on that I would be most grateful.

    Regards

    May 26, 2015 at 5:32 pm #7750
    akfreak
    Member

    Well I spoke to John Lauer (the ChiliPeppr originator) and he said you have to UAE trial and error to set up the steps correctly. Had said to peek at the Shapeoko setup and use that as a starting point.

    I am helping a friend finish us OX build with TinyG using Chilipeppr

    May 26, 2015 at 8:26 pm #7754
    cmcgrath5035
    Moderator

    I would think your OX setup would be similar to a ShapeOko2, but have no idea what belt pitch and pulley sizes you might have.
    Search the wiki for tinyG Configuration and for ShapeOko.

    Unfortunately, the wiki is what it is.

    Spindle choice is a wide open topic. Most any spindle will do AL sheet if you are willing to wait (slow speed). Have a browse around

    You’ll see lots of examples of what folks are doing and are happy with.

    May 27, 2015 at 6:15 pm #7757
    snooperace
    Member

    Thanks for the information here is what I have

    for the z axis I have an 8mm lead screw with 2mm pitch
    the x axis is belt drive with a 3mm pitch GT3 belt and a 20 tooth cog drive by a nema 23

    the y axes is drive by two nema 23’s both on belts with 20 tooth cogs and gt3 belts 3mm pitch.

    I have set $nTR=26.67 as that is what was calculated for the x and y axes
    $nsa=1.8
    $nmi=8
    Polarity is set to 0 for all drives except for one of the y axes motors as it is a duel drive y axis.

    Can you also please tell me how I can type out the config in to a text file and send the entire file to the tinyg rather than having to type it in one line at a time

    I have also noticed that when I am able to get one of the axes to move it will start off then stop and just make a noise. Can you tell me what could be the cause of this.

    sorry for all the dumb questions.

    thank you very much

    May 28, 2015 at 4:32 pm #7758
    cmcgrath5035
    Moderator

    Hmmm, first I have seen of 3mm pitch belts (but by no means do I claim to have seen it all, by a long shot).

    If these are 20 tooth pulleys, 1 rotation should be 20 teeth, and $_tr would be 20*3=60mm.
    Most NEMA23 setups I have seen have been with GT2 belts and 20 tooth pulleys I guess, $_tr=40 mm for those.

    $ztr would be 2mm for 2mm pitch leadscrew.

    If you use Chilipeppr, the configuretinyG widget can be very helpful.See

    You can also review this

    If you want something from CLI, look here:

    Once you have a config file, here is an easy way to make it available for review

    By the way, I highly recommend you enter and maintain parameters in MM, not inches. Virtually all wiki and help items are in mm

    I have also noticed that when I am able to get one of the axes to move it will start off then stop and just make a noise. Can you tell me what could be the cause of this.

    Need a bit more detail; are you entering a GCode command such as G0 X10 (to move to coordinate X=10 mm)?
    After a move, depending on settings, the motors will remain energized for a period of time to hold the position, perhaps that is what you call ‘make a noise’.

    • This reply was modified 9 years, 5 months ago by cmcgrath5035.
    May 31, 2015 at 3:11 am #7774
    snooperace
    Member

    Thank you @cmcgrath5035

    here is my config settings. I have just added the homing switches and I am trying to work my way through that so that I dont have to keep resetting the tinyg each time it homes.

    $$
    [fb] firmware build 440.14
    [fv] firmware version 0.97
    [hp] hardware platform 1.00
    [hv] hardware version 8.00
    [id] TinyG ID 3W5230-LJD
    [ja] junction acceleration 5000 mm
    [ct] chordal tolerance 0.0100 mm
    [sl] soft limit enable 0
    [st] switch type 0 [0=NO,1=NC]
    [mt] motor idle timeout 2.00 Sec
    [ej] enable json mode 0 [0=text,1=JSON]
    [jv] json verbosity 1 [0=silent,1=footer,2=messages,3=configs,4=linenum,5=verbose]
    [js] json serialize style 1 [0=relaxed,1=strict]
    [tv] text verbosity 1 [0=silent,1=verbose]
    [qv] queue report verbosity 1 [0=off,1=single,2=triple]
    [sv] status report verbosity 1 [0=off,1=filtered,2=verbose]
    [si] status interval 250 ms
    [ec] expand LF to CRLF on TX 0 [0=off,1=on]
    [ee] enable echo 1 [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 26.6700 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 26.6700 mm
    [2mi] m2 microsteps 8 [1,2,4,8]
    [2po] m2 polarity 1 [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 26.6700 mm
    [3mi] m3 microsteps 8 [1,2,4,8]
    [3po] m3 polarity 1 [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 10.0000 mm
    [4mi] m4 microsteps 8 [1,2,4,8]
    [4po] m4 polarity 1 [0=normal,1=reverse]
    [4pm] m4 power management 2 [0=disabled,1=always on,2=in cycle,3=when moving]
    [xam] x axis mode 1 [standard]
    [xvm] x velocity maximum 800 mm/min
    [xfr] x feedrate maximum 800 mm/min
    [xtn] x travel minimum 0.000 mm
    [xtm] x travel maximum 800.000 mm
    [xjm] x jerk maximum 5000 mm/min^3 * 1 million
    [xjh] x jerk homing 40 mm/min^3 * 1 million
    [xjd] x junction deviation 0.0500 mm (larger is faster)
    [xsn] x switch min 3 [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 250 mm/min
    [xlv] x latch velocity 10 mm/min
    [xlb] x latch backoff 5.000 mm
    [xzb] x zero backoff 5.000 mm
    [yam] y axis mode 1 [standard]
    [yvm] y velocity maximum 800 mm/min
    [yfr] y feedrate maximum 800 mm/min
    [ytn] y travel minimum 0.000 mm
    [ytm] y travel maximum 600.000 mm
    [yjm] y jerk maximum 20 mm/min^3 * 1 million
    [yjh] y jerk homing 40 mm/min^3 * 1 million
    [yjd] y junction deviation 0.0500 mm (larger is faster)
    [ysn] y switch min 3 [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 250 mm/min
    [ylv] y latch velocity 10 mm/min
    [ylb] y latch backoff 5.000 mm
    [yzb] y zero backoff 5.000 mm
    [zam] z axis mode 1 [standard]
    [zvm] z velocity maximum 500 mm/min
    [zfr] z feedrate maximum 800 mm/min
    [ztn] z travel minimum 0.000 mm
    [ztm] z travel maximum 100.000 mm
    [zjm] z jerk maximum 20 mm/min^3 * 1 million
    [zjh] z jerk homing 40 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 3 [0=off,1=homing,2=limit,3=limit+homing]
    [zsv] z search velocity 250 mm/min
    [zlv] z latch velocity 5 mm/min
    [zlb] z latch backoff 5.000 mm
    [zzb] z zero backoff 5.000 mm
    [aam] a axis mode 3 [radius]
    [avm] a velocity maximum 230400 deg/min
    [afr] a feedrate maximum 230400 deg/min
    [atn] a travel minimum -1.000 deg
    [atm] a travel maximum -1.000 deg
    [ajm] a jerk maximum 5760 deg/min^3 * 1 million
    [ajh] a jerk homing 11520 deg/min^3 * 1 million
    [ajd] a junction deviation 0.0500 deg (larger is faster)
    [ara] a radius value 0.1990 deg
    [asn] a switch min 0 [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 deg/min
    [alv] a latch velocity 100 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 75.000 mm
    [g55y] g55 y offset 75.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 0.000 mm
    [g56y] g56 y offset 0.000 mm
    [g56z] g56 z offset 0.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
    tinyg [mm] ok>

    May 31, 2015 at 11:07 am #7776
    cmcgrath5035
    Moderator

    I don’t understand your $_tr values.
    For X and Y you still have 26.67mm. Did you change pulleys?
    For Z, you have $ztr=10mm, but you have a 2mm pitch lead screw?
    Can you share your calculation method that results in 26.67 and 10?

    These values will result in velocity and position errors, but by themselves should not cause homing to fail.

    What happens when you try to home, that causes you to reset?

    Have you tried homing 1 axis at a time? (X, then Y, Then Z)?

    You have the homing switches properly designated for Xmin, Ymin and Z min.

    Are you sure that the axes move in the proper direction/ For example, id you issue a G91 (relative mode) then a G1 X-5, does the gantry move toward the X0 limit switch?
    Polarity is sort of a relative thing.

    You have set up for NO switches, which are less noise immune than NC switches..
    Did you use shielded cable to wire up your switches? The shields should be grounded ONLY at the tinyG end.

    If you can, post parameters to a cloud file(dropbox, etc) as suggested.
    The forum tool removes blanks, making these long files more difficult to visualize.
    I usually download you file and use a ‘diff’ tool to highlight differences from a known good file.

    May 31, 2015 at 11:17 am #7777
    cmcgrath5035
    Moderator

    In first post your wrote:

    what I need now is how do I configure my tinyg to understand my machine and its limits , distance. for arguments sake my first attempt to drive just the X drive from one side to the next using chilipepper to jog it chilipepper reports that the x axis travel is 9cm when in fact it is 60cm.

    Keep in mind that tinyG has no idea where you gantry actually is, what is does know is how many microsteps it has commanded from the 0,0,0 location. It calculates the movement per microstep from the parameters, $_tr, $_mi and $_sa,.

    You report of 60cm (600mm) when tinyG reports 9cm (90mm) does not makes sense.
    Don’t mess with limits and homing until you get your parameters correct.
    Zero the gantry in the middle of the work area, then work your parameters until commands G1 X10, a G1 Y10 and G1 Z10 move the correct distance in the correct direction.

    May 31, 2015 at 12:15 pm #7778
    snooperace
    Member

    @cmcgarth5053

    Dropbox account created

    https://www.dropbox.com/s/hfnfq9urksctdlv/Modsetup.txt?dl=0
    This is my current settings I have plugged in to Tiny G.

    The calculations for my x and y stepper I get from http://prusaprinters.org/calculator/

    On the oxbuild store the gt3 belt I got reviles that I have a 3mm tooth to tooth pitch.

    Although being in the IT industry not on the programming side I am really having a hard time getting chilipeppr and tinyg working reliably. I have not yet got to the point where I am trying to get the correct measurements. I am still having issues with loading a gcode file and running it.
    Sometimes the code will run and at other times not with no identification as to what is causing it.

    I dont have issues communication with tinyg using coolterm. All my problems are with chilipeppr.

    I use scetchup and scetchucam to generate the gcode.

    This is a very steep learning curve and although I thought I was up to it I am not so sure now. If there was more feedback as to what chilipeppr was doing and if there is a problem at least then I could try and solve it.

    I have also had issue with the configure widget it does not appear to save the changes to the tinyg nor will it copy the settings to the other drives so not sure if the changes are accepted or not.

    I do appreciate the assistance provide on this forum thanks

    May 31, 2015 at 2:34 pm #7782
    cmcgrath5035
    Moderator

    Cool calculator, but tinyG does not work like that.

    You provide $xtr = 60 mm (=20 teeth * 3 mm pitch) , Travel per Rotation
    You provide $sa=1.8 (=200 steps per rotation)
    You provide $xmi = 8 microstep setting
    And tinyG computes the distance that each step ‘tick’ moves, which would be 60/(200*8) mm, for internal use.

    So you need to fix your $xtr, $ytr and $ztr

    I would stick with the chilipeppr logo Gcode that auto loads for early experiments,.

    Don’t run Gcode until you can jog the correct distance reliably.

    May 31, 2015 at 5:09 pm #7785
    snooperace
    Member

    Thanks Carl not sure what you mean by chilipeppr logo gcode.
    Also can you tell me why I am having communication problems with chilipeppr I have tried a solution you suggested in a post I have read elsewhere ” Disconnect CP from tinyG using the ‘disconnect’ icon in the SPJS widget (the Reconnect black pop-up will appear), then reload CP/tinyG using the browser refresh icon on the browser menu bar, then reconnect to your tinyG by selecting the Reconnect”
    Here is a screenshot of what I am getting on CP please note the yellow check marks
    https://www.dropbox.com/s/06pr5100e7wd9jg/Capture.JPG?dl=0

    Regards

    May 31, 2015 at 6:09 pm #7786
    snooperace
    Member

    Here is a very strange occurrence working on the x axis alone using an electronic vernier I have changed $1tr= from 5 to 100 and the distance moved for G0 X20 remains 45mm no matter what $1tr is changed to.

    This is using coolterm to send the gcodes to the tinyg

    when the settings are changed is it required to reset the board or will the setting changes be accepted on the fly

    May 31, 2015 at 9:00 pm #7787
    cmcgrath5035
    Moderator

    The display in the middle of your CP screenshot is a rendering by the simulator of a Gcode file that auto loads with CP.
    If you go to the Gcode widget, that Gcode will be sent to tinyG when you select the “run” [right arrow] icon.

    Looking at your screenshot, on the left, in the Serial Port Console widget, all the lines of commands that have been sent that have yellow checkmarks – they have not been executed and responded too.
    When they execute, they turn green.

    On the right side, the 77 under tinyG confirms that tinyG is not respoonding to commands.
    I believe this is 77 commands waiting response.

    Are you sure that COM11 is tinyG?

    For your second post, simple answer, no, changes to tinyG parameters is immediate IF the change is executed. In coolterm, you have to look for the response message.
    The only exception to this is $p1frq, the pwm frequency – that does require a reset.

    Or try this:
    $1tr=10
    $1tr (this will read back the value of $1tr, should be 10
    $1tr=20
    $1tr (do you get a $1tr=20 response)?

    May 31, 2015 at 10:55 pm #7788
    cmcgrath5035
    Moderator

    By the way, having reread this thread I realize I added confusion by referring to $xtr, which is not a parameter, rather than $1tr, with motor 1 assigned to x axis. It does appear you realized that as you properly refer to $1tr, etc.

    My suggestion: turnoff linit switches and for now don’t fiddle with Gcode,
    We need to get the machine running so you can draw a roughly right size 10mm (or 20 mm square from the command line. By roughly right, I mean setting $1tr=$2tr=$3tr=60mm (assuming your original 20 toot pully and GT3). While you are at it, $4tr=2mm. You should then be able to zero your machine in the work space and from the command line (CoolTerm or CP) enter

    G21 G91 (mm mode, set incremental mode)
    G1 X10
    G1 Y10
    G1 X0
    G1 Y0

    This should traverse a square, 10mm on a side

    And by roughly right, I mean 10mm with tolerance.
    You will want to go back and perhaps ‘tweak’ your $ntr values so that a command
    G1 X100 repeatedly moves as close to 100.0 mm as you can get (and are comfortable with).
    Belt backlash and other sources of error might dictate that $1tr-59.5 rather than 60 to get closest to a 100mm move.

    June 1, 2015 at 4:29 pm #7794
    snooperace
    Member

    ok here we go again followed your suggestions Carl, disable the home switches, Set $ntr=60 on all three motors for the x and y axis and set $4tr=2

    At this point I am just checking $1tr to move 10mm in the x direction.
    entered g21 g91
    entere g1 x10 and the machine moved 120mm or 12cm

    I then changed $1tr to 6
    Confirmed that $1tr was indeed 6 Even reset the tinyg and checked it again to confirm.
    went through the process again starting with g21 g91
    then g1 x10
    the x axis moved 100mm
    See attached
    https://www.dropbox.com/s/b46hsl7wmxsmlcw/g%20code.txt?dl=0
    https://www.dropbox.com/s/wfpjskm79oie9su/IMG_0922.MOV?dl=0

    Not sure where to go to now nor what I am doing wrong

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