My RoboTeq firmware saga.....
17/08/19 18:09
Hi can you tell me what’s going on with the firmware for this model range, I downloaded and installed HBL23XX-Overall-Firmware-Update-v20-052419 and got an overvault fault. When I installed the v18d firmware the controller worked again but, of course I can’t use any V2 features.
Can I use the HBL23xxA V2 firmware with my HBL2372?
Are you working on the HBL23XX V2 firmware, I noticed it’s been removed from the downloads page.
20/08/19 12:34
Unfortunately there is not a release for HBL23XX yet. And HBL23xxA is not compatible with your controller. Our engineering team is working on producing a firmware update for HBL23xx and we will notify you as soon as it is released. Could you please send me the results of UID and FID commands on your controller? To identify the exact controllers type.
I’m looking forward to your feedback,
20/08/19 14:33
Hi xxxxxxx, thanks for the reply.
Please see attachment for the returned values of the two commands.
In regard to the V2 firmware, are you aware of HBL23XX-Overall-Firmware-Update-v20-052419.zip that I downloaded on 080219? I installed it and got an over volt fault, it was reading 96v no matter what input voltage I sent the controller.
22/08 10:02
Please try updating with the attached file. In case you come accross the same ovelvoltage error please contact with me in order to investigate further.
Looking forward to your feedback,
22/08 12:37
Hi xxxxxx I’ve installed the firmware but now the controller won’t autodetect my laptop.
The usb light is on and the status led is flashing twice so I think it’s the over vault fault again but I can’t use Roborun via usb.
What should I do now?
23/08 12:59
For starters I have to ask you to update to the latest Roborun+ Utility. When that is done the next step is to update the firmware to your controllers using RS232. I ask you that because it is the most stable way of upgrading the firmware. You should use an USB to RS232 adapter. Then ensure that you perform a power cycle by disconnecting the power supply for some time in order for the capacitors to drain. If after doing that the problem is still present, please get back to me to proceed to the next steps of troubleshooting.
Looking forward to your answer,
27/08 23:25
Hi xxxxxxx I have re-installed the latest Roborun from the website
I have connected the controller to pc using rs232 to usb lead
It connects with a green light in the bottom right of Roborun screen, but no controller model is shown and the box to select controller does not work.
On the Console tab I click ‘Update Controller via COM Port’ and select the firmware you supplied to me.
I click ‘Program’, the box ‘Checking the Controller’ is ticked
I then get an error ‘Device starting string not detected’
I did try the trick I read in the Forums about turning the controller off and on while the script was waiting for the device restart but it did not work.
I have attached a picture of the firmware update error
28/08 12:06
In that case try connecting to your controller via usb. Then open device manager and check if your pc identifies the controller and how exactly it is beeing appeared. If is appeared as StmDFU or similar that means that your device is in dfu mode and you should open dfu loader manualy (type dfu loader in search bar). If that's not the case we should arrange a teamviewer session to see what's going on.
Please try the below solution and keep me informed regarding your results,
28/08 12:48
Hi xxxxxxx yes that is the case, it’s in DFU mode, but how do I get it out of DFU Mode? I re loaded the firmware, got a success message but when I quit the DFU Loader, turned off the controller, waited 10 mins and turned it back on the controller is still in DFU Mode?
I read somewhere that it is not possible to load an earlier firmware once V2 has been loaded, is this the case? Can I go back to V1.8 for a while so I can get on with my project?
Found this posted by Griffin Baker 5 years ago :-
“The controller will go in DFU mode if it boots and immediately crashes 5 times in a row.
Crashing after boot typically happens when a faulty script is loaded in flash and the configuration is set to script auto start.
Connect the PC via serial port and run Hyperterminal or similar terminal emulation software.
If after reset, you see Starting ... followed by FID= xxxx and then Starting ... again, this is likely to get a script crash scenario. Try sending !r 0 immediately after the FID=xxx and before the next Starting ...
If Starting ... only is repeating, then press and hold the w key. The controller will display IAP and the letter C every second. You will then be able to upload new firmware/”
I have never gotten around to even looking at scripting so its nothing to do with that so the firmware must be crashing? If you agree this is the case should I attempt to go back to V1.8?
I’ll await your reply before doing anything else
28/08 14:22
As it seems the firmware didn't update correctly, that's why you are still in DFU mode. First of all we should eliminate bad connectivity causes. Try using a different usb cable and/or a different pc. If firmware v.2.0 isn't able to be loaded the same will happen with v.1.8.
Looking forward to your reply,
28/08 15:38
Hi xxxxxx, I’ve used a new usb cable and using DFU mode reinstalled the firmware. Now the usb light is flashing and won’t connect to the pc, but the status light I think is flashing the idle pattern, but I can’t connect Roborun the rs232 won’t connect either. I can’t see a usb connection in device manager. I have tried the same on my old win 7 laptop with no difference
I await your reply
28/08 16:13
,
I followed once again our conversation and I figure out that there has been one mistake with the firmware I sent you. You don't need the HBL23XXA version for your controller. The right firmware is attached. In order to update the firmware via RS232 you should follow these(link) steps. If you are not in a rush we could check it together tomorrow via teamviewer.
I apologize for any inconvenience,
28/08 16:41
Oh, the wrong firmware! That’ll do it! I’ll go and try using DFU but as far as I can tell the steps in the link are exactly what I’ve been doing, DFU doesn’t get as far as loading the firmware as turning the controller off and on doesn’t work.
Probably speak to you tomorrow.
I tried it and now it won't connect via USB or RS232
So I think my controller is now a brick, good eh?
Also, notice they never mention the firmware they removed from the download page