×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

ZWO EFWmini (filter wheel)

  • Posts: 79
  • Thank you received: 23

Replied by rumen on topic ZWO EFWmini (filter wheel)

David,
Pic du Midi is a nice place i love it :)
We have a collaboration with the people there, if you meet Eric Joselin (the current director of TBL) or Remi Cabanac (the former) say Hi to them from me :)
Eric was here 2 weeks ago.

Are you a professional Astronomer?

best
Rumen
Last edit: 7 years 4 months ago by rumen.
7 years 4 months ago #12639

Please Log in or Create an account to join the conversation.

  • Posts: 14
  • Thank you received: 0

Replied by BREGOU on topic ZWO EFWmini (filter wheel)

Rumen,
It is so unexpected, you know people of the Pic du Midi !!!
I have met Remi Cabanac when i went to the Pic two years ago.
He makes us visiting "his" 2m telescope :-)
Unfortunately I'm not a professional astronomer but an "amateur".
I go to the Pic as an amateur. There is an old professional telescope, we call the "T60", that we can use.
You have some delail here : www.astrosurf.com/t60/
I also kow the professional that use the 1m telescope.

The goal of our week at the Pic du midi is to do some spectroscopy.
A friend and I, we are working with a professionnal on some targets that we study in spectoscopy.

Of course I also do love the Pic, it's a so wonderful place (especialy in winter with the snow !)

It's my turn to ask you, you are a professional astronomer ? what kind of collaboration do you have with the TBL ?
Here is my mail : dbregou at gmail dot com
Regards
David
7 years 4 months ago #12651

Please Log in or Create an account to join the conversation.

  • Posts: 79
  • Thank you received: 23

Replied by rumen on topic ZWO EFWmini (filter wheel)

Hi David
I am only part time professional astronomer :)
We use TBL to obtain data to study the magnetic structure of giant stars.

Enjoy at the Pic :)
Rumen
7 years 4 months ago #12655

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic ZWO EFWmini (filter wheel)

I am using Arch Linux with libindi 1.3.1-1
libindi-3rdparty 1.3.1-1-x86_64
kstars 16.12.0-1 (Version 2.7.2)

asi1600mm-cool connects and talks nicely to kstars
So I tried to get the EFWmini filterwheel working

I am having some problems with the wheel.

Kstars gives me;
2016-12-23T17:22:43 Unable to establish:
+ ASI Wheel
Please ensure the device is connected and powered on.

I edited the udev/rules.d/99-asi.rules as suggested
# FILTER WHEELS
#ATTR{product}=="ZWO EFW" ATTR{idVendor}=="03c3" ATTR{idProduct}=="1f01" GROUP="users", MODE="0666"
KERNEL=="hidraw*",ATTRS{idVendor}=="03c3",ATTRS{idProduct}=="1f01",GROUP="users",MODE="0666"

Threw in
$ sudo udevadm control --reload-rules
and even rebooted to be absolutely sure

Same thing.


I then tried to get more information about the problem, started indiserver locally and then asked kstarts to connect to that instance.
indiserver -vv indi_asi_wheel
2016-12-23T17:19:10: startup: indiserver -vv indi_asi_wheel
2016-12-23T17:19:10: Driver indi_asi_wheel: pid=1405 rfd=3 wfd=6 efd=7
2016-12-23T17:19:10: listening to port 7624 on fd 4
2016-12-23T17:19:10: Driver indi_asi_wheel: sending <getProperties version='1.7'/>

2016-12-23T17:19:10: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:19:10: Driver indi_asi_wheel: read <defTextVector device='EFW' name='DRIVER_INFO'>
2016-12-23T17:19:10: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='DEBUG'>
2016-12-23T17:19:10: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='SIMULATION'>
2016-12-23T17:19:10: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONFIG_PROCESS'>
2016-12-23T17:19:25: Client 0: new arrival from 127.0.0.1:42554 - welcome!
2016-12-23T17:19:25: Client 0: read <getProperties device='' name=''>
2016-12-23T17:19:25: Driver indi_asi_wheel: queuing responsible for <getProperties device='' name=''>
2016-12-23T17:19:25: Driver indi_asi_wheel: sending <getProperties version="1.7"/>

