OSX + Nebulosity + Atik 16IC-c

[niknak]

Also.. if you use the OpenPHD2 on the mac, you could switch on the debugging trace, then connect to the camera.

You should then see something about validating the VPID as part of the log - it will also tell you if the default version worked or not.

 Tried logging in PHD2 as well.

I have searched the log but cannot find any of the search terms "validate" or "VPID" within it

I can send you the log file if you think that would help ??

[NickK]

 Tried logging in PHD2 as well.

I have searched the log but cannot find any of the search terms "validate" or "VPID" within it

I can send you the log file if you think that would help ??

Sorry not VPID (that's USB, and it was a very long day yesterday), but "VUSBID". I changed the error message recently to standout (it has "CRITICAL ERROR" markers and explains that the camera will not provide images).

[niknak]

Sorry not VPID (that's USB, and it was a very long day yesterday), but "VUSBID". I changed the error message recently to standout (it has "CRITICAL ERROR" markers and explains that the camera will not provide images).

Hi Nick.

Really sorry for dragging this out and I do really appreciate your (and everyone elses) help with this.

I searched the error log for the term "VUSBID" but that term wasn't present either

Interestingly, I rang Atik this morning to see if they could shed any light and as soon as I mentioned the words " mac, nebulosity and legacy" guess whose name instantly appeared

[NickK]

Hmm can you send me the ATIKOSXDrivers.log?

[niknak]

Hmm can you send me the ATIKOSXDrivers.log?

Just PM'ed it over to you.

[NickK]

Yup - I've plugged my 16IC into the latest experimental ExampleApp with the latest drivers and the camera initialises so this sounds like the FTDI ChipID is different for your camera and mine. Once we have that we can use it to start the camera. Although interesting you have the same serial number.

D: 55352d8e.90ba3 : User has changed debug logging state: on

I: 55352d8e.90bc2 : ATIK Drivers version 1.47 (Apr 20 2015 17:31:55)

I: 55352d8e.90bd3 : Local time 2015/4/20 17:47:10 

I: 55352d8e.90be6 : ATIK OSX Driver 1.47 (Apr 20 2015 17:31:56)

I: 55352d8e.90c0f : ATIK OSX Legacy Driver 1.47 (Apr 20 2015 17:32:01)

I: 55352d8e.90dba : Detected legacy mappings

(

        {

        ftdiChipId = ee8f4c9;

        serialNumber = A3001QH8;

    }

)

I: 55352d8e.90e68 : Adding legacy mapping 0x0ee8f4c9 for serial number A3001QH8

I: 55352d8e.90e75 : New FTDIChipID mapping registered in legacy driver: A3001QH8 -> 0xe8f4c927

I: 55352d8e.90e95 : Mode: startSupport

D: 55352d8e.90ea0 : ** Listing all USB devices..

D: 55352d8e.90ee0 : ** USB Information listed from your system for each device line:

D: 55352d8e.90ee6 : ** USB Device Address - where on the bus, so if we have two ATIK cameras we can see them

D: 55352d8e.90eea : ** USB Vendor Id (VID) - the manufacturer's USB identifier

D: 55352d8e.90eed : ** USB Product Id (PID) - the product USB identifier

D: 55352d8e.90ef0 : ** USB Version number (bcd) - the version of the product

D: 55352d8e.90ef3 : ** USB connected speed - High speed, Full speed or Low speed

D: 55352d8e.90ef6 : ** USB connected state - the system stated of the device (powered, connected, captive, suspended)

D: 55352d8e.90ef9 : ** USB manufacturer string (some devices do have this field populated)

D: 55352d8e.90efc : ** USB product string (some devices do not have this field populated)

D: 55352d8e.90eff : USB LIST START

I: 55352d8e.9261a : fa000000: 0x05ac 0x8006 0x0200 H 0000061d

I: 55352d8e.92774 : fd000000: 0x05ac 0x8006 0x0200 H 0000061d

I: 55352d8e.92877 : fd100000: 0x0424 0x2513 0x0bb3 H 0000003f

I: 55352d8e.92976 : fa100000: 0x0424 0x2513 0x0bb3 H 0000001f

I: 55352d8e.92b6f : fa110000: 0x0a5c 0x4500 0x0100 F 0000003d

I: 55352d8e.92ca4 : fa200000: 0x05ac 0x8509 0x0516 H 0000001f

I: 55352d8e.92daa : fd110000: 0x05ac 0x8242 0x0016 L 0000003d

I: 55352d8e.92ef1 : fa120000: 0x05ac 0x0246 0x0108 F 0000001d

I: 55352d8e.92ff9 : fa113000: 0x05ac 0x821a 0x0042 F 0000003d

I: 55352d8e.931a8 : fa130000: 0x2687 0xfb01 0x0100 F 00001018

D: 55352d8e.931f5 : USB LIST END

D: 55352d91.e1387 : Iterating - device 0x0001716b

D: 55352d91.e139d : device iteration block start 0x0001716b

D: 55352d95.df827 : Flushing (cycle 1)... 0x0 bytes returned

D: 55352d95.df841 : using 0xee8f4c9 id for serial number 'A3001QH8'

D: 55352d95.df850 : CameraState transitioning from 2030405664 to 1.

D: 55352d95.df856 : CameraState transitioning from 1 to 0.

D: 55352d95.dfbff : ReadUSB 1 bytes to read

I: 55352d95.e2714 : VUSBID ok (FTDI ChipID was accepted by camera)

D: 55352d95.e2761 : ++ Identified: ART: ATIK ATK 16IC Camera A3001QH8 ++

D: 55352d95.e276b : Flushing..

D: 55352d96.686bf : flush complete.

D: 55352d96.68761 : ReadUSB 1 bytes to read

D: 55352d96.6b4cd : ReadUSB 256 bytes to read

D: 55352d96.e564d : Camera reported serial number '000001'

D: 55352d96.e566e : Flushing..

D: 55352d97.6b5f1 : flush complete.

D: 55352d97.6b7d4 : ReadUSB 256 bytes to read

I: 55352d97.e5934 :  Protocol version : 0x0107

I: 55352d97.e595c :  Description from camera is : 'ATIK 16IC'

I: 55352d97.e5967 :  Manufacturer : 'ATIK'

I: 55352d97.e596a :  Has FIFO      : no

I: 55352d97.e596d :  Is Interlaced : no

I: 55352d97.e5970 :  Can Ext. Trig : no

I: 55352d97.e5973 :  Can Preview   : no

I: 55352d97.e5976 :  Can Subsample : no

I: 55352d97.e5979 :  Can Overlap   : no

I: 55352d97.e597c :  Has Mech Shut : no

I: 55352d97.e597f :  Has Guide Port: yes

I: 55352d97.e5982 :  Has GPIO      : no

I: 55352d97.e5985 :  Sensor X Pixels: 659

I: 55352d97.e5988 :  Sensor Y Pixels: 494

I: 55352d97.e598b :  Sensor X Size: 740

I: 55352d97.e598e :  Sensor Y Size: 740

I: 55352d97.e5990 :  Max X bin: 4

I: 55352d97.e5993 :  Max Y bin: 4

I: 55352d97.e5996 :  Well depth : 234

D: 55352d97.e59a0 : EnableAmplifier(Off)

D: 55352d97.e5b33 : CameraState transitioning from 0 to 1.

D: 55352d97.e5c2a : claiming: ATIK 16IC (A3001QH8)

D: 55352d97.e5c32 : failed to claim ATIK 16IC (A3001QH8)

D: 55352d97.e5c37 : claiming: ATIK 16IC (A3001QH8)

D: 55352d97.e5c4e : successfully claimed ATIK 16IC (A3001QH8)

D: 55352d9c.6c4c2 : Set extension: kArtemisExtensionKeyPrecharge with value NO

D: 55352d9c.6c4d7 : Set extension: kArtemisExtensionKeySubsample with value NO

D: 55352d9c.6c4df : Set extension: kArtemisExtensionKeyTitanAutoBlackLevel with value NO

D: 55352d9c.6c4f7 : Frame setup debug (frame inputs):

D: 55352d9c.6c4fd :   Frame width x hieght: 0 x 0

D: 55352d9c.6c502 :   Subframe            : (0,0) 0x0

D: 55352d9c.6c508 :   Binning             : 1x1

D: 55352d9c.6c50b :   Camera dimensions   : 659x494

D: 55352d9c.6c518 : Resulting:

D: 55352d9c.6c51f :   Duration            : 0.030000 seconds

D: 55352d9c.6c523 :   Frame width x hieght: 659 x 494

D: 55352d9c.6c528 :   Frame Subframe      : (0,0) 659x494

D: 55352d9c.6c52b :   remaining subframe  : (0,0) 659x494

D: 55352d9c.6c52e :   Binning             : 1 x 1

D: 55352d9c.6c533 :   m_bHires            : 1

D: 55352d9c.6c538 :   nPix                : 325546

D: 55352d9c.6c53d :   bExpectPrecharge    : no

D: 55352d9c.6c542 :   m_bOversample       : no

D: 55352d9c.6c546 :   nExp                : 651092 bytes

D: 55352d9c.6c54c :   preview mode        : no 

D: 55352d9c.6c550 :   camera is interlaced: no 

D: 55352d9c.6c553 : Setting Post Processing options:

D: 55352d9c.6c557 :   subtract precharge  : no

D: 55352d9c.6c55b :   re-interlace        : no

D: 55352d9c.6c55f :   adjust oddbin       : no

D: 55352d9c.6c564 :   linearise           : no

D: 55352d9c.6c56a :   fix banding         : no

D: 55352d9c.6c7aa : CameraState transitioning from 1 to 3.

D: 55352d9c.6c7ca : CameraState transitioning from 3 to 2.

D: 55352d9c.6c96d : READCCD

D: 55352d9c.6c977 :  Expcode  : 12 (ExpActual=0.030000, Exposure=0.030000)

D: 55352d9c.6c97b :  Binning  : 1 x 1

D: 55352d9c.6c97f :  Subframe : (0,0) 659 x 494 pixels

D: 55352d9c.6c982 :  Preview  : not supported

D: 55352d9c.6c985 :  FIFO     : off (FIFO present: no, FIFO enabled no)

D: 55352d9c.6c988 :  Amplifier: on

D: 55352d9c.6c98b :  SubSample: on

D: 55352d9c.6c98e :  Precharge: IPCS

D: 55352d9c.6c991 :  Ilace req: no

D: 55352d9c.6c994 :  Bias     : no

D: 55352d9c.6c997 : CameraState transitioning from 2 to 3.

D: 55352d9c.6c9aa : **** DOWNLOADING ***

D: 55352d9c.6c9af : CameraState transitioning from 3 to 5.

I: 55352d9c.6c9ba : Camera FIFO not present - dropping to use chunks of chunksize 63264 bytes

D: 55352d9c.6c9be : **** bytes 651092 of 651092 bytes remaining

D: 55352d9c.6c9c2 : ReadUSB 63264 bytes to read

D: 55352d9c.e6aef : **** bytes 651092 of 651092 bytes remaining

D: 55352d9c.e6aff : ReadUSB 63264 bytes to read

D: 55352d9d.31fd4 : Download percentage 9%

D: 55352d9d.31fe7 : **** bytes 587828 of 651092 bytes remaining

D: 55352d9d.31feb : ReadUSB 63264 bytes to read

D: 55352d9d.828b1 : Download percentage 19%

D: 55352d9d.828d7 : **** bytes 524564 of 651092 bytes remaining

D: 55352d9d.828e2 : ReadUSB 63264 bytes to read

D: 55352d9d.d1e75 : Download percentage 29%

D: 55352d9d.d1e88 : **** bytes 461300 of 651092 bytes remaining

D: 55352d9d.d1e8c : ReadUSB 63264 bytes to read

D: 55352d9e.2e23e : Download percentage 38%

D: 55352d9e.2e271 : **** bytes 398036 of 651092 bytes remaining

D: 55352d9e.2e281 : ReadUSB 63264 bytes to read

D: 55352d9e.7d216 : Download percentage 48%

D: 55352d9e.7d229 : **** bytes 334772 of 651092 bytes remaining

D: 55352d9e.7d22d : ReadUSB 63264 bytes to read

D: 55352d9e.cd4c3 : Download percentage 58%

D: 55352d9e.cd4d3 : **** bytes 271508 of 651092 bytes remaining

D: 55352d9e.cd4d7 : ReadUSB 63264 bytes to read

D: 55352d9f.29469 : Download percentage 68%

D: 55352d9f.29486 : **** bytes 208244 of 651092 bytes remaining

D: 55352d9f.2948e : ReadUSB 63264 bytes to read

D: 55352d9f.79173 : Download percentage 77%

D: 55352d9f.79184 : **** bytes 144980 of 651092 bytes remaining

D: 55352d9f.79188 : ReadUSB 63264 bytes to read

D: 55352d9f.c9760 : Download percentage 87%

D: 55352d9f.c9786 : **** bytes 81716 of 651092 bytes remaining

D: 55352d9f.c9791 : ReadUSB 63264 bytes to read

D: 55352da0.24b06 : Download percentage 97%

D: 55352da0.24b1e : **** bytes 18452 of 651092 bytes remaining

D: 55352da0.24b42 : ReadUSB 18452 bytes to read

D: 55352da0.3c7d7 : Download percentage 100%

D: 55352da0.3c802 : **** DOWNLOAD COMPLETE ***

D: 55352da0.3c813 : EnableAmplifier(Off)

[niknak]

Yup - I've plugged my 16IC into the latest experimental ExampleApp with the latest drivers and the camera initialises so this sounds like the FTDI ChipID is different for your camera and mine. Once we have that we can use it to start the camera. Although interesting you have the same serial number.

Just tried on a native PC and on the win7 virtual box I have on my macbook.  Doesn't work on either ...... grrrr !

Calling a PC mate to see if he can shed any light.

I did wonder if the reason your chip id program can't see it is the fact that it doesn't have a driver ???

[NickK]

Does the camera appear on the windows device manager (on the printer and devices window)?

Have you tried the older window drivers that came with the camera?

[niknak]

Does the camera appear on the windows device manager (on the printer and devices window)?

Have you tried the older window drivers that came with the camera?

It does appear in the device manager.

I don't have the disk with the original software  so I cant try the old drivers.

[NickK]

It does appear in the device manager.

I don't have the disk with the original software  so I cant try the old drivers.

Ok if it appears on the device manager - this means that the operating system can see the camera. If it shows the devices then perhaps the new windows drivers support the legacy cameras (sorry I've not used windows to capture in a long time).

The options are either:

a) try the last window drivers to support the ATIK 16IC series (should have the ftdichipid as part of the drivers installed)

or

install the windows FTDIChipID drivers, and use the ChipID program separately ( http://www.ftdichip.com/Support/SoftwareExamples/FTDIChip-ID.htm ).

I'm getting pulled away here unfortunately - so if your friend can help with the FTDIChipID and chipid program then we're on the way, if not let's revisit tomorrow.

[niknak]

Well........ I've tried and tried.

I have visited the site that created the fdtichip-id program and followed all the instructions as far as can and it still yields nothing.

I am however not a PC person being a long term mac user - which explains my desire to get it working on a mac.

so ...... I'm taking it to a friend to see if he can get to the bottom of the FDTIChip-ID issue.

In the mean time .......

As the device manager can see it but also states that it has no driver .......

I was wondering if you (or anyone else) had a copy of the original 16IC-c driver.

According to ATIK it was missed of the latest Artemis software downloadable from the ATIK site.

[NickK]

Well........ I've tried and tried.

I have visited the site that created the fdtichip-id program and followed all the instructions as far as can and it still yields nothing.

I am however not a PC person being a long term mac user - which explains my desire to get it working on a mac.

so ...... I'm taking it to a friend to see if he can get to the bottom of the FDTIChip-ID issue.

In the mean time .......

As the device manager can see it but also states that it has no driver .......

I was wondering if you (or anyone else) had a copy of the original 16IC-c driver.

According to ATIK it was missed of the latest Artemis software downloadable from the ATIK site.

I'll have to switch over to the Mac Mini later (it has my windows install and main development environment) to trouble shoot this. Also have two job interviews over the next week just waiting to hear back from the main dates.

[niknak]

Finally !!!!!

Yay.

I contacted Atik and they sent the usb1 and usb2 drivers.

Once installed into windows, the chipID program could see and talk to the camera.

Got the serial number and the ChipID - see below.

[NickK]

Superb!

So the serial number and the chip id are what you need. This can be tested on the OpenPHD2 by adding the values into the settings window. Also you should be able to add this to the ExampleApp as a test bed.

I have just got an email from Craig around updating the drivers for Neb too, so after much badgering I think I should have time tomorrow to make a move on this (the mrs is out with old work colleagues). 

[niknak]

Superb!

So the serial number and the chip id are what you need. This can be tested on the OpenPHD2 by adding the values into the settings window. Also you should be able to add this to the ExampleApp as a test bed.

I have just got an email from Craig around updating the drivers for Neb too, so after much badgering I think I should have time tomorrow to make a move on this (the mrs is out with old work colleagues). 

Have added into ExampleApp and nothing happens - well, noting more than if you didn't have the camera plugged in at all.

In PHD2 I get the following error message.

[NickK]

Have added into ExampleApp and nothing happens - well, noting more than if you didn't have the camera plugged in at all.

In PHD2 I get the following error message.

Ok, stage two - getting the right FTDIChipID byte sequence to be passed. With OpenPHD2 can you do the following:

1. Disconnect the camera physically

2. Go into the ATIK camera setting - show me the number you have put in the boxes for the FTDIChipID, also select enable logging. Note these values are global to all profiles if I remember correctly.

3. Ok. so you're back on the connect/disconnect 

4. Connect the camera physically, then connect in OpenPHD2.

5. Wait for the connection then attempt to loop the exposures - this is likely disconnect if there's a wrong id.

6. Close OpenPHD and send me the driver log file on the backdrop (ATIKOSXDrivers.log).

In that it should show me if the id is being passed and if the byte sequence is correct. (i.e. the FTDIChipID).

[NickK]

What I mean by the byte ordering is 0x1A54F5C9 becomes 0xc9f5541a. It's been so long since I've done my 16IC that I can't remember which way around.

edit: no I was talking out of my behind. It's when you're packet sniffing the FTDIChipID you have to byte order.

My 16IC is  "Chip ID: 0x0EE8F4C9" so in the window you'd just put "ee8f4c9" (with out leading 0x hex indicator or leading zeros). Note the serial number will be case sensitive. 

[niknak]

Have you got an email address to send it to ??

or you you like the contents in forum ??

[NickK]

Have you got an email address to send it to ??

or you you like the contents in forum ??

Hi - send it atikosxdrivers@adrenalin-junkie.net (benefit of owning the domain).

[NickK]

Hi, just looked at the log:

553aaeb7.55005 : Using FTDIChipID 0xee4f5c9 for serial number 'A3001QH8'

D: 553aaeb7.55030 : CameraState transitioning from 0 to 1.

D: 553aaeb7.55031 : CameraState transitioning from 1 to 0.

D: 553aaeb7.554a0 : ReadUSB 1 bytes to read

I: 553aaeb7.57f19 : CRITICAL PROBLEM

I: 553aaeb7.57f3d : CRITICAL PROBLEM: VUSBID NOT CORRECT (check your FTDI chip ID 0xee4f5c9 - the camera will not download images)

I: 553aaeb7.57f40 : CRITICAL PROBLEM

D: 553aaeb7.57fa9 : ++ Identified: ART: 0403 df36 'A3001QH8' ++

D: 553aaeb7.57fc5 : Flushing..

Looks like that the FTDIChipID being used is 0xee4f5c9 (i.e. my 16ic) rather than your 0x1A54F5C9.

Later on, for each exposure:

  
D: 553aaec1.b5162 : **** FTDI CHIP ID VALIDATION FAILED - CAMERA WILL NOT SEND IMAGES - NO IMAGE DOWNLOADED - CHECK ID PROVIDED TO DRIVER ****

So this is the problem.. now we need to get down to getting your FTDIChipID number passed through instead. 

[niknak]

Hi, just looked at the log:

Looks like that the FTDIChipID being used is 0xee4f5c9 (i.e. my 16ic) rather than your 0x1A54F5C9.

Later on, for each exposure:

So this is the problem.. now we need to get down to getting your FTDIChipID number passed through instead. 

But that is the right ChipID (in the log file) isn't it ??

yours was ee8f4c9 and not  ee4f5c9 which is mine.

[NickK]

the log shows 0x0ee4f5c9 is being used (mine), when it should be 0x1A54F5C9. I've added the 0 that normally sits in front of my ftdichipid.

Nebulosity 3.3.2 has a problem here.. because it allows the serial number to be changed but not the FTDIChipID IIRC (rather than a pair of values). I've fed that to Craig already - he's asked for an update on the drivers for Neb.

On OpenPHD2 - this will work with setting the FTDI table numbers as:

Mine: "A3001QH8" -> "ee8f4c9"

Yours: "A3001QH8" -> "1a54f5c9"

In Nebulosity that will be the FTDIChipID in the preferences to "1a54f5c9".

[niknak]

the log shows 0x0ee4f5c9 is being used (mine), when it should be 0x1A54F5C9. I've added the 0 that normally sits in front of my ftdichipid.

Nebulosity 3.3.2 has a problem here.. because it allows the serial number to be changed but not the FTDIChipID IIRC (rather than a pair of values). I've fed that to Craig already - he's asked for an update on the drivers for Neb.

On OpenPHD2 - this will work with setting the FTDI table numbers as:

Mine: "A3001QH8" -> "ee8f4c9"

Yours: "A3001QH8" -> "1a54f5c9"

In Nebulosity that will be the FTDIChipID in the preferences to "1a54f5c9".

Just tried to change the chipid in openphd2 as requested but it doesn't see to want to save.

It just keeps defaulting back to the "ee" beginning?

It wont allow me to insert my "1a54f5c9" code

[NickK]

Just tried to change the chipid in openphd2 as requested but it doesn't see to want to save.

It just keeps defaulting back to the "ee" beginning?

It wont allow me to insert my "1a54f5c9" code

Small issue with the implementation with wxWidgets toolkit todo with having to press return at the end of the editing. Change the number in OpenPHD2, then before you click ok, press Enter - the table will then accept your edit. Select OK and when you return back to the camera settings it should appear changed.

Doing this on my OpenPHD2 by changing the first 'e' to 'a' gives the following in the logs:

I: 553b56ec.6dee2 : Legacy registerFTDIChipId adding mapping [A3001QH8] = 0xae8f4c9

So that is looking like it's just the enter key press at the end of editing that's required. There are some differences in User Experience that wxWidgets doesn't match OS X out of the box, will need to look in how that can be done with that particular widget without pressing Enter in a later release. 

[niknak]

Right.....

Got PHD2 to accept the correct ChipID using the method you state so some small progress.

I now get a white window inside the normally black window of PHD2 (see below)

I asked it to log before starting so I have emailed you the most current log file just now.