Having trouble with first g2core baby steps

> Did you run a “make clean” before your second compile?

Definitely. :)

I used these two git commands to refresh the git repo state back to pristine before the second compile:

$ git clean -dffx
$ git reset --hard HEAD

Thanks for the pointer about the heartbeat led, and suggestion for using master instead of edge. I'll try master tomorrow when I'm back on this, and keep an eye out for the heartbeat led just for awareness.

With the G2 code building with motors disabled... that sounds like it might have been the problem. I'll go looking for the correct CLI commands tomorrow too then. :)

Took a day longer to get back to this, but on it now. Noticing what seems like a few initial mistakes in the wiki page data, but figured I'd ask here just in case it's me misunderstanding. ;)

With the "Configuring System Groups" page here:

https://github.com/synthetos/g2/wiki/Configuring-0.99-System-Groups

Under "{hp:n} Hardware Platform", it has the return values listed as:

{hv:1}  TinyG Xmega series
{hv:2}  Arduino Due G2 (ARM)
{hv:3}  TinyG v9 G2 (ARM)

Should those be hp instead of hv? When manually typing in {hp:n}, the return values I receive start with hp.

On the Power Management page, under "Global Power Management" there is a table with "Setting", "Description", "Notes":

https://github.com/synthetos/g2/wiki/Power-Management#global-power-management-settings

The Notes for both the enable and disable setting list the exact same command to run: {md:0}. That seems wrong. Shouldn't enable be {me:0}?

Hmmm, the {hp:n} return value I'm getting seems incorrect. For master branch, compiled with make PLATFORM=DUE BOARD=gShield, I'm getting this return value:

{"r":{"hp":3},"f":[1,0,8]}

From the Configuring System Groups page, the "3" return value seems to indicate it's a TinyG v9 G2, when it should be "2", indicating "Arduino Due G2".

At a guess, the PLATFORM=DUE line taken from the PDF doc needs updating:

https://github.com/cmcgrath5035/G2core-DUE-External-Interfaces/blob/master/G2core%20DUE%20External%20Interfaces.pdf

Will experiment a bit shortly...

Ugh. Still can't get this to work. :(

If I build and flash g2core (master branch) using CONFIG=TestV9, then when I issue simple G-Commands they immediately run. eg X/Y/Z position changes (talking logically here, without any stepper drivers/motors hooked up).

For example:

{clear:n}
{"r":{"clear":null},"f":[1,0,11]}                                                                                              
{"sr":{"line":0,"posx":0,"posy":0,"posz":0,"feed":0,"vel":0,"momo":4,"stat":1}}
{ej:0}
?stat
Line number:         0                                                                                                         
X position:          0.000 mm                                                                                                  
Y position:          0.000 mm                                                                                                  
Z position:          0.000 mm                                                                                                  
Feed rate:           0.000 mm/min
Velocity:            0.000 mm/min
Motion mode:         G80 - cancel motion mode (none active)
Machine state:       Ready
g2core[mm] ok>
G0 X10 Y10 Z10 F20
$pwr
[pwr1] Motor 1 power level:       0.000
[pwr2] Motor 2 power level:       0.000
[pwr3] Motor 3 power level:       0.000
[pwr4] Motor 4 power level:       0.000
g2core[mm] ok> 
$1pm
[1pm] m1 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
$posx
X position:         10.000 mm
$mpox
X machine posn:     10.000 mm

This part seems to work. :)

When building and flashing g2core using PLATFORM=DUE BOARD=gShield (as per the PDF), as I'm using a Due board and can hook up the stepper drivers to the pins mentioned in the PDF... simple G-Code commands don't run. Even with motors (logically) definitely enabled before giving the G-Code commands.

{clear:n}
{"r":{"clear":null},"f":[1,0,11]}
{"sr":{"line":0,"posx":0,"posy":0,"posz":0,"posa":0,"feed":0,"vel":0,"unit":1,"coor":1,"dist":0,"admo":1,"frmo":1,"momo":4,"stat":1}}
{ej:0}
?stat
Line number:         0
X position:          0.000 mm
Y position:          0.000 mm
Z position:          0.000 mm
A position:          0.000 deg
Feed rate:           0.000 mm/min
Velocity:            0.000 mm/min
Units:               G21 - millimeter mode
Coordinate system:   G54 - coordinate system 1
Distance mode:       G90 - absolute distance mode
Arc Distance mode:   G91.1 - incremental distance mode (default mode)
Feed rate mode:      G94 - units-per-minute mode (i.e. feedrate mode)
Motion mode:         G80 - cancel motion mode (none active)
Machine state:       Ready
g2core[mm] ok> 
$1pm
[1pm] m1 power management         0 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$1pm=2
[1pm] m1 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$2pm=2
[2pm] m2 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$3pm=2
[3pm] m3 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$4pm=2
[4pm] m4 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$1pm
[1pm] m1 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$2pm
[2pm] m2 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$3pm
[3pm] m3 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
$4pm
[4pm] m4 power management         2 [0=disabled,1=always on,2=in cycle,3=when moving]
g2core[mm] ok> 
G0 X10 Y10 Z10 F20
g2core[mm] ok> 
Feed rate:          20.000 mm/min
Motion mode:         G0  - linear traverse
Machine state:       Stop
$posx
X position:          0.000 mm
g2core[mm] ok> 
$mpox
X machine posn:      0.000 mm
g2core[mm] ok>

In this second case, the commands are accepted but nothing "runs". I've been reading through all kinds of docs, looking through tonnes of the source... but literally nothing seems to address this. It just seems like there's something missing to make it "Ok, start now...".

Any hints?

Note, it's not a feed hold / resume thing. Tried that already. ;)

Aha, seems like the axis for the gShield/Due boards are disabled by default.

[xam] x axis mode                 0 [disabled]
[yam] y axis mode                 0 [disabled]
[zam] z axis mode                 0 [disabled]
[aam] a axis mode                 0 [disabled]

Next step, lets see if the steps are being send to the correct pins. :)

Excellent, motors can be turned. k, this is enough to start with.