ASCOM control EFW-USB1

[vladutz]

Hi
recently got this filterwheel. Any idea how to control this via the ASCOM driver? I use ASCOM 6.

I can see it comes with an Atik ASCOM driver (apart from the system driver), however when I try to install it  it says ASCOM 5 is required.

Any idea how I can use this wheel on the ASCOM 6?

[jonathan]

Hello,

Sorry not to have replied to this - another member has drawn my attention to it.

The latest core software installer provides the option to run an ASCOM 6 compliant installer for the EFW1 USB filterwheel - if you download it from the top of our downloads page at http://www.atik-cameras.com/support/downloads and run it, you will then need to select the option "ASCOM driver for Atik USB filterwheel" in the "Select Additional Components" window.

Best regards,

Jonathan

[BILL110366]

Hello

Quite new with all this, so forgive me if I miss something

I have a USB1 FW, and try to get it ON with my ASCOM setup.

I did all updates (ver 6 SP1 6.0.0.0.) and also ticked the USB FW during the ASCOM Core installation.

Now everytime I start the program, I get a little Window, saying either "Connect" or "Setup"

I may click either option, I always have an exception, talking about CLID and a long key.
I clicked on detail:
Any idea?

Thanks
Eric

Consultez la fin de ce message pour plus de détails sur l'appel du débogage
juste-à-temps (JIT) à la place de cette boîte de dialogue.

