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

[JXstaystonight]

I happened to come across “tiny2” during my research—it sounds like it’s an upgraded version. Hopefully, it’s useful to you!

https://www.raytron-microelectronics.com/long-wave-infrared-camera-modules/infrared-thermal-imaging-module-tiny2-c-series

[Turbo_slug]

Anyone know how the firmware of the ht203u can be restored?  I plugged mine into my android device which happened to also have the hikvision thermal app.  I somehow accidentally opened the app and it automatically updated my ht203u.  Now the device shows up as a hikthermal device and the  thermal image is distorted every time I use the ht203u app. 

Alternatively, anyone know how the USB PID, VID etc can be edited.  I'm guessing the tiny1 SDK might let me edit the parameters?

[ainu]

Do your ht-203u working in hikvsision application after "upgrade"? It was hikmicro viewer application?

What Vid and Pid you can get now from your device?

[Turbo_slug]

Vid is now 11231
Pid is now 258

Device shows up as Hikcamera when I plugged it in.

Yes, it was the Hikmicro Viewer app.

I'm able to see a thermal image using a generic USB OVC program but the HTI ht230u app won't display the image properly anymore.

[ainu]

My Identifier of the device is VID_2BDF PID_0102 REV_0409 MI_00

I dont think that vid and pid is reason of broken picture. May be hikmicro viewer send to 203u some initialization string or something, that make wrong soft state 203u "permanent".

[Turbo_slug]

My Identifier of the device is VID_2BDF PID_0102 REV_0409 MI_00

I dont think that vid and pid is reason of broken picture. May be hikmicro viewer send to 203u some initialization string or something, that make wrong soft state 203u "permanent".

Not sure.  I was able to use generic usb uvc software to pull the video stream from the camera and it displayed fine.

Is there anyway to restore the parameters that may have been changed?  It appears the camera still works fine.

So I played around with the generic uvc camera app some more.  It appears the camera has a number of resolutions or video streams that can be selected.  The ones i found of interest are 256x192 = grey video image, 256x196 = green video image, and another 256x196 = green video image that resembled the one i was now getting in the HT203u app.  It appears the ht203u app is using the wrong resolution/video setting.

[ainu]

What generic uvc application do you use to obtain "normal" image (and images that you described 196x...) and with which settings?

I dont know how to restore normal picture view in 203u smart camera app, but intresting what other software can achieve.

[Turbo_slug]

What generic uvc application do you use to obtain "normal" image (and images that you described 196x...) and with which settings?

I dont know how to restore normal picture view in 203u smart camera app, but intresting what other software can achieve.

There's a few different ones out there.  UVC_Camera on android is one.  nExt Camera is another.

[sydd]

I'm still curious whether it's possible to use any other app with this device..or if the official app can be configured to display a fixed color spectrum, e.g. that a certain pixel color always represents the same temperature no matter where I look.

Now the camera is barely usable outdoors because when the sky is visible it will clamp to the smallest value possible, when it's not it will constantly change the range it displays

[BrokeEngineering]

I just ordered a HT-203H.

It was a better deal then the U, Curious if anyone has tried this 1?

I Bought the focus lens (50.8mm, 18mm) but looks like the camera is a bit recessed?

I wonder if it will fit? How crucial is the spacing of focus lens to the camera lens?

[StevenNi]

I made the same mistake, I had the hikvision thermal app installed on my phone, so I can no longer use the native app.
Did you manage to solve the problem because HTI support says it's not their problem because we made the mistake ourselves.

[ainu]

Can anybody run python script on Linux (with installed opencv) with HT-203U attached?
The script just query available opencv properties on camera and print it values on terminal.
Please post this values in reply.

If YES, than you may need to change string "cap = cv2.VideoCapture('/dev/video2')" to select device name in your Linux system.

I think that can be helpful to user Turbo_slug to restore his partially broken camera.

[StevenNi]

Can anybody run python script on Linux (with installed opencv) with HT-203U attached?
The script just query available opencv properties on camera and print it values on terminal.
Please post this values in reply.

If YES, than you may need to change string "cap = cv2.VideoCapture('/dev/video2')" to select device name in your Linux system.

I think that can be helpful to user Turbo_slug to restore his partially broken camera.

I don't use Linux, but I hope Turbo_slug will respond.

My biggest issue is that the people from HTI are completely unprofessional. They simply don't know how to communicate with users and just try to rip you off because they don't care about your problem, which is actually their problem. Unfortunately, this seems typical of many Chinese manufacturers and sellers. They should have clearly stated that their thermal camera cannot be used on a phone where other thermal cameras and applications are already in use. Instead of providing a solution, they have just created more problems for us.

