HTI HT-203U 256×192 thermal imager for Android phones

[ainu]

"New" 1.0.3.28 release of ht-105/203 application from hti site have same interlaced bad image on my "broken" 203u.
I was tryed 1.0.3.24 (from seller), 26 (from hti site), 29 (from Google play) and all versions had bad interlaced image on my unit.

Vid 11231 and Pid 258 on "good" and "bad" 203u unit is the same. And same with some hikvision unit (I see it in device filter xml after decompile hikmicroviewer app). That is the reason why hikmicroviewer try to use 203u unit.
I think to write some "crazy" letter to hikvision support and ask him what hikmicro viewer can do wit "clone" 203u unit. May by I get some infrormation from they.
Another way is think about something like usb bus sniffer (if is possible at all on rooted smatrphone) that may be can answer what hikmicroviewer do with 203u unit and what hti app do too.

[ainu]

Can anyone show me the image output from the HTI HT-203U camera from a Windows computer, using the windows camera app?

I want to add support for it in the IRCAM software.

If it's not too late, than I want help you to add hti ht-203u camera to your IRCAM software. What exactly I must do?
In Windows Pot player can get video (and may be photo) from 203u unit.

[StevenNi]

Great work, spaceone. Thank you for provided information.
Can you compile libuvc (https://libuvc.github.io/libuvc/group__ctrl.html) and provide output of example (compiled example.c) in src folder?

My output of example is:

Code: [Select]

UVC initialized
Device found
Device opened
DEVICE CONFIGURATION (2bdf:0102/F10615613) ---
Status: idle
VideoControl:
	bcdUVC: 0x0110
VideoStreaming(1):
	bEndpointAddress: 129
	Formats:
	UncompressedFormat(1)
		  bits per pixel: 16
		  GUID: 5955593200001000800000aa00389b71 (YUY2)
		  default frame: 1
		  aspect ratio: 0x0
		  interlace flags: 00
		  copy protect: 00
			FrameDescriptor(1)
			  capabilities: 00
			  size: 256x392
			  bit rate: 40140800-40140800
			  max frame size: 200704
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(2)
			  capabilities: 00
			  size: 256x192
			  bit rate: 19660800-19660800
			  max frame size: 98304
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(3)
			  capabilities: 00
			  size: 256x196
			  bit rate: 20070400-20070400
			  max frame size: 100352
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(4)
			  capabilities: 00
			  size: 256x400
			  bit rate: 40249600-40249600
			  max frame size: 201248
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(5)
			  capabilities: 00
			  size: 256x196
			  bit rate: 19688000-19688000
			  max frame size: 98440
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(6)
			  capabilities: 00
			  size: 256x200
			  bit rate: 20193600-20193600
			  max frame size: 100968
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(7)
			  capabilities: 00
			  size: 192x520
			  bit rate: 39936000-39936000
			  max frame size: 199680
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(8)
			  capabilities: 00
			  size: 192x400
			  bit rate: 40664000-40664000
			  max frame size: 203320
			  default interval: 1/25
			  interval[0]: 1/25
	MJPEGFormat(2)
		  bits per pixel: 0
		  GUID: 4d4a5047000000000000000000000000 (MJPG)
		  default frame: 1
		  aspect ratio: 0x0
		  interlace flags: 00
		  copy protect: 00
			FrameDescriptor(1)
			  capabilities: 00
			  size: 120x160
			  bit rate: 7680000-7680000
			  max frame size: 38400
			  default interval: 1/25
			  interval[0]: 1/25
			FrameDescriptor(2)
			  capabilities: 00
			  size: 240x320
			  bit rate: 10240000-10240000
			  max frame size: 153600
			  default interval: 1/30
			  interval[0]: 1/30
			FrameDescriptor(3)
			  capabilities: 00
			  size: 640x360
			  bit rate: 10240000-10240000
			  max frame size: 460800
			  default interval: 1/30
			  interval[0]: 1/30
	FrameFormat(3)
		  bits per pixel: 16
		  GUID: 4832363400001000800000aa00389b71 (H264)
		  default frame: 1
		  aspect ratio: 0x0
		  interlace flags: 00
		  copy protect: 00
			FrameDescriptor(1)
			  capabilities: 00
			  size: 240x320
			  bit rate: 8192000-8192000
			  max frame size: 0
			  default interval: 1/30
			  interval[0]: 1/30
END DEVICE CONFIGURATION

First format: (YUY2) 256x392 25fps
bmHint: 0001
bFormatIndex: 1
bFrameIndex: 1
dwFrameInterval: 400000
wKeyFrameRate: 0
wPFrameRate: 0
wCompQuality: 0
wCompWindowSize: 0
wDelay: 0
dwMaxVideoFrameSize: 200704
dwMaxPayloadTransferSize: 12288
bInterfaceNumber: 1
get_mode: Invalid mode (-51)
Device closed
UVC exited
[

I have "broken" 203u too, but no sad - it work   with usb camera application enough to me. But I want to help other users and to learn how I can manage this unit.

Some strange that output of th.py in your camera is the same of my "broken".
Also output of ffmpeg, v4l2-ctl is the same (and serial number of device too).

I try to decompile apk file of ht105-203u and hikmicro viewer by apkedit and search for some initial codes, that it send to unit. But at this moment no luck to me.

You are correct that the camera functions as a USB camera. However, the issue is that I use thermal cameras outdoors due to the nature of my work, making it completely impractical to use as a USB camera on my computer. The camera needs to be mobile.

As you mentioned, the question is whether to contact Hikvision support or HTI. However, I believe neither of them is interested, as they are Chinese manufacturers without any technical support or warranty. I am considering reporting them to the consumer protection inspectorate because they sell their products in the EU without any warranty. However, this is also questionable since the EU will soon introduce sanctions on goods from China. It's a really awkward situation.

[BrokeEngineering]

How the actual camera FPS? Can you record a quick video ?

[Turbo_slug]

Not ideal, but there are apps on the playstore that allow you to view the video stream on your phone.

On a side note.  It appears the pallette color settings are toggled by the ht203u app but the setting is retained in the usb camera.  I have another fully working camera. When I change the palette color, the palette color is retained even when I use a generic uvc camera app to view the videos stream.  Unplugging/replugging the camera does not change the color either.  I believe the resolution setting is a parameter stored on the camera, and it got changed by the hikvision app. 

I'm guessing the sensor is a tiny1 inside the camera.  Has anyone tried using the sdk from iray to see what parameters can be edited? 

[StevenNi]

The only viable solution is for the team at HTI to provide the necessary firmware update. However, I am not optimistic about this happening, as they seem uninterested in addressing their customers' issues.

[Turbo_slug]

The only viable solution is for the team at HTI to provide the necessary firmware update. However, I am not optimistic about this happening, as they seem uninterested in addressing their customers' issues.

I dont think the firmware was actually changed.  The good ht203u has the same firmware version.  I believe it's a parameter setting that got changed

[BrokeEngineering]

Has anyone opened one of these up? Maybe the firmware can be easily dumped and someone with a working 1 can dump the firmware file and one with a broken 1 can try flashing the dump.

[spaceone]

How the actual camera FPS? Can you record a quick video ?

Attached video recorded with:
ffmpeg -input_format yuyv422 -video_size 256x392 -i /dev/video2 ht-203u.mkv     

[BrokeEngineering]

How the actual camera FPS? Can you record a quick video ?

Attached video recorded with:
ffmpeg -input_format yuyv422 -video_size 256x392 -i /dev/video2 ht-203u.mkv   

That is a lot better then I expected. Did you get the focus lens as well?

[spaceone]

However, when recording directly on the phone with the HTI android app, it records videos with 15 fps only.

I ordered macro lens seperately, there wasn't any with the camera, but I must still print the enclosure, so I cannot use it at the moment. If anyone knows where I could download the stl file, let me know.

[BrokeEngineering]

However, when recording directly on the phone with the HTI android app, it records videos with 15 fps only.

I ordered macro lens seperately, there wasn't any with the camera, but I must still print the enclosure, so I cannot use it at the moment. If anyone knows where I could download the stl file, let me know.

Which caera do you have? Give me lens dimensions and camera dimensions and I will make for you

[ainu]

Attached video recorded with:
ffmpeg -input_format yuyv422 -video_size 256x392 -i /dev/video2 ht-203u.mkv   

Can you execute command: "v4l2-ctrl -d /dev/video2 --list-controls" ?
At my 203u unit it returned nothing.
If I add --verbose it says than query execute is ok and nothing else.
Why I ask? For ht-301 exist way to change color palets by command "v4l2-ctl --set-ctrl zoom_absolute=" (offset is 0x8800 set in hti_helpers.hpp) see (https://framagit.org/ericb/miniDart/-/commit/deadd5a95f9fdc097fd6cb23658789ff939f96b2).

v4l2-ctl --set-ctrl zoom_absolute=0x8801 or 0x8000 (calibrate) give me error that control  zoom_absolute unknown.

I want to find working way to change color pallet on 203u. On "broken" unit changes color pallet saves exactly the same as Turbo_slug described above.
Next step will be to find offset and value to change default resolution.

I was try libuvc uvc_set_zoom_abs with 0x8801  and 0x8000 value and nothing is changed.

[spaceone]

Can you execute command: "v4l2-ctrl -d /dev/video2 --list-controls" ?
At my 203u unit it returned nothing.

Correct command on my side is:
v4l2-ctl -d /dev/video2 --list-ctrls  --verbose

However I also don't get anything, only VIDIOC_QUERYCAP: ok.

With v4l2-ctl -d /dev/video2 --all, i get also this (excluding Driver info which I already posted before):

Code: [Select]

Video input : 0 (Camera 2: ok)
Format Video Capture:
        Width/Height      : 256/392
        Pixel Format      : 'YUYV' (YUYV 4:2:2)
        Field             : None
        Bytes per Line    : 512
        Size Image        : 200704
        Colorspace        : sRGB
        Transfer Function : Default (maps to sRGB)
        YCbCr/HSV Encoding: Default (maps to ITU-R 601)
        Quantization      : Default (maps to Limited Range)
        Flags             : 
Crop Capability Video Capture:
        Bounds      : Left 0, Top 0, Width 256, Height 392
        Default     : Left 0, Top 0, Width 256, Height 392
        Pixel Aspect: 1/1
Selection Video Capture: crop_default, Left 0, Top 0, Width 256, Height 392, Flags: 
Selection Video Capture: crop_bounds, Left 0, Top 0, Width 256, Height 392, Flags: 
Streaming Parameters Video Capture:
        Capabilities     : timeperframe
        Frames per second: 25.000 (25/1)
        Read buffers     : 0

Perhaps you'll find it helpful.

I can also capture the video using qv4l2, but besides the resolution, I cannot change anything else in there. Menus (tabs) for User and Camera controls are completely missing.

[Turbo_slug]

Anyone know what microbolometer sensor is inside?  It doesn't look like a tiny1b or tiny1c.

[StevenNi]

Anyone know what microbolometer sensor is inside?  It doesn't look like a tiny1b or tiny1c.

It appears that the HTI HT-203U is essentially a clone of the HIKMICRO Mini2 V2. That's why it's baffling to me that it doesn't function with their app, or any other app for that matter (and trust me, I've tried them all).

Regardless, I'm sending mine back to the seller.

[Turbo_slug]

Anyone know what microbolometer sensor is inside?  It doesn't look like a tiny1b or tiny1c.

It appears that the HTI HT-203U is essentially a clone of the HIKMICRO Mini2 V2. That's why it's baffling to me that it doesn't function with their app, or any other app for that matter (and trust me, I've tried them all).

Regardless, I'm sending mine back to the seller.

Have you tried an older version of the hikmicroviewer?

[StevenNi]

Anyone know what microbolometer sensor is inside?  It doesn't look like a tiny1b or tiny1c.

It appears that the HTI HT-203U is essentially a clone of the HIKMICRO Mini2 V2. That's why it's baffling to me that it doesn't function with their app, or any other app for that matter (and trust me, I've tried them all).

