# Platform info before upgrading **URL:** \ **Category:** Open AT\ **Created:** [February 16, 2011, 10:51am UTC](https://forum.sierrawireless.com/t/platform-info-before-upgrading/4898 "2011-02-16T10:51:55Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![BenFT01](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@BenFT01](https://forum.sierrawireless.com/u/BenFT01)\ **Post date:** [February 16, 2011, 10:51am UTC](https://forum.sierrawireless.com/t/platform-info-before-upgrading/4898/1 "2011-02-16T10:51:55Z")
A while ago there was a little discussion of this. [https://forum.sierrawireless.com/t/determining-version-of-q2687-h-or-g/3937/7](https://forum.sierrawireless.com/t/determining-version-of-q2687-h-or-g/3937/7) I’m doing remote upgrades and I want to be sure I am uploading the correct application for the firmware and the hardware. Is there a command and a corresponding table provided to help a machine identify what the module is and what it is running? The string response to ATI seems to vary with the firmware e.g. my Supreme 20 returns “FSUP05 Product”, whereas previously it was something like “FSU005” my Xtend FXT001 does give “FXT001 Product” but I don’t have an FXT009 yet, can I guarantee it will return “FXT009”?? And is the string format varying with the firmware releases? The firmware version seems reliable, so I can cope with that. ---
**Author:** ![victorjd](https://avatars.discourse-cdn.com/v4/letter/v/9fc348/32.png) [@victorjd](https://forum.sierrawireless.com/u/victorjd)\ **Post date:** [February 16, 2011, 1:43pm UTC](https://forum.sierrawireless.com/t/platform-info-before-upgrading/4898/2 "2011-02-16T13:43:15Z")
> [@BenFT01](#): > > The firmware version seems reliable, so I can cope with that. Yes, we use ATI3 answer. Firmware string format varying between 6.xx and 7.xx fws, but not fatal - our config tool uses universal procedure for extracting from answer wanted info: module name, module “family”, fw version. ---
**Author:** ![BenFT01](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@BenFT01](https://forum.sierrawireless.com/u/BenFT01)\ **Post date:** [February 16, 2011, 2:17pm UTC](https://forum.sierrawireless.com/t/platform-info-before-upgrading/4898/3 "2011-02-16T14:17:44Z")
Thanks victorjd. The trouble is with relying on the firmware version, is it could have the wrong firmware in it. But if you are reasonably organised its a much better method than none at all. FSU10 ati3 R74\_00gg.FSUP05 2120060 041709 19:18 AT+WHWV Hardware Version 4.23 ATI : WAVECOM WIRELESS CPU MULTIBAND 900E 1800 FSU20 ati3 R7.44.0.201008311212.FSUP05 2146096 083110 12:12 at+whwv Hardware Version 4.22 ATI: Sierra Wireless FSUP05 Product FXT001 ati3 R7.44.0.201008311212.FXT001 2146096 083110 12:12 at+whwv Hardware Version 1.00 ATI: Sierra Wireless FXT001 Product I hope they have settled to a format now. 😒 ---
**Author:** ![BenFT01](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@BenFT01](https://forum.sierrawireless.com/u/BenFT01)\ **Post date:** [February 17, 2011, 3:12pm UTC](https://forum.sierrawireless.com/t/platform-info-before-upgrading/4898/4 "2011-02-17T15:12:16Z")
Well the answer from SW is that there is no non-firmware dependant method of determining the hardware. All of FSU/FXT units are Q2686/7 variants so all firmwares can run on these. There is also no table of expected responses to ATI3, ATI etc for the different firmware versions. I’m amazed that with millions of units in the field, the need for a consistant version format being available for programatic interogation has not been addressed. ❓ Or is it just me? ---
**Author:** ![BenFT01](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@BenFT01](https://forum.sierrawireless.com/u/BenFT01)\ **Post date:** [February 18, 2011, 9:53am UTC](https://forum.sierrawireless.com/t/platform-info-before-upgrading/4898/5 "2011-02-18T09:53:29Z")
Can others post their ATI3 reponses, and perhaps ATI, so we can all see what the variety of possible replies are? Might be a useful record for others tackling the same problem. FSU20 ati3 R7.43.0.201003261552.FSU005 2139952 032610 15:52 ati WAVECOM WIRELESS CPU MULTIBAND 900E 1800 See what they did here? R7.43 instead of R7.44 and the hardware code in the firmware changes from FSUP05 to FSU005 (well the other way around chronologically). Cunning.