Messages

1

Optics / Re: GRIN lens with diameter of 0.5 mm

« on: September 01, 2016, 01:37:39 PM »

Hi Daniel,

What should I be careful of then, when using a relay lens of 0.5 mm diameter (I'm trying to order some now)? Do I need to worry about it's length or should I be able to focus the images by changing the distance between the two GRIN lenses?

Thanks,

Austin

2

Optics / GRIN lens with diameter of 0.5 mm

« on: August 26, 2016, 09:04:40 PM »

Hi everyone,

Has anyone successful used a 0.5 mm diameter GRIN lens with this system? What were the dimensions of the brass jacket you used. How much of the lens did you have going into the body of the scope? How much of the brass jacket protruded from the scope? We see that the thickness of the baseplate is about 1 mm so we were thinking of having 1 mm of the brass jacket protrude from the scope body and having 1 mm up in the scope body.

Thanks!

Austin

3

Electronics / Re: No control over CMOS components

« on: August 22, 2016, 02:31:53 PM »

Okay everything is working now. Full control of the camera from the software. Problem was not the soldering to the side of the C21 capacitor, but the ground sheath of the coax to the plate. It appeared to only cover 3/4 and after covering full area of the plate it connected on first attempt. It could have also been that the solder was "dirty."

Thanks again!

Austin

4

Electronics / Re: No control over CMOS components

« on: August 19, 2016, 12:33:21 PM »

Sorry, I realize I was unclear. When clicking connect, I have a grey screen for about two seconds, during which time the dialog box says "LED power udpdated: 0." But immediately following that I get the red screen. If it is any help, I also downloaded an open source webcam software, and that software is also able to recognize the miniscope as miniscope, but not able to stream video. 4th PC I have tried it on. Windows 7. All my LEDs are bright and unwavering with movement of wires. USB3.0/3.1. Disabled encryption services. All USB drivers are up to date. Please let me know if any other info is helpful. Reset many many times. Reinstalled software/firmware several times. Intel Core i7 @3.4 GHz 64 bit.

Thanks as always,

Austin

5

Electronics / No control over CMOS components

« on: August 18, 2016, 01:15:24 PM »

Hello all,

I thought I had solved my issues, but, alas, there is still more fun to be had. Currently everything appears to be working. However, upon connecting it will read that it is updating LED power and unsuccessfully so, followed by an msCam frame retrieve error. All physical components seem to be in compliance. Is there a way to test for malfunction of the CMOS? I had found a revised version of the firmware that sends a soft reset to the CMOS upon connecting, and figured it would be worth trying. The problem there is that the scope now has a silent install, and when reset will reprogram itself automatically.

Thanks!

Austin

6

DAQ Software/Firmware / Re: Issues Uploading Firmware

« on: August 17, 2016, 02:47:26 PM »

Hi again,

Simply running as administrator fixed the issue.

Austin

Hello everyone,

I have 3 stable LEDs, i7, Windows 7, disabled encryption, USB3.1 ports, USB3.0 SS cable, 50 ohm coax (7" long), the drivers for the USB ports are up to date, and successfully programmed the DAQ where it shows up as MINISCOPE. However, when I click connect (even several times) I will get a few seconds of grey and then a red screen with the error being msCam frame retrieve error, recording ended. Whenever I click anywhere in the miniscope software interface it says miniscope must be connected to change settings. However, it is showing up as MINISCOPE under imaging devices. Interestingly, trying different USB ports can give different issues, such as a frame grab error rather than a frame retrieve error. You can also get errors where the Cypress BootLoader may successfully program the EEPROM, but then fail to change the display name to MINISCOPE. However, in the fastest USB port (the 3.1) there seems to be fewer of those issues, and it only seems to have the msCam frame retrieve error.

Any suggestions?

Thanks!

Austin

7

DAQ Software/Firmware / Re: Issues Uploading Firmware

« on: August 17, 2016, 02:36:35 PM »

Hello everyone,

I have 3 stable LEDs, i7, Windows 7, disabled encryption, USB3.1 ports, USB3.0 SS cable, 50 ohm coax (7" long), the drivers for the USB ports are up to date, and successfully programmed the DAQ where it shows up as MINISCOPE. However, when I click connect (even several times) I will get a few seconds of grey and then a red screen with the error being msCam frame retrieve error, recording ended. Whenever I click anywhere in the miniscope software interface it says miniscope must be connected to change settings. However, it is showing up as MINISCOPE under imaging devices. Interestingly, trying different USB ports can give different issues, such as a frame grab error rather than a frame retrieve error. You can also get errors where the Cypress BootLoader may successfully program the EEPROM, but then fail to change the display name to MINISCOPE. However, in the fastest USB port (the 3.1) there seems to be fewer of those issues, and it only seems to have the msCam frame retrieve error.

Any suggestions?

Thanks!

Austin

8

Optics / GRIN lense acquisition

« on: July 25, 2016, 04:37:14 PM »

Dear all,

We are currently trying to get in contact with companies that manufacture GRIN lenses appropriate for the scopes. Can anyone provide information about GRIN lenses they obtained recently (since GrinTech has become less than cooperative), for example which company, the specifications of the lenses, cost, and whether or not they produced quality images? Anything would be a great help. Additionally, we have GRIN lenses for the Doric system. Is the scope able to be modified to accommodate the Doric lenses?

Best,

Austin
Graduate Research Assistant
University of Maryland School of Medicine

9

DAQ Software/Firmware / Re: Two LEDS (no DataLink), CMOS LED and LED PCB on, msCam retrieval error.

« on: July 21, 2016, 05:32:19 PM »

Problem solved. On the wiki it appeared in several images of the DAQ that the inner conductor was soldered to the middle pin on the DAQ PCB and not the correct solder to the side of the C21. This caused some confusion. I now have all 3 LEDS lit, however, I still get msCam frame retrieve errors. Likely another faulty soldering job.

Austin

10

DAQ Software/Firmware / Two LEDS (no DataLink), CMOS LED and LED PCB on, msCam retrieval error.

« on: July 21, 2016, 01:03:48 PM »

Hello all,

My name is Austin Ramsey. I am a graduate student at the University of Maryland School of Medicine. I have managed to solder the components listed in the walkthrough. I now have CMOS attached to the DAQ PCB attached to a Windows 10 (HP Pavillion dv5) laptop. I have tested for shorts between the DAQ PCB and CMOS and have resolved those issues, I think. I am curious as to whether or not anyone has had this issue before and how they came to a resolution. The data link LED is not lit. I am wondering at which point in the process it should have lit up. When the CMOS is attached via coax/SMA to the DAQ the luxeon blue LED PCB is constitutively on, as is the red LED on the CMOS PCB. This doesn't seem correct either. I can successfully flash the firmware onto the EEPROM, and have the DAQ enumerate as MINISCOPE under imaging devices in Device Manager. When I try to connect it will pause for a second and read out msCam retrieval error (not grab error) followed by the red screen.

Please advise. Thanks!

Austin