Regardless, I'm sending mine back to the seller.

Have you tried an older version of the hikmicroviewer?

I've tried every app, including their older versions.

[Fraser]

Turbo Slug,

The two most likely identities for the core in these budget 256x192 pixel cameras are the Infiray Tiny1 and Guide Sensmart TIMO256. The picture you posted suggests a TIMO256 but it is hard to be certain unless I see the front of the core.

Fraser

[StevenNi]

Turbo Slug,

The two most likely identities for the core in these budget 256x192 pixel cameras are the Infiray Tiny1 and Guide Sensmart TIMO256. The picture you posted suggests a TIMO256 but it is hard to be certain unless I see the front of the core.

Fraser

Most budget cameras utilize the Infiray Tiny1, which is why I am surprised that the HT-203U is incompatible with applications from other manufacturers, even if they also use the Infiray Tiny1. I believe the issue lies within the firmware, and for that the use of the Infiray Tiny1 across different devices should be a problem. In my experience, I have used cameras at work that were compatible with applications from various manufacturers while using the same camera module, so this situation is quite perplexing to me.

[Turbo_slug]

Turbo Slug,

The two most likely identities for the core in these budget 256x192 pixel cameras are the Infiray Tiny1 and Guide Sensmart TIMO256. The picture you posted suggests a TIMO256 but it is hard to be certain unless I see the front of the core.

