Event timestamps about celex4-opalkelly HOT 5 CLOSED

@tbolten Your assumption is correct. eventVector.back().t should be changed along with the "EventFrameTime" and the "ClockRate", and m_uiTimeStamp needs to be changed as m_uiTimeSlice changes.
We have fixed this bug in the file: "Sources/SDK/eventproc/fpgadataprocessor.cpp". Please check out our latest updated SDK. Thanks a lot for your insight questions.

from celex4-opalkelly.

Thanks for your answer. I will update the SDK in my development environment and test it.

from celex4-opalkelly.

I checked out the current master-branch and builded the SDK. When using a slightly modified version of your example 'Samples/GetFrameBufferByCallback'

--- a/Samples/GetFrameBufferByCallback/getFrameBufferByCallback.cpp
+++ b/Samples/GetFrameBufferByCallback/getFrameBufferByCallback.cpp
@@ -61,6 +61,7 @@ void SensorDataObserver::onFrameDataUpdated(CeleX4ProcessedData* pSensorData)
        }
        else if (EventMode == sensorMode)
        {
+               std::cout << "Yes, here is data coming ..." << std::endl;
                //get buffers when sensor works in EventMode
                if (pSensorData->getEventPicBuffer(EventBinaryPic))
                {
@@ -93,6 +94,8 @@ int main()
        
        pCelex->openSensor("");
        pCelex->setFpnFile(FPN_PATH);
+       //pCelex->setEventFrameTime(80);
+       //pCelex->setClockRate(30);
        emSensorMode sensorMode = EventMode; //EventMode, FullPic_Event_Mode or FullPictureMode
        pCelex->setSensorMode(sensorMode);

I get the expected output:

[...]
API: setFEFrameTime 60 ms
Address: 2; Value: 375000; Mask: 16777215
API: setFullPicFrameTime 40 ms
Address: 2; Value: 1000000; Mask: 16777215
Address: 0; Value: 1; Mask: 1
Address: 0; Value: 0; Mask: 49152
Address: 0; Value: 0; Mask: 1
Yes, here is data coming ...
Yes, here is data coming ...
[...]

But, as soon I modify the eventFrameTime or the clockRate the program hangs:

[...]
Address: 2; Value: 1000000; Mask: 16777215
API: setEventFrameTime 80 ms
************* API: setClockRate 30 MHz
Address: 0; Value: 1; Mask: 1
Address: 0; Value: 0; Mask: 49152
Address: 0; Value: 0; Mask: 1
[... nothing is happening anymore ...]

I have not looked further, why this could be. Do you have an idea?

from celex4-opalkelly.

@tbolten Sorry, this is caused by a parameter typo in our source code "Sources/SDK/eventproc/fpgadataprocessor.cpp". It has been corrected in our latest updates. Please check it out. Thanks.

from celex4-opalkelly.

I updated my development environment again - and now I get the expected values. Thank you for fixing this.

from celex4-opalkelly.