Are you having problems using some of the functions on a newly shipped Ti-E? It turns out there are several problems which can all be cured by a simple hub update. All of these problems stem from a firmware mismatch between the scope body and the hub. Problems include:
- Ti-E Z focus not responding via knob control
- Ti-E Filter cube not responding
- Software control and manual control over focus and/or filter turret, or objectives unresponsive
- Long boot times when scope starts up
If you are experiencing any of these items, there is a simple test to perform to see if the problem could be a firmware version mismatch:
Turn the scope off, then turn it back on. Does your Firmware version read “Firmware 4.0” on the front panel of the scope? If so follow the directions below to update the hub firmware:
- Download the instructions for firmware update, and hub main + hub sub firmware, from my website here.
- DO NOT extract either hub firmware ZIP just yet.
- Read the following outline below, then decide if you’re up for this. If not, contact your local Nikon rep to have this performed. If you are in Northern California, you can find out who from my company can perform this upgrade, via this link.
- There are a total of 3 firmware update-able units inside the Ti-E. These are:
- Ti-E Microscope Body Firmware
- Ti-E Hub “Main” Firmware
- Ti-E Hub “Sub” Firmware.
- Because we saw in the initial restart test that our scope showed Firmware v4, we know the following condition exists:
- Microscope Body = V 4.00 or higher
- Hub Main = V ??? – all we know is that it’s incompatible
- Hub Sub = V ??? – all we know is that it’s incompatible
- So what we need to do is update only hub main and hub sub. Now the trick here is to NOT MIX UP THE HUB MAIN AND HUB SUB FIRMWARE. If you do this, you will end up sending the scope back to Nikon repair for firmware recoding, so follow my instructions below to the letter!
- Follow the instructions provided in the PDF for hub updates, or follow my “extra safe” instructions below.
Update Instructions (use at your own risk!)
- Restart (i.e. power cycle) the scope.
- Extract only the files, which are zipped, named “HUB-A_MCPU_Ver310”.
- Run the “Hub-AM_FTD.exe” program. It will show you the current firmware of the main hub. Select “File” Then “Open an S-Record”.
- Browse to and select the firmware file named “Hub-AM.mot”. DO NOT select any other file name!
This is the hub update application. note the Big red box is where the current version of the firmware is displayed. If your firmware shows 3.1 or higher, do not proceed. - Click the start button to apply the update.
- when complete. Close the updater. Restart the microscope.
- Delete the extracted files that we used to run the update, i.e. the entire folder named “HUB-A_MCPU_Ver310”.
- Next repeat steps 3-7 above, but instead of using “Hub-A_MCPU”, use “Hub-A_SubCPU” and use firmware file “Hub-AS.mot”.
- When complete, test the scope for proper operation, to confirm that the problems you saw originally are no longer present.
*Note that the key thing we don’t want to do here is to mix up the “-as” and the “-am” files, which is why in my instructions I have you extracting, updating and deleting each set of files individually.
– Austin
Comments
4 responses to “Nikon Ti-E Hub Firmware v4.00”
I have A Nikon Ti Eclipse. In multi acquisition mode, say I select 20 sites to visit in time lapse, and the co-ordinates are on the table – all looking correct. When the program runs, the stage goes to the first spot OK, but then for the second, it goes to a random spot at zero y (nowhere near where it was supposed to be) then it goes to other spots correctly. Its like a ghost spot. Reinstall, new computer, etc, no change in this bizarre effect. Could it be firmware??
Hi Nigel, this sounds like a fun problem! (Right…)
OK so what stage do you have? Is it an official “nikon” stage? Or a 3rd party like Prior, ASI, Mertzhauser, Ludl or such? Also, What version of elements?
I’ve seen some wierdness in Elements in a few versions back where it wouldn’t handle negative XY coordinates correctly. The other problem could be that the XY value sent from elements to the stage exceeds the stage’s values, and when the stage sees this it somply goes to 0,0 because it can’t go to -2000,-2000 or something like this. One simple test would be to re-zero the stage by trying:
– Zeroing the stage by leaving it in a center position
– zeroing the stage in the lower left corner
-zeroing the stage in the upper right corner.
If these changes affect the problem in any way the issue is somewhere in the coordinates issued.
If this keep having problems please shoot me an email and we can schedule a time to jump online so i can take a look at it. I’m assuming you are GMT 0 so it’d be sometime in your afternoon, like 2pm?
-Austin
Hi Austin,
I’m facing exactly the same problem with a Nikon Ti with a Nikon motorized stage. It’s occuring since few years in a complete random way, with mosaics or multi positions acquisitions. Nikon told me I’m the first one reporting this issue… It seems I’m not the only one at the end.
Changing the origin might resolve the issue, the problem is: I don’t know how to do it. Using the TiControl software, it’s not possible to change the origin.
So I’m coming to you to know if you were able to fix Nigel problem and how you did it. You will be of inestimable help.
Thank you very much in advance
B
What version firmware do you have on the scope and hub?