I am not sure if these issues are seen across other products, but the PowerPro AW battery firmware file management needs a lot of work.
Here are some of the issues that I have seen.
1. There is a separate process for RS-232 and RS-485, but it appears that both are needed. Why?
2. The EXE file for the 232 update displays "PIC BMS 485 Firmware Updater".
3. None of the ZIP files that you download, display the actual firmware version(s) contained in the file.
4. The latest ZIP file only contains an update for the heater logic. Again, no version info is included.
5. This latest ZIP file on the website has replaced all previous files on the website that had updates for the BMS and RSD. How are those now accessed?
6. What are the latest/greatest versions that customers should be updating to for each module in the battery?
7. In the previous ZIP files there are hex files for 100Amp, 140Amp, 200Amp current charging. Why are those needed?
8. The HEX files should not be named the fixed component. ex: "PowerPro Heater logic change.hex". They should simply have the Product and version number. Details about what is fixed/updated is contained in the changelog.
9. Are these HEX and BIN files cumulative? This is why versioning is so important.
I realize that the PowerPro is a new product, but file management is a pretty basic process, at the same time is CRITCAL in keeping the customers up-to-date and preventing issues.
Here are some of the issues that I have seen.
1. There is a separate process for RS-232 and RS-485, but it appears that both are needed. Why?
2. The EXE file for the 232 update displays "PIC BMS 485 Firmware Updater".
3. None of the ZIP files that you download, display the actual firmware version(s) contained in the file.
4. The latest ZIP file only contains an update for the heater logic. Again, no version info is included.
5. This latest ZIP file on the website has replaced all previous files on the website that had updates for the BMS and RSD. How are those now accessed?
6. What are the latest/greatest versions that customers should be updating to for each module in the battery?
7. In the previous ZIP files there are hex files for 100Amp, 140Amp, 200Amp current charging. Why are those needed?
8. The HEX files should not be named the fixed component. ex: "PowerPro Heater logic change.hex". They should simply have the Product and version number. Details about what is fixed/updated is contained in the changelog.
9. Are these HEX and BIN files cumulative? This is why versioning is so important.
I realize that the PowerPro is a new product, but file management is a pretty basic process, at the same time is CRITCAL in keeping the customers up-to-date and preventing issues.
Last edited: