FLIR One Developer / Blog / Topics / android, AndroidThings, Raspberry Pi, SDK 3 / FLIR One 3.01 SDK Fails on AndroidThings

FLIR One 3.01 SDK Fails on AndroidThings

Home Forums FLIR developer community General discussion FLIR One 3.01 SDK Fails on AndroidThings

This topic contains 3 replies, has 2 voices, and was last updated by Profile photo of Matthew Mauriello Matthew Mauriello 1 year, 9 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)

  • Author

    Posts

  • #6039

    Profile photo of Matthew Mauriello
    Matthew Mauriello

    Participant

    I have been working on a research application for about a year that utilizes the FLIR One v2 camera, we’re to the point where we want to build a number of test platforms but unfortunately the FLIR One v2 cameras for Android have become extremely rare and expensive (used cameras being between $350 – $400 on Amazon). Our application/hardware also uses AndroidThings for the OS and a Raspberry Pi as a hardware controller.

    For a while AndroidThings did not support access to the GPU on the Raspberry Pi, which meant we could not update to the latest FLIR One SDK to try the v3 FLIR One camera. Recently AndroidThings updated to 6.0.1 enabling access to the GPU. I can see from the logs that OpenGL support is being found by the SDK when trying to run the sample application, so it looks like the issues reported in the following threads may be resolved:

    OpenCL for Android: or what GPU library is being used by the SDKs?
    VisibleAlignedRGBA888Image results in “No DC image”

    However, when the camera connects to the sample application the system immediately crashes and reports the following errors:

    01-26 15:53:02.837 875-875/com.flir.flironeexampleapplication E/UsbCommunicator: Invalid device: Unsupported USB Vendor ID of 424
    01-26 15:53:03.799 875-899/com.flir.flironeexampleapplication E/libGLESv2_swiftshader: badness: unreachable case reached: getImplementationColorReadFormat external/swiftshader/src/OpenGL/libGLESv2/Framebuffer.cpp:550. colorbuffer->getInternalFormat(): 0
    01-26 15:53:03.799 875-899/com.flir.flironeexampleapplication E/swiftshader: AndroidEnterDebugger
    01-26 15:53:03.799 875-899/com.flir.flironeexampleapplication E/libGLESv2_swiftshader: badness: unreachable case reached: getImplementationColorReadType external/swiftshader/src/OpenGL/libGLESv2/Framebuffer.cpp:614. colorbuffer->getInternalFormat(): 0
    01-26 15:53:03.799 875-899/com.flir.flironeexampleapplication E/swiftshader: AndroidEnterDebugger
    01-26 15:53:06.104 875-899/com.flir.flironeexampleapplication E/AndroidRuntime: FATAL EXCEPTION: GLThread 101
                                                                                    Process: com.flir.flironeexampleapplication, PID: 875
                                                                                    java.lang.Error: std::exception
                                                                                        at com.flir.flironesdk.FrameProcessor.getProcessedFrames(Native Method)
                                                                                        at com.flir.flironesdk.FrameProcessor.processFrame(FrameProcessor.java:636)
                                                                                        at com.flir.flironesdk.FrameProcessor.onDrawFrame(FrameProcessor.java:872)
                                                                                        at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1571)
                                                                                        at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1270)

    I understand that there may not be a solution to this issue, but any feedback is appreciated.

    #6043

    Profile photo of Matthew Mauriello
    Matthew Mauriello

    Participant

    For a little more context: though the first error indicates the problem is with FrameProcess.java:636, Android Studio pulls up FrameProcessor.class and notes the error is on line 420:

     private void processFrame(FrameProcessor.FrameQueueEntry entry) {<br />
            entry.dequeueTime = System.nanoTime();<br />
            RenderedImage[] images = this.getProcessedFrames(entry.frame, entry.typesBitMask, entry.desiredSinkType, entry.emissivity, entry.isSpanLocked, entry.msxDistance, entry.msxWidth, entry.msxHeight);
    ...
    }
    

    Failing on the call to this.getProcessedFrames call and crashing the application.

    #6045

    Profile photo of Dominique
    Dominique

    Moderator

    Hi Matthew,

    We understand what you are trying to do, but in this case you are working with an unsupported platform for the FLIR ONE. We definitely encourage exchanging information on here, so please continue sharing your progress.

    Have you thought about working with the PureThermal USB Lepton board – have you considered it yet?

    Thank you,
    Dominique Strauss

    #6046

    Profile photo of Matthew Mauriello
    Matthew Mauriello

    Participant

    Unfortunately, that would be an extreme last resort that we probably wouldn’t have time to accommodate as we aim to deploy in March.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.