×

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

Bi-monthly release with minor bug fixes and improvements

Driver for Pegasus Indigo Filter Wheel

  • Posts: 45
  • Thank you received: 3
pegasusastro.com/products/indigo-filter-wheel/

This filter wheel is pretty new to the market. I'm interested in buying it based on the build quality, features, and price point. But INDI support is a requirement.

Is there any chance we will have support in the near future? The interface looks pretty simple.

I'd be happy to donate to the INDI community if it helps. :)
1 year 3 months ago #88742

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

I added support for this driver to INDI GIT. Needs testing.
The following user(s) said Thank You: Chris Barbour
1 year 3 months ago #88756

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

  • Posts: 45
  • Thank you received: 3
Great! I'll put an order in for the filter wheel. I'll take care of testing the code, unless someone else gets to it before I do.
1 year 3 months ago #88820

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

  • Posts: 45
  • Thank you received: 3
I built KStars from the head commit as of ~2022-12-07T02:08:47Z

So far, I'm not able to connect to the filter wheel. Console log:
2022-12-09T00:26:32: [ERROR] Failed to connect to port (/dev/cu.AeropexbyAfterShokz-GAIA). Error: Port failure Error: Resource busy. Check if device is connected to this port. 
2022-12-09T00:26:26: [INFO] Trying connecting to /dev/cu.AeropexbyAfterShokz-GAIA @ 9600 ... 
2022-12-09T00:26:26: [ERROR] Serial read error: Timeout error. 
2022-12-09T00:26:23: [INFO] Trying connecting to /dev/cu.Bluetooth-Incoming-Port @ 9600 ... 
2022-12-09T00:26:22: [INFO] Trying connecting to /dev/cu.usbserial-FW6POOD6 @ 9600 ... 
2022-12-09T00:26:20: [ERROR] Failed to connect to port (/dev/cu.AeropexbyAfterShokz-GAIA). Error: Port failure Error: Resource busy. Check if device is connected to this port. 
2022-12-09T00:26:14: [INFO] Trying connecting to /dev/cu.AeropexbyAfterShokz-GAIA @ 9600 ... 
2022-12-09T00:26:13: [ERROR] Serial read error: Timeout error. 
2022-12-09T00:26:10: [INFO] Trying connecting to /dev/cu.Bluetooth-Incoming-Port @ 9600 ... 
2022-12-09T00:26:08: [WARNING] Communication with /dev/cu.usbserial-FW6POOD6 @ 9600 failed. Starting Auto Search...

I enabled debug logging. I'm not sure where the log files live on OSX, or if there's any additional information I can supply.

OSX System Information for the filter wheel
Indigo FW:
 
  Product ID:	0x6015
  Vendor ID:	0x0403  (Future Technology Devices International Limited)
  Version:	10.00
  Serial Number:	FW6POOD6
  Speed:	Up to 12 Mb/s
  Manufacturer:	Pegasus Astro
  Location ID:	0x14100000 / 52
  Current Available (mA):	500
  Current Required (mA):	90
  Extra Operating Current (mA):	0
 

Connection panel:

1 year 3 months ago #88900

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

  • Posts: 45
  • Thank you received: 3
I can confirm the filter works using serial commands. Here's a quick session:
echo 'WI' > /dev/cu.usbserial-FW6POOD6
echo 'WV' > /dev/cu.usbserial-FW6POOD6
echo 'WM:4' > /dev/cu.usbserial-FW6POOD6
echo 'WR' > /dev/cu.usbserial-FW6POOD6
echo 'WR' > /dev/cu.usbserial-FW6POOD6
cat -v < /dev/cu.usbserial-FW6POOD6
 
WI:1^M
WV:1.2^M
WM:4^M
WR:1^M
WR:0^M
1 year 3 months ago #88914

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

  • Posts: 45
  • Thank you received: 3
Using cat, I can confirm that INDI connects to the wheel and sends a command:
cat -v < /dev/cu.usbserial-FW6POOD6
FW_OK^M

