scanConsole checks coms after it configures
What
scanConsole
(attempts to) configures all loaded front-ends in a loop and when that loop is completed it reports that All FEs configured
(see here).
It then goes on to check that the front-end can be communicated with here. If this checkCom()
call fails, the scanConsole
output reports the following:
[11:43:45:375][ info ][ scanConsole ]: #################
[11:43:45:375][ info ][ scanConsole ]: # Configure FEs #
[11:43:45:375][ info ][ scanConsole ]: #################
[11:43:45:375][ info ][ scanConsole ]: Configuring 0x4269
[11:43:45:413][ info ][ scanConsole ]: All FEs configured in 37 ms!
[11:43:45:414][ info ][ scanConsole ]: Checking com 0x4269
[11:43:45:424][ error ][ Rd53a ]: Did not receive any data for 0x4269
[11:43:45:424][critical][ scanConsole ]: Can't establish communication, aborting!
This is a bit misleading, since it states that the front-ends were configured but then goes on to say that there is no communication with them possible; that is, the front-ends were actually not configured (or, if they were, they were most likely configured improperly).
Solution/Fix/Suggestion
Prior to configuring as in the above, should scanConsole
first check that communication can be established between all front-ends?