I am testing my set up with Indi on a Mac Mini and I am running into problems with my Atik equipment.
1. On a profile with Atik camera but no EFW, driver starts and camera is visible. However, when I start an exposure, it never finishes. It hangs.
2. When I add my Atik filterweheel (EFW) to the profile and starts it, the EFW driver does not start and the EFW is not visible in the Ekos interface.

Interestingly, when I start the Atik FW driver from the Tools>Devices>Device manage ... it starts the camera and not the EFW.
In that case I see 2x Atik 383L+

The EFW is visible in the list of USB devices on my Mac mini.
The same problem occurs when I run from another Mac machine (laptop)

I attach the log file for reference.

File Attachment:

File Name: log_20-05-39_2023-02-22.txt
File Size: 214 KB


Best regards

Marcel

Read More...

Hi Rob,

Could be, although the train problem only appears when I add the EFW to the profile, so there seems to be some sort of dependency.
Maybe I should first try to solve the problem with the Atik drivers on Mac Mini and then test the train behaviour again.

Would yo recommend me to start a separate forum thread on the Atik driver problem?

M

Read More...

Hi Rob,

Same behaviour with port selector selected.
I can see the EFW in my list of USB connected devices but it is not picked up by Indi.

Also note that without the EFW in my profile the camera does not work correctly.
It starts an exposure and gets stuck. It never finishes.

Marcel

Read More...

I tested with the new version: www.indilib.org/jdownloads/kstars/beta/kstars-3.6.3.dmg

Same behaviour persists.
For profile excluding EFW the editing of train works well but camera exposure hangs after started
For profile including EFW Indi drivers start up excl. EFW but no tabs visible in Ekos.

I attach the log file of the test run.

File Attachment:

File Name: log_20-05-39.txt
File Size: 214 KB


Read More...

Thanks everybpdy for picking this up. I observed some additional unexpected behaviour today:

I have a profile with an Atik 383L CCD camera and an Atik EFW filter wheel.

When I start this profile I see all the equipment with the exception of the filter wheel.
The FW does not show up in the indi driver tabs and cannot be used.
In this configuration the train dropdown and edit buttons in the camera tab are greyed out.

When I edit the profile and remove the filter wheel, the train drop down and edit buttons are active.
However, in this case, I still cannot do exposures, the camera goes into "capturing" mode and hangs there.

When I add back the filter wheel to the profile, the boxes are greyed out again.

Read More...

Hi Frederick,

Thanks for your response. The box and the pencil are grayed out.

BR

Marcel

Read More...

Hi Alfredo,

Unfortunately not. Neither have I received any response to my post yet.

BR | Marcel

Read More...

After working on a Raspberry Pi for years I am now trying to make Kstars working on a Mac Mini with Intel i5 CP and MacOS 12.0.1
In the process I am running into a number of problems:

    1. The train profile does not work. The drop down is grayed out. See separate thread:
Link>
2. My Atik FW2 is not recognized and does not start up although it is connected, powered up and is part of the profile
3. When trying to make an image with my Atik camera I see two behaviors: either it starts and does not complete (hangs) or Kstar chashes
4. Problem of overlapping windows that has already been reported in a separate thread: Link>

I attach some screenshots and the log file. Hope someone can help.

Read More...

I think I have found the solution. This is a known problem that is solved by switching off all sound alerts in the settings menu.

See also:
indilib.org/forum/ekos/10822-kstars-memo...-crash.html?start=12
indilib.org/forum/astroberry/11735-kstar...rpi-4-4gb.html#82971

Read More...

For some time now I have the problem that connection to my equipment fails at some random time during the night.

The power is still on, but the connection with the USB ports on my raspberry pi 4 fails.

See attached this indi log:
drive.google.com/file/d/1DkzPbTEGEOmbKuR...p9w/view?usp=sharing

The syslog of my pi (attached) shows the following messages

astroberry01 python3[23067]: swig/python detected a memory leak of type 'INDI::BaseDevice::Properties *', no destructor found.

Followed by many errors w.r.t. USB ports like these:

