News:

When asking for technical help at the very least let us know the version of firmware you are running.
Cliff's Calibration (Mapping) Guide is a MUST READ: http://www.vemssupport.com/forum/index.php/topic,97.0.html

Main Menu

HELP: Firmware upgrade gone bad

Started by antonch, August 08, 2007, 11:33:44 PM

Previous topic - Next topic

miniminor63

thanks, pretty much what I thought out myself:) I will try to upload the temp stuff using the method you told me know. I am using that package for the firmware.

Thanks!

miniminor63

#16
BTW, when you run the tempsensor_upload12x12.bat thats given with the package you linked to in your last message, it starts with telling you :

"will upload 1.0.53 firmware + your chosen temp factor files"

I want 1.0.73, not 1.0.53...., its just a typo, but still not as it should be:)

[email protected]

I saw that, they should sack the bloke who does the firmware packages...
But then he wouldnt be here to run the forum! :P
;)
Rob


miniminor63

lol, I will rather edit that typo my self than make that guy suffer then  :P.

I am only glad my box is up and working again. and are actually pretty happy that I found the error myself:)

But why oh why must the temp sensor stuff be so complicated. I have loads of datapoints for my sensors (provided to me by bosch), and then I think it should be just to go into a list and find the correct one, and upload it. I am sure it is a reason why its not like that, but I dont get it:)


Sprocket

Really glad you got it sorted buddy!!!!

That tempsensor_2252_256_upload.bat file is one of your earlier ones rob that i edited ;) I changed the firmware version at the top and gave the file that name, as I have several with different Xfactors written in it, it was easy to file it that way. I did this when i was trying to find the best Xfactors for my sensors, its still pants, i havent spent the time to sort out this winhex thing to get the easytherm data into the hex file format.

The bat file works oakley doakley for me, it is odd the hex patch file crashes though :-\

My fault :-\ I hold my hands up, now wheres that virtual pint thing gone ;)

Denmark

well,

This have just happend to me,as i was trying to upgrade to 1.0.73 from 1.0.38

but i cant even run this command, as it says file not found.


tools\megaloader.exe firmware\upload.hex -wE 38400 -c com1


So now i cant do anything.

I did get the 1.0.73 firmware in, but could again not find out ,to get the H2 tabel right, so i tryde lots of times, but suddenly it went wrong, and i now cant get communication,
Other then in the terminal program

Anyone got any info on how i get futher?

Thanks,
Skassa
working on the boxer

Denmark

got it working again :)


So i will try it again
working on the boxer

billman

#22
Hi,

i tried today to upgrade to 1.1.32alpha and got the OK from the V3 GUI. After that i started the MT and accidentally i go to the 16x14 (not supported now) iand tried to upload a 16x14 setup i made. Since then i can not connect to VEMS. I tried the 2+3 pin bridging of the Serial cable but megaloader couldnt find the upload.hex file. It is not in the package i am using nor teh 1.1.27Beta that i used till now.
I have also tryed to change the file from Upload.hex to Vems.hex and then i get the no Hallo message. Thsi hard reset doesnt work for me.

No Power to VEMS-Bridging-Power on -then connect the Serial2USB adaptor i got from VEMS that worked till now with no probs.


Any thoughts?

Thanks