Amber/Raytheon Triple Field of View (TFOV 60/180/500 mm) Lens

[MrSheep]

I recently acquired this extremely rare TFOV Lens. I have only seen it in brochures and I am happy to have it in real life now haha. More info to come.

[MrSheep]

Here are some pics of the Internals. A very interesting design. The fixed lenses rotate on the inside and are controlled by a controller, mini stepper motors, hall-effect sensors, and a very unique gearing/clutch system. I put some tape over the coverings while I work to minimize dust getting inside.

[MrSheep]

Here are the electronics. There is a DC to DC converter that is 24V to 24V prob just for isolation purposes. I looked up the part (which is obsolete now) and this part alone $300!

The lens is controlled by one control board here. I will be analyzing it to see how to control the lens. So far the lens DB9 port only wires to the RS232 MAX chip. And Wires to the 24V DC to DC converter.

Has anyone heard of Optimum Optical Systems? Maybe they can chime in on how this lens is controlled.

[MrSheep]

Here is an image of the lens from the phoenix brochure I found on the wayback machine on "www.flirthermography.com" https://web.archive.org/web/20060516074340/http://www.flirthermography.com/cameras/all_cameras.asp

This lens was also in the Merlin and Radiance HS brochures:

https://web.archive.org/web/19990429060018/http://www.amber-infrared.com/products/radianceHS.html

The photo attached with the red chart mentions the DFOV and TFOV lenses under the Radiance HS product description. Cool to see how this lens ended up in the Merlin and Phoenix brochures.

Here is also a link to a mention of this lens on the merlin accessories page on indigo-systems old website:
https://web.archive.org/web/20040603074145/http://www.indigosystems.com/product/merlin_options.html

Phoenix Accessories Page:
https://web.archive.org/web/20040603025902/http://www.indigosystems.com/product/phoenix_specs.html

[MrSheep]

To get this lens working it looks like I have to reverse engineer the firmware. (Unless someone knows how this lens works)

The chips below are of interest to me. Attached is the data-sheet for the MCU and EEPROM (I think?)

[IR_Geek]

Wow that is an excellent find to go with your Amber cameras.    Noticed the electronics board had a SN of -001.   May not be many of those lenses "in the wild".   However the model number on the lens front says Rev C.    Very interesting indeed.    One of your screen captures from the brochures says it's an F/4 and not an F/2.3     While it will work, you will have to bump your integration time up to overcome the signal loss and build a specific NUC table for each focal length to get best image quality.   Easy enough with the cooled Ambers's and RTools.

Look forward to seeing some imagery from that monster.

[MrSheep]

Thank you for this. I always wondered what were the negative affects of using mismatched F Numbers. Now I know that you need to increase integration time to account for the loss of "photon energy" due to the higher F number. Now my question is how much do I have to do this. Is there a specific formula I should follow or is it just until you get a good image.

And will do! I have to first figure out how to get the lens to respond to commands. I wonder if FLIR has as user manual for it somewhere in their archives as it was once an Indigo product back in 2005. I think from 2005 to 2006 they switched to the SC6000 series cameras and the merlin and phoenix cameras were no longer offered. Check out the two brochures.

[IR_Geek]

It really depends on the responsivity of the system, but generally speaking a F/4 captures about 1/2 of the energy as a F/2.8    See diagram. 


With the Amber have a cold stop of F/2.3  it will be a little less.   That of course assumes equal transmission through the lens.     Good rule of thumb is look at a scene or blackbody of the temperature you are looking for and watch the digital counts till they are about half way between cold or hot saturation.  The Amber's are 12 bit (4095), so about 2048 counts.     

One of the great things about cooled cameras is the adjustability ... also one of the biggest downsides too!    Guess that's why most people prefer the uncooled 'turn key' cameras.

If FLIR carried them forward then there is a good chance they had the software.  Key would be if it's still around or can be found.    I know my organization upgraded cameras - Amber, Indigo, FLIR - and kept lenses.    My work still has shelves of older lenses that we utilize with newer cameras.    It's amazing to see 30+ year old IR lenses used with state of the art focal planes.

[MrSheep]

Wow this is great information indeed. I am still learning when it comes to this stuff. It wasn't until a few months ago that I finally learned about integration time. I guess since as you stated normal uncooled cameras don't really care about that stuff since it is fixed and can't be changed.

