Astronomy Hardware - NexImage CCD Camera

[Timothy]

There doesn't seem to be an "Astronomy Hardware" forum, so this seemed my next best bet...

I have a NexImage CCD camera for astrophotography.  It is based on a Sony CDD and a Phillips controller.  It configures under Windows XP/7 using the Phillips SPC900NC driver.

With PCLinuxOS, it appears in Hardware under Webcams as "Unknown":
Vendor: ‎AME Optimedia Technology Co., Ltd
Description: ‎Unknown
Media class: ‎
Connection Bus: ‎USB
Bus PCI #: ‎2
PCI device #: ‎5
Vendor ID: ‎0x06be
Device ID: ‎0x8116
Misc
Module: ‎pwc

It is available for selection in wxCam as /dev/video1. However, it just doesn't work.  wxCam freezes up and only unfreezes when the NexImage is unplugged.  I did some Googling around, and it seems as if it should work... others seem to have had success under other Linux flavours.

Are there any Linux astronomers out there who can offer advice?

Thanks for any help.

[T6]

if the module says unknown this is because there is no module loaded to handle this device, no driver

do you know what driver handles this particular camera?

could be a simple module to load in the kernel or that the kernel we use doesn't have it and you need to add it, something that can be done

[nerdful1]

I use an SBIG st-2000xcm imager, and have a dedicated laptop for observing.

I tinkered with Linux and the imager last year, then decided to use the default XP, since it will be supported for a couple years, and give time to pursue a pure Linux setup.
Also the Meade Autostar doesn't run under wine, etc.

Another reason I shelved Linux was because I was waiting for the dust to settle for my favorite Linux distro, and preferred to wait.

SBIG had quite a bit of Linux support until the developer died, but his stuff is still on the SBIG site.

Maybe someone smart here can get some hints from the Linux stuff posted there.
http://www.sbig.com/sbwhtmls/softpage.htm

As we speak, I am dual booting the astro computer with 2010.2, and going to pack it with all but the imaging stuff like kstars, etc.

PCLinuxOS in the past always raised questions from the public when I was running the LX200GPS 16" with (What is this free os you are using?).

I'm willing to test anything that will lead to astro stuff being approved for the repo.

[SARGE-FMJ]

pwc was the old module for phillips cameras. I don't think it is still being developed. Current phillips cameras are supported with the uvcvideo and v4l2 drivers (I think I spelled it right). I would install them from the repository and blacklist the pwc driver and see if it configures with the uvcvideo v4l2 drivers.

Hope this helps.

[Never_More]

If you can't find a driver for it you could go get Crossover it is commercial based windows emulator.  I think you can run it that way matter fact I am pretty sure you can.

[Timothy]

First: Thanks Nerdful1 for the suggestions, I'll go check out the link you sent.  I was running dual-boot too, but now I've switched to XP in a VirtualBox virtual machine.  It runs seamlessly as a "Windows" window in PCLOS.  The only downside is that the package in the PCLOS repositories doesn't support USB, so I had to go and download VBox from the VirtualBox website and install it from their package.  And therein lies the rub... VBox-USB can't use the NexImage if PCLOS-USB can't configure it.  Everything else works perfectly (Nikon D80, USB/RS232 converter, NexHub COM port replicator).

Second: Thanks SARGE-FMJ.  I'll try blacklisting pwc and see what happens.  I'm not sure what my mileage will be as the NexImage is based on an older (circa 2006) Phillips controller.  I'll let you know how that goes...

Added 09:50EDT
Blacklisting pwc:  It certainly had an effect, but not the desired one.  The original Phillips controller must have supported sound too, because now it's configuring as "USB Sound Device" using Module:snd_usb_audio.

Is there a way to force the NexImage to use uvcvideo??

Added 12:30EDT
Now PCLOS is seeing it as a scanner... Module:usbcore.

I surrender!

[nerdful1]

Tried the new getvirtualbox, but usb still doesn't work, and like the previous post, the SBIG st-2000xcm is in the hardware list as a scanner.

[Old-Polack]

Tried the new getvirtualbox, but usb still doesn't work, and like the previous post, the SBIG st-2000xcm is in the hardware list as a scanner.

Did you install the VBox guest additions specific to the version installed? Did you then reboot both the guest and the host systems? USB working fine here with VirtualBox 3.2.4 r62467.

[nerdful1]

That doesn't come down with the get VB?

My searches here relate to older pclos, and OSE stuff.

