Bugs
0
Updating firmware from 6.08 to 7.05 FAILS REMOTELY!
When updating our firmware programs on customer units from v6.08 to v7.05 remotely we can't accomplish this without asking something of the customer we really can't reliably expect from all of them.
They have iqango, connected via bluetooth.
Currently the only solution I have found is the following:
1) Remotely connected: using v6.08 install a blank program, power cycle
2) Email a v7.05 blank program to the customer, they use iqango to send it to the module, power cycle
3) Remotely connected: using v7.05 install the real program, power cycle
Attempting to remotely perform step 2 results in an immediate rejection of the remote connection.
This program is simply a single MC41
Customer support service by UserEcho
I did find my v6.08 blank program had the connectivity set to "ask user" I set those both to "always" and I was able to proceed to step 2 and connect remotely and start the download of the blank v7.05 program. However it stops for a long time at 392kB and eventually goes to 393kB and has the message remains "Waiting for MC41[0]..."
if I cancel at this time it leaves the module in a state I can't connect to it in a remote situation....even giving me fits with a direct can connection. I'm currently waiting to see if not canceling will get a better outcome as I see it finally went to 394kB.
Waiting and not canceling eventually go to 395kB and disconnected itself. I was able to reconnect remotely and finish as desired however. But this long wait is very painful when you consider the farming folks we service. Very long time a cell service is asked to be constant, especially since they often call on the same phone.
Do you have the same issues going from 6.08 to 7.04 then 7.05?
I couldn't tell you, we upgraded straight from 6.08 to 7.05
Ok I installed v7.04 and tried the same routine. I did successfully perform the firmware upgrade from 6.08 to 7.04 and then the final program in 7.05, but it felt the same as when I did it in all in 7.05, I just had the kB slow down 2kB earlier.
Now the slow down occurs at 390kB rather than 392kB
and it takes 5 min to go from 390kB to 393kB, where in 7.05 this occurred at 392kB to 395kB
Ok, thank you for trying that. Can I ask what firmware version you are running on your G12?
the G11 firmware is 1.12.2.1722
the G12 firmware is 2.01.8.53
my iqango is 7.05.54
Well I have had a "few" successful upgrades with this method...but far to many failures that leave the module at the point where I need to disconnect the IDtag to get to communicating with the module again. So this is as effective as "bricking" the module as far as a remote connection is concerned.
It should be possible to update both firmware and application from 6.08 to 7.05 in one update operation.
What symptoms do you see when attempting to send your 7.05 application directly to the machines with 6.08, without any intermediate update?
As you are going to 7.05, are you changing bus speed remote? I assume not as you mentioned G11 firmware, only machines with G12 can use higher bitrates than 250 kpbs.
Are there any other CAN nodes on the Diagnostics bus where you have the G11/G12?
What software are you using when you connect remote from the office? IQANdesign, IQANrun or IQANgo?
We tried directly replacing the full 6.08 program with the 7.05 version, but having basically the same issues we decided to try the simplest program first. With the program hanging up around the 370-390kB range, and knowing the program is in the 480kB range...I thought eliminating the size might help.
We are not changing bus speeds, always 250 kbps for our stuff.
We do have a CAN keypad(s) on this node, I'll unplug that and see if I have any better results.
In the office I would generally use IQANdesign. I tried IQANrun to do the same operation only because I was wondering if there would be a difference. I didn't see one at that time.
I disconnected the keypads, and tried a direct replacement and it connected and started, then disconnected me about 21kB in.
Starting over with the keypads disconnected, I updated to the blank v6.08, then directly updated to the blank v7.05 it stopped and is doing the usual 5 minutes for the last 3-4 kB. In the end, after doing this I was able to update to the desired v7.05 full program. But it's this 5min hang time that is our high risk move with our customers. If it fails, there is nothing we can do for them remotely, and we have to ship them a new MC41. So right now the only reliable solution we have is not to update these remotely past the latest 6.08 program we have for them.
The other issue we have is these are basically farmers...even sending them the program directly is very difficult...they can't find the program on their phone. But the good cell service is also a factor.
So for whatever reason, this intermediate "blank" program is doing something for me.
Basically I don't see any difference even when all other CAN devices have been disconnected. Only the G12 is connected.