In the previous versions, the app immediately switches from No response from Slave Device to displaying the data table correctly. Now it takes a while and, by the looks of things, it queues the remaining pools and quickly pushes them in TX (at a rate of about 100ms/packet)
In the previous versions, the app immediately switches from No response from Slave Device to displaying the data table correctly. Now it takes a while and, by the looks of things, it queues the remaining pools and quickly pushes them in TX (at a rate of about 100ms/packet)