Should I try crossover too? I have 1 day to get it at a discount, this has nothing to do with my recent tinkering with virtualbox, just a coincidence. Maybe because I tried crossover a year ago, they are emailing me. (Or reading the forum:))

Thanks

[Old-Polack]

That doesn't come down with the get VB?

My searches here relate to older pclos, and OSE stuff.

Should I try crossover too? I have 1 day to get it at a discount, this has nothing to do with my recent tinkering with virtualbox, just a coincidence. Maybe because I tried crossover a year ago, they are emailing me. (Or reading the forum:))

Thanks

The guest additions come with the VBox installation as an ISO image one mounts like an installation CD. The Guest additions must be installed separately on each individual VM created, while it is running, as each is a separate, unique machine, so far as the host system is concerned.

[nerdful1]

Oh, that thing. Ok, it says it is 'attached to ccdops'. Vboxguestadditions.iso 31.92MB.
CCDops is the name of the astronomy software that runs the imager.

CCDops installs without a hitch, along with a companion program that is a driver update checker.

They both run ok on their own.

When trying to communicate with the imager over the USB, is when it fails.

It also does the same thing under WINE.

I supposedly get a good deal until tomorrow for Crossover, but I bet I'll have the same problem.

I may just buy it just to have it for the experience, and another tool to have to wean others off Windows.

I gave up on this a year ago when after days of grief, found that the Intel processor on the new laptop locked out vm hardware.

Then I awaited 2010, and in meantime bought a machine with dual AMD chip, and vm hardware enabled.

Can never seem to be able to catch the ring as I go around this carousel.

Thanks

[Old-Polack]

Oh, that thing. Ok, it says it is 'attached to ccdops'. Vboxguestadditions.iso 31.92MB.
CCDops is the name of the astronomy software that runs the imager.

CCDops installs without a hitch, along with a companion program that is a driver update checker.

They both run ok on their own.

When trying to communicate with the imager over the USB, is when it fails.

It also does the same thing under WINE.

I supposedly get a good deal until tomorrow for Crossover, but I bet I'll have the same problem.

I may just buy it just to have it for the experience, and another tool to have to wean others off Windows.

I gave up on this a year ago when after days of grief, found that the Intel processor on the new laptop locked out vm hardware.

Then I awaited 2010, and in meantime bought a machine with dual AMD chip, and vm hardware enabled.

Can never seem to be able to catch the ring as I go around this carousel.

Thanks

One of us, at least, is having a problem understanding the other. I have no idea what you are trying to say in the blue line above.

From the start:

1. First you install VBox

2. Then you create a VM and install the OS.

3. From the running OS you install the guest additions.



4. Reboot the guest VM.

5. Shutdown the guest VM.

6. Reboot the host OS.

7. Start VBox.

8. Plug in the USB device then click Settings --> USB --> Add icon.

9. Check the box of the item from the menu.



When I choose EPSON USB2.0..., I get this;



10. Select Storage from the left pane.



11. Select the CD icon, then in the drop down menu select the physical drive, if you have a CD, or the ISO image to use.

12. Click the OK button.

13. Start the VM; when it's up and running, Devices --> USB Devices --> <Your device>



14. If your device is shown and checked it is connected, and you can now install the drivers and software it uses.

[nerdful1]

Yes, I had gone that far I believe.

I don't have the machine in front of me, but will try later.

I remember the part about selecting usb, I remember selecting the 2.0, and also it was seeing my lid camera, usb mouse, usb key, and the imager, although is says unknown device.

In PCC it would show the SBIG as a MFG, but listed as a scanner, with no firmware.

The old Linux software on the SBIG site is supposed to do some basic camera operations, and I didn't try as it involved either compiling, using outdated libraries and such, or using an old version of other distros, maybe red hat.

I would also like a solution not involving the purchase of a windows os. Wine doesn't need that, and I'm investigating crossover today as I remember no clue as to how far I went, or if Xover needs xp installed too, or if it is stand alone, if the paid version is locked to one machine, etc.

Then there is ReactOS to play with in a native install, but I want everything on PCLinuxOS ideally.

Please advise me on this thought:

I'll use a fresh computer with a linux distro shown on the SBIG instructions, and get it operational.

Then, would it be possible to say, lift the firmware files from it, or at least have someone knowlegeable figure out what is needed to run it on PCLOS.

Thanks.

Now off to read about xover for a bit

Thanks