Jul 22 02:08:34 astroberry01 kernel: [16492.657469] usb 1-1.4: clear tt 1 (9082) error -71

Any suggestions how to fix this? Any further information I need to provide?

BR Marcel

File Attachment:

File Name: syslog.txt
File Size: 3,770 KB


Read More...

My scheduled program does not continue after making a meridian flip.
Mount seems to perform flip correctly and continues tracking after that.
My scheduler seems to keep running after the flip, but nothing happens.
No alignment, no guiding, no capture.

It could be that, second before the meridian flip, my PHD2 stops, maybe due to deviations caused by my cables starting to hit the pier.

See attached log file at timestamp 1:58

Any ideas, suggestions, work-arounds?

BR

Marcel

File Attachment:

File Name: log_21-16-26.txt
File Size: 601 KB


Read More...

Thanks Derek, the dmesg suggestion was a good one.
I see the problem related to the following error message:

usb_serial_generic_read_bulk_callback - urb stopped: -32

Any suggestions what this is and how to solve it?

BR

Read More...

The USB port is correct and the baud rate as well.
Indi connects to the mount but after some initial interaction, the connection breaks.
Sometimes I can even unpark and slew 1-2 times before the connection is lost.
I need to then disconnect and connect the driver again to move the mount to the parking position.

M

Read More...

Hi Community,

I have a problem with my Ioptron CEM120EC mount.
After months of good operation, I now have connectivity problems between my Pi and the mount.

Shortly after starting the driver and connecting to the mount I get the error message: 
[ERROR] Read Command Error: Timeout error. (see attached log file).

The mount loses its bearings and the only way to get it moving again is to disconnect and then connect the driver again.

Problems started after a recent OS update (sudo apt update && sudo apt upgrade). Maybe it is related.

I connect the CEM120EC with my Pi4 through USB.

Interesting other detail: before the connectivity problems started I had to set the baud rate manually. It did not save with the driver defaults.
Since the connectivity problems started, the driver picks up the baud rate automatically.

Any suggestions what is the problem and how to fix it?

Best regards,

Marcel Noordman

 

File Attachment:

File Name: indi_ioptronv3_telescope_170753_2022-01-17.log
File Size: 7 KB


Read More...

Marcel Noordman created a new topic ' CEM120 connectivity problems' in the forum. 2 years ago

Hi community,

After many months of good operations, my ioptron CEM120EC mount is giving me problems.
More specifically connectivity problems. I can connect to the mount but it then gives me an error message: 

[ERROR] Read Command Error. Timeout error (see attached driver log).

The mount loses its bearings and stops functioning well. Another message I sometimes get is:

Error setting RA/DEC

I recently updated my OS (sudo apt update && sudo apt upgrade); maybe there is a connection there?

I am running Astroberry on a Pi4.
The mount is connected directly to the Pi through a USB cable.

I have tried different ports on the pi and I tried to connect through a passive USB hub. No improvement.

Any suggestions on what can be wrong and how to fix it?

Best regards,

Marcel Noordman

Hi community,

After many months of good operations, my ioptron CEM120EC mount is giving me problems.
More specifically connectivity problems. I can connect to the mount but it then gives me an error message: 

[ERROR] Read Command Error. Timeout error (see attached driver log).

The mount loses its bearings and stops functioning well. Another message I sometimes get is:

Error setting RA/DEC

I recently updated my OS (sudo apt update && sudo apt upgrade); maybe there is a connection there?

I am running Astroberry on a Pi4.
The mount is connected directly to the Pi through a USB cable.

I have tried different ports on the pi and I tried to connect through a passive USB hub. No improvement.
I can get the mount moving again by disconnect and connecting again.

Also interesting that previously the driver did not pick up the right baud rate from the config (had to set it by hand).
As the connectivity problems started, the baud rate setting problem dissapeared.

Any suggestions on what can be wrong and how to fix it?

Best regards,

Marcel Noordman




  

File Attachment:

File Name: indi_ioptronv3_telescope_170753.log
File Size: 7 KB
 

File Attachment:

File Name: indi_ioptronv3_telescope_170753.log
File Size: 7 KB



 

Read More...