TinyG Connection Issues

Home › Forums › TinyG › TinyG Support › TinyG Connection Issues

Viewing 15 posts - 16 through 30 (of 39 total)
1 2 3
  • Author
    Posts
  • August 1, 2014 at 3:27 am #6545
    chmr
    Member

    Gwandad, good to hear you have some progress.
    I’d like to clear up some confusion: Tinyg and GRBL are two different controllers offering the same functionality (with only a few differences). You have either tinyg or grbl, not both at the same time.

    Tinyg is a copntroller board + firmware.
    GRBL is a Arduino controller board + grblshield (motor driver) + firmware.

    “Universal Gcode sender” is not so universal after all, it only works with grbl, not with tinyg (speaking of the official version here, other people have ported it to tinyg).
    “GRBL controller” is a very misleading name for a software that sends Gcode to GRBL and only works with GRBL.

    To speak with Tinyg, you need other software:
    Tgfx, which you already have,
    Chilipeppr works within a browser window and has some nice features like a real preview of the Gcode,
    jCNC also works nicely with preview (german website).

    Coolterm is a very basic and simple tool, useful when you want to get directly to the tinyg hardware/firmware and want to exclude the influence of any other software. If it does not work, check the connection settings for baud rate and flow control (if tinyg is set to $ex=1, use XON in Coolterm; if $ex=2, use CTS in Coolterm).

    And you can only have one piece of software talking to tinyg at any one time, so you have to disconnect/terminate tgfx before connecting with Coolterm for example.

    August 1, 2014 at 7:28 am #6549
    cmcgrath5035
    Moderator

    I’ll add that you should be aware that tgFX will change tinyG to $ex=2, RTS/CTS flow control on startup if it is not already in that state.

    If you plan to use tgFX, I suggest you adopt a “$ex=2 mindset” and run Coolterm that way as well so as to avoid forgetting to switch.

    Two other tidbits
    1. You can run $$ from the tgFX CLI window, but the response gets double spaced and is harder to read.
    2. Coolterm can be used to send a Gcode file, in addition to being a very simple CLI interface for parameter queries and setting.

    August 2, 2014 at 7:38 am #6553
    gwandad
    Member

    Firstly let me thank you. You have obviously done a lot of homework on my account. I really appreciate it!
    You certainly cleared up some confusion. I think through following a video in open build completely lost track of the facts that I had a tiny G and not arduino and was expecting my results to be the same as theirs. Big mistake! I have now deleted all the G RBL programs. After setting cool term and TGF X as per your instructions. I can now execute $$ and get a dump. Unfortunately I have never used dropbox, so I will have to check into that as well. For the last time I will put the dump here. Sorry about that.

    The movements I was getting from the machine were quite erratic and almost throwing the machine off the table. I changed the velocity maximum and feed rate maximum from 16,000 to 1600 in both cases. The speed now seems reasonable to my untrained eye. The movement distances were also very far out so I used a ruler to set the distances. Unscientific but it worked. Hopefully tomorrow get the wooden base into the machine and should be able to do some useful testing.
    I’m still having some trouble with TGF X in that I can’t jog the individual motors.
    I had a look at chilli pepper and J CNC but decided to leave those to look at in the future. I can’t get TGF X to execute commands either, so I have quite a bit to learn as it is!
    fb] firmware build 435.10
    [fv] firmware version 0.97
    [hp] hardware platform 1.00
    [hv] hardware version 8.00
    [id] TinyG ID 2X2660-FNE
    [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 2.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 53.3400 mm
    [1mi] m1 microsteps 8 [1,2,4,8]
    [1po] m1 polarity 1 [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 53.3400 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 53.3400 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 8.0000 mm
    [4mi] m4 microsteps 8 [1,2,4,8]
    [4po] m4 polarity 0 [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 1600 mm/min
    [xfr] x feedrate maximum 1600 mm/min
    [xtn] x travel minimum 0.000 mm
    [xtm] x travel maximum 220.000 mm
    [xjm] x jerk maximum 5000 mm/min^3 * 1 million
    [xjh] x jerk homing 10000 mm/min^3 * 1 million
    [xjd] x junction deviation 0.0100 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 3000 mm/min
    [xlv] x latch velocity 100 mm/min
    [xlb] x latch backoff 20.000 mm
    [xzb] x zero backoff 3.000 mm
    [yam] y axis mode 1 [standard]
    [yvm] y velocity maximum 1600 mm/min
    [yfr] y feedrate maximum 1600 mm/min
    [ytn] y travel minimum 0.000 mm
    [ytm] y travel maximum 220.000 mm
    [yjm] y jerk maximum 5000 mm/min^3 * 1 million
    [yjh] y jerk homing 10000 mm/min^3 * 1 million
    [yjd] y junction deviation 0.0100 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 3000 mm/min
    [ylv] y latch velocity 100 mm/min
    [ylb] y latch backoff 20.000 mm
    [yzb] y zero backoff 3.000 mm
    [zam] z axis mode 1 [standard]
    [zvm] z velocity maximum 800 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 50 mm/min^3 * 1 million
    [zjh] z jerk homing 1000 mm/min^3 * 1 million
    [zjd] z junction deviation 0.0100 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 800 mm/min
    [zlv] z latch velocity 100 mm/min
    [zlb] z latch backoff 20.000 mm
    [zzb] z zero backoff 10.000 mm
    [aam] a axis mode 1 [standard]
    [avm] a velocity maximum 60000 deg/min
    [afr] a feedrate maximum 48000 deg/min
    [atn] a travel minimum 400.000 deg
    [atm] a travel maximum -1.000 deg
    [ajm] a jerk maximum 24000 deg/min^3 * 1 million
    [ajh] a jerk homing 24000 deg/min^3 * 1 million
    [ajd] a junction deviation 0.1000 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.0100 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.0100 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

    August 2, 2014 at 9:10 am #6554
    chmr
    Member

    Hi Gwandad, I looked through your config and did not find anything unreasonable. I only noticed two minor things:

    The “travel per revolution” for X and Y axes is configured as 53.34mm. If the parts list of the Ox is up to date, it should be 60mm (belt has a tooth every 3 mm, and the pulley has 20 teeth; 3 x 20 = 60mm per turn). Might want to recheck this, but your measurement is definitely more reliable than (possible outdated) theoretical values.

    And I think it’s good that you lowered max velocity, you might want to do the same for acceleration/jerk ($xjm etc). 5000 million seems a bit high to me, my Shapeoko runs at (very conservative) 80 million. Better start low and later test the limits when you have confidence in the machine.

    I can’t really help on tgfx, as I don’t use it myself, but clicking on the bottom bar opens the console where you can type in commands and see the results.

    I wish you mucho fun with your Ox!

    August 2, 2014 at 1:34 pm #6555
    cmcgrath5035
    Moderator

    Gwandad

    Good progress indeed!
    I second chmr’s speed comment. I typically run cutting feed rates of 800 (Set by Gcode). Your NEMA23’s generate a lot of torque; depending on the mass of your spindle you will probably need to secure your OX to the table top somehow or it may move around a bit.
    Start slow and work your way up, depending on the cutting you are doing and the material.

    In tgFX, the crosshair cursor (moved around by the mouse or touch pad) must be within the bounds of the preview box, which is drawn to the dimensions of Xmax, Ymax. The four arrow keys on the keyboard are for X+, X-, Y+, Y-, while the – key moves Z- and = key moves Z+
    Holding down the shift key moves faster.

    For me, dropbox is an adjective, not Proper noun. Any cloud service that provides a URL for connection should work. A useful way to share configs and Gcode files.

    August 3, 2014 at 1:25 am #6560
    gwandad
    Member

    Great joy & jubilation in the house. This afternoon I printed out the sign “SHAKEOKO 2” using a sharpie pen fixed to the z rail & executed the gcode from the Shakeoko tests.
    Thank you both for your assistance. chmr, you got me out of the wilderness & in OZ I would owe you a beer, but given the distance I will drink a toast to you both, later this afternoon. I do hope you appreciate the effort I am putting in for you guys!!!

    June 18, 2015 at 7:32 am #7858
    gwandad
    Member

    I’ve been out of action for quite a while, but am getting back into it now.I have made some nice things, but there is one remaining issue & that is the home switches. I can’t get the TinyG to recognise them. I’ve gone though the Homing & Limits Github, & seem to have all the relevant settings. If I do a home on x for instance, it runs through the switch & rattles against the stop. If I set the Xmax to 300 (mm) & push the carriage to the far side, a home (28.2 X0) sends it back the 300mm OK, so it looks like a faulty switch, but it’s not. All 3 switches are new & test OK wwith a multimeter. The Y & Z act in the same manner. Any suggestions, please?

    June 18, 2015 at 8:02 am #7860
    cmcgrath5035
    Moderator

    Lots of changes since last you posted (Aug 2014).

    Can you post your current settings?
    Post a set of parameters that have Limit switches enabled.
    Use this Method:

    Have you upgraded FW to build 440.14?
    There have been improvements in the use of switches,.

    FYI, tgFX is way out of date and no longer supported.
    Have you tried Chilipeppr?

    June 25, 2015 at 9:13 pm #7867
    gwandad
    Member

    Sorry for the delay.
    Hopefully this will be the info you requested https://www.dropbox.com/sh/0se9hqhy19dsyfl/AADUz3xbkPQZv1DeK0YZl5Gta?dl=0
    Yes I found out abouttgFX. Shame, I really liked it!
    I’m using Chilipeppr, or learning anyhow.

    June 26, 2015 at 10:02 am #7871
    gwandad
    Member

    Forgot to mention I followed https://www.synthetos.com/tinyg-homing-how-to/ through with no success.

    June 26, 2015 at 4:40 pm #7883
    cmcgrath5035
    Moderator

    For sure Chilipeppr has a learning curve, but is feature rich and being actively used and improved.

    You have an Ox machine, which is belt drives, correct?
    NEMA23 Motors?
    Your $1tr, $2tr and $3tr = 1.25mm look strange, I normally see =40mm for this sort of machine. How did you come up with 1.25mm?

    June 27, 2015 at 2:02 am #7885
    gwandad
    Member

    Yes, the OX is belt driven & has 3 Nema23 & one Nema17.
    I sent you the wrong file, I had been dropping a lot of values down to see if speed had any effecf, but I have to confess, I have absolutely NO idea where I got 1.25mm from! Of course it should be 60. I have put the current file in Dropbox as Dump2 Thanks.
    Back to the problem, Ihave (Ithink) checked the dump with TinyG Configuration for Firmware Version 0.97 & it looks ok to my untrained eye. The switches have absolutely no effect. I have even changed the TinyG card! No Joy
    I can use the machine OK without them, but I feel I should have them for safety if nothing else.

    • This reply was modified 9 years, 6 months ago by gwandad.
    June 27, 2015 at 5:52 am #7887
    cmcgrath5035
    Moderator

    Hmm, I looked in your dropbox location and see no Dump2 file, I see 4 files all 32 hours old.
    OK, you had 3mm belts so $_tr=60 is correct for 20 tooth pulley

    What I do see (in the $_tr=1.25mm dump) are NO switches set up a homing on Xmin and Ymin, homing and limit on Zmax. As such, look OK

    Are you sure they are NO?
    What command are you using to attempt homing?
    Using command line or CP?

    If you issue just a home X axis, what happens, nothing?
    No movement, no flashing leds?

    June 27, 2015 at 6:18 pm #7889
    gwandad
    Member

    Sorry Mate, I’ve really made a mess of this. New link https://www.dropbox.com/s/a0e1byha72tau2l/%24%24Dump2.pdf?dl=0
    Switches are actually NC.
    I am using CP & have gone through Homing and Limits Description and Operation for TinyG several times. I disable Y & Z, use G28.2 X0. If the spindle is placed about halfway & the command is executed, spindle moves slightly to the right, then accellerates to the left & crashes into the stop & switch. If I move it to the far side it will stop when it reaches max & goes into it’s expected latch/unlatch then stops OK. It just doesn’t recognise the switch. Same if I do the same on Y.
    I had reached this same impasse last year before I got ill & convinced myself that it was the card. With a new TinyG, exactly the same!

    June 28, 2015 at 7:32 am #7890
    cmcgrath5035
    Moderator

    OK, now see Dump2.pdf. Settings look good for starters.

    Your description is very readable, but hard to understand.
    Keep in mind that “left” and “right” are subjective and that many OX machines have a different default definition of where 0,0,0 is located, when compared to typical ShapeOko machines, so readers can get very confused. Likewise, the terms “front” and “back” are subjective and based on the readers frame of reference.

    I am not a homing user yet, so these questions are based on how I think I would debug your situation.

    Manually put you gantry in the center of the workspace and set that as 0,0,0.
    1. when you issue G0 X10, does gantry move 10 mm away from the X homing Switch.
    2. When you issue G0 X-10, does they gantry then move 20 mm toward the homing switch?
    3. Likewise for Y and Z axis.
    I expect you see what I am asking – are the switches located at Xmin, Ymin and Zmax?

    Next question would be, are you sure that the Xswitch is connected to the Xport on TinyG (Y and Z as well)?

    I would also suggest you start a separate (new ) thread. You seem to be connected and basically operational for now, so a topic such as “TinyG homing issues”, with a terse description of your setup, a repost of the link to settings and results of you homing attempts might attract others with homing experience.

    Homing works for many (most discussion is is on the Chilipeppr sites these days) so I suspect some sort of configuration issue with you switch setup.

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