Created attachment 58 [details] Logs files. 1. Configure Reader as following firmware version : 2.1.2 StartLanguage": 10,13,11, StartMarket: "1,0,1,0",1. 2. Launch RSU #154 on Mac, connect the Reader, follow step to start upgrade. 3. Disconnect Reader in the middle for RSU upgrading the Reader. 4. Change Reader languages set to ‘ending langset’ ($langset,10,13,11,6) 5. Close RSU, Open RSU. 6. Reconnect Reader to RSU actual result: RSU shows it is an incompatible Reader. Expected result: RSU continue to upgrade Reader to 2.4.8
Your test case is close but not quite right. The purpose of accepting the final language set (10,13,11,6 in this case) is to handle the case where we update the firmware (to 2.4.8) write part of the configuration including the new language set and then the update fails before we can complete writing all the configuration. We catch that case because even though the firmware has been updated the UOM is still 255 and the brandname contains our encoded info. We change the UOM back to it's original value only when we are completely done with the update. It is not going to be possible for you to interrupt the update between writing the new language set and update completing because it takes less than a second. The best way to simulate/reproduce it is to take a reader that has already been upgraded to 2.4.8 and set the brandname to the encoded value ($brandname,2.1.2*0) and the uom to invalid ($uom,255) and the language set to the new value ($langset,10,13,11,6). Then start the RSU and plug in the reader. It should recognize that configuration was not complete, send it down and set the UOM back to the original value (0 in this case) as well as the brand name to "FreeStyleLibre".
got it.