×

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

Bi-monthly release with minor bug fixes and improvements

Testers Needed on OS X: SBIG, MGEN, Fishcamp, ATIK, and Arduino

  • Posts: 43
  • Thank you received: 3
Hi!

I use the MGEN autoguider and would be glad to help testing your driver.

Cheers
Stephan
5 years 9 months ago #26259

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

  • Posts: 2876
  • Thank you received: 809
Thank you very much, please try the dmg in the link I provided and let me know if it works.

Rob
5 years 9 months ago #26276

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

  • Posts: 2876
  • Thank you received: 809
My Arduino arrived today. I had to try it out. It took me some time to find the right file to upload to the Arduino. It was StandardFirmata.ino and was located in the indiduino directory in the official libindi git. Once I loaded that file, INDI Duino worked great on Mac OS X. So that work I did this weekend was worth it. I could have a lot of fun playing with INDI, my Mac, my raspberry pi, and an Arduino.



First successful test, turning on a simple LED in the Simple Switcher Arduino INDI Driver.
5 years 9 months ago #26278
Attachments:

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

  • Posts: 7
  • Thank you received: 1
Hi rlancaste, can you have a look at this? indilib.org/forum/focusers-filter-wheels...t-work-on-macos.html
It's an Arduino focuser, can use under linux, but can't work under macOS .
5 years 9 months ago #26299

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

  • Posts: 2876
  • Thank you received: 809
First, are you planning to use Moonlite Focus or do you want to use indi-duino, which has an Arduino Focuser?

In terms of the port being busy or not available, I would plug it in and go to the terminal. Do an ls /dev command and see what the ports are. That way you can check to see that it is in fact this port. Second, almost certainly I expect there will be a /dev/cu.wchusbserial1410 and a /dev/tty.wchusbserial1410 (using your example). I found that for indi-duino the cu port worked ok, but with my moonlite I think it wanted tty. Note that you might also have to change permissions on the port to make it available.
The following user(s) said Thank You: Lynx
5 years 9 months ago #26300

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

  • Posts: 2876
  • Thank you received: 809
I built a new dmg and posted it. So the latest version includes the SBIG, MGEN, Fishcamp, ATIK, and Arduino drivers. Also it includes some icon fixes. And most importantly, it includes a crucial dylib that was missing in the latest version of the app that is needed for plate solving. But now to test these drivers, just use the regular build.
5 years 9 months ago #26302

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

  • Posts: 7
  • Thank you received: 1
I will try it latter. 3q very much
5 years 9 months ago #26317

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

  • Posts: 43
  • Thank you received: 3
Hi!

I just tried connecting my MGEN auto guider to ekos OS X. The device connects!

2018-06-03T11:08:15: [ERROR] Error loading user configuration. Unable to open config file. Error loading file /Users/stephan/.indi/Lacerta MGen Autoguider_config.xml: No such file or directory. To save user configuration, click Save under the Configuration property in the Op
2018-06-03T11:08:15: [INFO] Connect::14MGenAutoguider: considering device connected
2018-06-03T11:08:14: [INFO] Connect::10MGenDevice: FTDI device 0x0403:0x6001 connected successfully
2018-06-03T11:08:14: [INFO] Connect::10MGenDevice: Connecting device 0403:6001 using FTDI 1.4 v1.4.0 snapshot unknown
2018-06-03T11:08:09: [INFO] TurnPowerOn::10MGenDevice: trying to turn device on
2018-06-03T11:08:09: [ERROR] ask::10MGCMD_NOP1: no ack (0 bytes read)
2018-06-03T11:08:09: [INFO] Connect::10MGenDevice: FTDI device 0x0403:0x6001 connected successfully
2018-06-03T11:08:09: [INFO] Connect::10MGenDevice: Connecting device 0403:6001 using FTDI 1.4 v1.4.0 snapshot unknown

The configuration error does seem to be an issue.

The MGEN menus are displayed in the remote GUI window.

However, I am not yet able to capture an image. In the CCD control panel I chose Lacerta MGEN but I get the following messages:

2018-06-03T13:18:34 Capture failed. Check INDI Control Panel for details.
2018-06-03T13:18:34 Capturing image...
2018-06-03T13:18:34 Restarting capture attempt #2
2018-06-03T13:18:34 Capture failed. Check INDI Control Panel for details.
2018-06-03T13:18:34 Capturing image...
2018-06-03T13:18:34 Restarting capture attempt #1

I am a newbie using ekos so I guess it's me misunderstanding rather than an issue with the driver.

Could you please give me some pointers on what to test next?

Cheers
Stephan
5 years 9 months ago #26385

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

  • Posts: 2876
  • Thank you received: 809
Thank you for trying it out!

So the configuration error is actually no big deal, it just means you havent saved your configuration yet. Just hit save in the indi control panel options for the mgen autoguider and that warning will go away.

The info you pasted is very helpful, but it might be even better to get the log file. In the ekos summary page, you will see the logs button. Before you connect, it would be good to go in there, turn on verbose logging, log to file, and click all the related checkboxes to what you are currently testing. Then after you try to connect and take an image, go back there and click open logs directory. Then attach the relevant file here in the forum.

Thanks,

Rob
5 years 9 months ago #26388

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

  • Posts: 2876
  • Thank you received: 809
By the way,

This weekend i have been working with the indiduino (arduino) and fishcamp drivers. As i mentioned I bought an arduino and i was leant a fishcamp for testing. The indiduino driver testing has gone very well. I have successfully built several of the example circuits and then connected and used them in KStars. There were a couple of issues though and I have made some corrections to the code. The corrections will be included in the next dmg. The fishcamp testing has not gone as well as that, but its promising. If i initialize the camera in phd or nebulosity, it then works perfectly in kstars and indi. But the indi firmware loading routine does not currently get the camera set up correctly.

Thanks,

Rob
5 years 9 months ago #26389

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

  • Posts: 1029
  • Thank you received: 301
Hello,

About MGen, in the current state of the driver code, the only feature is the remote controller.

First thing is that you need the kernel to release the port for libftdi1 to be able to control it. This part is probably OK if your MGen starts turned off, and turns on when the driver requests it to.

Second thing is that you can't - yet - use it as a CCD proper. Go to the remote UI tab, and turn remote interface on. The driver will then periodically send the remote frame as a CCD frame. You can use the buttons in the same tab to navigate, and if you have a good network bandwidth, you can increase the frame rate. All features of MGen are accessible this way. Once the guider is configured, turn the remote UI off to avoid Ekos getting confused on what is your camera picture and what is the MGen UI (you'll see it appear in the first tab of Ekos).

I suggest that once the driver is connected properly, you set the port name to use and the image settings to be compressed, and save the configuration. With this the driver won't return to default settings every time is starts.

I know this should have proper documentation, Jasem already requested that. I plan to do that once the PHD2-compatible interface is implemented.

-Eric
5 years 9 months ago #26391

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

  • Posts: 2876
  • Thank you received: 809
Thanks Eric!

Based on the messages Stephan reported, do you think it connected properly, was the firmware loaded, and was the camera released from the kernel? It did say connected successfully. Do you think if Stephan followed your special procedure, it would work on Os X the same as it does on Linux? I just want to make sure there isnt some other os x issue I should address such as ftdi connection issues, firmware loading issues, or commands that are not os x compatible.

Thanks,

Rob
5 years 9 months ago #26404

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

Time to create page: 0.401 seconds