Problem with parameter FG_CAMSTATUS_EXTENDED in SDK 5.10

    We have identified a problem with the new version of the Balser Framegrabber SDK - this occurs with both version 5.10

    as well as with version 5.11. Version 5.7 (64 bit) does not show this behavior - here our application works without errors and no error is displayed in MicroDisplay.


    In the screenshot of MicroDisplayX from the data attachment, I have marked DMAs 2 and 3 (camera port 1) - here FVAL and LVAL are OFF and the following error is displayed in the LOG for DMAs 2 and 3:


    [2024-07-04 14:01:21,068] ERROR Failed to get parameter with type: Invalid parameter [board-index=0, board-serial=75111bb3, board-type=7511, dma-index=2, error=-2070, handle=(struct Fg_Struct_s const * __ptr64)000001B85FBA48A8, parameter-id=2050, parameter-name=FG_CAMSTATUS_EXTENDED, thread-id=2548, type=2]


    [2024-07-04 14:01:21,068] ERROR Failed to get parameter with type: Invalid parameter [board-index=0, board-serial=75111bb3, board-type=7511, dma-index=3, error=-2070, handle=(struct Fg_Struct_s const * __ptr64)000001B85FBA48A8, parameter-id=2050, parameter-name=FG_CAMSTATUS_EXTENDED, thread-id=3936, type=2]


    Our applet was not changed from SDK version 5.7 to 5.10 or 5.11.

    What can we do that it works for the new version of the SDK, too?



    Our environment:

    mE5

    2x e2v UNIIQUA C1MCL-ST (dual base)

    Hello MiNe,

    I am sorry to hear that you encountered this issue. Have you already contacted Basler Support on this case, as not to have two threads tackling the same issue. This forum is more focused on VisualApplets Design questions etc. - while the Runtime is still in the same environment, I can not give you a direct answer to this.

    Addtionally, were you the one creating the Applet or was it provided to you? IF you can provide the .hap file we can try to recreate the bug on our site.



    I will ask the appropiate engineers and report back to you once I know more.


    Best Regards,

    Kevin

    Hello Kevin,

    we have not yet contacted Basler directly.

    In the previous project a few years ago, we used Runtime 5.6 (32 bit) under Windows 7 (64 bit).

    Now the operating system is Windows 10 (64-bit) and we are also using the 64-bit version of

    the runtime and the created applet.

    We created the applet ourselves - I can provide you with the .hap file.


    Best regards

    Michael

    Hello Michael,

    Thank you - that would be much appreciated. If you are able to create a minimalistic version of your applet that also triggers the same error we can investigate it further.

    As I see it from your screenshot you have two cameras , 4 DMAs . I assume that two DMAs will transport the original image while the other two describe a downsampled output, correct?


    Best Regards,
    Kevin

    Hello Kevin,

    unfortunately I don't have the time to rebuild the applet at the moment - but it's not that big.

    Can I somehow send you the file directly (not publicly)?


    Correct, 2 Cameras in base configuartion and 4 DMAs. Two DMAs transport the image data

    (processed or for support cases the original image), the other two DMAs transport results of the

    calculations of the processed image data (each DMA has 2 values with 4 bytes each).


    Best regards

    Michael