[ainu]

Need values from camera that normal working in hti app. When compare its from "broken" camera we can understrand "What happens?".

[BrokeEngineering]

Need values from camera that normal working in hti app. When compare its from "broken" camera we can understrand "What happens?".

I dont have any thermal camera apps instaled on my phone, when camera comes I will install the HTI app and post

[ainu]

To BrokeEngineering and StevenNi :
If you use Windows and want to help community, then you can also run th.py with edit /dev/video2 to number '0' or '1' or next (I think no more than 15) until you get information.

[StevenNi]

To BrokeEngineering and StevenNi :
If you use Windows and want to help community, then you can also run th.py with edit /dev/video2 to number '0' or '1' or next (I think no more than 15) until you get information.

I have the same problem as Turbo_slug.
If I understood you correctly, the value data should be sent to you by people whose camera is working properly.

If it means anything to you, Hikmicro Viewer installed hm-tm32-3rg/t firmware on ht203u, so as far as I can tell, Hikmicro Viewer not only changed some parameters but also installed another firmware on the HT203U.

[ainu]

Nobody know what exactly it do. I think hikmicro viewer change default rezolution settings in 203u.
Usb camera app give list of available rezolutions, but wich hti app need - what is the question. May be it 256x192 grayscale or may be 256x384 gray and green scale frames.

On you hti app image looks like interlaced (line full then line empty then another line full etc)?
View on usb camera app rezolution 256x400. Is you image on hti app like this?

[StevenNi]

Nobody know what exactly it do. I think hikmicro viewer change default rezolution settings in 203u.
Usb camera app give list of available rezolutions, but wich hti app need - what is the question. May be it 256x192 grayscale or may be 256x384 gray and green scale frames.

On you hti app image looks like interlaced (line full then line empty then another line full etc)?
View on usb camera app rezolution 256x400. Is you image on hti app like this?

Who knows, but something has definitely changed and the hti app is messing up the image.

[Turbo_slug]

I haven't fixed mine.  Try searching this forum for the tiny1c sdk and see whether it has any tools for fixing this.

I believe the ht203u app is no longer working because it's using the wrong resolution setting.  I'm able to see the various resolution settings using other uvc camera apps, and I can still get a working video stream if the correct one is selected.

[StevenNi]

I haven't fixed mine.  Try searching this forum for the tiny1c sdk and see whether it has any tools for fixing this.

I believe the ht203u app is no longer working because it's using the wrong resolution setting.  I'm able to see the various resolution settings using other uvc camera apps, and I can still get a working video stream if the correct one is selected.

We will try to find a solution. We are waiting for someone whose camera works so we can compare the settings.

For me, the biggest problem is that the people from HTI are completely uninterested. They simply do not respond, which is highly irresponsible behavior. This issue is their fault, it is because they did not state that other app and cameras cannot be used on the same phone as theirs. This is definitely the first and last time I will buy something from them. I own cameras from two other manufacturers, and whenever I had a problem, they were always responsive and helpful.

Therefore, my recommendation to everyone is to avoid HTI. You cannot expect any technical support from them. Instead, avoid these Chinese brand and buy from proven world brands that offer support, as that is the most important thing when you encounter a problem.

[spaceone]

I haven't fixed mine.  Try searching this forum for the tiny1c sdk and see whether it has any tools for fixing this.

I believe the ht203u app is no longer working because it's using the wrong resolution setting.  I'm able to see the various resolution settings using other uvc camera apps, and I can still get a working video stream if the correct one is selected.

We will try to find a solution. We are waiting for someone whose camera works so we can compare the settings.

I have a brand new HT-203U, working with android app https://play.google.com/store/apps/details?id=com.hti.xtherm.hti160203u&hl=en-US&pli=1.
To be queried with the python script posted earlier, I had to use quirks option for module uvcvideo:

Code: [Select]

modprobe uvcvideo quirks=2    Courtesy to https://www.eevblog.com/forum/thermal-imaging/hti-ht-203u-thermal-imager-raspberry-pi-os/msg5670365/#msg5670365 and http://www.ideasonboard.org/uvc/faq/#faq6
Otherwise no parameters are returned.

lsusb info:

Code: [Select]

Bus 003 Device 004: ID 2bdf:0102 HIK HikCamera
v4l2-ctl --list-devices 

Code: [Select]

