Some times the temperature readings are abnormal

Home Forums FLIR One developer community General discussion Some times the temperature readings are abnormal

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

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

  • Author

    Posts

  • #7448

    Profile photo of surendra
    surendra

    Participant

    i don’t know what factors effect it. for every 1 minute i am getting a frame and calculating temperature from pixles. In count of 10 i am only able to get correct readings 2 to 3 times every time the data is like this

    Abnormal Data:
    “temp_readings”: [
    {
    “item”: “light”,
    “temperature”: “246.31”
    },
    {
    “item”: “fan”,
    “temperature”: “238.96”
    }

    Correct data:

    “temp_readings”: [
    {
    “item”: “light”,
    “temperature”: “27.44”
    },
    {
    “item”: “fan”,
    “temperature”: “27.05”
    }

    #7449

    Profile photo of Allison
    Allison

    Moderator

    Hi Surendra,

    I would try performing tuning to mitigate this issue. Tuning triggers a flat field calibration (FFC) which calibrates the camera’s sensors allowing for a more accurate temperature reading. Other than that, I would check that your code is definitely calculating the temperature correctly and there’s nothing strange going on with the pixel coordinates.

    Please let me know if neither of those options mitigates the issues and I will be happy to continue troubleshooting.

    Thank you,
    Allison Torchia

    #7450

    Profile photo of surendra
    surendra

    Participant

    public static final Device.TuningState TuningSuggested?

    Now i am doing what you said before calculating i am performing tuning. What is the above static method for and how to use it?. But it didn’t change anything.

    if(flirOneDevice!=null) {
    flirOneDevice.performTuning();
    if(currentTuningState==Device.TuningState.Tuned) {

    calculateReadings();
    }
    }

    • This reply was modified 1 year, 3 months ago by Profile photo of surendra surendra.
    • This reply was modified 1 year, 3 months ago by Profile photo of surendra surendra.

    #7455

    Profile photo of Allison
    Allison

    Moderator

    Hi Surendra,

    The above static method sets the Tuning state, so if automatic tuning is enabled or if you have a method that looks at the state to see when to perform tuning it will read that value and proceed accordingly.

    Since tuning does fix the values, there are a couple things to try.

    If you could use the FLIR One app by FLIR and measure the same objects temperature and/or the example app that would be helpful. If you get abnormal readings with one of those apps then we would know it’s a hardware problem and can troubleshoot from there, if the readings are normal, then it’s a software problem and we’ll need to troubleshoot your code for calculateReadings();

    If you can’t measure the same objects, just measuring anything and looking for variations in temperature on the order of what you’re seeing could be helpful.

    If it’s a software problem it would be really helpful if you could post your code so I can help find where the issue is coming from.

    Thank you,
    Allison Torchia

    #7499

    Profile photo of surendra
    surendra

    Participant

    Hi Allison,
    can u give me a solution to this issue mentioned in this thread https://developer.flir.com/forums/topic/flir-one-does-not-show-anything-after-opening-the-activity-couple-of-times/

    How to recover the device in resume state.

    • This reply was modified 1 year, 3 months ago by Profile photo of surendra surendra.

    #7502

    Profile photo of surendra
    surendra

    Participant

    any one know about this issue?

    #7506

    Profile photo of Allison
    Allison

    Moderator

    Hi Surendra,

    Have you tried the different solutions mentioned in this thread: https://developer.flir.com/forums/topic/recover-the-device-connection/

    What phone are you using and what version of Android OS? I’m having difficulty recreating this issue with the latest SDK.

    Thank you,
    Allison Torchia

    #7509

    Profile photo of surendra
    surendra

    Participant

    Hi Allison,
    i am using Android device with marshmallow running in it. i am using latest SDK 3.0.1 .

    i have tried above solutions in thread. Scenario is like this app is started when device starts(Boot load) where camera is already running. i can see frame received in console but the frame is dark with out any image when i store the frame. And the screen is also dark showing nothing. In OnStart and OnRestart i am calling Device.startDiscovery().

    • This reply was modified 1 year, 3 months ago by Profile photo of surendra surendra.

    #7526

    Profile photo of Allison
    Allison

    Moderator

    Hi Surendra,

    I apologize for the delay. I have several questions to continue troubleshooting.

    What Android device are you using (Phone type and model)?

    Does your onStop() method call stopDiscover?
    Are you getting any error messages in your logs or do they look normal?
    When you initialize your GLSurface do you set:
    thermalSurfaceView.setPreserveEGLContextOnPause(true);

    Thank you,
    Allison Torchia

    #7528

    Profile photo of surendra
    surendra

    Participant

    Hi Allsion,

    It is not a mobile phone it’s a hub running with marshmallow. In onstop() method stop discover is being called.

    Error LOG:
    08-11 19:20:04.775 27132-27132/com.flir.coldstoragecamera E/PreviewActivity: onStop, stopping discovery!
    08-11 19:20:06.825 27132-27132/com.flir.coldstoragecamera E/UsbCommunicator: Invalid device: Unsupported USB Vendor ID of 413c
    Invalid device: Unsupported USB Vendor ID of b95
    08-11 19:20:06.842 27132-28069/com.flir.coldstoragecamera E/libEGL: call to OpenGL ES API with no current context (logged once per thread)
    08-11 19:20:06.865 27132-27169/com.flir.coldstoragecamera E/UsbDeviceConnectionJNI: device is closed in native_control_request
    08-11 19:20:07.084 27132-27132/com.flir.coldstoragecamera E/UsbCommunicator: Invalid device: Unsupported USB Vendor ID of 413c
    Invalid device: Unsupported USB Vendor ID of b95
    08-11 19:20:07.781 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolGenericPacketParser.c: 129 RBProtocol_genericPacketParser_consumeBuffer]: Received magic number 0x3A4E6000, expected 0xBEEF
    08-11 19:20:07.782 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolParserFunctions.c: 885 RBProtocolParserParseIncomingBuffer]: generic packet parser is in an error state!
    08-11 19:20:07.792 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolGenericPacketParser.c: 129 RBProtocol_genericPacketParser_consumeBuffer]: Received magic number 0xD2C0D34, expected 0xBEEF
    08-11 19:20:07.792 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolParserFunctions.c: 885 RBProtocolParserParseIncomingBuffer]: generic packet parser is in an error state!
    08-11 19:20:07.794 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolGenericPacketParser.c: 129 RBProtocol_genericPacketParser_consumeBuffer]: Received magic number 0xD280D1F, expected 0xBEEF
    08-11 19:20:07.794 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolParserFunctions.c: 885 RBProtocolParserParseIncomingBuffer]: generic packet parser is in an error state!
    08-11 19:20:07.801 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolGenericPacketParser.c: 129 RBProtocol_genericPacketParser_consumeBuffer]: Received magic number 0xC0FFD8FF, expected 0xBEEF
    08-11 19:20:07.802 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolParserFunctions.c: 885 RBProtocolParserParseIncomingBuffer]: generic packet parser is in an error state!
    08-11 19:20:07.804 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolGenericPacketParser.c: 129 RBProtocol_genericPacketParser_consumeBuffer]: Received magic number 0xDA624D79, expected 0xBEEF
    08-11 19:20:07.804 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolParserFunctions.c: 885 RBProtocolParserParseIncomingBuffer]: generic packet parser is in an error state!
    08-11 19:20:07.807 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolGenericPacketParser.c: 129 RBProtocol_genericPacketParser_consumeBuffer]: Received magic number 0x9E030331, expected 0xBEEF
    08-11 19:20:07.807 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolParserFunctions.c: 885 RBProtocolParserParseIncomingBuffer]: generic packet parser is in an error state!
    08-11 19:20:07.808 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolGenericPacketParser.c: 129 RBProtocol_genericPacketParser_consumeBuffer]: Received magic number 0x5DEF19E7, expected 0xBEEF
    08-11 19:20:07.808 27132-27169/com.flir.coldstoragecamera E/RDW: (a170e930)[RBProtocolParserFunctions.c: 885 RBProtocolParserParseIncomingBuffer]: generic packet parser is in an error state!
    08-11 19:20:07.888 27132-27160/com.flir.coldstoragecamera E/libEGL: eglMakeCurrent:731 error 3006 (EGL_BAD_CONTEXT)
    08-11 19:20:07.900 27132-27160/com.flir.coldstoragecamera E/libEGL: eglMakeCurrent:765 error 300d (EGL_BAD_SURFACE)
    08-11 19:20:11.839 27132-28072/com.flir.coldstoragecamera E/UsbCommunicator: Invalid device: Unsupported USB Vendor ID of 413c
    Invalid device: Unsupported USB Vendor ID of b95

    i am initializing this also thermalSurfaceView.setPreserveEGLContextOnPause(true);

    #7530

    Profile photo of Allison
    Allison

    Moderator

    Hi Surendra,

    There are a couple things to note. The FLIR One was really designed to be used with mobile phones so there may be unanticipated issues that come up when developing with other devices. Even with mobile phones our compatibility list and developers have to constantly adapt to the incredible variation in hardware and software across different phones despite running all running Android OS.

    That being said, I recognize the one of the errors you’re running into and we’re currently working on a workaround. The issue is that GLSurfaceView’s context is not properly being preserved. It’s an issue with GLSurfaceView even with thermalSurfaceView.setPreserveEGLContextOnPause(true), context is not always preserved. This results in the EGL_BAD_SURFACE error when the app is reopened. This issue happens more often on non-mobile phone devices such as tablets and may be related to GPU which is why I mentioned the earlier compatibility notes. Right now the best solution is to unplug and replug in the FLIR One if none of the methods from the other forum threads solve the issue. Alternatively, you may try rendering without GLSurfaceView. An example of this is provided in the example app with PreviewActivity instead of GLPreviewActivity.

    I will update you as we make progress with this.

    I haven’t seen this before

    E/UsbCommunicator: Invalid device: Unsupported USB Vendor ID of 413c<br />
    Invalid device: Unsupported USB Vendor ID of b95

    Are you ever able to view images with your device? If not it may be that your device simply cannot interface with the FLIR One. However, if you are able to get images than there is something else going on. If you could specify the hardware you’re using I may be able to help troubleshoot further with that.

    Thank you,
    Allison Torchia

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

You must be logged in to reply to this topic.