I understand how to create a user application that can implement a custom location engine and that the output of this could be sent via UART or via access to other peripherals which are available to user code.
But can the user code override the location of the tag so that any calls via the BLE or other interfaces (e.g. using the manager app) will report the tag location in the same way as is possible with the built-in location engine? So the tag operates exactly as before but the location values are from the custom location engine?
I am thinking the built-in location engine must write its output to memory somewhere and this is used when the APIs are called to get the tag location. Can the user application write to the same memory and override the values.
If it were possible to alter the existing location engine code and compile that along with the user application then this would certainly meet our needs. I can see why an API based approach would be cleaner but I expect that would take longer to make available?
Do you have a rough timeline to make the LE code and build available?
Is the release date realistically going to be days, weeks or months do you think?
Would it enable me to add (or alter) the code so that instead of a tag sending positional data, it could send range data as well (or instead)? Possibly adding (or replacing the LEP command with), say, LER if required?