Having the serial port open does of course cause INDI to throw an error, so I'm not sure if anything is sent beyond this point.
1 year 3 months ago #88916

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

  • Posts: 45
  • Thank you received: 3
Ahhh, here is the actual debug log:
cat /Users/cbarbour/.indi/logs/2022-12-09/indi_pegasusindigo_wheel/indi_pegasusindigo_wheel_00:24:00.log
 
DEBUG	81516.547377 sec	: Connecting to /dev/cu.usbserial-FW6POOD6 @ 9600
DEBUG	81516.552552 sec	: Port FD 4
DEBUG	81516.552587 sec	: Connection successful, attempting handshake...
DEBUG	81516.552832 sec	: CMD <W#>
>EBUG	81516.571840 sec	: RES <FW_OK
DEBUG	81516.572213 sec	: Handshake failed.


Possible newline weirdness with the response?
Last edit: 1 year 3 months ago by Chris Barbour.
1 year 3 months ago #88917

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

Thank you for the log. Looks like it was cutting off one extra byte. Can you please pull again and try?
1 year 3 months ago #88919

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

  • Posts: 45
  • Thank you received: 3
Sorry for the delay. Here's the new build log:
DEBUG	158.106518 sec	: Connecting to /dev/cu.usbserial-FW6POOD6 @ 9600
DEBUG	158.111188 sec	: Port FD 3
DEBUG	158.111234 sec	: Connection successful, attempting handshake...
DEBUG	158.111521 sec	: CMD <W#>
DEBUG	158.126772 sec	: RES <FW_OK
>
DEBUG	158.127208 sec	: Handshake failed.
1 year 3 months ago #88936

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

Ok that is worse.. trimming new line was the correct thing to do in the previous version. At any rate, I relaxed the handshake, please git pull and test again.
1 year 3 months ago #88943

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

  • Posts: 45
  • Thank you received: 3
