cmcgrath5035

Forum Replies Created

Viewing 15 posts - 106 through 120 (of 1,771 total)
1 2 3 … 7 8 9 … 117 118 119
  • Author
    Posts
  • September 9, 2020 at 9:31 am in reply to: Trouble Shooting Setup #11893
    cmcgrath5035
    Moderator

    Is your Dropbox parameter list still accurate?

    September 9, 2020 at 9:14 am in reply to: Trouble Shooting Setup #11892
    cmcgrath5035
    Moderator

    The Chillipepr Jog widget has a setting for how far to move with each click.
    When you click to make one jog move, you should see a G0Zxx command in the serial port console.
    So if you set jog granularity to 1 mm, then a 1mm jog should show in the Serial Port Console as a G0Z1 command.

    Are you seeing that?

    Do other axes jog accurately?
    Are you sure you stepper motor parameters are correctly entered?

    You issue implies that too many step pulses are being sent to the motor or that the motor is moving too far per step pulse

    September 7, 2020 at 2:26 pm in reply to: Trouble Shooting Setup #11890
    cmcgrath5035
    Moderator

    BTW
    a G0Z10 would move the Z axis to 10mm position in absolute mode, or up 10mm in incremental mode.

    Enter the G0Z10 in the Serial Port Console widget, typically lower left corner of screen

    September 7, 2020 at 2:23 pm in reply to: Trouble Shooting Setup #11889
    cmcgrath5035
    Moderator

    Lets focus on Chilipeppr setup, the one I am most familiar with

    Easiest way to move Z is to use the Jog widget. based on settings, you can move axis up or down with fine or coarse adjustments.

    I think your M4 parameters are OK, $4tr=1.25 is typical but depends on what thread is used on the gantry
    Make sure to reset the tinyG after making parameter changes to make sure the changed parameters are installed.

    Are you using external stepper drivers by chance?

    September 7, 2020 at 12:17 pm in reply to: Trouble Shooting Setup #11885
    cmcgrath5035
    Moderator

    What method do you use to send Gcode?
    Terminal app, Chilipeppr, cnc.js, etc ?.
    Chilipeppr has a logo file that performs a graphical hello world of sorts

    If you are planning to use Z homing (to top of range), then $ztm = -50 and $ztm = 0 and you need to build you Gcode appropriately.
    Most folks don’t use the Z limit Switch. It can create a lot of confusion for users who run auto level with PCB milling.

    If you command Z axis to move 10mm, does it move just 10mm?

    OK, found it , code is here https://github.com/synthetos/TinyG/blob/master/firmware/tinyg/tests/test_003_squares.h

    Not exactly Gcode, but you can see what is going on.
    It is not compatible with ShapeOKO, attempts to traverse 10,20 and 40mm cubes.
    Code probably pre-dates the shapeoko

    September 6, 2020 at 4:43 pm in reply to: Trouble Shooting Setup #11881
    cmcgrath5035
    Moderator

    If you are homing the machine before you run tests to set the 0,0,0 point,
    then $ztn should be -32 and $ztm should be 0.0

    I am off to find the Gcode for Test 3, Squares, to see what it specify’s for maximum z level. Have never run it myself.

    Note that $ztn and $ztm really only matter if you use soft limits.
    Since $sl=0, soft limits are off

    Try turning homing and limits off, i.e. $xsn=$xsm=$ysn=$ysm=$zsn=$zsm=0.
    Jog or manually move your gantry to where you think 0,0,0 should be and hit the tinyG reset, which will make that location 0,0,0.
    then run squares.

    Can I assume you have read
    https://github.com/synthetos/tinyg/wiki/Homing-and-Limits-Description-and-Operation
    ? It is not necessarily intuitive, until you have been here for a while

    • This reply was modified 4 years, 2 months ago by cmcgrath5035.
    September 6, 2020 at 2:56 pm in reply to: Trouble Shooting Setup #11879
    cmcgrath5035
    Moderator

    Helpful way to communicate, but unfortunately the upper half of the $$ parameter dump is missing from the file.
    Missing from this info are the Z axis settings.
    By FW design, the level at top of Z , the Z limit switch, is Z=0 and all Z motion should be negative from there.
    My Guess is that your Z zero is not set right ore the Zmax value is >0 ?
    You need to determine the actual range of Z motion f.or your setup, then set $zmn and $zmx accordingly

    See if you can move a full $$ dump to the dropbox

    September 5, 2020 at 10:28 am in reply to: TinyG Makes noise but stepper doesn't move #11877
    cmcgrath5035
    Moderator

    @cheshirecnc
    The previous poster had several unusual parameters, it would be good for you to provide more specifics.
    What motor does not move? (m1-m4)
    Did you verify that stepper works on a different port?
    A $$ dump of your settings might help

    September 2, 2020 at 8:09 am in reply to: Tinyg causing Power Supply to shut down #11875
    cmcgrath5035
    Moderator

    Yes, it might be worth a careful hack, there are several folks you have wire-or-ed in a serial link, as in the Pi item.
    Be very mindful of levels and ground loops. The serial link on J14 is a direct connection to the microcontroller. The microcontroller is not tolerant to 5V logic.

    If the FTDI device has failed, it is somewhat difficult to predict if it’s serial out leads remain high impedance

    August 31, 2020 at 8:58 am in reply to: Tinyg causing Power Supply to shut down #11872
    cmcgrath5035
    Moderator

    I assume your Arduino test is with a Mega? As said above, I believe that Mega has native USB interface and connects with a different driver than the FTDI.
    So the above tests could imply a missing FTDI driver, which is what you need to interface tinyG.

    But you indicated that the proper driver was loaded.

    If you have a voltmeter, you could check that

    This is the applicable schematic page
    https://github.com/synthetos/TinyG/blob/a364308c8800ee2fb2227bb83f5d8edce0aae304/hardware/v8schematics/v8d/tinyGv8d%20-%20schematic%20page1.pdf

    The FT230X device interfaces the USB, converts to serial.
    Look closely on your tinyG2 for solder drips or ?? around that device.

    August 30, 2020 at 8:37 am in reply to: Tinyg causing Power Supply to shut down #11869
    cmcgrath5035
    Moderator

    OK, I now know you are fluent in Mac and Windows and were using Chilipeppr.

    First – as far as I can tell, your tinyG1 is dead, because it fails the naked boot.

    Let’s focus on tinyG2. Is your inability to see the USB connection based on looking at the Chilipeppr GUI?

    Why do I ask?
    I assume you know that SPJS needs to be running for the CP GUI to see the tinyG.
    Back in early August, I can’t easily determine the date, SPJS stopped working because Google terminated underlying support for a webapi that SPJS used. SPJS had to be rebuilt by it’s author, John Lauer.
    If you have been using Chilipeppr to test your tinyG2, you need to determine if SPJS is actually running on your computers.
    Your activity seems to bridge the timeframe in which Google created this mess for SPJS. You need to look hard to see if SPJS is actually running. Google Search is your friend, I have no experience with this current fiasco, but amm seeing it playout on the Chilipeppr forums.

    As an alternative, you could try cnc.js.

    • This reply was modified 4 years, 2 months ago by cmcgrath5035.
    August 29, 2020 at 12:30 pm in reply to: Tinyg causing Power Supply to shut down #11867
    cmcgrath5035
    Moderator

    Earlier in this thread you reported

    Test 3:
    Connect Power Supply to new Tinyg, calling it T2.
    Outcome: The new Tinyg turn on and is working.

    I guess that did not include connecting to your control computer.

    The USB interface on the tinyG board is defined by an FTDI to serial converter chip.
    The FTDI should be considered to be hardware, it does not participate in the boot process and proper functionality of the FTDI device is not tested until you attempt a connection, as you are now.

    Think back to the situation that needed to be stopped with the Emergency stop. What laptop process were you running to send Gcode to the tinyG that needed to be stopped?

    August 29, 2020 at 9:50 am in reply to: Tinyg causing Power Supply to shut down #11865
    cmcgrath5035
    Moderator

    The boot up sequence 1 – 3 you describe is correct as you have described it for the default parameter set. You can modify step 3 behavior (turn off the LED) with a change to parameter $p1pof, if you are not using the PWM spindle interface it does not matter.

    It’s too late now, I would not have recommended soldering directly to the J17-J19 pins, there are numerous hobbyist prototype lead sets that will push on to these individual pins.
    Soldering directly to any interface introduces the potential of ESD damage to the devices.

    You seem to have done the right things for you windows machine, have you tried all the available USB Ports on your PC?

    Open the Windows device manager app, which will eneumerate the connected USB devices. Observe the list as you insert the tinyG cable, then refresh the list. If you see no changes in device manager, the new USB hardware being connected is not being detected, independent of driver. tinyG uses an FTDI device as the USB interface.
    That interface is similar to Arduino Uno, so if that is what you tested then it should work for tinyG.
    Watch the device manager as you connect the UNO to get familiar with the process.

    If you can’t get the device to show in Device Manager, something is very wrong.

    August 29, 2020 at 9:32 am in reply to: Reading Due Configuration #11864
    cmcgrath5035
    Moderator

    You are on the right path.
    G2core remains under heavy development and has not attracted third party GUI support yet from Chilipeppr, CNC.js etc, especially in the config management domain.
    Product developers utilizing G2core are addressing the same challenges you are to meet their specific needs

    August 27, 2020 at 12:09 pm in reply to: Reading Due Configuration #11860
    cmcgrath5035
    Moderator

    This is a G2core issue, and would probably be better placed in
    https://synthetos.comforums/g2core
    but I’ll leave it here for now.

    Are you familiar with the G2core Wiki, specifically these references?
    https://github.com/synthetos/g2/wiki/Configuring-Version-0.99
    https://github.com/synthetos/g2/wiki/g2core-Communications

    If you dig thru all of this, you will find methods to dump current parameters and load them individually or in bulk.
    By default, all this will be JSON centric.

    I know of no GUI method (such as Chilipeppr or cnc.js) to implement this, but may be out of date.
    You are likely aware that some parameters, for example Coordinate space settings, might be modified by Gcode.
    Deciding what parameters to check and reset might be a challenge

  • Author
    Posts
Viewing 15 posts - 106 through 120 (of 1,771 total)
1 2 3 … 7 8 9 … 117 118 119