Question about Communication between INAV Configurator and FC

[lydianb79]

Hi,

In the last Months I had a lot of fun with migrating Targets from Betaflight no INAV and creating Custom Targets.
SInce I as well started to play around with custom Boards I came across the following question.

What exactly is happening after clicking on Connect in INAV Configurator when you end up with the message "No Configuration received"?

What is the role of the two in the Process (if at all)?

define TARGET_BOARD_IDENTIFIER "BLUB"

define USBD_PRODUCT_STRING "BLUB_FC"

Is there a way to troubleshoot something like this myself?

[sensei-hacker]

What exactly is happening after clicking on Connect in INAV Configurator when you end up with the message "No Configuration received"?

We can see the "no configuration recieved within ..." message is generated at line 373 of js/serial_backend.js
The condition is !CONFIGURATOR.connectionValid, if there's not valid connection.

What does a valid connection mean? We find connectionValid set at line 293 of that same file, js/serial_backend.js
The conctions for that are at 284 and 288. Configurator sends an MSP message asking for the build info, and one for the board info (which version of INAV is running on what type of FC, on that particular serial port).

So it will fail if there isn't an INAV board on that port.
Or if there is any kind of communication error, such as using a USB charging cable rather than a data cable.

For Configurator development and debugging, git clone the source then run Configurator in debug mode. On Linux that can be done with:

NODE_ENV=development npm start

Other operating systems have similar but different syntax to set a variable in the environment of a particular process.

[lydianb79]

Awesome! Thanks a lot for pointing me in the correct direction! That should get me definitely closer.

[lydianb79]

Solved, it was not obvious....
It was caused by the definition of the OSD Chipset in the Target which did not exist on the Board.