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...

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...

I am using an ioptron CEM120 mount with the corresponding INDI driver for this model.
The problem that I encounter is that the driver automatically picks the highest baud rate (230400), at which the connection to the mount does not work.
After adjusting the baud rate to 115200 the mount is able to connect.
I saved this configuration, and I even checked the two config files in the .indi folder, reflecting the correct baud rate.
Nevertheless, when I restart the driver, it defaults back to the higher baud rate, necessitating a manal intervention.

Any idea where this unexpected behavior comes from?

BR

Marcel
 

Read More...

Note that the slew-to-tracking issue only appears when slewing from a situation where the mount is not tracking previously (e.g. parking).
When slewing when already tracking (e.g. one object to the next), the mount does initiate tracking after the slew.
This is inconvenient when e.g. running an automated schedule from park position.

With regards to the connectivity issue I described in my last post: I was not able to reproduce it today.
I tested with 3.5.6 beta and 3.5.2 stable on a Pi3 with 4GB.

BR

Marcel

Read More...

Hi MIke,

Some time has passed.. I replaced the handset batteries and upgraded the firmware of the CP3 box to V2. 

File Attachment:

File Name: indi_lx200ap_experimental_19_30_11.log
File Size: 20 KB
 

File Attachment:

File Name: log_22-02-59.txt
File Size: 307 KB


I have now more predictable behavior from the mount w.r.t. connecting, (un)parking, meridian flip, and slewing to the right spot.

However, I still experience two problems:
- The mount does not automatically start tracking after slewing to an object from park position. When slewing from a tracking situation, tracking commences for the new object.
- The month seems to lose connection to the raspberry pi after some time with the following error message "ERROR    558.837511 sec    : check_lx200ap_status: wrote, but nothing received.
ERROR    563.841507 sec    : Reading sidereal time failed 1769300527"
- Upon this error message, the mount stops tracking and does not respond to other comments.

I attach the log files for your reference. Hope somebody can help.

BR | Marcel


 

Read More...

Hi MIke,

I was finally able to test the new driver under KStars 3.5.4 Beta.
While executing your instructions I noticed the following deviating behavior (log attached):
Start- Up light in the indi driver panel did not go to red
After pressing cold start, the mount is directly visible in the planetarium
Unpark from the Ekos GUI does not work
I then get multiple error messages.

Note that my AP control box is on version L (old).

BR

Marcel 

 

File Attachment:

File Name: log_22-26-58.txt
File Size: 502 KB


Read More...

Hi Mike,

Thanks for the help. I am running astroberry distro on a pi 3B+
When connecting to the indinightly repository I get the following error message:

astroberry@astroberry01:~ $ sudo apt-add-repository ppa:mutlaqja/indinightly
[sudo] password for astroberry: 
Traceback (most recent call last):
  File "/usr/bin/apt-add-repository", line 95, in <module>
    sp = SoftwareProperties(options=options)
  File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 109, in __init__
    self.reload_sourceslist()
  File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 599, in reload_sourceslist
    self.distro.get_sources(self.sourceslist)    
  File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in get_sources
    (self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Raspbian/buster

After executing the other two lines and restarting the pi for good measures I notice that Kstars is still in version 3.5.3 stable.

Any suggestions?

Marcel
 

Read More...

Ready to test....

Rookie question: how do I install nightly build on my pi4?
And how do I check that I have the right version of the driver before I start testing?

Marcel

Read More...

Hi Mike,

Thanks for the instructions.Hi Mike,

Thanks for the instructions.

When following your procedure I still run into problems that block me from using the driver.

All goes well until the step where I need to write the park information.
There is no red light next to the part position field and when I try to write the park data, I get an error message that I cannot write parking information while slewing or parking. I also, after a cold start and unparking, seem to be able to park again.

I attach the log file.
Hope somebody can help.

Best regards,

Marcel

File Attachment:

File Name: log_22-55-58_2021-06-18.txt
File Size: 315 KB


When following your procedure I still run into problems that block me from using the driver.

All goes well until the step where I need to write the park information.
There is no red light next to the part position field and when I try to write the park data, I get an error message that I cannot write parking information while slewing or parking. I also, after a cold start and unparking, seem to be able to park again.

I attach the log file.
Hope somebody can help.

Best regards,

Marcel

Read More...

Hi Mike,

I attached the log file to my original message.

I also found out that I am using an old firmware version on my AP1200 GTOCP3 board: version L.
So maybe (probably?) that is the problem. I will upgrade the ROM Chip to version V2 and test again.

Clear Skies!

Marcel

Read More...

Hi Mike,

Thanks for the instructions.

When following your procedure I still run into problems that block me from using the driver.

All goes well until the step where I need to write the park information.
There is no red light next to the part position field and when I try to write the park data, I get an error message that I cannot write parking information while slewing or parking. I also, after a cold start and unparking, seem to be able to park again.

I attach the log file.
Hope somebody can help.

Best regards,

Marcel 

Read More...

I am struggling with the same issue and way fewer programming skills than the rest of you.

What I have noticed however is that if I connect two identical Atik CCD cameras to one Raspi and start Ekos with Atik CCD in the profile, I see the two cameras as Atik and Atik_2. I can e.g. assign one as main camera and the other as a guider. What is more, the allocation of the cameras (Atik or Atk_2) is consistent between sessions as long as I do not change the USB port that I connect them to. What I have not tested yet, but what I expect, is that this behavior extends to more devices as long as they are consistently connected to the same USB port on the Raspi, e.g. through a USB hub. So FW and FW_2, EAF and EAF_2 etc.)

What I have also noticed is that all attributes of my two cameras are the same except for the USB port-related info (1-1.1, 1-1.2 etc.). It shows up in the KERNEL info.
So if I can create unique alias based on the USB port the device is connected to, and I can connect that unique alias to a custom driver, I might be able to define them as different resources that I can use to create profiles etc. For the time being, I am even struggling to do the first step in this experiment, but maybe someone with more skills want to try it out.

Read More...