SXmini M Class (TEMP CONTROL)

[dems86]

Every time I try to load the file it says unsupported file


Sent from my iPhone 6+ using Tapatalk

You unzipped it right?

THE WGU CLUB
Card Carrying Member/Co-Founder

 

[DonnyX]

Yes I'm loading the SX I file


Sent from my iPad using Tapatalk

 

[Vlad1]

Eh, no. If you read through the forums back about 6 or 7 pages, I am the one who even discovered the Eco bug problem, I just didnt know it was a bug with Eco mode (others however did figure it out).

The big software complaints were the gravity sensor and battery life, the battery life could have been addressed with a simple screen off timeout setting (which is likely the main reason for the increase in battery life when using Eco mode in the first place).

I am the one who listed the instructions for installing the software update and listed many of the changes and bugs that were introduced and if you read through the posts, I am the one mostly complaining about it.

This update should have been IMMEDIATELY pulled and fixed and repushed out when these problems were discovered, especially the battery in Eco mode, many not lurking around here on the forums likely probably think they have a bricked device now, I know I was ...... because I thought I had shorted the device somehow.

If my device becomes inconsistent, I buy a pack of smokes. When that happens, that mod maker has failed. I nearly did that yesterday, all because of a broken firmware update. Sure, now we know about Eco mode, but if you were the one who discovered it and couldnt figure out what caused it and were, as I was, unable to vape for an hour or so because you were getting a check battery everytime you put a new battery in, you might understand a bit more.

We need to start holding these companies responsible, this is the DEFINITION of fanboy'ism. The mod is great but the company did a bad thing and they need to be held responsible via criticism, just as dna should have been held responsible for having no reverse battery protection on their DNA20 boards. Regardless of the quality of the device, leaving a user potentially unable to use their device is unacceptable.

Can you PM me a list of Bugs you've identified? I'd like to build a bug list and verify each myself and possibly send up the ladder. I don't use all the features so I don't necessarily have a good test plan but if I had known bugs I could look into them. And being in a consolidated list would be much more convenient than scouring the thread.

 

[littlewierdo]

Every time I try to load the file it says unsupported file

Follow these instructions, to clarify, you need to reinstall the driver.

Just an fyi, you will need to reinstall the driver if you already have it installed.

Requires Windows and a PC.

Go here (SXmini maker,SXmini,yihisxmini,yihiecigar,sx350,yihi sx350, yihi sx350 mini, yihiecigar sx350 mini, gravity sensor,www.yihisxmini.com,120w device) and scroll all the way to the bottom of the page, in the 3 column from the left is a download section, start by downloading the driver (do not close the browser) and install like usual.

On this same page, right below the driver, there are two files, Upgrade firmware for m class 120 watts and another for 150 watts. They both work, have no idea what the difference is between them as far as functionality or performance (I installed both and functionality wise, they were identical).

The first bit is the name of the file, the second number is the size of the file after its been unzipped, the third is the date the file was modified. Which one you should use is as good a guess as mine, but they do both work and are functional, by the way, the Powerful and Powerfu+ is reversed with both of these files so the same bug even exists.

I am using the 120 watt file in case you want to know which one I decided to keep (again, I verified that they both work).

SXmini-M Class 1st upgrade software_SXmini_Logo-120W_20150525-1424_V2.1.SXI --> 115,313 --> 5/22/15

SXmini-M Class 1st upgrade software_SXmini_Logo-150W_20150525-1711_V2.1.SXI --> 115,353 --> 5/22/15

Whichever you decide to use, extract them somewhere you can locate (they must be extracted, the SXI software wont accept a rar file).

Now, open the software, it can be found in your start menu under All Programs-->Yihi SXI-->SXI (right click on SXI and run as administrator, click the ok box to confirm when it appears).

Now press your fire button on your SX Mini 5 times and continue pressing the fire button until you get to link off, press your up button to turn link on, then plug in to your pc.

When the program opens, click Connection, then click Install Driver, then click the Start Windows 7 or Windows 8 (32X or 64X) setting button.

In the new window, you should see your SX Mini listed in the dropdown, click the button right below that to install the driver (Install WCID Driver) and confirm any prompts that appear (I believe there is an unsigned certificate that will appear, click ok).

Once done, you can close the window with the dropdown box and you should see the previous window that was open, you'll now click the Connect button and in green, it should tell you the device is connected.

Now, at the top, click the return button and click the Upgrade button. Click the open file button and locate the firmware file you downloaded and extracted earlier and click open (or double click on the file).

