cmcgrath5035

Chris
1. What schematic package do you use? I am looking for a quick learn open source package.
2. I did a bit more Googling, find several versions of this controller on Ebay, from Amazon, etc. Variations seem to be the size of Heat Sink that the PWB is mounted on.
3. I am >50% (not 100%) sure that the pwm input to this controller is an opto-isolator input diode. The controller seems to also support a POT for control, which makes me wonder if they do nothing more than convert the pwm input to a DC voltage then drive their own pwm output based on that voltage. So my guess is that all that **might** be needed here is R1 and Q1, with R2 replaced by the input diode on the controller. I’ll also guess that one could pick off 12V from the tinyG fan pin, but I don’t think I would try that without making some actual measurements.
The 7812 12V regulator is rated up to 1A.

Alhaddar
In the documentation you have, is there perhaps a URL from which we can pull a copy? Or can you perhaps scan the text and post to a dropbox ?

Did you actually build the level shifter I drew up for you a while back for the SSR? We are talking about a similar approach here, but supplying with 12V rather than 24V.

https://www.synthetos.com/topics/i-tried-to-run-spindle-using-solid-state-relay/#post-6694

Factory reset – I assume you mean a defa=1?
Second one this week…….

Rhino
Looking at your Gcode “Lots o Shapes.cnc”, nothing looks “illegal” in the startup lines.
I’ll just comment that code I run does not have the line ‘G90 G21 G49’; but those are legit commands.
As a general rule, when I run a job, I follow this workflow
I don’t have home or limit switches, by the way.
1. Move to my desired start (0,0,0) location either manually, by jogging or by G0 commands (or a combination)
2. Reset tinyG
3. Send the Gcode

What are you using to send Gcode? Coolterm, tgFX, etc….

I have noted a couple quirks, which may/may not apply to fw 438.02.
+Some jogging implementations leave tinyG in a funky state
+tgFX frequently has trouble running a second job without a tgFX restart
+ My jobs always(by template in Gcode generator) end with an M60, after which tinyG seems to be in JSON mode and needs to get switched back to text, which it does automatically when it sees a non-JSON command, but the first text mode command gets dropped. So, for example, to move back to zero manually, I have to enter G0, then G0 X0.
+Aggressive manual movement of you gantry can send non-trivial voltages back into tinyG (the steppers becomes generators). The resulting noise could be improperly flipping bits. A reset of tinyG should clear any impact.

Try the reset before running your jobs.

Also, consider having you Gcode generated with line numbers. Makes the file larger, but easier to discuss.

BTW, this is sort of a hijack(by me) of this thread, continue the start up topic,if desired, in a new thread.

• This reply was modified 10 years, 3 months ago by cmcgrath5035.

You are apparently running from windows.
Load up Coolterm as well and get aquainted.

Good luck on your journey

Chris
Yes, it has been apparent for a while that some units shipped a while ago with what I’ll call an ‘unclean’ loaded default.
Bogus parameters in $$ dump are an indicator, alas you are not seeing everything with $$, so sometimes we have to recommend defa=1 sort of blindly.

Have fun

Just curious, What power supply voltage you using with your tinyG and motors? 24V?

• This reply was modified 10 years, 3 months ago by cmcgrath5035.

Are you running your tinyG(and motors) from a 12V supply?
Why? Is that what Ox recommends?

Most folks run 24V, 4 to 6Amp capability, you can go higher V (tinyG rating 30V)if willing to deal with heat.
I’m thinking that NEMA23s are seriously starved for torque with 12V.
And use descent wire between your power supply and tinyG – 18ga suggested.

See

https://github.com/synthetos/TinyG/wiki/Connecting-TinyG

On tinyG, 12V pins are for fans, NOT input.

Gantry should move with some resistance manually. Resistance depends A LOT on belt tension, which from chmr’s description sounds like a lot.

From your description, movements up to F10000are OK
A G1 X300 F8000 moves to X300 at velocity 8000mm/min
A G0 X300 moves to X300 at velocity $xvm, You have $xvm at 16000

Try changing $xvm to 10000 and see if G0 X300 now works.

Your funky motor noises sound like not enough torque per step pulse.
Torque comes from current thru stepper winding. Twice as much current when pulses are 24V vs 12V.

• This reply was modified 10 years, 3 months ago by cmcgrath5035.

ictoamm
The value for $xtm above looks bogus. Did you set that? Compare your settings to the Ox thread posted to Alden above.

Bogus parameters can sometimes be cleared with a defa=1 . Note that you will then have to reset the configuration parameters specific to your machine.

What is particularly interesting is that the other Ox thread has the opposite issue – G0 Z20 move moving too slow .

You might also consider trying $4mi=4. Alden recommends Z microsteps = 4 in Shapeoko world, but Ox has a very fast (8mm/rev) lead screw, so that may not be good answer here.

The travel per revolution parameters for the Ox are quite different from Shapeoko space, where much of the tinyG testing takes place. There is the remote possibility that a calculation issue (bug) has been triggered.