Miniscope Board

General Category => DAQ Software/Firmware => Topic started by: Matteo23jl on May 30, 2017, 01:44:27 PM

Title: Miniscope Device Manager
Post by: Matteo23jl on May 30, 2017, 01:44:27 PM
Good morning,

I have a problem installing the miniscope.

I built the miniscope and I started following the prcedure on http://miniscope.org/index.php?title=Software_and_Firmware_Setup

1) I set the jumper modality BOOT FROM USB,
2) I installed the driver for the miniscope,
3) I uploaded the firmware msDAQ_Firmware.img through the Cypress application

The problem appeared as soon as I power cycled the miniscope.

Windows does not show anymore any Miniscope in the Device Manager (now it doesn't even show the Westbridge device it used to show before installing the driver).
Miniscope should be appear ad Imaging Device, instead I can see only the driver of miniscope.

Is there a step I miss? Is it possible to solve this problem. I need to go on with the work.

Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Daniel Aharoni on May 31, 2017, 04:27:16 AM
Hi Matteo,
Sorry for the slow response over email. I usually am more responsive to discussion board posts anyways.

From the looks of it, this sounds like a driver incompatibility issue. Have you tried hooking up your programmed DAQ PCB to other computers?

Since the DAQ PCB doesn't show up as a Westbridge device or Bootloader in Cypress Control Center once you have successfully programmed the EEPROM, the issue is likely with how the DAQ PCB enumerates as a generic webcam. The source of this issue is hopefully some weird compatibility issue between my implementation of the USB Video Class protocol and your specific computer.
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 13, 2017, 12:32:56 AM
Good morning to everybody,
I have a still problem installing the miniscope.
Here I have attached the a word file with all the screenshots of what I did during the installation.
If someone can find any mistake or can help it would be great!
Thank you so much,
Matteo
Title: Re: Miniscope Device Manager
Post by: Daniel Aharoni on June 13, 2017, 06:31:20 PM
Hi Matteo,
It looks like your DAQ PCB is still booting up as a Cypress Bootloader even after you have programmed the EEPROM with the firmware. If the jumpers and switches are set correctly this shouldn't happen (The DAQ PCB should show up under Imaging Devices and not under USB controllers in Device Manager). Since the DAQ PCB is still booting up as a bootloader it means it isn't grabbing the firmware off the EEPROM on power up. I have never seen this before and can't think of what the cause would be apart from a physical issue with the PCB.

I can't remember if you have other DAQ PCBs to use to see if this problem shows up on them too.
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 13, 2017, 07:51:29 PM
Hi Daniel,
thank you that you replied me. Tomorrow I will try it with Mac. Here is the pics of our DAQ-PCB. We have only this so far.
Sincerely,
Matteo
Title: Re: Miniscope Device Manager
Post by: Daniel Aharoni on June 14, 2017, 03:57:45 AM
Hi Matteo,
The Miniscope system will not run on MAC unless you directly boot into Windows 7 or 10 through BootCamp. Just FYI.
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 05:03:38 PM
Hi Daniel,
I fix the problem. For some reason the EEPROM doesn't work properly, so I have desoldered it and I have put a new one!
Now I think I have a common problem...
I attached a screenshot!
Thank you
Sincerely,
Matteo
Title: Re: Miniscope Device Manager
Post by: Daniel Aharoni on June 15, 2017, 05:38:18 PM
Hi Matteo,
It is great to hear that you are making progress!

Can you give me a little bit more detail concerning the problem you are having now? From what it looks like you are able to connect to the Miniscope and get a live video stream but it crashes and the screen turns red shortly after?
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 06:32:05 PM
Hi Daniel,
thank you for your answer..I have attached the screenshot as you can see.
The Software writes that The Miniscope must be connected.
What could be?
The window of the video is grey.
Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 06:41:54 PM
Hi Daniel:
New problem, I have connected one more time the DAQ-PCB and the MINISCOPE in Imaging Device doesn't show up!
Looks like I have the same problem.
What could be?
Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 06:47:56 PM
The LED ( this from the beginning, from the moment I have assembled the DAQ-PCB) turn on are only 2.the LED U12 is turn off.
What does it mean?
Sincerely,
Matteo
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 06:59:24 PM
In the website you have written:
"Connect a USB3.0 cable between the DAQ PCB and computer being careful not to apply too much force or torque on the USB connector. Make sure to use a short (under 3ft to 5ft) USB3.0 cable.
Make sure the bottom 2 LEDs turn on."

But in the forum everyone report that 3 LED should be turn on!
Why? Did I miss anything?
Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 07:01:55 PM
Here
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 08:00:00 PM
Hey Daniel,
Here is the picture of my coax cable
Thank you for your help!
Sincerely,
Matteo
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 08:17:50 PM
Hi Daniel,
Here is the link of the coax cable:

https://www.digikey.com/products/en?keywords=897611670

It looks like the same cable that you have used in the videos of Youtube in the website.
Is it correct?
So far there is no impedance reported. it is 50?
Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Daniel Aharoni on June 15, 2017, 09:23:16 PM
Hi Matteo,
Does the red LED on the CMOS PCB light up when you hook up your Miniscope to the DAQ PCB and power everything up?

The U12 LED, which is the Data Link LED, lights up when there is a stable power and data connection between the DAQ PCB and the CMOS PCB. This LED should light up right away when you power everything up, even before you load the Miniscope DAQ Software or connect to the Miniscope system through the software. If the Data Link LED does not light up then the most likely cause is a problem with the coax cable or coax cable connections.
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 15, 2017, 11:08:39 PM
Dear Daniel,
As I have reported before the Miniscope doesn't show up any more in Device Manager.
yes, As I connect everything I have a REd Light in the CMOS of the Miniscope and 2 green lights in the DAQ PCB
I have attached the picture in the pdf file here.
Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 16, 2017, 04:11:21 PM
Hi Daniel,
As I understand, when I programm the EEPROM the first time it shows up in Device Manager as MINISCOPE, but as I disconnect it, the MINISCOPE doesn't appear in IMAGING DEVICE anymore. My DAQ PCB is a v2.01, I have put the pins in K1, K2,K3 and TP1 and TP3. Th jumpers only in K1 and K2 (as USB), K2 as EEPROM. I have also putted the pins in J9 (?): 3 pins with jumper in the center and right side.
These are all the pins and jumper that I have soldered. Is everything correct?
Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Matteo23jl on June 17, 2017, 12:06:39 AM
HI Daniel,
We would like to buy a new DAQ-PCB to be sure that our works properly and eventually resolve our problem and understand if this is caused by software or hardware.
Also can you send us or exchange with us one that works (and we can send our to you so you can see it)? So we can test at least our miniscopes.
If someone also has an extra DAQ-PCB that works and he doesn't use (one left over), please contact me
Thank you,
Matteo
Title: Re: Miniscope Device Manager
Post by: Daniel Aharoni on June 18, 2017, 04:43:38 PM
Hi Matteo,
That third LED should light up the moment the CMOS PCB is connected when everything is working. This light runs independently of the computer the system is hooked up to or the firmware being loaded properly to the board. It looks like there are issues with the PCB and/or solder of your boards.