-
-
Wonder if it's possible to drop a Lepton 3 to replace the Lepton 2 on the F1 Rosebud sled. I'd be curious to see if there's a software resolution restriction in place or if 160x120 would actually work out. Call me crazy but I really like the sled since it's an integrated device allowing me to carry one unit as opposed to a dongle. I only see the 80x60's on Digikey...
-
#351 Reply
Posted by
cynfab
on 08 Sep, 2015 21:01
-
Mine just arrived!!
In the sealed box:
Quick start & warranty card
Thank You card from Bill Terrel
microUSB cable
Spacer
Case
Lanyard
Box has a "Made for iPod" sticker inside ( I guess they ran out of Android boxes)
As expected the app doesn't recognise the camera when plugged in and turned on on my S4 mini.
It does however work ok on my Digiland $49US tablet. Updated the firmware and everything.
Frame rate on the preview is slow, but usable, will take a video & some snapshots soon...
Plugging it into my linux box lsusb -vv gives the following
Bus 002 Device 007: ID 09cb:1996
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x09cb
idProduct 0x1996
bcdDevice 1.08
iManufacturer 1 FLIR Systems
iProduct 2 FLIR ONE Camera
iSerial 3 FLIRONEF0xxxxxxxxx
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 96
bNumInterfaces 3
bConfigurationValue 3
iConfiguration 4 SBIBDP Configuration
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 0
iInterface 5 iAP Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 6 com.flir.rosebud.fileio
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 6 com.flir.rosebud.fileio
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 7 com.flir.rosebud.frame
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 7 com.flir.rosebud.frame
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
It works about the same with my 2012 Nexus 7.
...ken...
-
#352 Reply
Posted by
marshallh
on 08 Sep, 2015 23:27
-
Received, it's a letdown.
Image quality is comparable to the last one (i.e. blurfest). Can't turn off MSX, though the MSX is decent quality and adjustable. If you try to charge with anything besides a 1A charger, it actually slowly dies, presumably because the cpu running linux inside it draws more power than it can charge with.
Charged with my smartphone cable for an hour, now it will not boot under its own power.
Because of this it is not possible to upgrade the firmware.
At this point it seems the Seek is more useful and doesn't require a stupid charging system just to run its own linux-based glue logic.
-
#353 Reply
Posted by
in.Vitro
on 09 Sep, 2015 00:28
-
Is the Image quality that bad?
As you say, the first gen was very very blurry.. :/ but they said that it has 4 times the resolution of the first generation
maybe I wait a few years when the F1 has the same resolution as the Seek but its less nosier and has manual adjustible focus....for 250$
-
#354 Reply
Posted by
marshallh
on 09 Sep, 2015 00:45
-
FLIR ONE V2 DISASSEMBLY
Use a plastic spudger to remove the halves, which are conjoined by 4 smalll pads of adhesive.
Lift up the battery connector to unplug it.
Combo LPDDR/NAND is the bga device with the serial QR code on it.
Unscrew 3 outer security torxes and lift the pcb directly straight out.
USB/Lightning pcb is a 4pin connector that plugs into a smd header.
Unclip 2 of the translucent white assembly from the pcb.
Lift vertically to remove assy and lepton from socket.
-
#355 Reply
Posted by
Fraser
on 09 Sep, 2015 01:31
-
I do not like the look of that screen connection mess on top of the USB plug !
I am starting to think FLIR could be playing games over the true resolution of the LEPTON 3. Having re visited all the FLIR blurb I get the definite feeling that they did not want to specify the physical pixel count. There is even comment in one pre release document saying that picture appearance is more important than resolution ! This almost appeared to say that the new LEPTON had better image manipulation 'magic'. I wonder if we are back to our old friend of cheap low resolution imaging chips. Namely interpolation.
I would comment further if I had a working unit but as mine was DoA I will have to wait to see the images on my phone.
I will do a side by side comparison of the ONE with two other 160*120 pixel cameras. If FLIR are not being totally honest about the 160*120 physical resolution I think we will spot it.
If this is smoke and mirrors marketing crap, my camera will be heading back to FLIR pronto. I still have the email confirming physical resolution as 160*120 from FLIR CS.
I should have stuck with professional thermal cameras. At least they have real specs and you can trust them !
Aurora
-
-
I find the following fairly unique -- The use of "Rosebud" (Citizen Kane, "Sled") used to describe the FLIR G2 in the kernel boot log (thanks Mike for posting) is quite interesting. At frame 0:42 to 0:43 shows the same kernel load addresses, kernel version, load addresses, etc. JFFS2 kernel image sizes differ (firmware differences?). Also appears G2 no longer has dropbear SSHd running on init/boot (firmware differences?)
(
Interesting output around G1 and G2 with regard to inserting lepton.ko kernel module, would love to compare differences between the two. Equally interesting is G1 running an SSHd without an ethernet interface. Odd the G2 is reporting SPI and other verbose output not seen in G1. Again, suspect possible firmware differences?
Would love to have 'root' on the G1/G2 and start comparing the kernel modules, modinfo, etc. Very interested to hear about interpolation findings. Thanks all for the thread, very much appreciate the constant learning I have while reading these threads. All the best.
-
-
-
#358 Reply
Posted by
marshallh
on 09 Sep, 2015 04:32
-
After putting it back together, it charges properly, and charge LED does not blink erratically. It seems the battery connector may have loosened to marginal contact during shipping.
-
#359 Reply
Posted by
Fraser
on 09 Sep, 2015 04:49
-
I wonder if that is what is wrong with mine. I get no life out of it at all. No LED, nothing.
It's going back to FLIR though so I am loathed to mess with it. A possible weak area in the design ?
At least if we see strange behaviour when charging it will be reasonably easy to open the unit to check that connector.
Aurora
-
#360 Reply
Posted by
Fraser
on 09 Sep, 2015 05:02
-
Maybe my X-Ray machine can see if the power connector is correctly mated in my unit. The problem will be seeing through or around the Battery. I'll take a look later.
Aurora
-
-
I am starting to think FLIR could be playing games over the true resolution of the LEPTON 3. Having re visited all the FLIR blurb I get the definite feeling that they did not want to specify the physical pixel count
I would comment further if I had a working unit but as mine was DoA
..well if they don't want the old one back I'd be happy to take a look inside to confirm the physical pixel count
-
-
Is the Image quality that bad?
Although I couldn't compare side to side I'd say it was better than the Seek, definitely less noise.
MSX is a big help to improve readability of image - there will be some filtering to scale up the IR image to the phone's screen resolution.
-
#363 Reply
Posted by
tomas123
on 09 Sep, 2015 08:15
-
BTW just for fun I used the UsbWebCamera App to connect my E4 ub UVC mode to the phone and it works just fine - framerate and lag are not much worse than on the E4's own screen!
Certainly do you know the thread "Flir Ex: Realtime raw radiometric data streaming via UVC
It's simple, to patch the libuvc library for android to get a E4 RAW stream
Unfortunately the
Flir One G2 is not a UVC camera
Plugging it into my linux box lsusb -vv gives the following
Bus 002 Device 007: ID 09cb:1996
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x09cb
idProduct 0x1996
bcdDevice 1.08
iManufacturer 1 FLIR Systems
iProduct 2 FLIR ONE Camera
iSerial 3 FLIRONEF0xxxxxxxxx
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 96
bNumInterfaces 3
bConfigurationValue 3
iConfiguration 4 SBIBDP Configuration
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 0
iInterface 5 iAP Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 6 com.flir.rosebud.fileio
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 6 com.flir.rosebud.fileio
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 1
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 7 com.flir.rosebud.frame
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 7 com.flir.rosebud.frame
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
filtered
>grep -i interface FlirOne.txt
bDeviceClass 0 (Defined at Interface level)
bNumInterfaces 3
Interface Descriptor:
bInterfaceNumber 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 0
iInterface 5 iAP Interface
Interface Descriptor:
bInterfaceNumber 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 6 com.flir.rosebud.fileio
Interface Descriptor:
bInterfaceNumber 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 6 com.flir.rosebud.fileio
Interface Descriptor:
bInterfaceNumber 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 7 com.flir.rosebud.frame
Interface Descriptor:
bInterfaceNumber 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 7 com.flir.rosebud.frame
bDeviceClass 0 (Defined at Interface level)
the
seek camera has also a
iAP InterfaceThe libseek library is using the first interface iAP Interface
https://github.com/zougloub/libseek
>grep -i interface seek.txt
bDeviceClass 0 (Defined at Interface level)
bNumInterfaces 2
Interface Descriptor:
bInterfaceNumber 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 0
iInterface 3 iAP Interface
Interface Descriptor:
bInterfaceNumber 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 4 com.thermal.pir206.1
Interface Descriptor:
bInterfaceNumber 1
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 240
bInterfaceProtocol 1
iInterface 4 com.thermal.pir206.1
bDeviceClass 0 (Defined at Interface level)
compare with
E4 UVC camera
check Flir E4 USB announcements
$ lsusb -v
Bus 001 Device 006: ID 09cb:1007
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x09cb
idProduct 0x1007
bcdDevice 0.00
iManufacturer 7 FLIR Systems
iProduct 8 FLIR Ex-Series
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 241
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 14 Video
bFunctionSubClass 3 Video Interface Collection
bFunctionProtocol 0
iFunction 10 FLIR USB Video
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 14 Video
bInterfaceSubClass 1 Video Control
bInterfaceProtocol 0
iInterface 2 FLIR Ex-Series
VideoControl Interface Descriptor:
bLength 13
bDescriptorType 36
bDescriptorSubtype 1 (HEADER)
bcdUVC 1.00
wTotalLength 85
dwClockFrequency 0.001000MHz
bInCollection 1
baInterfaceNr( 0) 1
VideoControl Interface Descriptor:
bLength 18
bDescriptorType 36
bDescriptorSubtype 2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType 0x0201 Camera Sensor
bAssocTerminal 0
iTerminal 0
wObjectiveFocalLengthMin 0
wObjectiveFocalLengthMax 0
wOcularFocalLength 0
bControlSize 3
bmControls 0x00020260
Focus (Absolute)
Focus (Relative)
Zoom (Absolute)
Focus, Auto
VideoControl Interface Descriptor:
bLength 9
bDescriptorType 36
bDescriptorSubtype 3 (OUTPUT_TERMINAL)
bTerminalID 3
wTerminalType 0x0101 USB Streaming
bAssocTerminal 0
bSourceID 6
iTerminal 0
VideoControl Interface Descriptor:
bLength 7
bDescriptorType 36
bDescriptorSubtype 4 (SELECTOR_UNIT)
bUnitID 4
bNrInPins 1
baSource( 0) 1
iSelector 0
VideoControl Interface Descriptor:
bLength 11
bDescriptorType 36
bDescriptorSubtype 5 (PROCESSING_UNIT)
Warning: Descriptor too short
bUnitID 5
bSourceID 4
wMaxMultiplier 0
bControlSize 2
bmControls 0x00000217
Brightness
Contrast
Hue
Sharpness
Gain
iProcessing 0
bmVideoStandards 0x1b
None
NTSC - 525/60
SECAM - 625/50
NTSC - 625/50
VideoControl Interface Descriptor:
bLength 27
bDescriptorType 36
bDescriptorSubtype 6 (EXTENSION_UNIT)
bUnitID 6
guidExtensionCode {d41f59fa-5094-463a-b3bb-e7858a831fa3}
bNumControl 4
bNrPins 1
baSourceID( 0) 5
bControlSize 2
bmControls( 0) 0x0f
bmControls( 1) 0x00
iExtension 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 16
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 14 Video
bInterfaceSubClass 2 Video Streaming
bInterfaceProtocol 0
iInterface 0
VideoStreaming Interface Descriptor:
bLength 14
bDescriptorType 36
bDescriptorSubtype 1 (INPUT_HEADER)
bNumFormats 1
wTotalLength 79
bEndPointAddress 130
bmInfo 0
bTerminalLink 3
bStillCaptureMethod 0
bTriggerSupport 0
bTriggerUsage 0
bControlSize 1
bmaControls( 0) 27
VideoStreaming Interface Descriptor:
bLength 27
bDescriptorType 36
bDescriptorSubtype 4 (FORMAT_UNCOMPRESSED)
bFormatIndex 1
bNumFrameDescriptors 1
guidFormat {59555932-0000-1000-8000-00aa00389b71}
bBitsPerPixel 16
bDefaultFrameIndex 1
bAspectRatioX 0
bAspectRatioY 0
bmInterlaceFlags 0x00
Interlaced stream or variable: No
Fields per frame: 2 fields
Field 1 first: No
Field pattern: Field 1 only
bCopyProtect 0
VideoStreaming Interface Descriptor:
bLength 38
bDescriptorType 36
bDescriptorSubtype 5 (FRAME_UNCOMPRESSED)
bFrameIndex 1
bmCapabilities 0x03
Still image supported
Fixed frame-rate
wWidth 320
wHeight 240
dwMinBitRate 912384
dwMaxBitRate 912384
dwMaxVideoFrameBufferSize 153600
dwDefaultFrameInterval 2666664
bFrameIntervalType 3
dwFrameInterval( 0) 666666
dwFrameInterval( 1) 1333332
dwFrameInterval( 2) 2666664
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
>grep -i interface E4.txt
bDeviceProtocol 1 Interface Association
bNumInterfaces 3
Interface Association:
bFirstInterface 0
bInterfaceCount 2
bFunctionSubClass 3 Video Interface Collection
Interface Descriptor:
bInterfaceNumber 0
bInterfaceClass 14 Video
bInterfaceSubClass 1 Video Control
bInterfaceProtocol 0
iInterface 2 FLIR Ex-Series
VideoControl Interface Descriptor:
baInterfaceNr( 0) 1
VideoControl Interface Descriptor:
VideoControl Interface Descriptor:
VideoControl Interface Descriptor:
VideoControl Interface Descriptor:
VideoControl Interface Descriptor:
Interface Descriptor:
bInterfaceNumber 1
bInterfaceClass 14 Video
bInterfaceSubClass 2 Video Streaming
bInterfaceProtocol 0
iInterface 0
VideoStreaming Interface Descriptor:
VideoStreaming Interface Descriptor:
VideoStreaming Interface Descriptor:
Interface Descriptor:
bInterfaceNumber 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
bDeviceProtocol 1 Interface Association
-
-
I do not like the look of that screen connection mess on top of the USB plug !
I am starting to think FLIR could be playing games over the true resolution of the LEPTON 3. Having re visited all the FLIR blurb I get the definite feeling that they did not want to specify the physical pixel count. There is even comment in one pre release document saying that picture appearance is more important than resolution ! This almost appeared to say that the new LEPTON had better image manipulation 'magic'. I wonder if we are back to our old friend of cheap low resolution imaging chips. Namely interpolation.
I would comment further if I had a working unit but as mine was DoA I will have to wait to see the images on my phone.
I will do a side by side comparison of the ONE with two other 160*120 pixel cameras. If FLIR are not being totally honest about the 160*120 physical resolution I think we will spot it.
If this is smoke and mirrors marketing crap, my camera will be heading back to FLIR pronto. I still have the email confirming physical resolution as 160*120 from FLIR CS.
I should have stuck with professional thermal cameras. At least they have real specs and you can trust them !
Aurora
I think this is just the consequence of 12um pixels paired with that small lens.
The "picture appearance is more important than resolution" quote is probably aimed at people comparing the FLIR to the Seek thermal (since the Seek is still higher res but arguably worse picture)
-
#365 Reply
Posted by
tomas123
on 09 Sep, 2015 08:40
-
I am starting to think FLIR could be playing games over the true resolution of the LEPTON 3.
...
This almost appeared to say that the new LEPTON had better image manipulation 'magic'.
a resolution test with a heating wire will show the true resolution
one square = one sensor pixel of Flir Exx
the result is really sharp (thanks to good optics of the Flir Exx)
Wow
...
one square = one sensor pixel of Flir One G1 (80x60)
Well, the result is definite poorer, as the 80x60 crop of the Exx ...
I love the artefacts around the heating wire on the RAW image of the Flir One G1
-
#366 Reply
Posted by
Fraser
on 09 Sep, 2015 12:26
-
Well the Faxitron is warming up and I will see is I can get any useful imaging of my units internal. The battery will be a PITA though.
Mike,
Sadly FLIR want the dead unit back. No surprises there. Any decent company will want to characterise production failures to avoid repetition. Pity though. I would have loved to keep it for the core alone. FLIR do not strike me as that generous though.
Aurora
-
#367 Reply
Posted by
frenky
on 09 Sep, 2015 14:13
-
When you will make a comparison with other thermal cameras with similar resolution; please make some photos in the dark so that msx won't interfere.
Sent from my LG-D855 using Tapatalk
-
#368 Reply
Posted by
Fraser
on 09 Sep, 2015 14:22
-
The issue wit taking pictures in the dark is the noise floor of the visible light camera. It may add noise to the image as the MSX algorithm searches for edges in the noise ? I can certainly give it ago though.
Aurora
-
#369 Reply
Posted by
frenky
on 09 Sep, 2015 14:25
-
It would be interesting to see the same scenes with and without light so we can see what happens with the details & noise...
Sent from my LG-D855 using Tapatalk
-
#370 Reply
Posted by
Fraser
on 09 Sep, 2015 14:44
-
-
#371 Reply
Posted by
mct75
on 09 Sep, 2015 16:30
-
Can MSX not be turned off? It seems like more of an annoyance than anything else, because I would use a Flir One for macro-type imaging than anything else.
-
#372 Reply
Posted by
in.Vitro
on 09 Sep, 2015 18:24
-
You can Stick "milky" tape in Front of the Camera
-
-
You can Stick "milky" tape in Front of the Camera
Yes - if you just blank it out, the camara turns up the gain & noise becomes annoying ( the software really should be able to sense that the light level is low and disable MSX).
Using translucent tape keeps the light level up while suppressing the edges
-
#374 Reply
Posted by
Fraser
on 09 Sep, 2015 19:54
-
I have heard from Bill on another matter and have taken the opportunity to ask him about the apparent slow frame rate of the Android camera. I hope he may respond on this with news of whether they expect to improve the situation.
Aurora