×

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

Bi-monthly release with minor bug fixes and improvements

Command to get/set pos ZWO EFWmini

  • Posts: 10
  • Thank you received: 0
Could anyone let me know the command to get/set the position of ZWO EFWmini? Or the way to know them.
When I put indi_getprop, Therminal replied as
connect: Connection refused

What I would like to do is take images with DSLR/EFW from Bash script like this;

sudo python3 switch3.py #waiting for START by push button through GPIO on RPi3
#set EFW position 1 <—I want this!
sudo gphoto2 --set-config burstnumber=04
sudo gphoto2 --set-config shutterspeed2=006
sudo gphoto2 --capture-image
sudo gphoto2 --set-config shutterspeed2=012
sudo gphoto2 --capture-image
#set EFW positon 2
sudo gphoto2 --set-config burstnumber=04
sudo gphoto2 --set-config shutterspeed2=006
sudo gphoto2 --capture-image
sudo gphoto2 --set-config shutterspeed2=012
sudo gphoto2 --capture-image


gphoto2 commands work well.

I use; Pi3 raspbian, and ZWO EFWmini
INDI Library v1.4.1 based on:
www.indilib.org/download/raspberry-pi.html

Installed udev rule(Linux) based on:
"EFW filter wheel software Manual(Linux & OSX)"
astronomy-imaging-camera.com/manuals/EFW...Linux%20OSX%20EN.pdf

I got some info. from the terminal as shown below.

pi@ras_pi1:~ $ lsusb
Bus 001 Device 006: ID 1c4f:0027 SiGma Micro
Bus 001 Device 005: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 004: ID 03c3:1f01
Bus 001 Device 007: ID 04b0:0414 Nikon Corp.
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@ras_pi1:~ $ ls -l /dev/bus/usb/001/004
crw-rw-rw- 1 root users 189, 3 Mar 26 14:24 /dev/bus/usb/001/004

pi@ras_pi1:~ $ more /lib/udev/rules.d/99-efw.rules
# FILTER WHEELS
ACTION=="add", ATTRS{idVendor}=="03c3", ATTRS{idProduct}=="1f01", GROUP="users", MODE="0666"

pi@ras_pi1:~ $ ls -l /dev/hidraw0
crw-rw-rw- 1 root users 247, 0 Mar 26 14:24 /dev/hidraw0

pi@ras_pi1:~ $ dmesg | grep EFW
[ 1.972106] usb 1-1.3: Product: ZWO EFW
[ 1.977293] hid-generic 0003:03C3:1F01.0001: hiddev0,hidraw0: USB HID v1.01 Device [ZW0 ZWO EFW] on usb-3f980000.usb-1.3/input0

pi@ras_pi1:~ $ sudo indiserver -vv indi_asi_wheel
2017-03-27T03:45:45: startup: indiserver -vv indi_asi_wheel
2017-03-27T03:45:45: Driver indi_asi_wheel: pid=1947 rfd=3 wfd=6 efd=7
2017-03-27T03:45:45: listening to port 7624 on fd 4
2017-03-27T03:45:45: Driver indi_asi_wheel: sending <getProperties version='1.7'/>

2017-03-27T03:45:45: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONNECTION'>
2017-03-27T03:45:45: Driver indi_asi_wheel: read <defTextVector device='EFW' name='DRIVER_INFO'>
2017-03-27T03:45:45: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='DEBUG'>
2017-03-27T03:45:45: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='SIMULATION'>
2017-03-27T03:45:45: Driver indi_asi_wheel: read <defSwitchVector device='EFW' name='CONFIG_PROCESS'>
^C

Best regards,
Tatsuji
7 years 1 day ago #15703

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

indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=1"
indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=2"
indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=3"

...etc
Last edit: 7 years 1 day ago by Jasem Mutlaq.
7 years 1 day ago #15705

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

  • Posts: 10
  • Thank you received: 0
Thank you for your prompt answer knro.
But my request was refused as follows. I think my setup of the system may have some problem or imperfection.

pi@ras_pi1:~ $ indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=1"
connect: Connection refused
pi@ras_pi1:~ $ sudo indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=1"
connect: Connection refused

Best regards,
Tatsuji
7 years 1 day ago #15707

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