Now, verify the message below the upgrade button, it should be completely green, if any part of it is red, you probably have the wrong file or the software isnt seeing your device. If everything is green, click the upgrade button and you should see a progress indicator, when it reaches 100%, youre done.

What I didnt mention is, you'll have to do a battery pull after the update to reboot the device, press and hold the fire button while inserting the battery and you can verify the software version.

Also, if you have trouble with your PC seeing the device, some have suggested pulling the battery, plugging in the USB cable, then scrolling to the Link On setting and performing the update with the battery not inserted. Makes no difference how you do it (some have said this is a bad idea because if it comes unplugged during the update, you could end up with a borked device, frankly, it makes no difference if there is a battery or not, if you unplug while its sending the data, youd end up with the same result, only a partial update of the software).

Most everything is straight forward, but Ill give you a quick heads up with the new software, do NOT do a battery pull with the device in Eco mode, switch to another mode (soft, standard, powerful, powerfu+) BEFORE you pull the battery or you'll get a check battery message (it will see your battery as dead every time, if you forget, just change the mode and pull and reinsert the battery, not a biggie, but you should know this going in).

 

[Mowgli]

With the release version:

Take a hit
push the up button once
lights out in 5 seconds

Annoying but do-able until a stable firmware upgrade is released

 

[refuzeandrezizt]

With the release version:

Take a hit
push the up button once
lights out in 5 seconds

Annoying but do-able until a stable firmware upgrade is released

It's pretty funny that I am not the only person who has done this. Another mod I had did this as well, and that is what I would do so the screen didn't stay on for what seemed like forever (it was one minute as well). I did this for a little bit with the M, but nowadays I just don't worry about it that much. But, when I decide to upgrade this thing, that will be a pro in my book.

 

[Quantum Mech]

Eco mode, many not lurking around here on the forums likely probably think they have a bricked device now, I know I was ...... because I thought I had shorted the device somehow.
.

This ! Exactly where I was
Driving along thinking I have at least 10hrs to go with no vape thinking do I try and buy something
Is my mod toast, will this be my fault or will my vendor sort it

Lucky for me I am lurking here and now know what the crack is

Thanks to all that sust it out

 

[littlewierdo]

With the release version:

Take a hit
push the up button once
lights out in 5 seconds

Annoying but do-able until a stable firmware upgrade is released

This works BUT it changes to your M1 setting so as long as your M1 setting is what you're currently using, its fine.

Frankly, I dont use the memory settings as they are useless to me since they dont store temperature so my M1 setting is still set to 5 watts, I use the M2 setting because its at 15 watts.

 

[2legsshrt]

Eh, no. If you read through the forums back about 6 or 7 pages, I am the one who even discovered the Eco bug problem, I just didnt know it was a bug with Eco mode (others however did figure it out).

The big software complaints were the gravity sensor and battery life, the battery life could have been addressed with a simple screen off timeout setting (which is likely the main reason for the increase in battery life when using Eco mode in the first place).

I am the one who listed the instructions for installing the software update and listed many of the changes and bugs that were introduced and if you read through the posts, I am the one mostly complaining about it.

This update should have been IMMEDIATELY pulled and fixed and repushed out when these problems were discovered, especially the battery in Eco mode, many not lurking around here on the forums likely probably think they have a bricked device now, I know I was ...... because I thought I had shorted the device somehow.

If my device becomes inconsistent, I buy a pack of smokes. When that happens, that mod maker has failed. I nearly did that yesterday, all because of a broken firmware update. Sure, now we know about Eco mode, but if you were the one who discovered it and couldnt figure out what caused it and were, as I was, unable to vape for an hour or so because you were getting a check battery everytime you put a new battery in, you might understand a bit more.

We need to start holding these companies responsible, this is the DEFINITION of fanboy'ism. The mod is great but the company did a bad thing and they need to be held responsible via criticism, just as DNA should have been held responsible for having no reverse battery protection on their DNA20 boards. Regardless of the quality of the device, leaving a user potentially unable to use their device is unacceptable.

Kinda hard to hold anyone in China resposible. I'm sure they will figure it out. I'm like you I thought it had bricked my M when I changed batteries. Don't buy a pack of smokes!! Always carry a Provari with you.

 

[Vlad1]

This works BUT it changes to your M1 setting so as long as your M1 setting is what you're currently using, its fine.

Frankly, I dont use the memory settings as they are useless to me since they dont store temperature so my M1 setting is still set to 5 watts, I use the M2 setting because its at 15 watts.

