Forum Replies Created
-
AuthorPosts
-
cmcgrath5035
ModeratorBest way to attach pictures and other large documents is to copy them to a cloud drive (Gdrive, etc.) and post a URL link here.
I am not sure a video would be helpful here.
Based on your Test results, I have to agree with you that it appear T(inyG)1 has failed.
Not at all clear what might have happened.Diagnosis on boards like this is difficult and repair(device replacement) more )so.
ModeratorI recognize you from previous threads as working on a set-up using external drivers, at least partially. Some comments/suggestions will assume you were successful in implementing them.
A first comment would be that your power supply working without load does not necessarily mean that the PS is OK. Most modern transformerless DC supplies have automatic shutdown circuits that disable the supply in over-current situations. It is possible that the output protection circuit was damaged by the emergency shutdown.
You need to load test your 24V supply with a known good load, such as a DC motor (not stepper)Another quick test would be to completely disconnect tinyG from your setup then try powering up the tinyG in total isolation. A naked tinyG requires only a few 10s of milliamps to boot up when there are no external connections. Find an old wall wart supply in the 10V to 24V range, verify polarity, and see if tinyG will boot in total isolation, including leaving the USB disconnected, just Input Power and Ground.
Connecting power should produce the boot-up LED flashing sequence followed by a brief (default 2 sec) all green LEDs on, then extinguish.
If tinyG fails this naked boot-up, then something on the board has failed.
Diagnosis of such a failure will be difficult, should you want to try here is a link to the Schematics
https://github.com/synthetos/TinyG/tree/master/hardware/v8schematics/v8hModeratorRE: Comment 2) My X-Y1-Y2-Z machine does not use External Drivers. I have Nema 23 (not 32, sorry) motors on M1, M2, and M3 connectors. The M4 motor is a NEMA 17 which is more than adequate for my spindle.
My NEMA 23s are https://www.omc-stepperonline.com/nema-23-stepper-motor/nema-23-bipolar-1-8deg-2-4nm-340oz-in-1-8a-4-95v-57x57x104mm-4-wires.html low currrent 23’s.RE Comment 3) tinyG can assign X, Y,Z, A,B or C motion to any of M1-4.
If you want a 4 axis machine, one of the motion axes will have to drive two motors. So what you really want I’ll call and X-(Y1 Y2) – Z – A. If Z and A both need to be NEMA32’s, you will need to use external drivers, which is what you are attempting.I am assuming that when you run Test 11, where D3 moves its motor and D4 does not move its motor, if you disconnect D3 and then D4 moves(operates). That indicates to me that the J19 port cannot source enough power to drive two inputs in parallel.
RE Comment 4) This possible issue with the logic interface to the external drives is both logic voltage (ports are 3.3V logic) and current drive (fan out capability). Implementing 3.3V to 12V level shifters should work, assuming the input voltage rating on your external drivers can handle 12V, which is true with most of the ones I have seen. Keep in mind that the inputs to the external drivers are typically a led emitter (~2V drop) and a series limiting resistor.
ModeratorGood luck with it.
Just to reinforce, make sure that the X1 Driver and the X2 Driver individually connected to J17(or J18 or J19) work OK before connecting them in parallel.ModeratorSorry for ignoring you of late, for some reason the automatic notification of a post I have set up has not been sending of late.
I see from other posts you have been digging in to some of the legacy traffic related to output pulse width.
I’ll also assume that You issue 2 has the objective of creating an (X1X2)YZ machine as a workaround for the motor4 port (J20) not working with your external drivers.
Connecting two external drivers to J17 “should work”.
Logically it will work if you can invert the logical operation of one of the external drivers, so one will be CW and the other CCW when commanded to move.Assuming that your 2HSS86H units have opto isolated inputs, which are typical in this application, I’ll suspect that the tinyG logic pins might not be able to source adequate current to properly operate the two opto-isolator ports in parallel. In logic terms, the Fanout (load capability) of the microcontroller output port that drive J17 might be inadequate current drive for the opto-isolator switches. On possible solution might be to bradboard a one input, two output buffer and level translator circuit to increase the Fanout of the J17 pins.
First, try your double load on all three of the outputs, J17,J18,J19.
One of those might have slightly higher drive capability. This is somewhat of a stretch, but easiest to implement. If J18 does work, for example, then build a Y(X1X2)Z machine.AFAIK, most others solved this issue by finding external drivers that work, by trial and error.
Do you have a really heavy spindle load? I drive Nema32s on my XY1Y2Z machine directly from the tinyG driver devices, with Z being a NEMA27.
All this ver depended on the mass of your machine, of course.ModeratorThe work area size is controlled by the Chilipeppr application.
Try a post at their new forum location https://forum.makerforums.info/c/ChiliPepprModeratorFirmware for tinyG is here
http://synthetos.github.io/ModeratorWhat CAM software do you use with your setup?
There is a tool change macro in Chilipeppr and I believe in cnc.js as well,
I have never tried them but perhaps they would give you some hints.
Google finds lots of hitsI assume you have studied this wiki page https://github.com/synthetos/TinyG/wiki/Coordinate-Systems
Not understanding exactly how your machine is running and aligning tool position with work piece, its not obvious how shifting coordinates would do what you want, but you believe it would.
I have to assume you are generating your own Gcode, since the detail of how coordinate systems would affect your design would seem to be custom.The wiki reference above describes how to change coordinate systems on the fly. The CAM systems have example of how to stop running Gcode to make a toolchange. Seems like a custom combination of the techniques could achieve what you need.
A lot of assumptions on my part. Any of them help so far?
Moderatorignore this, just ensuring followup notification
-
This reply was modified 4 years, 6 months ago by
cmcgrath5035.
ModeratorGreetings
A couple comments on your $$dump
1. Thanks, it usually speeds debug
2. Give this wiki item a read. https://github.com/synthetos/TinyG/wiki/Power-Management $_pm=2 is usually the preferred choice, unless you have a specific reason to pick $_pm=3
3. Are you sure that Motors 1 and 4 are 400deg/rev (0.9 Step angle)? That is how they are set up, it is just unusual to see.
4. Did you choose $4mi=8 intentionally? $4mi= 4 or 2 is more typical, particularly for heavy Zaxis loads (heavy spindles) $mi=8 and $sa=0.9 makes for a very high precision Z axis, not typically required.All those settings are legit, just unusual
tinyG boards are fairly tough, but trace damage is possible.
Some folks have had issues with bad 4 pin connectors on the motor outputs.
Pull your tinyG back out, use a Multimeter to check continuity of the motor 4 screw terminals and the solder blobs on the bottom. Also visually trace the paths back to the driver chip to see if they look to be compromised.FYI the tinyG V8 schematics are here for your reference https://github.com/synthetos/TinyG/tree/master/hardware/v8schematics
ModeratorHere is a link to an old discussion on the topic
https://synthetos.comtopics/is-dual-gantry-homing-supported/#post-10025Here is a discussion on G2core
https://github.com/synthetos/g2/issues/359ModeratorSorry, missed this post.
Axis setup for rotary (A,B,C) is different than linear.
Are you sending a valid move code for a rotational motor?What version of G2Core do you have?
What “Board” file did you compile with?
Using external motor drivers?Do you really want 2 rotational axis?
G2core can also do X,Y,Z,U,V,W, 6 linear interfaces.ModeratorI sort of stumbled on this rather old thread which may be of interest to you
https://synthetos.comtopics/how-to-configure-himing-switches-in-tinyg2/#post-8990A quick look sort of confirms to me that, at least 4.5 years ago, your
#define Z_HOMING_INPUT 1
above should be
#define Z_HOMING_INPUT 6
maybe?From the “er” message, it is input 6 that is acting like a limit
ModeratorHmmm, have not played much with G2 homing
See https://github.com/synthetos/g2/wiki/Digital-IO#digital-inputs-during-homing
What is the value in Parameter {zhi: ?
Behavior implies that the switch being hit is still acting as a limit, not homing
Moderator@kiwigrant, I am a little confused by your powering from USB comment, are you running a tinyG V8 or an arduino of sorts?
V8 schematics are here https://github.com/synthetos/TinyG/tree/master/hardware/v8schematics
Power is on sheet 2. USB is terminated by the FTDI device (FT230) and it may push out some 3.3V to the 3.3V bus, but is not intended to run that way.-
This reply was modified 4 years, 6 months ago by
-
This reply was modified 4 years, 6 months ago by
-
AuthorPosts