HikCamera: UVC Camera (usb-0000:00:14.0-3):
        /dev/video2
        /dev/video3
        /dev/media1


Device Details:

Code: [Select]

v4l2-ctl -d2 -D
Driver Info:
        Driver name      : uvcvideo
        Card type        : HikCamera: UVC Camera
        Bus info         : usb-0000:00:14.0-3
        Driver version   : 6.6.65
        Capabilities     : 0x84a00001
                Video Capture
                Metadata Capture
                Streaming
                Extended Pix Format
                Device Capabilities
        Device Caps      : 0x04200001
                Video Capture
                Streaming
                Extended Pix Format
Media Driver Info:
        Driver name      : uvcvideo
        Model            : HikCamera: UVC Camera
        Serial           : F10615613
        Bus info         : usb-0000:00:14.0-3
        Media version    : 6.6.65
        Hardware revision: 0x00000409 (1033)
        Driver version   : 6.6.65
Interface Info:
        ID               : 0x03000002
        Type             : V4L Video
Entity Info:
        ID               : 0x00000001 (1)
        Name             : HikCamera: UVC Camera
        Function         : V4L2 I/O
        Flags            : default
        Pad 0x01000007   : 0: Sink
          Link 0x0200000d: from remote pad 0x1000009 of entity 'Camera 2' (Camera Sensor): Data, Enabled, Immutable

Extract from python script:

Code: [Select]

[ WARN:0@0.308] global cap_gstreamer.cpp:2839 handleMessage OpenCV | GStreamer warning: Embedded video playback halted; module source reported: Could not read from resource.
[ WARN:0@0.309] global cap_gstreamer.cpp:1698 open OpenCV | GStreamer warning: unable to start pipeline
[ WARN:0@0.309] global cap_gstreamer.cpp:1173 isPipelinePlaying OpenCV | GStreamer warning: GStreamer: pipeline have not been created
CAP_PROP_FRAME_HEIGHT=400.0
CAP_PROP_FRAME_WIDTH=256.0
CAP_PROP_CONVERT_RGB=1.0
CAP_PROP_FORMAT=16.0
CAP_PROP_ZOOM=-1.0
CAP_PROP_FPS=25.0
CAP_PROP_FOURCC=1448695129.0
CAP_PROP_FORMAT=16.0
CAP_PROP_MODE=0.0
CAP_PROP_GAIN=-1.0
CAP_PROP_EXPOSURE=-1.0
CAP_PROP_CONVERT_RGB=1.0
CAP_PROP_RECTIFICATION=-1.0
CAP_PROP_MONOCHROME=-1.0
CAP_PROP_SHARPNESS=-1.0
CAP_PROP_AUTO_EXPOSURE=-1.0
CAP_PROP_GAMMA=-1.0
CAP_PROP_TEMPERATURE=-1.0
CAP_PROP_TRIGGER=-1.0
CAP_PROP_TRIGGER_DELAY=-1.0
CAP_PROP_FOCUS=-1.0
CAP_PROP_GUID=-1.0
CAP_PROP_ISO_SPEED=-1.0
CAP_PROP_BACKLIGHT=-1.0
CAP_PROP_PAN=-1.0
CAP_PROP_IRIS=-1.0
CAP_PROP_SETTINGS=-1.0
CAP_PROP_BUFFERSIZE=4.0
CAP_PROP_BACKEND=200.0
CAP_PROP_CHANNEL=-1.0
---End


Some additional info from ffmpeg:
ffmpeg -f v4l2 -list_formats all -i /dev/video2   

Code: [Select]

[video4linux2,v4l2 @ 0x55c438515b00] Raw       :     yuyv422 :           YUYV 4:2:2 : 256x392 256x192 256x196 256x400 256x196 256x200 192x520 192x400
[video4linux2,v4l2 @ 0x55c438515b00] Compressed:       mjpeg :          Motion-JPEG : 120x160 240x320 640x360
[video4linux2,v4l2 @ 0x55c438515b00] Compressed:        h264 :                H.264 : 240x320

I'm able to get video output with some resolutions, for example:
ffplay -input_format yuyv422 -video_size 256x192 -i /dev/video2   

[ainu]

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.

[spaceone]

Because I have also a build-in laptop camera, I had to change the example.c to search by the vendor id, to be able to select the right camera.
Here are the results, but it seems they are also the same as yours:

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


[spaceone]

DId you guys already find this downloads from HTI ?
http://m.hti-meter.com/en/h-col-103.html

Perhaps there are some helpful tools in there.