Are you sure? Mine just enters my current memory location.

 

[2legsshrt]

I'll tell you a bug I'm getting real tired of is on here. I have had to log it probably 10 times so far this morning. If I go to another thread check my mail anything but stay right here I have to log in again and Stay Logged In doesn't help

 

[Yozhik]

Seems to me there is a simple solution going forward on firmware upgrades for YiHi. They should release an update first as a beta, get input on how it works, then release a standard version once it's finalized. That way those of us who want to be on the cutting edge of new features or fixes can jump on the beta (while accepting there may need to be work-arounds for bugs), while those who want rock-solid stability can wait for the post-beta standard release.

By the way, I'd suspect they already run an in-house beta program. This would just be adding an external beta program so that everyone is happy with the way that firmware updates proceed.

 

[littlewierdo]

Are you sure? Mine just enters my current memory location.

Yup, just tested, let me try again...

Ok, this is weird cause now it stayed where it was. *shrug*. Ill see if I can figure out whats going on with this, a new 'feature' to figure out lol.

 

[2legsshrt]

Seems to me there is a simple solution going forward on firmware upgrades for YiHi. They should release an update first as a beta, get input on how it works, then release a standard version once it's finalized. That way those of us who want to be on the cutting edge of new features or fixes can jump on the beta (while accepting there may need to be work-arounds for bugs), while those who want rock-solid stability can wait for the post-beta standard release.

Sounds like a great idea to me.

 

[littlewierdo]

Seems to me there is a simple solution going forward on firmware upgrades for YiHi. They should release an update first as a beta, get input on how it works, then release a standard version once it's finalized. That way those of us who want to be on the cutting edge of new features or fixes can jump on the beta (while accepting there may need to be work-arounds for bugs), while those who want rock-solid stability can wait for the post-beta standard release.

Or, some simple QC testing. Standard operating procedure, go through all the features, do battery pulls, reboot the device, there arent that many possibilities using different combinations of settings to spend an hour or so testing every possible outcome.

I find it hard to believe that a normal company wouldnt use Eco mode for a day or so and have to do a battery pull and not see this problem unless they didnt test it for a day or two before releasing it.

This says to me they wrote the software and pushed it out without even playing with it for a day before releasing to the public.

You know how I know they designed the USB port for charging but now have changed their mind because the USB port is incorrectly mounted? Because the battery cover they put on the device is a PITA to remove and if THEY were having to remove the battery cover day after day, they would have done something different. You can tell how a company intends a device to be used by just how obnoxious different aspects of that device are and all of this is a simple matter of quality control.

I dont care if they are Chinese or not, if they want to play in the world economy and compete with other device manufacturers, we dont hold them to a lower standard than the rest of the world. Thats racism pure and simple.

 

[craigsdocks]

Yes I'm loading the SX I file


Sent from my iPad using Tapatalk

You have the sx mini m class device or do you just have the sx350j chip? ... you have to get the chip update from main page and the mini m class device update from the mini site, I had a hell of a time cause I was getting errors on comp screen, because they are different update numbers, look at my post [HASHTAG]#4428[/HASHTAG]

 

[DonnyX]

Thanks for all of your help guys, I successfully updated my SX Mini. [emoji106]


Sent from my iPhone 6+ using Tapatalk

 

[DonnyX]

You have the sx mini m class device or do you just have the sx350j chip? ... you have to get the chip update from main page and the mini m class device update from the mini site, I had a hell of a time cause I was getting errors on comp screen, because they are different update numbers, look at my post [HASHTAG]#4428[/HASHTAG]

I didn't do the connect and load the file before I loaded the firmware so I was getting that error message. Thanks


Sent from my iPhone 6+ using Tapatalk

 

[littlewierdo]

I didn't do the connect and load the file before I loaded the firmware so I was getting that error message. Thanks

Yay, glad it worked.

 

[Vlad1]

So I guess I'll open myself up for some spam here but I'm honestly not seeing what all the fuss is about here with this update. There is 1 known bug that I know of and it's being worked on. And there's a difference in the ordering of the preheat modes, not necessarily a bug but it is wonky and different than it was previously.

So if you will help me in identify the bugs with this release I'll try to consolidate them into a list. Please PM me with the Problem and in what circumstances you see the problem. Please don't PM me with things like, "it feels, it seems, it's different etc.." that I couldn't possibly verify. And don't PM me with either the Eco mode error or ordering of the preheat modes. I already know about them.

For example:
Eco Mode "Check Battery" error, Removing and replacing a battery when in Eco mode will produce this error.