Hi ,
today I tried to update my SkyStar (v1) via a PC of a friend (cause usually I am a MAC user running on High Sierra which isn't supported (don't know why) – without success ☹ Is there any trick?
What I did: run the installer, launched the App on the PC, Aspire SkyStar was switched on and waited. Then there was a Microsoft sound and few seconds later the USB sign on the display of the Aspire. It also immidiately started charging. But there was no launch oft he device itselft which showed me the actual Firmware version, Device name and Hardware version in the Application. And I also couldn’t choose the update file from the Application.
What am I do wrong? Cannot be that difficult.
Regards,
Frank
Thank you for the information. our service checked with our engineer, some parts of the bin file have missed, our engineer is dealing with it.
If any updated information,we will share with you here at the first time.
Best Regards
It's the V02 update file. It is supposed to be 2mb in size and it's 86kb
I can upgrade/reinstall firmware V01 by using the .exe here:
C:\Program Files\STWProduct_egt\Release\STWANDDKY_USBUpdate_exe\OutExe_stwDky
called: ECU_Upgrade.exe
The file for V02 is the issue, it's not complete.
Anyone from Aspire have the proper V02 file to share? and update the support section for the Skystar?
"Now we know why at the first several times , the application window can not show firmware,hardware name .
You need to install and run the application file firstly,then connect charging cable.
If you have connected charging cable with Skystar mod at the begining,then install application file,it will not show current firmware and hardware name.
But you can unplug charging cable and re-connect it with Skystar mod. Then the application file will detect mod normally.
For the file error message when you choose bin file,our engineer will check and improve the BIN file later."
So that's good to know for others/beginners (like me) ;-) Regarding to the .bin file I got the identical info like you:
"Currently ,I'm not sure the root cause,but I will pass your case to our R&D department. Sorry to bring you unpleasant experience and inconvenience."
So lets wait when their software development team solved the problem... =;
We just updated the file for the Skystar for windows, we checked that it works on our PC with windows operating system, please help check if it works on your pc with windows operating system.
Please wait in patience, our engineer is dealing with the file for MAC system
Thanks &Best Regards
Our engineer is dealing with the MAC file, if any information,we will share there at the first time ;)
C:\Program Files\STWProduct_egt\Release\STWANDDKY_USBUpdate_exe\OutExe_stwDky\ECU_Upgrade.exe
On YouTube a guy said something about first pull out the batteries, connect and then plug them in again
But if this would be the right way, why Aspire doesn't tell you - see here https://blog.aspirecig.com/how-to-update-the-firmware-of-aspire-mods/ I mean nothing more simple than that...
goto C:\Program Files\STWProduct_egt\Release\STWANDDKY_USBUpdate_exe\OutExe_stwDky
and open ECU_upgrade.exe
it will show you that it recognizes your Skystar.
What i was saying in my last post is that you won't be able to upgrade regardless because the v02 file on their site is incorrect.
I would be glad to minimum be able to select the incorrect v02 file. But even this is impossible. Or do you say that the installer doesn't show Firmware version, Device name and Hardware version just cause the fw update file is incorrect? I don't think so.
I am wondering why Aspire don't give any support feedback like "Hey, we know about this issue and will solve in x days/weeks". Not very userfriendly...
Only thing to do is wait for an answer from Aspire (if they ever reply)
well, I'll give it a last try today. I got feedback from the ASPIRE Support USA and they said:
Hello Frank,
What's your exact computer system version ? Please ensure you use original Aspire charging cable that comes with Skystar mod together.
I just use my windows 7 ultimate version computer to upgrade Skystar firmeware from V01 to V02 and complete the upgrade successfully without problem.
You can also change USB port of computer to try. Some USB port of computer only has charging battery function ,can no transfer data.
Hi Tiber,
I now have been at a reseller store here in Germany http://tantedampf.de Like you already explained also the tech specialist from „Tante Dampf“ said the files are corrupted and there is no firmware update possible! It’s on Aspire to solve this problem. So I wonder how their support could tell me to successfully manage the update while a professional guy like him who is doing things like this nearly every day isn’t.
All in all it’s time to officially tell Aspire HQ about this issue – as far as it isn’t already known.
Regards,
Frank
Aspire need to get a proper software developer to sort their update software and firmware out because this isn't the first Aspire product I've had this issue with.
@Tina
"Hello Frank,
The V02 firmware of Skystar for windows that uploaded at our official website is not broken.
If you download and installed firmware for other model mod in your PC before,please delect and unload it firstly,because you can not use it to upgrade for Skystar.
Ensure you download and install firmware from our website correctly.
Here is link:
https://www.aspirecig.com/upgrade/SkyStar/514.html
When you use charging cable to connect Skystar mod and PC,the screen of Skystar mod will diplay USB sign,that means the PC will transfer data to Skystar mod normally.
There are two files after you uncompress RAR file.
Install the file"aspire UpdateVV1.5_Setup(4)" firstly."
Then click “Aspire-Update” icon to open it ，click "OpenFile"button,choose file"SkyStar210_S_V02.bin ",click "Update" button，complete upgrade.
Reinstalling V01 works absolutely fine using the actual .exe file in the folder i listed above.
Their V02 is 100% broken, why the hell are they denying it?
Take a look at this screen shot (right click and open in new tab to see it full size)
https://i.imgur.com/wVQKs5j.jpg
There is a 1.9mb difference between the two .bin (firmware) files.
Ask them the file size of their V02 file, I would put money on it being 2mb in size and not the 86kb that downloads from their site.
service@aspirecig.com
Our service will check your problem with our engineer and give the suggestion from our engineer /:)
It was a totally new install of the "aspire UpdateVV1.5_Setup(4)" on a very new PC. After clicking on the “Aspire-Update” application to choose bin file, the upgrade stopped cause I could choose the update .bin file (OpenFile), BUT the „Update“ button won’t become active to run. See screenshot here https://d.pr/i/iZ13sI
Sorry, after so many tries, after so much feedback from others here Aspire definately has to check it!!! And also has to stop denying it don't you agree @Tina
@Tina you guys really need to download the file from the site and try yourselves before telling us to go to service with the issue. Ifranky already tried that and they told him it was a problem on his end when it's not. It's the update file, it's broken.
How many times do I need to type the same thing and repeat myself?
SORT THE UPDATE FILE OUT, IT IS BROKEN
our service will check with our engineer for the information you provided and find out the reason and solution.
Thank you again for the suggestion
Today, I got this response:
"Currently, I'm not sure the root cause, but I will report your case to our R&D department."
And so we wait?
I'm somehow a little bit frustrated about that. Errors can always happen but to not accept them when many users report them is not very customer friendly. Thought I bought "something better"...
I then post on here with clear instructions to replicate the issue and what the problem is.
Only to get a cookie cutter reply to get in touch with service. This is after someone posts in this thread saying they already have and got a cookie cutter reply about making sure you run the program first etc.
You guys are a massive, if not the biggest player in vape hardware and I get told to do the leg work (which previously stated leads to cookie cutter replies from service) for an issue you have 100% of the information about to fix.
It is as simple as someone internally taking their .bin file (that was stated in ifranky's post that service tested as working) and re-uploading it to the website.
I don't get how this is a week long thread.