There are FLIR consumer devices with 320x240 sensors, like the E8, but they're a lot pricier, and low-FPS due to ITAR. Consumers in the US can buy 60FPS FLIR monoculars as well, but they come with ITAR restrictions.
The T2S+ seems to be 256x192, 25FPS. Still a bargain, if you ask me, even if it's not as sharp.
No, it cannot. India and Mexico are where the factories will likely migrate to in the post-Chinese manufacturing world. Brazil probably wasn't even considered.
It's kind of funny how Brazil always ends up named as part of the "BRIC" group. India put a spacecraft on the moon. Russia is, well, Russia. China is unquestionably a world power. Brazil is... The world's soy and cattle farm.
As a Linux systems engineer I’ve looked behind the curtain at HAOS and was very impressed by how well things are implemented. Been running it for years in KVM and have never had an issue.
Used my Infriray while house hunting. Possibly saved me big time €. Great also for spotting leaks any water in/on surfaces shows up quite clearly. In the same vein I use it to spot pet accidents.
The infriray is the Chinese knockoff brand which is actually better than flir because they don’t have to follow the US weapons law. So with it I get 30(?) fps instead of the ~5 with flir. Resolution is better too. It’s very sensitive and can clearly show a hand print on a surface for a minute or so even if you only touch it for 1/2 a second.
I saved money by not buying a badly insulated house. There were some walls that shocked me in how little they were insulated. Also found a roof leak in another house
How do you generally know when the long test is over? Is there a way to get a notification of completion? Is it ok to begin using the drives while testing? I personally run my new drives through a few rounds of badblocks
(--device=sat is for the normal SATA or USB devices of Linux, such as "/dev/sda", which use SCSI commands; --device=nvme would be for NVME SSDs; other cases are described in the man page)
Then you can read from time to time the test log:
smartctl --log=xselftest --device=sat /dev/***
When the test has finished, a line announcing that will appear in the log, saying that the test has passed or failed. If there are errors, they will appear in the log while the test progresses.
In theory you can make a script that runs periodically smartctl, e.g. once every 5 minutes, and which parses the smartctl output and signals the end of a test.
However, because I run such tests only seldom, when buying a new disk, I did not write such a script.
You can use the HDD during the test, unless the test had been started with:
That just displays in a nicer form the same logs that can be read with smartctl.
The progress displayed is somewhat illusory, because the estimated time until finish that is provided by the HDDs is unreliable. It is frequently wrong for the long test by even 20% to 50%, which means a difference of several hours.