2016-12-23T17:19:25: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:19:25: Client 0: queuing <defSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:19:25: Driver indi_asi_wheel: read <defTextVector device='EFW' name='DRIVER_INFO'>
2016-12-23T17:19:25: Client 0: queuing <defTextVector device='EFW' name='DRIVER_INFO'>
2016-12-23T17:19:25: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='DEBUG'>
2016-12-23T17:19:25: Client 0: queuing <defSwitchVector device='EFW' name='DEBUG'>
2016-12-23T17:19:25: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='SIMULATION'>
2016-12-23T17:19:25: Client 0: queuing <defSwitchVector device='EFW' name='SIMULATION'>
2016-12-23T17:19:25: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONFIG_PROCESS'>
2016-12-23T17:19:25: Client 0: queuing <defSwitchVector device='EFW' name='CONFIG_PROCESS'>
2016-12-23T17:19:25: Client 0: sending <defSwitchVector device="EFW" name="CONNECTION" la
2016-12-23T17:19:25: Client 0: sending <defTextVector device="EFW" name="DRIVER_INFO" lab
2016-12-23T17:19:25: Client 0: sending <defSwitchVector device="EFW" name="DEBUG" label="
2016-12-23T17:19:25: Client 0: sending <defSwitchVector device="EFW" name="SIMULATION" la
2016-12-23T17:19:25: Client 0: sending <defSwitchVector device="EFW" name="CONFIG_PROCESS
2016-12-23T17:19:25: Client 0: read <enableBLOB device='EFW' name=''>
2016-12-23T17:19:31: Client 0: read <newSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:19:31: Driver indi_asi_wheel: queuing responsible for <newSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:19:31: Driver indi_asi_wheel: sending <newSwitchVector device="EFW" name="CONNECTION">

2016-12-23T17:19:31: Driver indi_asi_wheel: read <message device='EFW' name=''>
2016-12-23T17:19:31: Client 0: queuing <message device='EFW' name=''>
2016-12-23T17:19:31: Client 0: sending <message device="EFW" timestamp="2016-12-23T17:19:
2016-12-23T17:19:31: Driver indi_asi_wheel: read <setSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:19:31: Client 0: queuing <setSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:19:31: Client 0: sending <setSwitchVector device="EFW" name="CONNECTION" st
2016-12-23T17:20:17: Client 0: read <newSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:20:17: Driver indi_asi_wheel: queuing responsible for <newSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:20:17: Driver indi_asi_wheel: sending <newSwitchVector device="EFW" name="CONNECTION">

2016-12-23T17:20:17: Driver indi_asi_wheel: read <setSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:20:17: Client 0: queuing <setSwitchVector device='EFW' name='CONNECTION'>
2016-12-23T17:20:17: Client 0: sending <setSwitchVector device="EFW" name="CONNECTION" st

Any ideas?
7 years 3 months ago #13295

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic ZWO EFWmini (filter wheel)

Following up on the above.

I have tried using indiserver on my raspberry Pi 3. Using the latest snap shot.

When I plug the USB cable from the EFW straight into my pi the electric shock symbol (low voltage appears) on the pi screen,
while the filter wheel is homeing back to its position.

It rotates nicely. :-)

indiserver -v indi_asi_wheel indi_simulator_ccd
2016-12-23T21:59:31: startup: indiserver -v indi_asi_wheel indi_simulator_ccd
2016-12-23T21:59:31: Driver indi_asi_wheel: pid=1497 rfd=3 wfd=6 efd=7
2016-12-23T21:59:31: Driver indi_simulator_ccd: pid=1498 rfd=4 wfd=9 efd=10
2016-12-23T21:59:31: listening to port 7624 on fd 5
2016-12-23T21:59:31: Driver indi_simulator_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-12-23T21:59:31: Driver indi_simulator_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-12-23T21:59:31: Driver indi_simulator_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-12-23T21:59:31: Driver indi_simulator_ccd: snooping on CCD Simulator.FILTER_NAME
2016-12-23T21:59:31: Driver indi_simulator_ccd: snooping on SQM.SKY_QUALITY
2016-12-23T21:59:31: Driver indi_simulator_ccd: snooping on Telescope Simulator.EQUATORIAL_PE
2016-12-23T21:59:31: Driver indi_simulator_ccd: snooping on Focuser Simulator.FWHM
2016-12-23T21:59:34: Client 0: new arrival from 192.168.1.1:55494 - welcome!
2016-12-23T22:00:40: Client 0: read EOF
2016-12-23T22:00:40: Client 0: shut down complete - bye!

I then tried kstars on my desktop and connected to the pi indiserver.
When I try to connect to the EFW I get;
Connect():EFWOpen()=4

