alden

Yes, you have that right. Any group sent with a null value (“”) will return the members of that group. Here are some other examples:

{“2″:””} returns motor 2 settings
{“x”:””} returns X axis settings
{“sys”:””} returns system settings
{“g54″:””} returns offsets for G54 coordinate system
{“hom”:””} returns system homing state

See here for the JSON overview:
https://github.com/synthetos/TinyG/wiki/JSON-Operation

Here is a list of available groups that are now on the wiki here:
https://github.com/synthetos/TinyG/wiki/JSON-Details

{“1″:””} return motor 1 settings
{“2″:””}
{“3″:””}
{“4″:””}
{“x”:””} return X axis settings
{“y”:””}
{“z”:””}
{“a”:””}
{“b”:””}
{“c”:””}
{“sys”:””} return system settings
{“pos”:””} return work coordinate positions fox XYZABC axes. In mm or inches depending on G20/G21
{“mpo”:””} return absolute machine positions fox XYZABC axes. Always in mm, regardless of G20/G21
{“ofs”:””} return current offsets fox XYZABC axes. Sums coordinate system and G92 offsets. in mm.
{“hom”:””} return homing state fox XYZABC axes, and ‘e’ for the entire machine. 1=homed, 0=not.
{“p1″:””} return PWM channel 1 settings (currently there is only 1 PWM channel)
{“g54″:””} return offsets for work coordinate system #1 (G54)
{“g55″:””} #2
{“g56″:””} #3
{“g57″:””} #4
{“g58″:””} #5
{“g59″:””} #6
{“g92″:””} return G92 offsets currently in effect
{“g28″:””} return coordinate saved by G28 command
{“g30″:””} return coordinate saved by G30 command

Can you please post your settings for the motors and axes? I’d start by looking at the configuration.

Question: Are you trying to run a dual motor Y gantry? If so, then the best way to do this is to set up Y normally, then map motor 4 to the Y axis by setting $4ma=1 (the Y axis). You may also need to make sure the Y on motor 4 has polarity reversed. All other settings should be the same.

• This reply was modified 11 years, 4 months ago by alden.

Edward, Thanks for the note and the diagnosis. I actually drew that crude picture on the Shapeoko forum to advise people to disconnect the power and not the ground.

I will try to reproduce your issue with the good instructions you have provided.

–Alden

Edward,

Are you disconnecting the board using the Estop? I’m wondering if transients on the DC power line are killing the board. Also, if so, was the board running when it was stopped, or was it idle?

Let’s see if we can get to root cause on this. Do you have 2 boards? Is the behaviour the same on both? If it’s a transient problem perhaps it would be useful to experiment with a capacitor across the Estop.

BTW: Turning the motors will cause the green LEDs to flash due to the back-EMF from the motors – this is normal and should not be an issue.

–Alden

Glad you got it working, and I appreciate the thoughts. The version 8 board has the homing connections brought out on screw terminals. We do try to advance the board – I guess this is little comfort as you have a v7, but your suggestions are welcome.

I also did a re-write of the homing pages to make it easier to walk through. See:
https://github.com/synthetos/TinyG/wiki/Homing-and-Limits-Description-and-Operation
https://github.com/synthetos/TinyG/wiki/Homing-and-Limits-Setup-and-Troubleshooting

If your goal is to specify A rotation in degrees I would not use radius mode. Perhaps you have this worked out so it translates, but I have not worked through your math to see if this is correct. Presumably you have seen these topics, bit I list them here for reference:

https://github.com/synthetos/TinyG/wiki/TinyG-Configuration#1tr—travel-per-revolution
https://github.com/synthetos/TinyG/wiki/TinyG-Configuration#xam—axis-mode
https://github.com/synthetos/TinyG/wiki/TinyG-Configuration#ara—radius-value

To set up A for a 4.5 gearing I would do the following

$4tr=80 (as you have done)
$aam=1 (standard mode)
$ara — don’t care. It won’t be used.

I also notice that your A feed rate max exceeds your max velocity, which is not normally the case.

Master is the “official” stable build. But unfortunately it’s quite a bit behind the current state; something I hope to remedy this coming week as I am not (otherwise) working.

I’d call edge the beta build. I try to push only if I think it’s stable, but it has not been shaken down beyond what I can do myself. So edge is currently the place to go.

Dev is a sandbox environment for development. There’s not guarantee that it even compiles, let alone runs well. Often what’s in dev is test or experiment of some sort. Best to be avoided.

The profile header is the way to go if you want to hard-wire up a profile. The best way is to create your own profile, then add it to the list of profiles and the set of profiles in profile.h, then uncomment it and comment out the rest. A rather crude form of compile-time binding, but it works.