************** Texte de l'exception **************
System.Runtime.InteropServices.COMException (0x80040154): La récupération de la fabrique de classe COM pour le composant avec le CLSID {78B6AF10-6C12-41B0-8DA9-533271F5F05E} a échoué en raison de l'erreur suivante : 80040154.
   à System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
   à System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
   à System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
   à System.Activator.CreateInstance(Type type, Boolean nonPublic)
   à ASCOM.DriverAccess.MemberFactory..ctor(String progId, TraceLogger ascomDriverTraceLogger)
   à ASCOM.DriverAccess.FilterWheel..ctor(String filterWheelId)
   à FilterWheelTester.Form1.btConnect_Click(Object sender, EventArgs e)
   à System.Windows.Forms.Control.OnClick(EventArgs e)
   à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   à System.Windows.Forms.Control.WndProc(Message& m)
   à System.Windows.Forms.ButtonBase.WndProc(Message& m)
   à System.Windows.Forms.Button.WndProc(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Assemblys chargés **************
mscorlib
    Version de l'assembly : 2.0.0.0
    Version Win32 : 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    CodeBase : file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
FilterWheelCommander
    Version de l'assembly : 1.0.0.0
    Version Win32 : 1.0.0.0
    CodeBase : file:///C:/Program%20Files%20(x86)/Common%20Files/ASCOM/FilterWheel/FilterWheelCommander.exe
----------------------------------------
System.Windows.Forms
    Version de l'assembly : 2.0.0.0
    Version Win32 : 2.0.50727.5460 (Win7SP1GDR.050727-5400)
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Version de l'assembly : 2.0.0.0
    Version Win32 : 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Version de l'assembly : 2.0.0.0
    Version Win32 : 2.0.50727.5462 (Win7SP1GDR.050727-5400)
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
ASCOM.DriverAccess
    Version de l'assembly : 1.0.6.0
    Version Win32 : 6.0.10028.2207
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/ASCOM.DriverAccess/1.0.6.0__565de7938946fba7/ASCOM.DriverAccess.dll
----------------------------------------
ASCOM.Interfaces
    Version de l'assembly : 1.0.0.0
    Version Win32 : 1.0.0.0
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/ASCOM.Interfaces/1.0.0.0__565de7938946fba7/ASCOM.Interfaces.dll
----------------------------------------
ASCOM.Utilities
    Version de l'assembly : 6.0.0.0
    Version Win32 : 6.0.10028.2207
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/ASCOM.Utilities/6.0.0.0__565de7938946fba7/ASCOM.Utilities.dll
----------------------------------------
System.Core
    Version de l'assembly : 3.5.0.0
    Version Win32 : 3.5.30729.5420 built by: Win7SP1
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Microsoft.VisualBasic
    Version de l'assembly : 8.0.0.0
    Version Win32 : 8.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
mscorlib.resources
    Version de l'assembly : 2.0.0.0
    Version Win32 : 2.0.50727.5456 (Win7SP1GDR.050727-5400)
    CodeBase : file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
System.Windows.Forms.resources
    Version de l'assembly : 2.0.0.0
    Version Win32 : 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase : file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_fr_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------

************** Débogage JIT **************
Pour activer le débogage juste-à-temps (JIT), le fichier de configuration pour cette
application ou cet ordinateur (machine.config) doit avoir la valeur
jitDebugging définie dans la section system.windows.forms.
L'application doit également être compilée avec le débogage
activé.

Par exemple :

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

Lorsque le débogage juste-à-temps est activé, les exceptions non gérées
seront envoyées au débogueur JIT inscrit sur l'ordinateur
plutôt que d'être gérées par cette boîte de dialogue.

[bhfisher]

Seems that I have the same problem,
Havent used the kit all summer, upgraded the Laptop and running Win 7 Pro.

Everthing installes and works OK apart from my EFW1.

Running Ascom 6SP1. Have tried both the latest core software installer and the Filter wheel CD version on the Website. The CD Version downloads with ASCOM V5, tried running with this without sucess. ASCOM 6SP1 can be configured to install the CD version of the software by adding the Atik Setup programme to the “ForcePlatformVersion in the Profiler Explorer, unfortunatly didnt help either.

Maxim DL has the Atik Filter Wheel in its ASCOM list but wont connect.

Attempting to connect using the Atik filter wheel control software produces the 'exception error' similar to the last post.

The issue seems to be Windows not accepting the driver. It recognises the device but wont install the driver (either version). Have followed the Win7 Driver installation instruction on the website. Have also manually pointed the device at the driver location, let it search and pointed it at the C drive with subfolders selected, still wont load.

Any advice would be appreciated if anyone manages to solve the problem.

Cheers

[BILL110366]

Hello,

Atik Staff??? any idea?
cheers
Eric

[Jerryaxe]

Hi Rui

Any idea?

is this bug resolved cause I need to upgrade to the latest version of ASCOM and don't want to loose my filter wheel?

Thanks

Jerri

[shiraz]

same problem, but found what I was doing wrong.

The core installer told ASCOM6 about the filter wheel, but did not install the Windows driver.
TheWindows 7 driver  loading process  http://www.atik-cameras.com/external/InstallingDriverswithWindows7_64bit.pdf  worked, but only when I downloaded the "drivers" package  from the "software" section - not when I download the USB1 filter wheel specific drivers from the "installation CD" section of the download page (which of course is what I did first).
 
Now running well under ASCOM6, but took about 3 hours of hair pulling to get to that state - needs some Atik housekeeping

[zalt]

Thank you shiraz, for sharing your success recipe.

No success or me though, on 64-bit Windows 8.

Bought the EFW-USB1 a year ago.
At that time I installed and used the wheel on a 32-bit Windows 7 notebook, using the CD http://www.atik-cameras.com/external/Website/Downloads/USBFilterWheel_CD.zip and upgraded to ASCOM 6SP1.
The filter wheel worked ok, but wasn't useful in this configuration as the computer was too slow for proper USB camera transfer.

Just got a powerful Win8x64 notebook, but cannot get past the the COMException error when clicking Connect or Setup after starting C:\Program Files (x86)\Common Files\ASCOM\FilterWheel\FilterWheelCommander.exe.
I have tried a number of times, with "all posible combinations". Also when starting fully clean, in this order:

• Installing ASCOM 6SP1.
• Installing http://www.atik-cameras.com/external/Website/Downloads/AtikDrivers.zip (2nd on http://www.atik-cameras.com/support/downloads)
• Installing http://www.atik-cameras.com/external/Website/Downloads/SetupArtemisUniversal.exe (1st on http://www.atik-cameras.com/support/downloads), selecting only the driver for EFW-USB1.
• From the Windows Device Manager, adding/updating driver using the USB1 folder from step two.

Running as administrator does not help.
There's also a shortcut for C:\Program Files (x86)\Atik\ArtemisCCD\FilterWheelRunner.exe, but the Connet-chekbox (only enabled control) apparently does nothing.

Atik support, any clue?
I assume this is not because of Windows 8, simply because the installer material is a bit messy.
Thanks anyway.

And I would have saved time and bought the USB2 wheel if I could find email support for Atik. (reminding me of my upcoming CCD purchase for my Hyperstar)

-olav

[Jerryaxe]

Atik team,

I have the same issue as the others.
I bought a new laptop for imaging with Windows 7 pro and ascom V6.
My camera is fully recognized by the Ascom driver (Atik 4000
) and I can get whatever software to work with it.
For the filter wheel v1, I used the different drivers on the website and nothing works. Even the filterwheel soft can't connect to it and gives me the error message below (same as Bill 110366).
I tried all dirvers and USB1 drivers as well..... don't ask I already tried.

The error message is still the same ie error 80040154

What do we need to make it work? The filter wheel is still working perfectly on my old laptop with Ascom 5.5 and the old drivers (windows XP).... Unfortunately, my old computer is about to die and works only once in a blue moon which is why I have to change.

A clear answer is required now otherwise I will have to bin my fully fonctional filterwheel due to lack of support and buy a new one.
 
If nothing is done, I will be happy to share the news on all forums in France, UK, Australia and US.

Jerry, a non impressed customer....

P.S : the filterweel works under artenmis capture ? but only on this one and nothing else.

[Steve]

Good Morning,
Sorry to be slow to response to this but please do read the sticky notes at the top of the boards.  If you would like a response from Atik please contact Support at Atik-cameras.com
The EFW1 is a discontinued product so we can’t promise it will be working with modern PC hardware indefinitely.  However it does work fine on our win7 64 bit systems under ASCOM with the software updates on our website.  If you would like Atik help with these Support at Atik-Cameras.com is the place to go.
Best
Steve   

[Steve]

Hello Again,

Should have added this on to the end of the last message.  It might help

Best
Steve

The FilterWheelCommander program cannot be used to control the USB1 filterwheel with 64-bit versions of Windows.   However, the USB1 filterwheel can be controlled both using Artemis Capture and through ASCOM.  To get this working, you will need to install the drivers (instructions and download link are in the "Drivers" section of our downloads page http://www.atik-cameras.com/support/downloads),  ensure that the ASCOM framework is installed if ASCOM control is required (see http://ascom-standards.org/), then run the Atik core software installer (available for download at the top of our downloads page http://www.atik-ameras.com/support/downloads), checking the "ASCOM driver for Atik EFW1 filterwheel" option in the "Select Additional Components" window if ASCOM control is required.   Incidentally, "FilterWheelRunner" only works with EFW2 filterwheels.

[Jerryaxe]

Thanks Steve

Problem solved. You absolutely need to use the usb1 driver otherwise it does not work on windows 7 64.

For those who still have an issue, please let me know and I will try to help.

Steve, regarding the support, I think that provided we use the ascom platform to use the filter wheel, there should be no real difference in the code. W8 will be sonn W9 as it was only developped to get back on track with the tablets which have 99% dna of w7.
The main change may come from ascom newer versions....

[bergleopard]

I was pending with this nearly one year ago, no Chance to make this filter wheelrunning on Windows 7 64. I wrote to Atik Support; got no answer.
This night I tried it again to install this EFW USB1 on my new Windows 7 64bit labtop
Now I saw this postings , and tried to follow the described procedure. No success via ascom , Astroart or Atik software
But even my supplier (Teleskop-Service) did not got any solution or answer from Atik and can solve this problem with his educated technical People.
I realy do not understand why Atik was still selling such products when it does not work on current Computer Software like Windows 7 64 bit and announed by time how to procede and supply the Software update and let the customers searching arround, unbelievable bad habit; its realy a very bad bad Support and behaviour of this Company.