Fraser

I agree.  It definitely doesn't look like a Tiny1b or Tiny1c.  It does resemble a Timo256, but there aren't too many photos of the Timo256 on the internet to compare to.  Note the black plastic that the core is mounted to, has "256" stamped " on it, so I have a feeling it's referring to the Timo256.

EDIT: I pulled it apart just now and took a better look at the core.  I'm pretty confident to say it is a Timo256.  The dimensions are 13x15mm and it matches the photos on GSTIR's website.

[StevenNi]

Turbo Slug,

The two most likely identities for the core in these budget 256x192 pixel cameras are the Infiray Tiny1 and Guide Sensmart TIMO256. The picture you posted suggests a TIMO256 but it is hard to be certain unless I see the front of the core.

Fraser

I agree.  It definitely doesn't look like a Tiny1b or Tiny1c.  It does resemble a Timo256, but there aren't too many photos of the Timo256 on the internet to compare to.  Note the black plastic that the core is mounted to, has "256" stamped " on it, so I have a feeling it's referring to the Timo256.

EDIT: I pulled it apart just now and took a better look at the core.  I'm pretty confident to say it is a Timo256.  The dimensions are 13x15mm and it matches the photos on GSTIR's website.

I've never heard of Timo256, so it's no surprise that it doesn't work with other app. I'm now certain that there is no fix for this issue.