Author Topic: Yet another cheap thermal imager incoming.. Seek Thermal  (Read 728033 times)

0 Members and 3 Guests are viewing this topic.

Offline LesioQ

  • Contributor
  • Posts: 47
  • Country: pl
  • Every king should be naked.
Re: Yet another cheap thermal imager incoming.. Seek Thermal
« Reply #2375 on: January 02, 2018, 08:15:49 pm »

How can I induce firmware reload to Seek Thermal XR camera flash IC ?
I mean version, built-in into apk.
Either Android way or Windows-way.


Offline methael

  • Newbie
  • Posts: 3
  • Country: ca
  • Physics student at york university
Re: Yet another cheap thermal imager incoming.. Seek Thermal
« Reply #2376 on: August 24, 2018, 07:23:15 am »
Hello everyone,

I have looked at the code for seek thermal compact, and everyone seemed to have written their code interfacing the iAP interface. I am wondering why this interface and not the other that is available?

If you look at the lsusb that was posted here(in the link below) it says that theres another interface available. (the interface is called com.thermal.pir206)

I am wondering this because i had to write c++ code to communicate with this camera and i also used winusb to do it. I decided to use iAP interface cause everyone else used it. I want to be able to run 2 seek thermal cameras in parallel.  I have done that using multi-threading however i realized that there seems to be some sort of race condition. When using winusb_readpipe function with two seek thermal cameras, the function sends the data to a unique winusb_interface_handle however the PipeID remains the same. So i think that two threads might be racing for this function. So i was thinking to communicate with the second camera run on the other interface because it has another pipeID. However when i do winusb_controltransfer/winusb_writepipe/winusb_readpipe using the second interface i will get windows errors like "Invalid access to memory location",A device attached to the system is not functioning" and "The parameter is incorrect". I am confused as to why?

Any help is appreciated thank you!

I found this link on endpoints and pipes.
It makes me think that my conclusion on the problem is correct. As there are 2 devices hence 2 endpoints but only 1 pipe. So my 2 threaded readpipe functions are just racing for the pipe.
« Last Edit: August 25, 2018, 12:30:01 am by methael »

Offline IwuzBornanerd

  • Regular Contributor
  • *
  • Posts: 179
  • Country: us
Re: Yet another cheap thermal imager incoming.. Seek Thermal
« Reply #2377 on: August 25, 2018, 05:28:38 pm »
I'm not clear from your post whether you are actually getting data from both cameras.  Are you getting images from both cameras but erratically?  What do you observe that makes you think there is a race.  One pipe for two distinct devices seems crazy and makes me wonder if you got 2 handles to the same device (which does not make sense to me either but might be more likely than the one pipe for 2 devices).

I have run 3 Seeks simultaneously using 3 separate instances of my C/C++ code and did not notice any problems, but that is using libusb under Debian Linux and I have not tried running multiple cameras in separate threads of one program.  i also don't process many errors...
I am not opposed to exercise, unless it is an exercise in futility.

Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo