DAVIS346 Blue not working properly(installed required version 16) about jaer HOT 18 CLOSED

Also, while using the latest libcaer, the error message

Timestamps on host and device are drifting away

shows up.

from jaer.

from jaer.

I'm not quite sure which one is the device name.
To be more specific:

1. The device name recognized by my computer is DAVIS346.
   

2. As depicted in the picture, the AEChip is set as Davis346blue,so the bar of jAER writes Davis346blue - DAVIS346
   

3. The bias settings are loaded from biasgenSettings/Davis346b/DAVIS346blue.xml.

Which name should the renamed bias setting file keep consistency with?

from jaer.

from jaer.

The following screenshots are taken without the device connected to my computer(I didn't take the device with me at home), hope that won't bring much difference.

1. Before I load the DAVIS346blue.xml, the Bias Current Config is shown as below:
   

2. After I reload the DAVIS346blue.xml, the Bias Current Config is shown as below:
   

Looks like the reloading doesn't change anything.
Did I get the wrong bias setting?

For the second question, the device cannot work properly in libcaer. The reconstructed picture is not normal(just like the picture I sent in my first comment), not presenting what's in front of the lens.

from jaer.

Is there any chance that this problem is caused due to the camera was connected to a USB2.0 port?

from jaer.

How do I confirm that the upgrade to version 16 is fine?

from jaer.

from jaer.

from jaer.

I took a picture of the flashy interface after upgrade to logic version 6.

Here's how the device is upgraded(following the instructions in automatic upgrade part from Reflashing Guide):

1. Open flashy1.2.0.
2. We saw an button titled update logic and clicked the button
3. Falshy informed us it's successfully updated.
4. Unplug and replug the device and we saw the above picture.

Here's a question to @tobidelbruck .

git pull the biasgenSettings folder and load the renamed biases from
Davis346Blue.xml.
When the device name changed, all the preference keys also changed. You
just need to load these settings from this file with the new AEChip name.

Does this anwser mean that I need to rename any file to make the camera work properly?

from jaer.

If we've used the automatic upgrade method to update the logic version, is it possible that it will burn the incorrect FPGA logic file for a different camera?

Is this a circumstance that we should try manually update/reflash the device?

from jaer.

from jaer.

I know it's not recommended, but considering the compatibility with widely-used jAER(1.6.x), I think downgrading the logic version back to 9912 is a safe method to make the camera work.

So I want to know is there logic 9912 in the commit history of https://github.com/inivation/devices-bin/tree/master/logic ? If there is, would you mind helping me locate the file?

I appreciate a lot!

from jaer.

from jaer.

When I tried to flash my device back to logic 9912 using Flashy1.2.0, I selected logic 9912 file and clicked upload logic bitstream button.
I got an Exception said:

Unable to send vendor OUT request 0xbe: LIBUSB_ERROR_PIPE

and an USB error massage said:

Error message：’System started.‘(code 0 at time - 1509359616)
Error message：’VR_CPLD_UPLOAD INIT: unsupported CPLD ID'(code 74 at time 1133314048).

The screenshot is shown as below.

1. Is is a prove that our reflashing to logic 16 was not successful?
2. How do I fix the camera?

from jaer.

from jaer.

I’ve downgraded the logic to 9912.
The camera is now able to work properly.

Thank you @tobidelbruck and @llongi for your help!

from jaer.

Just a quick update: I've managed to find the issue with the logic update and the blue DAVIS.
There will be new firmware (v5) and logic (v18) released in the course of the next week to fix this.
jAER and cAER will also have new releases that require those versions at that time.

from jaer.