File Set Reader vs IQ BT Interaction Mapper
Quote from jakov on 03/05/2024, 10:29Hi, I'm using the IQ BT Mapper and currently I've connected it to the File Set Reader block and it's not showing any information. If I use it with the File Reader block, everything is fine. Sometimes it could be the missing Time Offset option in File Set Reader.
Hi, I'm using the IQ BT Mapper and currently I've connected it to the File Set Reader block and it's not showing any information. If I use it with the File Reader block, everything is fine. Sometimes it could be the missing Time Offset option in File Set Reader.
Quote from jakov on 03/05/2024, 14:44I play the same data through File Reader and File Set Reader and see different results. I am attaching a simple mission, the data is too large to send. Can you please verify this with your data. Thanks.
I play the same data through File Reader and File Set Reader and see different results. I am attaching a simple mission, the data is too large to send. Can you please verify this with your data. Thanks.
Uploaded files:Quote from mm_dev on 03/05/2024, 16:58Without sample data that demonstrates this issue we can't really validate it. As far as I can tell the File Set Reader is working as expected, but I don't have any records here for checking the Interaction Mapper block (and there is no WiFi or BT equipment here for generating one on the fly).
In the mission, the File Reader is using the file with index 1 while the File Set Reader is using index 0. Without the corresponding records we can't check if that is already a problem or not.
Also that mission uses the IQ WiFi Interaction Mapper, not the IQ BT Interaction Mapper.
Without sample data that demonstrates this issue we can't really validate it. As far as I can tell the File Set Reader is working as expected, but I don't have any records here for checking the Interaction Mapper block (and there is no WiFi or BT equipment here for generating one on the fly).
In the mission, the File Reader is using the file with index 1 while the File Set Reader is using index 0. Without the corresponding records we can't check if that is already a problem or not.
Also that mission uses the IQ WiFi Interaction Mapper, not the IQ BT Interaction Mapper.