That update worked. There's still some weirdness in the logs though.
cat ~/.indi/logs/2022-12-11/indi_pegasusindigo_wheel/indi_pegasusindigo_wheel_19:25:32.log
INFO	0.009612 sec	: Session log file /Users/cbarbour/.indi/logs/2022-12-11/indi_pegasusindigo_wheel/indi_pegasusindigo_wheel_19:25:32.log
DEBUG	10.149900 sec	: Connecting to /dev/cu.usbserial-FW6POOD6 @ 9600
DEBUG	10.162549 sec	: Port FD 3
DEBUG	10.162591 sec	: Connection successful, attempting handshake...
DEBUG	10.162919 sec	: CMD <W#>
>EBUG	10.181088 sec	: RES <FW_OK
INFO	10.182332 sec	: Pegasus INDIGO is online.
DEBUG	10.183617 sec	: CMD <FV>
>EBUG	10.196103 sec	: RES <>>
DEBUG	10.197070 sec	: Auto search is disabled because /dev/cu.usbserial-FW6POOD6 is not a system port.
DEBUG	10.197116 sec	: Toggle Debug Level -- Driver Debug
DEBUG	10.197138 sec	: Toggle Logging Level -- Driver Debug
INFO	10.197161 sec	: Session log file /Users/cbarbour/.indi/logs/2022-12-11/indi_pegasusindigo_wheel/indi_pegasusindigo_wheel_19:25:32.log
INFO	10.197178 sec	: Setting current filter to slot 1
DEBUG	10.197610 sec	: CMD <WM:1>
>EBUG	10.212537 sec	: RES <WM:1
DEBUG	10.212919 sec	: Configuration successfully loaded.
INFO	10.230219 sec	: Debug is disabled.
DEBUG	11.184150 sec	: CMD <WF>
DEBUG	12.186778 sec	: CMD <WF>
DEBUG	13.189718 sec	: CMD <WF>
DEBUG	14.191763 sec	: CMD <WF>
DEBUG	15.197438 sec	: CMD <WF>
DEBUG	16.202859 sec	: CMD <WF>
DEBUG	17.208108 sec	: CMD <WF>
DEBUG	18.213444 sec	: CMD <WF>
DEBUG	19.214457 sec	: CMD <WF>
DEBUG	20.215666 sec	: CMD <WF>
DEBUG	21.216412 sec	: CMD <WF>
DEBUG	22.217688 sec	: CMD <WF>
DEBUG	23.219095 sec	: CMD <WF>
DEBUG	24.219855 sec	: CMD <WF>
DEBUG	25.221256 sec	: CMD <WF>
INFO	25.533124 sec	: Setting current filter to slot 1
DEBUG	25.533668 sec	: CMD <WM:1>
>EBUG	25.558617 sec	: RES <WM:1
DEBUG	26.223247 sec	: CMD <WF>
DEBUG	27.224775 sec	: CMD <WF>
INFO	27.392466 sec	: Setting current filter to slot 2
DEBUG	27.392917 sec	: CMD <WM:2>
>EBUG	27.430888 sec	: RES <WM:2
DEBUG	28.230795 sec	: CMD <WF>
DEBUG	29.234854 sec	: CMD <WF>
INFO	29.453719 sec	: Setting current filter to slot 4
DEBUG	29.454109 sec	: CMD <WM:4>
>EBUG	29.479140 sec	: RES <WM:4
DEBUG	30.237878 sec	: CMD <WF>
DEBUG	31.242458 sec	: CMD <WF>
DEBUG	32.247267 sec	: CMD <WF>
INFO	33.152451 sec	: Setting current filter to slot 5
DEBUG	33.152961 sec	: CMD <WM:5>
>EBUG	33.175804 sec	: RES <WM:5
DEBUG	33.250717 sec	: CMD <WF>
DEBUG	34.256660 sec	: CMD <WF>
INFO	35.125356 sec	: Setting current filter to slot 1
DEBUG	35.125853 sec	: CMD <WM:1>
>EBUG	35.160009 sec	: RES <WM:1
DEBUG	35.262212 sec	: CMD <WF>
DEBUG	36.266369 sec	: CMD <WF>
DEBUG	37.269836 sec	: CMD <WF>
DEBUG	38.270316 sec	: CMD <WF>
DEBUG	39.274502 sec	: CMD <WF>
DEBUG	40.280047 sec	: CMD <WF>
DEBUG	41.285390 sec	: CMD <WF>
DEBUG	42.287425 sec	: CMD <WF>
DEBUG	43.287896 sec	: CMD <WF>
DEBUG	44.288815 sec	: CMD <WF>
DEBUG	45.289985 sec	: CMD <WF>
DEBUG	46.292814 sec	: CMD <WF>
DEBUG	47.296506 sec	: CMD <WF>
DEBUG	48.300762 sec	: CMD <WF>
DEBUG	49.306592 sec	: CMD <WF>
DEBUG	50.312163 sec	: CMD <WF>
DEBUG	51.314517 sec	: CMD <WF>
DEBUG	52.315171 sec	: CMD <WF>
DEBUG	53.315960 sec	: CMD <WF>
DEBUG	54.316617 sec	: CMD <WF>
DEBUG	55.320368 sec	: CMD <WF>
DEBUG	56.321334 sec	: CMD <WF>
DEBUG	57.322593 sec	: CMD <WF>
DEBUG	58.324233 sec	: CMD <WF>
DEBUG	59.327384 sec	: CMD <WF>
DEBUG	60.331911 sec	: CMD <WF>
DEBUG	61.336491 sec	: CMD <WF>
DEBUG	62.337075 sec	: CMD <WF>
DEBUG	63.340848 sec	: CMD <WF>

The WF commands continue to be sent every second.
1 year 3 months ago #88946

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

It is weird.... my hack didn't solve the issue, just exposed it more. Can you debug and see in line 209, what's the exact value for res? how many bytes? what each byte is?
Last edit: 1 year 3 months ago by Jasem Mutlaq.
1 year 3 months ago #88947

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

Time to create page: 1.150 seconds