aharoni-lab / miniscope-v4 Goto Github PK

I receiced V4 from labmaker, but it cannot imaging. The DAQ only has two LED lighting, I'm not sure if it is a normal situation. The software constantly warns me "frame retrieve faild", then "reconnected". I have tried many methods, like changing computers, changing deviceID(the computer's facing camera worked), installing the firmware. So what is the problem?
Any help would be greatly appreciated!!!

Suggestion for improvement:

The DAQ Hardware wiki page says "Voltage supplied over the DC jack should be between 5V and 12V".

This might be misleading for users that are unfamiliar with the system, since we regularly come across situations in which users plug in 9V or 12V with a standard setup and fry their miniscopes.

For the miniscope v4 perhaps the range should not be as extense, or maybe a more conservative procedure can be suggested:

Voltage supplied over the DC jack depends on setup configuration such as cable length, type of cable, commutation, etc. A good starting point would be a 6V voltage, and likely not more than 9V is needed since the required voltage at the miniscope is 5V. We suggest you use a variable power supply and closely monitor how much power is actually reaching the scope to avoid damage.

Thank you for the contribution of the system. We are studying it.
But we have one question now. What downloader are using for the atmega328? We can't find 1.8V downloader for the atmega328. Most of atmega328‘s downloader in the market is 5V with USB supplying the power.We think 1.8V is the best voltage for Python480.
Best wishes!

This is intended to be more of a discussion and spot to organize and document ideas, as the google discussion is a bit dated and long.

Image striping during acquisition
During acquisition occasionally the image becomes misaligned due to a buffer issue. Seems to occur more often when using a commutator. I'm aware this issue has be documented and discussed elsewhere (see google groups discussion, I just want to create a more centralized issue to track progress and solutions.

I've been working a decent amount on identifying and fixing them, but haven't come up with a satisfying method. Currently I manually find the beginning and end of each occurrence, then interpolate them out using the bookend frames (so that motion correction and source extraction don't go haywire), and then throw out the activity from those interpolated times. Usually this only results in a handful of lost frames at a time, but when it lasts hundreds of frames it's very detrimental.

I've found it helpful to classify the stripes into two categories - stable and moving (see examples below).

• Stable offset stripes seem to be a consistent buffer offset problem (discussed in the google group). It can persist for much longer, and sometimes indefinitely until the scope is power cycled. As @daharoni and others have worked out, the data during these periods can be recovered, though the size of the buffer or offset don't appear consistent (2 examples of different stable offsets below).
• Moving stripes appear to be much shorter lived, but have an unstable pattern that might make data recovery difficult. I've only seen it persist for about 10 frames at a time though.

Here's a link to example data showing both issues:
https://drive.google.com/drive/folders/1JoomTZ7Ty0XKJo9ZNjIwy6_CUKqlzK_N?usp=sharing

Screenshots

All of the following occurred in sequence:

Normal frame

Example offset pattern

Another example offset

Example of moving (non-stable) striping 1

Example of moving (non-stable) striping 2

Back to normal imaging (after about 135 frames)

Additional context
Google groups discussion of issue

Describe the bug
The KiCad schematic cannot be loaded properly, as the cached library Miniscope-v4-Rigid-Flex-cache.lib, which contains some of the symbols used, is missing.

To Reproduce
Steps to reproduce the behavior:

1. Clone the repository.
2. Open the project with KiCad
3. Open the schematic

Expected behavior
The library is included in the repository. The schematic can be loaded properly.

Screenshots

Additional context
We would like to convert the Miniscope V4 PCB to KiCad V6, add an automation pipeline for production data export with KiBot and make some small improvements, e.g. add radii where the traces meet the EWL contact rings, to increase robustness. This is closely related to the same effort that we go to with the Miniscope-LFOV: Aharoni-Lab/Miniscope-LFOV#3

Hi,there.
Thank you very much for the open source material,these are very good projects.

We found a small problem of the miniscope. The setting parameters remain the same, but with the increase of the display time, the displayed image becomes whitish (the image displayed after ten minutes is brighter than the image just after power-on).
The display effect is as follows，(Using ImageJ, the third image is the image ten minutes later subtract the image ten minutes earlier）

My guess is that the heat of the serializer that affects some chips (such as power chip U8_TLV7103318DSER, L4_BLM15HD102SN1D or L5_ADL3225V-470MT-TL000). but I'm not sure.The deserializer chip of DAQ don't get as hot as the serializer chip of miniscope.Probably because the DAQ board dissipates heat better.Moving the affected chip away from the serializer may be an option.
We dissipate heat on the serializer of Miniscope (using a very heavy copper heatsink), and there is basically no difference in brightness. The effect is as follows:

Do you have any suggestions? The whitening problem of the image currently affects the imaging effect.

Hello there,
We want to enlarge the thin ring of EWL, the original ring is difficult to assemble. Do you think any problems will occur? I am worried that this change will adversely affect the camera.
The change looks like this：

Sorry to ask this question repeatedly， I cancelled it for the first time.

would love if the miniscope brightness could go below 1. I tried setting it to 0.5 in the config but unsure it actually worked. (yes gain is already down... I could increase sampling rate then downsample later but that is annoying to have to do for one animal only :-p)

@sneakers-the-rat did a nice writeup on this as well here: Aharoni-Lab/Miniscope-DAQ-QT-Software#68

Hello there,
We want to enlarge the thin ring of EWL, the original ring is difficult to assemble. Do you think any problems will occur? I am worried that this change will adversely affect the camera.
The change looks like this：