@Exerqtor
Thank, I tried using your structure but ended up having to make some modifications.
It looks like you cannot access globals (within a macro) that are declared by calling another macro from within that macro. I.e. the behavior is not limited to config.g. At least that seems to be the case with 3.5.0-beta3.
I created a minimal config.g which calls init.g. At the start init.g calls setGlobals.g and later on tries to use a global (created in setGlobals.g). This failed wih the same message as before. This seems identical to your structure, so I'm not sure why I'm getting a different behavior
I then moved the call to setGlobals.g into 'config.g' (before the call to init.g). All is well.
I'm not sure if there is any downside to this approach ... most all the printer setup is now performed in init.g (and other macros that it calls). My config.g is simply, this:
;M929 P"anEventlog.txt" S3 ; start logging
;
;Minimal config.g
; Setup and enable Network first so that if errors, still have DWC available
M550 P"srsender" ; set printer name
;M551 P"mypassword"
;M552 S1 P"IoT2" ; enable wifi with ssid (standalone only)
;M552 S1 ; enable ethernet (standalone only)
M586 C"*" ; enable CORS
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
;
; Setup Global Variables
M98 P"setGlobals.g"
; Initialize
M98 P"init.g"