From 3rdparty/indi-asi/EFW_Filter.h I see;
typedef enum _EFW_ERROR_CODE{
EFW_SUCCESS = 0,
EFW_ERROR_INVALID_INDEX,
EFW_ERROR_INVALID_ID,
EFW_ERROR_INVALID_VALUE,
EFW_ERROR_REMOVED, //failed to find the filter wheel, maybe the filter wheel has been removed
EFW_ERROR_MOVING,//filter wheel is moving
EFW_ERROR_ERROR_STATE,//filter wheel is in error state
EFW_ERROR_GENERAL_ERROR,//other error
EFW_ERROR_NOT_SUPPORTED,
EFW_ERROR_CLOSED,
EFW_ERROR_END = -1
}EFW_ERROR_CODE;

So presumably this means kstars thinks my filter wheel has error code EFW_ERROR_REMOVED

I will try to find a powered hub and see if it works with that.
7 years 3 months ago #13297

Please Log in or Create an account to join the conversation.

  • Posts: 79
  • Thank you received: 23

Replied by rumen on topic ZWO EFWmini (filter wheel)

Yes most likely the lack of power is the problem. Good powered USB hub should work. I am saying "good" because my experience is that the cheap powered hubs usually do the things worse...

Rumen
The following user(s) said Thank You: Adrian
7 years 3 months ago #13300

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic ZWO EFWmini (filter wheel)

Still no luck.

I tried two different powered USB hubs, similar error.
Latest indi on raspberry Pi II as the server with the EFW connected to the powered USB hub.
When I connect the EFW there is no low voltage on the PI. The filter wheel homes its position.
I start indiserver on the pi
$ indiserver -vv indi_asi_wheel indi_simulator_ccd

The log is attached below:

File Attachment:

File Name: log.txt
File Size:9 KB



