Multicontroller 7096, why so unstable soft...

[fewponds]

I just received few 6095 pumps and the controller 7096. "Wow" this is what I thought unpacking the stuff... All was setup immediately, instructions read... lets connect controller to PC... what was my disappointment when it appeared controller (its software) was broken down during just its firs update!
I think it is really unfair to deliver so unstable, untested software product, and claiming for it more then 100$, while in my opinion, the device is worth really no more then 30$. This is, as I see common problem - the stability of the software update, not mentioning about problems with COM ports. Only from 1 to 3 can be used? Come on Tunze, on my PC up to 7 COM ports are occupied, should I be IT specialist to make 7096 visible for your controller software... I feel just being fooled.... Just my 5c.

 

[Craig Borowski]

I apologize for the difficulties you're having. The 7096 has been tested extensively and is very stable and trouble free for the vast majority of users. Nevertheless, due to the complexities of the Windows OS and the wide range of hardware in use around the world, the software will on occasion require a little troubleshooting to function correctly.

Changing the COM port is not difficult. I don't see which version of Windows you're using, so for the steps below I'll assume you're on Windows 7. If not, please let me know and I will provide different instructions on Monday.

First we need to try running the program in Compatibility Mode. Right click on the program and select Properties. From there select the Compatibility tab and choose to run the program under the XP SP2 mode. If that doesn't fix it then please proceed below to change COM settings.

Open up the Control Panel and from there select the System and Security category. Towards the bottom of the list that appears you should see Device Manager. Click on Device Manager and a new window will open up. Look down the list for the Ports (COM&LPT) option and click the + sign to expand the list. If there is a Generic Device listed, right click on that and select Properties. (If there is not a Generic Device listed, then expand the Universal Serial Bus further down the list and see if you can find it there. If you do, right click and select Properties.)

Now choose the Port Settings tab and from there click Advanced. At the top of the new window you will be able to select a new Com Port Number. Assign it either 1, 2 or 3. Then click OK to exit that window. (Windows 7 should automatically register the change, but you may need to hit Refresh Devices or Scan for New Hardware from the Action menu above.)

Then try running the program again. If it still does not find the device, try restarting the computer and trying again.

 

[fewponds]

Hi

I am still using Win XP on my laptop, and unfortunately it looks like there was connection loss during software update, which bricked out the controller firmware, here is the log from AVRootloader, I received just after first attempt of connection:
11.01.13-14:26:07-562 > connects
11.01.13-14:26:07-656 > Connecting on port COM5...
11.01.13-14:26:08-218 > Device connected
11.01.13-14:26:08-218 > Process commandline...
11.01.13-14:26:08-218 > connects
11.01.13-14:26:08-218 > Program...
11.01.13-14:26:08-218 > execute compiled data
11.01.13-14:26:08-218 > 1.1.0.6
11.01.13-14:26:08-218 > selected options in compiled file:
11.01.13-14:26:08-218 > - programming FLASH
11.01.13-14:26:08-218 > - FLASH data are encrypted
11.01.13-14:26:08-218 > - erase FLASH during programming
11.01.13-14:26:09-703 > Cmd.SetBuffer.WriteData() ICOM: write error.
11.01.13-14:26:10-859 > Device disconnected

After that all hanged for a looooong time....

Few hours later I had run this avrootloader again, trying to revert firmaware but it returned: "Error: Installed software version is higher as the update", which almost make me sure, according also to this forum contents, that the controller crashed and I have to send it back to retailer...

 

[fewponds]

. (duplicate post...)

 

[rvitko]

Unfortunately, yes it has to be returned to the dealer to exchange. From what I am told by the factory this will only happen if something disrupts the power or USB during the update.

 

[Craig Borowski]

Losing connection during an update does usually result in corrupted firmare. If you are unable to successfully complete the update, then you will need to return the unit to the retailer for replacement.

 

[fewponds]

Thank you for your interest, and yes, I have just arranged the return. But question is what should I do to prevent the next one from the damage (I am using laptop so power loss is almost unlikely)?
Maybe I should remove AVRootloader components from the disk, to disable the initial firmware update, and test the connection with the main program Tunze7096.exe ?

Anyway I can hardly imagine such sensitivity of professional(?) software on unexpected events (even with my 10 years experience in IT industry...)

 

[fewponds]

...

 

[rvitko]

I can sympathize from your stand point, but keep in mind, mass consumer electronics sell in millions or hundreds of thousands and have full teams of engineers, we have one programmer, one electrical engineer and we sell at most a thousand a year of this controller. This raises the price and means it is not perfect to the level of a product from Apple or Microsoft. The only fix will be exchanging it unfortunately, it needs to be rebooted with new firmware. It is corrupted and thinks that it has a higher firmware than the version you are trying to add and won't accept it.

 

[fewponds]

Being less skeptical at the end, users are very happy with its features (as I know), and I would like to "taste" this also , but what should I do to not experience previous problems?

 

[rvitko]

With the replacement, only be careful that the computer doesn't sleep, or the usb or power disconnects and it should be fine. I can remember 3 years ago I got a new macbook and ran a firmware update and the battery died, when they say power must be connected, they mean it. It was very frustrating as it had to be sent in and was only 2 weeks old. I am sorry this happened but it is not so common, it happens but more often it is fine.