Riley

What happens when you issue a move? G0x10y10z2 ? You should see lights flashing (green) and your motors should move. If they are not moving (perhaps making noises) I would suggest that you have your motor wire pairs wired incorrectly.

This is the settings we use to build the firmware for Zentool configs.

https://github.com/synthetos/TinyG/blob/master/firmware/tinyg/settings/settings_zen7x12.h

Its not exactly what you would set at the command line but just read the file over and it should make sense.

Let me know if this helps or you have other issues.

Riley

Update… Yes we are looking into this! I think the worst come to worst case for TinyG v8’s is we might need to pull a resistor off the board for that line. Please hold up from doing anything yet (meaning messing with the board 🙂 we are working on getting a solution tested and up on the wiki. Those relays should work just fine with the voltage that the xmega can supply so there is hope.

Riley

Sorry to hear about your setup!

I am not entirely sure this is not a gcode issue. If they are BOTH doing this (coolterm and tgfx). I am going to see if I cant take a stab at running this on the mill tonight. Also, I do not know how the “work piece” could be “pure carnage” and the simulation or preview look fine. What is the “tail coming off the left”.

Riley

@InPhase,

UPFRONT WHAT TO DO:
I need you to load 380.06 and use this tgFX.
https://www.dropbox.com/sh/huiupgemipv8f4q/X2l_1EH-gx

The question I really need to understand is what are you trying to do?
I think you are trying to run the Ford file with tgFX and master and that fails?

You say it fails at the very same spot every time? Can you mark the line number its on (bottom label of tgFX “Block Number”)
I did that very thing as the images above demonstrate.

Here is another shot..

Here is it finished.. Note my travel max was off a bit.

So in my screen shots where was the issue? I am running 380.06 with tgFX build 2077. Can you try to do the very same test I did? Run the file with the motors inhibited or disconnected and see if your tgFX preview drawing looks like mine.

From what I have ran there is nothing wrong at all with the firmware or tgFX. Are you using tgFX build 2077? Also, have you tried sending the file with coolterm? Do you get the same results?

Also, YOU SHOULD NEVER NEVER NEVER us dev branch. This is dangerous! A lot of the time Alden has stuff that just starts motors moving on reset. Stuff like that on live machines = loss of fingers etc.

Riley

InPhase,

I am not sure which way is up in this post to be honest. Why are you changing code? Because 380.06 is not working with tgFX?

I ran that gcode you sent alden (I had to remove % at the top and bottom of the file as this char is reserved for TinyG stuff).

Its still running now. But things look good. Also as far at the “mach3” adapter we stated that this was “dicey” and we would avoid that. Was this done? I really am not sure what you are troubleshooting or what you want to accomplish also I am not sure what the state of your TinyG is at the moment :).

riley

@cmcgrath,

I think I am doing the dual builds because of the RXTX native serial libs that I have to include.

@All,
Building new bins now for all platforms. After this push I am getting jogging working asap. Other feature requests…. Please open “issues” on the tgFX github page. Label them as feature requests.

Riley

It is loaded with gbrl. Without it you do not have grbl.. then you do not have any code to drive the grblshield. You can always get an regular arduino and hook it up via usb to the rpi. This works fine too. The way Wyolum did it they used the broken out USART rx and tx pins (bypassing the USB). Saves you a usb port.

Riley