Anonymous | Login | Signup for a new account | 2021-01-26 14:48 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000931 | EMStudio | Serial Communications | public | 2014-06-21 03:39 | 2014-06-21 03:41 | ||||||
Reporter | Fred | ||||||||||
Assigned To | Fred | ||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | All | OS | All | OS Version | All | ||||||
Product Version | 0.0.1-SNAPSHOT | ||||||||||
Target Version | 0.0.1 | Fixed in Version | |||||||||
Summary | 0000931: Packets that are responded to with a nack/unknown packet ID should not be considered not responded to. | ||||||||||
Description | During interrogation of older firmwares without the new packet types, it appears that things have gone horribly wrong. This is in fact not true, rather you were sent nack/unknown packet ID and treated it wrongly. When you receive these you should warn the user (once at the end of interrogation) that they have old firmware (or new with deprecated stuff removed, but certainly different) and proceed as normal. At the moment you treat it as if no response was received. This is a very different case. | ||||||||||
Tags | No tags attached. | ||||||||||
Issue Type | Bug | ||||||||||
Attached Files | |||||||||||
Copyright © 2000 - 2011 MantisBT Group |