XYYZA Configuration on F16 Board

[AndyCXL]

Whilst I wait for my F16 PCB and programming dongle to arrive, I have been looking at the GRBL32 source code to be ready to setup and configure my CNC.

• I have Built the code successfully using STM32CubeIDE (with two minor errors corrected, which I hope I have successfully remedied, relating to the '... before (' error on TIM1)
• I have copied the basic DEFAULTS_SHAPEOKO_3 in defaults.h to a new section, DEFAULTS_SHAPEOKO_34TH and started looking at what is required for my machine (ShapeOKO 3 XL with dual Y-Axis motors and added Rotational A axis, so 5 axes in total X+Y-YZA)

  How do I configure dual (contra-rotating) Y axis? I can't see that in the settings in any of the examples How do I configure a rotational A axis as opposed to a linear axis

• I can see quite a lot of references to #ifdef STM32 but nowhere can I see any #define for this - am I missing something?

I have tried to sign in for an account on your shop website to get the user manuals, but no first sign-in email has arrived. In fact no email confirming the F16 purchase has arrived either.

Hope you can help as I am super keen to get started on my 4th axis journey with Vectric VCarve, UGS, F16 PCB (with 5x TMC2209 or DM542 drivers), and GRBL32.

[AndyCXL]

Can I presume that resolving the axis question is in g32core.h? Y axis has to be defined twice... the following excerpt from g32core.h seems to be in the right ball-park, but I can't see how Y_AXIS can be defined to be 1 and say 3 so the dual axis happens when Y is the command subject...?

define X_AXIS 0 // Axis indexing value.

define Y_AXIS 1

define Z_AXIS 2

ifdef STM32

if ( defined(STM32F1_4) || defined(STM32F4_4) )

#define A_AXIS 3

endif

if ( defined(STM32F1_5) || defined(STM32F4_5) )

#define A_AXIS 3
#define B_AXIS 4

endif

if ( defined(STM32F1_6) || defined(STM32F4_6) )

#define A_AXIS 3
#define B_AXIS 4
#define C_AXIS 5

endif

endif

[AndyCXL]

I can see quite a lot of references to #ifdef STM32 but nowhere can I see any #define for this - am I missing something?

I have found this, I suppose it was obvious given the single source-tree ambition that the per-board differences would be in the build properties, rather than defined in the code per-se.