I use Kstars on my desktop (this time I tried the Ekos virtual machine and updated all the software (indi-full and kstars-bleeding)
I use the Ekos icon in kstars to connect to the server on the pi (the option for asi-wheel is present after the software upgrade).
When I select Connect for EFW the LED icon stays red and the log window in indi says
Connect::EFWOpen() = 4

Meanwhile the log window in Ekos says
EFW is disconnected

7 years 3 months ago #13304
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic ZWO EFWmini (filter wheel)

:(
Still scratching head.

Tried the EFW on Win 10 using Ascom, it appears to work.
I noticed that the Motor on the front says China instead of Japan ? different batch.

Anyhow I poked asi_wheel.cpp and inserted a few debugging lines.
 
bool ASIWHEEL::Connect() {
	EFW_ERROR_CODE result;
 
        // Procras Start
        DEBUGF(INDI::Logger::DBG_ERROR, "%s(): Procras** Connect fw_id %d", __FUNCTION__, fw_id);
        DEBUGF(INDI::Logger::DBG_ERROR, "%s(): Procras** Connect fw_index %d", __FUNCTION__, fw_index);
        DEBUGF(INDI::Logger::DBG_ERROR, "%s(): Procras** Connect num_wheels %d", __FUNCTION__, num_wheels);
        // Procras End
 
 
	if (isSimulation()) { 

When i click connect in the indi control panel I see
2016-12-25T14:47:59: Connect(): EFWOpen() = 4
2016-12-25T14:47:59: Connect(): Procras** Connect num_wheels 1
2016-12-25T14:47:59: Connect(): Procras** Connect fw_index 0
2016-12-25T14:47:59: Connect(): Procras** Connect fw_id -1
2016-12-25T14:47:46: Debug is enabled.

I am encouraged by the num_wheels 1
7 years 3 months ago #13311

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic ZWO EFWmini (filter wheel)

:)

I downloaded the ZWO EFW_linux_mac_SDK and compiled the test_console application and
it rotates the wheel nicely.
It uses the library libEFWFilter.so.0.2.1116 dated Mon 12 Dec 2016 03∶28∶32 GMT

The indi-1.3.1/3rdparty/indi-asi/libEFWFilter.bin is some strange format and is dated Tue 15 Nov 2016 06∶36∶51 GMT

Now I have to figure out how to compile and indi_asi_wheel using the new library.
Last edit: 7 years 3 months ago by Adrian. Reason: typo xo instead of so
7 years 3 months ago #13312

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic ZWO EFWmini (filter wheel)

:)
It works !! (on both raspberry pi 3 (Jessie with latest indi for raspberry pi) and my desktop (Arch Linux)
But there are two required conditions
1: You MUST start indiserver as root with sudo

Good;
$ sudo indiserver -v indi_asi_wheel indi_simulator_ccd

Bad;
$ indiserver -v indi_asi_wheel indi_simulator_ccd

and
2: You MUST ensure that the Filter Wheel is in position 1 (ie when it connects it assumes the filter wheel is in position 1, instead of checking where it is first)

Now why must indiserver be run as root?
Last edit: 7 years 3 months ago by Adrian. Reason: pi3 not pi2
7 years 3 months ago #13314

Please Log in or Create an account to join the conversation.

  • Posts: 85
  • Thank you received: 40

Replied by Hans on topic ZWO EFWmini (filter wheel)

I run indiserver not as root and my ASI filter wheel works fine.
So there must be something wrong with your udev rules where you need to run it as root.

Oh, and I also do not have to make sure the wheel is at position 1 when starting indiserver.

-- Hans
The following user(s) said Thank You: Adrian
Last edit: 7 years 3 months ago by Hans. Reason: add wheel remark
7 years 3 months ago #13315

Please Log in or Create an account to join the conversation.

  • Posts: 89
  • Thank you received: 16

Replied by Adrian on topic ZWO EFWmini (filter wheel)

Thanks for the suggestion regarding permissions.

I am fighting to fix my permissions problem but still don't know what is wrong.

I wonder if indi is doing something weird. I can access and control the filter wheel as my ordinary user using the SDK, but
I can only use it in indi if I start indiserver as the super user.

Server:Raspberry Pi III on jessie and latest indi
indi on server started on cli after ssh to box, see examples below

Client:Kstars 2.7.2 Arch Linux (kstars 16.12.0-1)
Indi on client started via EKOS in Kstars, profile set to CCD Simulator as you
cannot start without specifying at least CCD Simulator.

2016-12-28 20:08 REBOOT Raspberry PI 3

Have a quick peek around
pi@astropie:~ $ more /lib/udev/rules.d/99-efw.rules 
# FILTER WHEELS
KERNEL=="hidraw*", ATTRS{idVendor}=="03c3", ATTRS{idProduct}=="1f01", GROUP="users", MODE="0666"
 
pi@astropie:~ $ dmesg | grep EFW
[    3.282382] usb 1-1.4.2.3: Product: ZWO EFW
[    3.292212] hid-generic 0003:03C3:1F01.0001: hiddev0,hidraw0: USB HID v1.01 Device [ZW0 ZWO EFW] on usb-3f980000.usb-1.4.2.3/input0
 
pi@astropie:~ $ lsusb
Bus 001 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 010: ID 03c3:1f01  
Bus 001 Device 009: ID 1618:0921  
Bus 001 Device 008: ID 03c3:1603  
Bus 001 Device 007: ID 04b4:6572 Cypress Semiconductor Corp. 
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 
pi@astropie:~ $ ls -l /dev/usb
total 0
crw------- 1 root root 180, 96 Dec 28 20:06 hiddev0
 
pi@astropie:~ $ ls -l /dev/hidraw0
crw-rw-rw- 1 root users 247, 0 Dec 28 20:06 /dev/hidraw0
 

hidev0 is root:root with 0600
hidraw0 is root:users with 0666

I am not sure here if the permissions on hiddev0 should be the same as those on hidraw0
pi@astropie:~ $ groups
pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi
pi@astropie:~ $ cat /etc/group | grep users
users:x:100:pi
 

The users group exists in /etc/group and pi is a member of users

Now try to run indiserver
pi@astropie:~ $ indiserver -v indi_asi_wheel indi_asi_ccd indi_moonlite_focus indi_eqmod_telescop
 

Get the EFWOpen(): Error as usual if trying to connect to the filter wheel.

Poke Around
pi@astropie:~ $ ls -l /dev/usb
total 0
crw------- 1 root root 180, 96 Dec 28 20:06 hiddev0
 
pi@astropie:~ $ ls -l /dev/hidraw0
crw-rw-rw- 1 root users 247, 0 Dec 28 20:06 /dev/hidraw0
 

Now shut indiserver down and restart as root

According to Jasem

ATTENTION: Never ever run indiserver or KStars as root user. Not only it is a bad practice security-wise, but it can lead sometimes to unexpected behavior and poor performance. Only run as root when strictly necessary and you know what you are doing.
pi@astropie:~ $ sudo indiserver -v indi_asi_wheel indi_asi_ccd indi_moonlite_focus indi_eqmod_telescop
 

The filter wheel connects and we can work away

Poke around in a terminal
pi@astropie:~ $ ls -l /dev/usb
ls: cannot access /dev/usb: No such file or directory
pi@astropie:~ $ ls -l /dev/hidraw0 
ls: cannot access /dev/hidraw0: No such file or directory


Can someone check if they have /dev/usb/hidev0 and its permissions?

Has anyone else seen /dev/hidraw0 and /dev/usb/hiddev0 disappear?
Last edit: 7 years 3 months ago by Adrian. Reason: Typo on hidraw0 as 0600 when it is 0666
7 years 3 months ago #13335

Please Log in or Create an account to join the conversation.

Time to create page: 1.123 seconds