One cool thing I figured out is that a Pleora PT1000 LVDS can be used with ResearchIR. Shame you cant do custom cameras on the newer FLIR Research Studio Software. Which is why I have both. Luckily any recordings you do on research ir you can just transfer to research studio most of the time.

The cool the about the Pleora module is that you can use convert RS422 signals to LVDS via a bunch of resistors to attenuate the signal to LVDS levels. I already was able to do this with an Indigo Merlin camera which is 12-Bit RS-422. So in theory I can do this with the amber camera as well.

(Please excuse the un-NUC'd image was just for testing purposes haha)

As for the software I hope they did too. I will ask if they even know about these lenses haha. Might have to send them some brochures to jog their memory. Maybe some engineer still knows about it.

[Fraser]

Regarding asking FLIR for technical information on obsolete cooled cameras……

I have spoken to FLIR USA about cooled cameras, some of which were actual FLIR products rather than Amber or Indigo Systems. I found that the USA support team only knew about very recent FLIR models and they even admitted that none of their team or USA based techs knew anything about the SC4000 and SC6000 ! They had not even seen one ! I suspect staff “churn” may be responsible for this situation and older “sages” have left the company. Fortunately FLIR USA CS forwarded my enquiry to FLIR, PARIS (France) where the scientific thermal camera division is now located. I spoke with an amazing chap who was clearly an expert on cooled science cameras of all ages. It turned out that he was the Chief of that divisions technical team ! He loved to discuss all things scientific thermal camera related and was very helpful. He sought out the information and obsolete software that I needed amongst his team and could not have been more helpful. It was a classic direct Technical Officer to Technical Officer interaction rather than via a customer services representative. This is what you need with these cooled cameras as, even within FLIR, they are a specialist product with only limited knowledge within the USA based customer support team. There may be older technical officers within FLIR USA who would have information or knowledge, but they can be hard to track down via FLIR CS.

In my personal experience it has been apparent that if the legacy information you seek is not within the excellent on-line FLIR archives, it is unlikely that FLIR USA customer support will be able to help. It appears that they do not have “off-line” archives that may be searched for obsolete equipment data and software. In the past I have been put in touch with members of FLIR USA management (a CEO no less) who tasked their subordinate teams with searching old PC’s for copies of obsolete software to send to me ! That may all have changed with the move to Teledyne as such is going beyond normal customer support limits.

I suggest that a call for support be raised with FLIR USA requesting information on the TFOV lens and suggesting forwarding the request to the FLIR PARIS scientific camera team. That way you may avoid the classic “sorry that is obsolete and we no longer hold data on it” response.

Fraser

[IR_Geek]

Ditto on what Fraser said.   FLIR can be complicated to find the correct person.  They have absorbed so much over the past 20+ years and there has been lots of churn.

the pleora stuff is good.  Could have sworn they had an RS422 version but can't find it.  maybe it was another company or converting to CameraLink.    To me, working with these scientific cameras are much more interesting than the 'pretty picture' uncooled systems. 

I need to gather my stuff together with pictures as I have several blackbodies, lenses, two Merlin Uncooled, a TAU2, an Omega, Radiance 1 shell, and several other items.

[MrSheep]

yes good point haha. I have been given that "This product is obsolete response" many times before. It was usually when I asked about the SC6000. I will ask to be forwarded to the Paris division.

IR_Geek yes. There was a RS-422 version of pleora but it is impossible to find. (I've looked forever. haha). So instead of waiting for it to pop up. I took it into my own hands and found out that the LVDS could work due to very similar chips internally. Then I found this article that confirmed my suspicions. I took each of the data and valid pins and attenuated them with resistors. Checked the voltages and tested it with my merlin camera. And it works! Was very happy it did since it was a breakthrough. Never would I have thought I would get older Merlin cameras to work with such a modern software like ResearchIR. And now I think the Amber cameras have a chance of working as well.

[MrSheep]

Just an update on this. I haven't had any luck with FLIR US or Paris side. Wish they still kept everything on their servers . I'd imagine most of these indigo products and manuals sitting on a shelf or desk somewhere collecting dust. Most will see them as junk but to us it is gold haha.

[MrSheep]

Still doing some research about this lens. Apparently Optimum Optical Solutions was acquired by FLIR:
https://www.vision-systems.com/non-factory/article/16749435/teledyne-acquires-optimum-optical-strengthens-tactical-ir-imaging-systems

So using our trusty wayback machine I found some documentation on the TFOV!
https://web.archive.org/web/20100308014912/http://www.optimumopticalsystems.com/Products.aspx?categoryid=427d08fa-674e-4eda-874b-b3eb40796c95

As well as some specs on an earlier Continuous zoom lens:
https://web.archive.org/web/20040805111054/http://optimumopticalsystems.com/flir.htm

What is nice is it looks like the continuous zoom lens uses standard RS232 settings, which can help in figuring out the commands for my TFOV

[bCubed]

The TFOV is amazing!  But I want to comment on using the Pleora PT1000-LV to interface to RS422 outputs.  Several times I have interfaced cameras using the PT1000-LV644-GEV-E interface to convert RS422 to GigE.  I didn't use resistors to attenuate the signals because the output from the RS422 is compatible with the input of the PT1000-LV644.  You might need resistors if you go the other way around, but if you only care about the outputs from the camera, then you have only to make a connector to get it operational.  I'm in the process of doing this now to my Galileo, but have done it successfully with a couple of Santa Barbara Focalplane cameras.

[MrSheep]

The TFOV is amazing!  But I want to comment on using the Pleora PT1000-LV to interface to RS422 outputs.  Several times I have interfaced cameras using the PT1000-LV644-GEV-E interface to convert RS422 to GigE.  I didn't use resistors to attenuate the signals because the output from the RS422 is compatible with the input of the PT1000-LV644.  You might need resistors if you go the other way around, but if you only care about the outputs from the camera, then you have only to make a connector to get it operational.  I'm in the process of doing this now to my Galileo, but have done it successfully with a couple of Santa Barbara Focalplane cameras.

Yeah I am going to try interfacing without the resistors. Hopefully nothing bad happens haha. Luckily the signals are from the camera to the Pleora. So if anything the Pleora would be the only one that would be damaged. Not the end of the world since they are pretty cheap and still available.

[MrSheep]

ok so I decided to dive a little deeper into extracting the firmware from this device. The TN87C51FA1 microcontroller looks like it is of the MCS-51 family and is a variant of the 8051. This microcontroller has 4Kb of EEPROM on it, so I am guessing this is where the firmware lies. I have the T84 universal programmer coming in the mail: https://xgecu.myshopify.com/collections/xgecu-t48-tl866ii-3g-programmer. I plan to test this with a blank chip first to see if it reads it properly. Once I know that the universal programmer works with my MCU I will move onto reading the actual chip.

The board also has a Xicor X24C04 4Kb EEPROM on it as well. So my question is does anyone have a guess as to what the EEPROM is for? The unit connects to a few magnetic sensors as well as an encoder on the focus motor. Would the EEPROM be responsible for the position information?

[MrSheep]

Made some more progress on this. I added a PLCC44 Socket to the board. Now I can remove the chip safely and read the chip. What I can try now is read whatever is on there and dump the firmware to another blank chip. Hopefully this will work as it will allow me to save a backup copy as well as experiment with the other chip without needing to mess around with the original. one.

After installing the new socket and putting back the original chip I tested the lens again by applying 24V. And to my relief the lens did it's boot up and homing sequence. Good to know the socket install was a success. I had to apply a lot of flux from a flux syringe as well as Chip-Quik. The chip would not budge at first then I remembered the board was potted. So I lifted one corner gently with a pick tool and one corner lifted all while the Chip-Quik kept everything molten. I worked my way around the chip not applying to much pressure and making sure the side I was working on was fully molten.

After the chip was removed I used flux and desoldering braid to remove all the excess solder from the pads as well as the pins. And after a lot of alcohol swaps and wipes to clean up the flux, I made sure there were no bridges using a magnifying lamp. I also used the pick tool again to make sure the solder joins were good and I didn't miss a pin.

A note on the middle part of the PLCC44 socket: The middle part comes attached from factory but I learned a trick on YouTube where you carefully snip off the legs so u can more easily reach the legs to solder the socket. I placed it back in after the job so it acts as a shim for the chip to make sure the chip doesn't go too deep into the socket.

[MrSheep]

I managed to read the chip! With the beep tone of my programmer and the success message, this indicated I was able to fully read the chip's firmware. I have attached the firmware in intel hex (.hex) and binary format (.bin).

You need to remove the .txt extension to get the original file.

You have to upload it to the program here. https://xgecu.myshopify.com/collections/xgecu-t48-tl866ii-3g-programmer
I tried to copy the ascii from the xprog program but couldn't. (I will try to figure out a way)

But here is a screen shot in the meantime. Some of the text is readable

Hopefully with enough reconstructing I can figure out how to connect to it via RS232

[MrSheep]

I managed to go another route. I parsed the Intel hex and got rid of all the extra bits such as address checksum etc:

(I attached the intel hex parsed and the intel hex with only the data portion)

Below is what the formatting of the parsed intel is:


Each line must have the format ":LLAAAATT<data>SS"
Where:
 1st char is a colon
 Everything afterward are 2-hex-char (high-nibble/low-nibble) representations of bytes, eg. "12"==0x12
 Those bytes are:
    LL is the length
    AAAA is the address
    TT is the record type
    <data> is 'LL' of data bytes
    SS is the checksum



After converting to ASCII we get this (https://www.rapidtables.com/convert/number/hex-to-ascii.html):

&ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿuxvØü®ƒ¯‚d`äð£€öÂmÆmÊ‹Ð‹uÐÂÖïe‚pîeƒ"ä“øt
“ùt“þt“õ‚Žƒèip
"ä“ö£€ôä“üt
“ýt“þt“ÿt“øt“õ‚ˆƒdp
"䓣¨ƒ©‚Œƒ‚𣬃­‚ˆƒ‰‚€ã
·ŽŽ¹¹¹Â€þïõ‚‹ð¤ÀàëÅðÎõƒ¤.þä5ðÍÿ…‚ðê¤.þí5ðýä3̋ð¤,üêð¤,ü酃ð¤,ü腂ð¤,ü…ƒðê¤-ýì5ðü酂ð¤-ýì5ðüðë¤-ýì5ðüÐàÿMNL"u𠈂‹ƒäûÌÀàäÉÍÀàäÊÎÀàÃï3ÿ¨æ3öæ3öæ3öë3ûê3úé3ùì3ü땃êžéì•‚@ü땃ûêžúéùÕðÈÐàþÐàýÐàÌøïNML"
<èüéýêþëÿ€ïè3PäÛûäšúä™ùä˜øÓì0ç³ÀÐ
â€ÀÐ
<Ðð ÷
"õð
âåð"ìÀà
¦
œ€çäßÿäžþäýäœü"õðÃï›õƒîšBƒí™Bƒì ðd€Èd€È˜‚ñ0òEƒp
Ó0ó
³ä3"ï+ÿî:þí9ýì8üMNO"Ãï›ÿîšþí™ýì˜üMNO"€ì¢çüíýîþïÿÛðìMNO"€
Ãï3ÿî3þí3ýì3üÛñìMNO"ЃЂä“p   t
“p££€t“o`£££€èt
“Ààä“Àà"+ûP

éÀàêÀàëÀàtÇÀàtÀàÀ‚ÀƒïÀàîÀàíÀàìÀà;ÐàøÐàùÐàúÐàû"ÐàûÐàúÐàùØ+ûP

¹ëøìöíöîöïöLMN"¹
Šƒ‹‚ìðí£ðî£ðï£ð€èëøìòíòîòïò€Ù+ûP

¹ëøæÿ"¹
Šƒ‹‚àÿ"¹Šƒ‹‚ä“ÿ"ëøâÿ"+ûP

¹ëøæüæýæþæÿNML"¹
Šƒ‹‚àü£àý£àþ£à€è¹Šƒ‹‚ä“üt
“ýt“þt“€Ñëøâüâýâþâ€Ã’÷+ûP

¢÷äuð
@uðÿÀàÀàÀà;åð/ÿÐà>þÐà=ýÐà<üØ"ÿFE

LULL
Password: OK
OSS/MOSS Controller Rev -  Firmware Version 1.10
Copyright (c) 1996-1997 Optimum Optical Systems
Command List:            Error Messages:
FN   Command Narrow FOV      FE   FOV Error
FM   Command Middle FOV      PE   Focus Error
FW   Command Wide FOV      ERR   Command Error
FI   Initialize FOV         CKE   Checksum Error
FS   Request FOV Status
Pnnnn   Focus Command
+/-   Focus Jog
PS   Request Focus Status
SF   Front Temperature Sensor
SR   Rear Temperature Sensor
MN   Activate Mechanism
MO   Deactivate Mechanism
MS   Request Mechanism Status
LUnnnn   Store Upper Focus Limit
LLnnnn   Store Lower Focus Limit
LS   Request Limit Status
OS   Request Optics Status
X   Transmit 20 bytes to Optics
R   Receive 20 bytes from Optics
W   Store 20 bytes in Optics
SFSR0000
FW
X
CKE
MN
MO
W
ERR - PE
FN
FM
ME
u‰!uèu˜RҎu¨Â
Âúcú~äõHŽGú~åH/õHåG>õGú~äõJŽIú~åJ/õJåI>õIäõAõBõCõDõ?õ@å?d€Ó”€Psî3•àýüy{A–@å@p?€Øåcÿ3•àþýü{zyxØy{A+–uaubï`   }~¹ ÿ~}|y{AØ–såcû3•àúëuð¤Ê«ðuð¤+ÊûïÛÿîšþ3•àýü{T{€zyxy{A–y{A<– ×Âxd†k„+-
°F
(HLÅMO   ‚P
FR
_SGWcX¶xeædSp#}~½ ¯H®GÁ}~Á ¯J®IÁÜxeædUpExi†•äõGHxh†•~î~ÏÃ3Ï3ÞùþåH/õHåG>õGxg†•~äÿåH/õHåG>õG€NxeædLpExi†•äõIJxh†•~î~ÏÃ3Ï3ÞùþåJ/õJåI>õIxg†•~äÿåJ/õJåI>õI€Ò0   u_}~Ä  €ûxdædOpExeædOp>xfædSp7åG~õ*KåHTÿõ*KåI~õ*KåJTÿõ*K}~Ð €@Òú~äõHŽGú~åH/õHåG>õGú~äõJŽIú~åJ/õJåI>õI¸xeæd0pzxh†•äõ   xg†•~î~ÏÃ3Ï3Þùþå   /õ   å>õxf†•~äÿå   /õ   å>õÿ~«   ªïÛõFîšõE¡Pfÿ~«FªEïÛÿîšþÁäõ'õ(¯F®E7€"xeædSpPfÿ~«FªEïÛÿîšþÁ€Ò¸}~Ô }~6 }~w ¸u_å_ÔP¯_úz_€í¸xeædFp3}~‰ ¯D®C­B¬A{€zyx{<ÃäŸÿäžÏ$ÿÏ4þÁ€xeædRp}~Œ €Ò¸ÚÂxeædIpï`}~¹ €   }~” HxeædWpuaÒ€axeædNpua
Ò€SxeædMpuaÒ€ExeædSp<0”.FfåapWf€åapNf€åadpMf
f€   }~¹ €Ò0;¡äõ'õ(¯F®E7g¸}~˜ u_ €ûu_u`å`ÔP0å__$døæÿ•ïTÄÿå`$Kø¦å__$døæÿ•å`$Køæ/ö`€Éï`   }~› ¸xeædOp
€0xeædNp€"xeædSp0—}~  €   }~¤ €Ò¸xeædSp6u`å`ÔP¯`úå`$Kø¦`€éï`}~› €   }~Ð €Ò€qï`}~› €*u`å`ÔPå`$Kø†*¯`K`€éúc}~¨ €4åFFpE¡äõ'õ(¯F®E7€FåFpE¡äõ'õ(¯F®E7€Ò0}~« }~d 
fÂu_åapu6€åadpu6€u6¯66ú~äõ1Ž0¯66ú~å1/õ1å0>õ0¯66ú~äõ3Ž2¯66ú~å3/õ3å2>õ2¯66ú~äõ5Ž4¯6ú~å5/õ5å4>õ4~#}
|«DªC©B¨A+Œ,-Ž./¯1å0þäýüy{,Ø–>~}|y{,–}~}|y{,
¦–¯FåEþäýü{Ty{,–¯3å2þäýü{Ty{,+–å4Ãþå5ÿäýüy{,–¯5å4þäýüy{,
¦–äÕ/ÿä•.Ï$ÿõ   ï4õÓå   ”þå”@åӔ@äõõ   €uu   ÿ}~² "u,u-u.u/ÿåapu8€åadpu8€u8¯88ú~äõ3Ž2¯88ú~å3/õ3å2>õ2¯88ú~äõ5Ž4¯88ú~å5/õ5å4>õ4¯88ú~äõ7Ž6¯8ú~å7/õ7å6>õ6¯   åþäýüy{,+–¯7å6þäýüy{,Ø–~}|y{,–¯/®.­-¬,{zyx
¦Ž01~#}
|«DªC©B¨A+Œ,-Ž./¯3å2þäýüy{,Ø–~à}|y{,–~Ð}|y{,
¦–å5%1ÿå450þïÕ/õFî•.õE"&å&uð„ÿ7å&uð„åðÿ7
fX~~˜"ÿ~«FªEïÛÿîšþÓï•Hî•G@ÿ~«HªGïÛõFîšõE}~² €2ÿ~«FªEïÛÿîšþÃï•Jî•IPÿ~«JªIïÛõFîšõE}~² "u"Âu`å`ÔPå`$Kø†#å"%#õ"å#`Ò`€â0¯""
"&Ž%³å(®'ÎÃÎßùÿbå(TÄÿå%zOÿb¯&bÒ³"u)åbp$åap   
‹)€åadp
‹)
‹)€Aåbpåap   ‹)€
åadp
‹)€ åap‹)‹)€åap‹)å)`}~¹ €3…ab¯aïp}~” € ïd
p}~¶ €ïdp}~º €"äõ9õ:õ;õ<õ=uu   ÿ;¡äõ'õ(¯F®E7u> •õÒ Â¡å=ÔP+¯<®;­:¬9{ z†y
xt

ðp •=€u=y{9Ӑ€ÎÒ¡å=ÔPu>
€läõ9õ:õ;õ<õ=¯<®;­:¬9{ˆzyxt

ðp
y{9Ӑ€ß å=ÔP+¯<®;­:¬9{ z†y
xt

ðp0”=€u=y{9Ӑ€ÎÒ å=ÔPu>
~Ò¡Â å=ÔP+¯<®;­:¬9{@z
yxt

ðp0•=€u=y{9Ӑ€Îå=ÔPu>
€Gäõ9õ:õ;õ<õ=å=ÔP+¯<®;­:¬9{ z†y
xt

ðp0”=€u=y{9Ӑ€Îå=ÔPu>
Ò Ò¡uaub¯>"(äõ"õ#õ$õ%õ&õ'å(p ҡ€Ò ¡å&ÔP+¯%®$­#¬"{ z†y
xt

ðp ”&€u&y{"Ӑ€Îå&ÔPÒ Ò¡
"u&äõ"õ#õ$õ%å&ÔP+¯%®$­#¬"{ z†y
xt

ðp0”&€u&y{"Ӑ€ÎÒ Ò¡å&ÔP
""#ïÔ@Ff€Nå#Ô@Ef€@å#Ô
@Df€2å#Ô@Cf€$å#Ô@Bf€å#Ô
@Af€å#$0ÿf""ïÔ0@
å"Ô:På"$Ðÿ"å"ÔA@
å"ÔGPå"$Éÿ""%Ž$å%®$ÎÃÎßùÿ7å$Tþå%Žä7äþå%ÎÃÎßùÿ7å%Tÿ7
f"&Ò¤Ò¥å&p&¤Ø~ï~Ò¤Ò¥0—}~¾ €   }~¤ €20–}~¾ €$Â¥Ø~ï~Ò¤Ò¥ —}~¾ €   }~  ""0€ûÒ…"™")äõ&õ'å)Ô@õ²å)TÄõ)å)$Žõ)u(
å(Ô   På)T€`ґ€‘å)Ã3õ)Ґ(€ß‘Ҳ
~~²u(
å(Ô
PҐå'Ã3õ'å&3õ&0’'å'p&(€ÛÒ²¯'®&"~"+èå+3@ ‰¯+‰è¡‰€¤‰å+Tÿ‰è¥‰u)u*
å*Ô   P"å)Ã3õ)Ґ
~~0“C)

~~*€×¯)"#u"
å"Ô   På#T€`ґ€‘å#Ã3õ#Ґ"€ß"(“u&
å&Ô   P3å(T€õ'å(Ã3õ(å'p“€ғ
~~Ґ
~~
~~&€Æғ
~~Ґ
~~
~~"Ґ
~~ғ
~~“
~~"“
~~Ґ
~~ғ
~~"%Ž$#
!«%ª$©#`©#ª$%å%p$ûf€ß")èå)3@ ‰¯)‰€
¤‰å)Tÿ‰¯*‰ä~~"%Ž$äõ"õ#Ãå#•%å"•$P
#å#p"€ë"ÀÐÀàÀ0˜$˜å_Ô)@u_å__$dø¦™å™d
p   Òå_$døv0™™ÂÐÐàÐÐ2ÿÿÿÿÿÿÿÿ

Making great progress

[MrSheep]

The garbled text is prob just the program's assembly code but what is most interesting is this part. (And wow 1996-1997 ) :

LULL
Password: OK
OSS/MOSS Controller Rev -  Firmware Version 1.10
Copyright (c) 1996-1997 Optimum Optical Systems
Command List:            Error Messages:
FN   Command Narrow FOV      FE   FOV Error
FM   Command Middle FOV      PE   Focus Error
FW   Command Wide FOV      ERR   Command Error
FI   Initialize FOV         CKE   Checksum Error
FS   Request FOV Status
Pnnnn   Focus Command
+/-   Focus Jog
PS   Request Focus Status
SF   Front Temperature Sensor
SR   Rear Temperature Sensor
MN   Activate Mechanism
MO   Deactivate Mechanism
MS   Request Mechanism Status
LUnnnn   Store Upper Focus Limit
LLnnnn   Store Lower Focus Limit
LS   Request Limit Status
OS   Request Optics Status
X   Transmit 20 bytes to Optics
R   Receive 20 bytes from Optics
W   Store 20 bytes in Optics
SFSR0000
FW
X
CKE
MN
MO
W
ERR - PE
FN
FM
ME

[Fraser]

I was just looking through a file that is supplied with the Amber UserMenu 3 program. It would appear that there is lens control functionality within UserMenu and the ICD file mentions a triple field of view lens  I am still working my way around the UserMenu files so cannot comment further on any lens control functionality. Take a look at the attached file in a text editor like Notepad and the ICD makes interesting reading.

Update: I just checked the menu creation files and I can see menu entries for controlling both the DFV and TFV lenses 

Fraser

[MrSheep]

Oh wow!!! You are correct:

>>;=======================================================================
>>; Menu 18 - TFV Lens
>>;=======================================================================

>>Function:
        TFV Lens Control
>>FunctionName:
   TFVLens
>>SelectionLetters:
   TF
>>MenuName:
   Lens
>>Description:
   Functions for use with the Tri-field of view lens

  Thanks for this great find. Will do more research myself, as well!

[Fraser]

The files associated with the UserMenu program are making interesting reading. I am hoping that there may be instruction entries that may be changed so that the software works with my Radiance 1 camera. In the GALPRC.MNU file I am seeing various codes and function numbers associated with commands. More investigation needed. I need to prove to myself that the communications test timeout is not a hardware issue as the ICD suggests that the link test uses no data packets.

Fraser

[MrSheep]

Yeah im going to have to do some deep diving myself. I am going to use a serial monitoring program and see what the reads and writes are.
I dont think these cameras respond in normal ASCII since most functions when using RTools' programs are seen in Hex commands.

The attached doc is from someone who owned a Galileo camera as well. He was able to decipher some of the command structure. I believe the Radiance 1 is the same just using different reserved commands.

In the text file left hex is prob the "write to camera" and the right is the response from camera.

(Write) 03 00 0A 02 00 24 FF FF 00 00 31 02 00 00   (Read)03 00 0A 02 00 24 00 00 00 00 33 00 00 00    //  AGC ON

[Fraser]

Something I am seeing from the files provided with UserMenu is file names "GALPRC" and "GALUPRC". I am thinking GALPRC is an advanced menu and GALUPRC is a standard menu. I hope there is no password barrier to accessing any advanced menu that may exist. I see that the GALUPRC ICD file mentions only the DFV lens whilst teh GALPRC ICD mentions DFV and TFV.

I tested both of my Radiance 1 cameras with UserMenu running on an era appropriate 80286 PC to see if that would work. I still had communications test timeout errors with NIL data received, so it is not a case of needing the right age of computer to use this DOS software.

Thank you for the file. Have you had UserMenu3 working with a Galileo ? I hope the copy of UserMenu3 that I have is not in some way faulty 

Fraser

[MrSheep]

Yeah I have not tested usermenu myself as I have been using the TWI software with the Galileo/Radiance HS. It is on my to do list though. I have to setup Dos in a box and hopefully I can communicate via that. Or else I have to find something old enough to run MS-DOS haha.

[Fraser]

I shall have to try the TWI software with my Radiance 1 to see if it complains about not seeing a Galileo HS connected. I should have done that before now That would show whether there really is a camera identity code present in the command protocol. Such a pity if there is and it is embedded in the UserMenu EXE file.

Fraser 

[MrSheep]

The TWI software is very specific with the firmware. Maybe typing 3.0 will work? But not sure. I find using RTool's Radiance 1 GUI the best. You dont need a license to run just the Radiance 1 software. Also I will update you on the Data Acquisition of the Radiance 1. If I can get the pleora LVDS working with the Radiance 1 you will most likely be able to use it in FLIR ResearchIR

[MrSheep]

Huge progress on both figuring out Usermenu as well as the TFOV menu. Given that there were no instructions in any of the usermenu version. I decided to just take a look at all the files itself under a text editor.

I came across a few batch files found in an older version of usermenu called GAL158 (GAL probably means Galileo ). They had a weird format so to investigate deeper I went into Usermenu itself. After firing up Usermenu and hitting F1, I found an interesting function under the Direct Menu Manipulation Commands:

;mn, ‹filename>, ‹menuname> (diagnostic user only).

After comparing this structure to the batch files I found that the command:                ;mn,Galuprc,MainMenu
came up a alot. So when firing up Usermenu.exe from Menu3 in DosBox I typed in (exactly as seen):    ;mn,Galprc,MainMenu

And boom it showed the advanced menu. I chose this specific command because of what @Fraser found earlier in Galprc
Also notice the difference between the titles in the attached photos. One says Usermenu Menu: Radiance HS and the other says Diagnostic Menu: Radiance HS

Once I get this connected to a serial monitor I will see what kind of commands (most likely hex) are being sent out. And hopefully this will once and for all solve the mysterious TFOV commands
But it is pretty late so I will investigate tomorrow haha.

[MrSheep]

Got around to playing with the .HEX File I extracted from the main 87C51 chip and these are the results. Plan is to play around with it in the a dev board.

[MrSheep]

Apparently in 2002 Indigo Systems (aka FLIR) made a fully enclosed system with this lens called the TH-10.
Looks like there were options for both Merlin and Phoenix MWIR systems. Very interesting 

https://web.archive.org/web/20040615085358/http://www.indigosystems.com/PDF/TH-10_Brochure.pdf

[ij-ami]

Apparently in 2002 Indigo Systems (aka FLIR) made a fully enclosed system with this lens called the TH-10.
Looks like there were options for both Merlin and Phoenix MWIR systems. Very interesting 

https://web.archive.org/web/20040615085358/http://www.indigosystems.com/PDF/TH-10_Brochure.pdf

We actually own one of these, which has the Radiance and the TFOV lens inside of it (see attached). We are able to talk to the camera, but not the lens, yet.

Your investigation so far has been really helpful in narrowing down some options on what commands to send it!

[MrSheep]

Wow what a find! How did you come across this camera? It is quite rare to have. (Also curious to see which Amber camera you have Radiance 1 or Radiance HS/Galileo)

And could you post more pictures of it? That would be helpful in figuring out how to communicate with it.

[ij-ami]

There are many electronic devices in storage procured over many years... I honestly couldn't tell you how we got this. It has a Radiance 1 in it (we actually have 3 of those!) and I've been talking to Fraser regarding his experiences with the camera, which has been very helpful.

I've attached some more pictures - if there's something specific you're looking for send me a PM.

(I'm slightly miffed about the lens connector ending in a molex, I'm suspicious that somebody at some later date may have done that)

[MrSheep]

Wow, I can see now how they fit the Radiance one in there .

How many wires are going from the molex to the DB9? A pic of the molex and other connections would help.

[ij-ami]

How many wires are going from the molex to the DB9?

5 wires, to pins 2, 3, 5 (presumably RX/TX/Ground) and pins 8 & 9 (24VDC/GND)

Once I get this connected to a serial monitor I will see what kind of commands (most likely hex) are being sent out. And hopefully this will once and for all solve the mysterious TFOV commands
But it is pretty late so I will investigate tomorrow haha.

Did you have any luck seeing any of the commands? I've tried sending the lens all kinds of things via RS-232, but see no changes and receive no responses, so I assume it's looking for something specific.

I did find the correct lens control command codes to send to the Radiance 1 camera, but those only control lenses that are connected via the front port on the camera... 

[MrSheep]

No I haven't. When I turn on the lens it does its limit switch homing sequence but after that I don't get any response from the RS-232.

This is why I am currently trying to decompile the original firmware to see if I can figure out the original commands of the lens. The hex code is attached in previous post, if you want to have a shot at it.

How is the TFOV lens connected? Is it connected via a main connector harness and not to the front lens connector of the radiance?

Do you have a picture of the rear wiring of the TH-10