cmcgrath5035

Forum Replies Created

Viewing 15 posts - 166 through 180 (of 1,771 total)
  • Author
    Posts
  • in reply to: tinyg odd communication #11741
    cmcgrath5035
    Moderator

    What you describe sounds like a noise issue with your limit switches, maybe.

    I have no experience with PiZero, but Pi3 works great so I do’t think it is Pi’s fault.
    Do you have shielded twisted pair to you limit SWs , shield grounded only at tinyG end?

    Since I have never run the tinyG tests, can’t vouch they actually work.

    in reply to: tinyg odd communication #11739
    cmcgrath5035
    Moderator

    Hmmm, please define “lost control”

    From your top post, issuing $sys creates a proper looking response, so I conclude basic command interface is sort of working.

    Are you sure CoolTerm and tinyG are running at same baud rate(115200)?

    Changing $ej can be tricky, because tinyG auto switches between Text and JSON based on the format of a command from Coolterm to tinyG.
    So send a text command, get text response; send JSON formatted command, get JSON formatted response

    in reply to: tinyg odd communication #11737
    cmcgrath5035
    Moderator

    Hmmmm, interesting.
    I have never tried these Test commands and don’t have an active machine available at the moment.

    I don’t think it is an issue, but see you have $ex set to 1 (XonXoff)
    Is CoolTerm set for XonXoff?
    Or try RTS/CTS.

    in reply to: plotting speed #11734
    cmcgrath5035
    Moderator

    Zootalaws has described what it takes to make a heavy machine perform, perhaps you have something more modest.

    Does your current setup print accurately, just too slowly?

    $xvm, $yvm are maximum velocities. Does your Gcode explicitly issue slower speeds?
    e.g. G0 x__ y__ F1000
    Once sent to the machine, that F speed will remain in effect until changed by a subsequent command, e.g. G0 x__ y__ F3000

    What CAM software do you use? Chilipeppr has a speed override capability, other interfaces may as well. Or go back to the source.

    in reply to: TinyG2 pinout diagram questions #11723
    cmcgrath5035
    Moderator

    You choose (parameter set) the type of switch you use, NC or NO.
    TinyG look for a transition form normal state to switch operated state.

    in reply to: TinyG2 pinout diagram questions #11717
    cmcgrath5035
    Moderator

    Q1 – Yes, the DUE should be able to interface to the 2 – 5v logic directly. Beware that G2Core is Enable active low (a.k.a. enable-bar). Not sure that is directly applicable with TB6600

    Q2 – the micostep outputs are binary programming for the the driver device, does the TB6600 support that input?
    Limit switch inputs are for a NO or NC switch . You need to provide some lead filtering similar to what is provided on tinyG or Gshield (R-C lpf)

    Q3 – That lead is GrblEnable, name of the Gshield pin when Gshield is used on a UNO with Grbl.

    Q4 – G2Core provides a o-100% Motor power control, similar to the pot ON tingG. See PL parameter at https://github.com/synthetos/g2/wiki/Configuring-0.99-Motors#summary
    TB6600 may not support that

    in reply to: Error Message Interpretation #11716
    cmcgrath5035
    Moderator

    Is this message insinuating that this is the command string the TinyG received from me?

    I think so, but have not seen this before.
    What are the Gcode commands (3-4 lines) before your G01 ??

    in reply to: Strange CoolTerm Connection Issues #11705
    cmcgrath5035
    Moderator

    I used CoolTerm many moons ago. I do recall that on occasion I have to start CoolTerm, then reset tinyG to see the command prompt tinyG>.

    My guess would be that the settings in your CoolTerm are not identical between your new desktop and your friends old laptop.
    I am think settings like what to do when enter is hit. Append nothing, CR, CFLF, etc. Cool Term has a number of options like this

    It might help if you capture a parameter dump with your once chance.
    That would be $$ then a CR

    in reply to: Motors stop but TinyG thinks everything's OK #11702
    cmcgrath5035
    Moderator

    Thanks for the follow-up, some good suggestions.
    This is a world where hobbyist techniques, connectors and layouts meet industrial applications.

    I’ll add to your list a caution that dealing with the typically fine gauge wires that connect stepper motors to the rest of the world can be difficult to work with and maintain. A forum suggestion a few years back suggested using wire ferrules, I found them very handy. Here is what I used:
    Wire Ferrules

    I suggest not connecting either Power – or Power + to Earth ground unless you really understand ALL the elements in your system.
    There are no universal standards for implementation of transformerless power supplies. Look at and read the schematics of your subsystems.
    Using optically coupled switches for interfaces like the tinyG output port that controls spindle motors can help. If your system uses external stepper drivers that connect to the internal logic ports on the tinyG controller, you will find that virtually all the available off the shelf units are opto-isolator coupled

    in reply to: Motors stop but TinyG thinks everything's OK #11700
    cmcgrath5035
    Moderator

    I understand your baffle.
    In a typical machine, none of the active devices (steppers, limit switches, spindles, etc) should have any electrical connection to the machine framework.

    If you wanted to pursue understanding what was going on, I would start by attempting to understand in detail how your power supplies are connected.
    The Low cost (relatively speaking) compact transformer-less DC supplies typically used in this space have a indeterminate relationship, output wise, to AC Line-in and Neutral. Some have their positive output sitting one one two diodes above at below Line in, while – output 24V below Neutral. Way back at your breaker box, Neutral and earth (green wire) are connected.
    But other designs are just the opposite, – out is referenced to Neutral and + output 24V above neutral.
    Very strange things can happen if you connect the wrong things together.

    in reply to: Footer Code #11697
    cmcgrath5035
    Moderator

    I am not sure I understand how you footer code is supposed to work.
    Is this string of Gcode commands appended to all jobs?
    For example, unclear to me what you expect $gco to do without a parameter. Is your desire to reset to the default coordinate system? I don’t think this will achieve that. I have never seen parameter settings blended with a Gcode file.
    Reset, what you are doing now (if I understand correctly) would re-read/reset all defaults.

    TinyG is tasked with running a job, not managing multiple jobs.
    You probably need to do that at the CAM layer, e.g. Chilipeppr or cnc.js

    in reply to: TinyG end stop switches/limits? #11695
    cmcgrath5035
    Moderator

    Review Limits

    Placing a disconnect switch in series with stepper winding leads would not be a good long term idea. It would de-energize the motor, but tinyG would have no idea it was disconnected and would continue to run whatever Gcode job was running at the time.

    Installing the limit switches per the Wiki would logically de-energize the motors.

    Stopping or pausing a running Gcode job is non trivial and is typically handled by the CAM layer (machine controller) software. Chilipeppr and CNC.js are typical CAM environments for tinyG, but there are others.
    Review this link Gcode

    • This reply was modified 4 years, 11 months ago by cmcgrath5035.
    in reply to: TinyG not reading arc commands correctly? #11690
    cmcgrath5035
    Moderator

    Thanks for posting the F360 analysis and recommendations.

    in reply to: Motors stop but TinyG thinks everything's OK #11689
    cmcgrath5035
    Moderator

    I thought a bit more on your problem and wondered as well, you did say that motion terminated but did not say it was a flashing leds/ limit exceeded sort of event.

    My guess would be that the coupled noise somehow affected code execution in the tinyG controller, although explaining how the program execution could remain ‘sane’ is a bit of a stretch. Best guess would be corruption of the dynamic part of the process (RAM values)while the tinyG FW and parameters, in non-volatile storage remained in-tact.

    in reply to: TinyG not reading arc commands correctly? #11686
    cmcgrath5035
    Moderator

    You are correct, traffic here has reduced quite a bit and spread across many other forums.

    Switching to mm Gcode is always the first suggestion.
    tinyG does all its calculations in mm, so each inch mode command has to get converted. The CPU only does 8 bit math, rounding errors with small (slight) arcs(large values of I and J in G3 commands) can result is arc end point disconnects.

    If mm mode does not solve your issues, regenerate you Gcode without arcs.

Viewing 15 posts - 166 through 180 (of 1,771 total)