alden

The Seeeduino is not an Arduino R3 pinout, in spite of the fact that it looks like one. The power connector is different. See here:

https://github.com/synthetos/grblShield/wiki/gShield-v5-Notes#5-volt-power-right-position

It sounds like the boot loader is working but the main program is not starting. You should reflash with the current Edge (438.02). The wiki explains how.

If you are going to program with an outboard programmer at this point we recommend the Atmel-ICE. The basic kit ($55) is all you need. THis gives real-time debugging in Atmel Studio 6.2.

Lastly, you should not need a level converter to use the Due serial. But please confirm serial operation. Carl pointed out the Espruino thread earlier. Please refer to this if you have serial signal level issues.

• This reply was modified 10 years, 1 month ago by alden.

I’m not sure, as Riley and Rob did all this work, but I think we did an on-the-fly re-write. All we needed was for the widget to calculate the F word (did I say that?) to set the velocity for the G1 move

Can you look at the file in a text editor and verify that is an intel hex file? Sometimes people download an HTML file by mistake. Are you pulling from here:

http://synthetos.github.io/

chmr is correct, you should be developing on the edge branch at this point. But that won’t solve your issue. A number of points:

– {“G28.2″:”X0 Y0″} is – indeed – an unrecognized command. Here is the correct way to send a Gcode command in JSON:
https://github.com/synthetos/TinyG/wiki/JSON-Details#gcode-in-json-mode

The command should be {“gc”:”g28.2 x0 y0″} — or some variant. Spaces and cases don’t matter.

– You can also run the JSON in relaxed mode, in which case the command would be {gc:”g28.2 x0 y0″}.
See:
https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97#js—set-json-syntax

– Many UI’s do not wrap the Gcode blocks, but just send them directly. This is OK, too. So this works as well:
g28.2 x0 y0

That is correct. Wire the limit switches between the ground and the switch inout – e.g. Xmin, Xmax, Ymin…

Note if the switch is Normally Open (NO) or Normally Closed (NC) and set the $st setting for the proper switch type. All switches must be the same type. We recommend NC switches as they provide better noise immunity from false triggers.

You will want to pay attention to switch wiring, as the wiring can pick up noise and fire if not done well. The RC circuits described above help a lot, but motor or spindle noise can creep in. The best strategy is to use twisted pair shielded cable. I have found guitar pickup cable to work well as it is all that plus it’s very small and flexible.

These pages provide some useful information:

https://github.com/synthetos/TinyG/wiki/Homing-and-Limits-Description-and-Operation

https://github.com/synthetos/TinyG/wiki/Homing-and-Limits-Setup-and-Troubleshooting

Mike – please contact us offline for a replacement.

What kind of machine are you building and what is the requirement for coordination between the axes?

The reason I ask is that it is possible to network 2 tinyg’s for 5+ axis control, but the communications lag makes fine control of 5 axes not possible. If you are not really doing a full 5 axis machine – instead doing 3 or 4 axes and indexing – then slaving a tinyg should work fine. If you are looking for full coordinated motion, however, it does not work well enough. We have tried this and know from experience.

It’s not possible to just slave another driver, as the board really only outputs 4 motor channels. So this is OK for doubling up a channel for a dual gantry situation, but not an option if you need truly independent 5th axis.