Acapulco Rolf is friends with Andrew

Acapulco Rolf thanked Andrew in topic dslr - image info 10 hours 44 minutes ago

Acapulco Rolf replied to the topic 'Is there a way to minimize the Ekos GUI with window controls?' in the forum. 3 weeks ago

This is the checkbox to be toggled:



Read More...

Acapulco Rolf is friends with Jasem Mutlaq

Acapulco Rolf replied to the topic 'Can't connect consustenlty to Canon T3i Camera' in the forum. 1 month ago

Hi Wouter

For my use case, so far the only consistently reliable way I've found to reconnect the DSLR when the connection fails is as follows:

unplug camera from usb
power off the camera
power on the camera
restart the raspberry pi
replug camera into usb


[2019-12-09T07:59:39.415 UTC INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 600D : "[ERROR] Camera_get_config failed (-110): I/O in progress "
[2019-12-09T07:59:39.417 UTC INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 600D : "[ERROR] Can not open camera: Power OK? If camera is auto-mounted as external disk storage, please unmount it and disable auto-mount. "
[2019-12-09T07:59:39.417 UTC DEBG ][ org.kde.kstars.ekos] - Canon DSLR EOS 600D is disconnected.
[2019-12-09T07:59:39.418 UTC INFO ][ org.kde.kstars.ekos] - "Canon DSLR EOS 600D is disconnected."


Attaching logs showing the issue from this morning for reference

Read More...

Acapulco Rolf replied to the topic 'Can't connect consustenlty to Canon T3i Camera' in the forum. 1 month ago

Hi Tom

I pretty much observe the same as you though I am running Stellarmate 1.4.3 on a Raspberry Pi 4/4Gb on Ubuntu 18.04.3

My Canon DSLR 600d intermittently disconnects

For me, the only way to reconnect the DSLR is this:

unplug camera from usb
power off the camera
power on the camera
restart the raspberry pi
replug camera into usb


The issue is intermittent for me, but enough to ruin an imaging session

I too have done some research and come up with the same remedies that you quoted but still observe the Canon DSLR disconnect issue intermittently

As I type, I'm currently shooting darks at various exposures and durations and so far so good.....for now....


Did you find a solution in the end...?

Equipment:
Skywatcher EQ5 Mount/EQMOD
Canon 600D DSLR
Altair 80mm refractor
ZWO CCD ASI224MC Guide Camera
MyFocuserPro2 focuser
Stellarmate 1.4.3 (Raspberry Pi 4)
Raspberry Pi 4 (4GB)

KSTARS 3.3.8
Stellarmate 1.4.3

Read More...

Thanks Jasem

From what you've shared it sounds like you are suggesting this might be a build issue, so i take it that one approach might be for me to do a local full compile from source, right?

I'll give that a go and confirm the outcome

Read More...

After installing the lastest nightly build (KSTARS 3.3.9) within Stellarmate, I'm seeing that my
Skywatcher mount no longer connects when the EQMOD INDI driver tries to startup.

The following message pops during the connection attempt:
"INDI Driver EQMod Mount crashed"





Video walkthrough here

[video]

Logs attached for reference
logs for v3.3.8 (successful connections)
logs for v3.3.9 (EQMOD mount fails to connect)


Rolling back to KSTARS 3.3.8 solves the issue

For information:
I'm looking to get the latest FITS header fixes that come with the latest nightly build to allow me to use ASTAP for platesolving

Currently ASTAP fails to solve (CDELT keywords issue) and looking at this post there is a fix for the CDELT FITS header issue in the latest nightlies

I observe that ASTAP solve works as expected on my setup when given an image with the CDELT keywords in the FITS header

I checked my recent image FITS headers and observe that they do not contain the CDELT keywords, so I'm looking for the recent fix in the latest 3.3.9. nightlies to overcome that

Equipment:
Skywatcher EQ5 Mount/EQMOD
Canon 600D DSLR
Altair 80mm refractor
ZWO CCD ASI224MC Guide Camera
MyFocuserPro2 focuser
Stellarmate 1.4.3 (Raspberry Pi 4)
Raspberry Pi 4 (4GB)

Logged as an issue here

File Attachment:

File Name: KStars3.3.8-EQMODissuedoesnotoccur-log_16-15-29.txt
File Size: 197 KB

File Attachment:

File Name: KStars3.3.9-EQMODissueoccurs-log_16-11-58.txt
File Size: 137 KB


Read More...

Acapulco Rolf replied to the topic 'myFocuserPro or myFocuserPro2 and INDI' in the forum. 3 months ago

Thanks Jasem
I've compiled the latest build with the v 0,5 MyFP2 changes and all appears to be well

I'm no longer able to reproduce the issue

Nice one

Thanks Alan, Rob and Jasem

Read More...

Acapulco Rolf replied to the topic 'myFocuserPro or myFocuserPro2 and INDI' in the forum. 3 months ago

Hi Pierre-Yves

I wasn't aware that this behaviour was frequent in other drivers too. Good to know

I've logged it as an issue on the INDI github page

Read More...

Acapulco Rolf replied to the topic 'myFocuserPro or myFocuserPro2 and INDI' in the forum. 3 months ago

Thanks Alan

What causes the behaviour with the fields "to the right" getting populated/non-populated given the steps i followed ?
NB: Nothing was manually changed when walking through those steps yet the fields "to the right" got set to zero and then subsequently got populated without any intervention

Read More...

Acapulco Rolf replied to the topic 'myFocuserPro or myFocuserPro2 and INDI' in the forum. 3 months ago

Thanks Rob

I'm now able to reproduce the issue consistently


Steps to reproduce the issue:

I'll walk through the steps to reproduce the issue based on Stellarmate as that's the build I use

1. Start up the Stellarmate Web Manager
stellarmate.local:8624

2. Start the INDI server
All devices defined in the equipment profile will start-up as expected

3. Open Kstars
4. From the Kstars "Tools" menu select "Ekos"
5. "Start" Ekos from the "Ekos Profile - KStars" GUI
In my case, I have it set in my equipmemt profile to "auto connect" all devices

6. Click "Connect" to connect all devices defined in the equipment profile
7. Once the "INDI Control Panel - Kstars" screen opens then navigate to the MyFocuserPro2 page

Note the values shown in "Absolute Position" and "Max Position" fields
e.g. In my case see the first screen capture below

Note the empty fields for Absolute Position and Max Position

8. Close the "INDI Control Panel - Kstars" screen
9. Click "Disconnect" to disconnect all devices
10. Stop Ekos
11. Close Kstars


Follow steps 3 through 7 again
Now note that this time once you get to step 7, the Absolute Position and Max Position fields are now populated as expected
e.g. In my case see the second screen capture below

12. Close all screens and disconnect devices
13. Stop the indi server via the Stellarmate web manager
stellarmate.local:8624


Repeat the steps 1 through 7 to reproduce the issue again

If you don't use Stellarmate, substitute steps 1,2 and 13 for the equivalent steps for your set-up

Abs and Max fields not populated




Abs and Max fields populated


Read More...