Are you sure INDI server is running when you type in that command?
The following user(s) said Thank You: Tatsuji_Tanaka
7 years 1 day ago #15711

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

  • Posts: 10
  • Thank you received: 0
I guess so because of following messsage.
pi@ras_pi1:~ $ sudo indiserver -vv indi_asi_wheel
2017-03-27T03:45:45: startup: indiserver -vv indi_asi_wheel
2017-03-27T03:45:45: Driver indi_asi_wheel: pid=1947 rfd=3 wfd=6 efd=7
2017-03-27T03:45:45: listening to port 7624 on fd 4
...
But let me know the way to verify it, if I am wrong.

Best regards,
Tatsuji
7 years 1 day ago #15712

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

  • Posts: 10
  • Thank you received: 0
I have rebooted RPi3, and tried again. I got following message from RPi3.

# on term1
pi@ras_pi1:~ $ sudo indiserver -v indi_asi_wheel
2017-03-28T00:15:15: startup: indiserver -v indi_asi_wheel
2017-03-28T00:15:15: Driver indi_asi_wheel: pid=1107 rfd=3 wfd=6 efd=7
2017-03-28T00:15:15: listening to port 7624 on fd 4

# Then I open one more terminal:term2 to input a command, and the message.
# on term2
pi@ras_pi1:~ $ indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=1"
No EFW.FILTER_SLOT.FILTER_SLOT_VALUE from localhost:7624

#after above comand input on term2 I got following message on the term1
2017-03-28T00:15:44: Client 0: new arrival from 127.0.0.1:42236 - welcome!
2017-03-28T00:15:46: Client 0: read EOF
2017-03-28T00:15:46: Client 0: shut down complete - bye!

Any suggestion?
Thanks for your help.
Tatsuji
7 years 12 hours ago #15723

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

  • Posts: 158
  • Thank you received: 32
Hello,

I tested this same thing. I had INDI running, although I don't use sudo to launch it, and sent commands to change the filter. Here is what I got:

bill@billpi:~$ indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=1"
bill@billpi:~$ indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=2"

Both commands were successful, and the slot moved to position 2. It did not move in the first command, because it was already on slot 1.
The following user(s) said Thank You: Jasem Mutlaq, Tatsuji_Tanaka
7 years 11 hours ago #15725

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

  • Posts: 10
  • Thank you received: 0
Thank you rockstarbill. I retried as user instead of super user, but failed again. I guess I have some wrong setup of INDI Library v1.4.1.
Unless any other way to find my problem, I am going to reinstall INDI Lib.
Tatsuji
7 years 10 hours ago #15726

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

  • Posts: 10
  • Thank you received: 0
By following query, I found the problem was "EFW.CONNECTION.CONNECT=Off"
pi@raspberrypi:~ $ indi_getprop
EFW.CONNECTION.CONNECT=Off
EFW.CONNECTION.DISCONNECT=On
EFW.DRIVER_INFO.DRIVER_NAME=ASI Wheel
EFW.DRIVER_INFO.DRIVER_EXEC=indi_asi_wheel
EFW.DRIVER_INFO.DRIVER_VERSION=0.5
EFW.DRIVER_INFO.DRIVER_INTERFACE=16
EFW.DEBUG.ENABLE=Off
EFW.DEBUG.DISABLE=On
EFW.SIMULATION.ENABLE=Off
EFW.SIMULATION.DISABLE=On
EFW.CONFIG_PROCESS.CONFIG_LOAD=Off
EFW.CONFIG_PROCESS.CONFIG_SAVE=Off
EFW.CONFIG_PROCESS.CONFIG_DEFAULT=Off

Then I set as;
pi@raspberrypi:~ $ indi_setprop "EFW.CONNECTION.CONNECT=On"
I got the control of EFW, and my Bash script did worked. Thank you all.
BTW, please let me know how to set "EFW.CONNECTION.CONNECT=On" automatically, or permanently.
6 years 11 months ago #15898

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

"EFW.CONNECTION.CONNECT=On" must be called before you can start controlling the device. Just add it to your script. If the driver is already running and connected, no need to call this property again, but when connecting to a driver that was just started by INDI server, then you must set it so that it connects.
The following user(s) said Thank You: Tatsuji_Tanaka
6 years 11 months ago #15908

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

Time to create page: 1.222 seconds