Good Morning,

Yesterday I soldered the cable using Magnus' link and it works fine.
Thanks again for the support. :)

greeting
Thomas



Read More...

Hello Magnus,

thanks for the link, but I have already found it and am rebuilding it. I still have an FTDI lying around here that I don't need, I'll convert it. :)

Thomas

Read More...

Okay you two

let's stick to English out of politeness :)

So Magnus you had 2 USB cables on the camera.
One cable for triggering the camera (Ekos) and one for data transmission from the camera to Ekos.
Fine :)

I saw you were busy researching the Bulb history of the camera in 2016. :)

So I need a shutter release cable. Understood.

@ jasem
forget the story with the arduino :)

Thank you both I will try to find data about it and build or get one.

greeting
Thomas

Read More...

Hallo Herrhausen,
Hmm, ja schon klar, nur wie löst Magnus die Kamera aus ??
Das Kabel steckt im PC. Vernachlässigen wir einmal den RS232/USB-Adapter. Wenn ich das richtig verstehe dann hat Magnus auf der einen Seite einen PC mit RS232/USB Ausgang - Kabel mit 2,5mm Klinkenstecker in die Kamera.
Da muss doch ein Adapter dazwischen sein der die Seriellen Signale in einfache Schaltsignale umwandelt was die Optokoppler/Relays/Transistoren ansteuert.

Sorry ich stehe da irgendwie auf dem schlauch.

Gruß
Thomas

Read More...

Hello Magnus

I've made myself a little smart.
www.gphoto.org/doc/remote/

"gphoto2 --get-config shutterspeed" gives me a list of numbers that correspond to the exposure time.
"0" would be for me = "bulb"

"gphoto2 --set-config shutterspeed = 0"
Puts the camera in "bulb mode"

The following command shows that the camera does not recognize the "bulb" command.

"gphoto2 --set-config shutterspeed = bulb"
"gphoto2 --set-config bulb = 1 --wait-event = 30s --set-config bulb = 0 --wait-event-and-download = 2s"

The camera does not recognize "eosremoterelease = Immediate".

thomas @ work computer: ~ $ gphoto2 --list-config
Detected a "Canon: EOS 350D (normal mode)".
/ main / settings / ownername
/ main / settings / capturesizeclass
/ main / settings / iso
/ main / settings / shootingmode
/ main / settings / shutterspeed
/ main / settings / aperture
/ main / settings / exposurecompensation
/ main / settings / imageformat
/ main / settings / focusmode
/ main / settings / flashmode
/ main / settings / beep
/ main / actions / syncdatetime
/ main / status / model
/ main / status / datetime
/ main / status / firmware version
/ main / status / driver
/ main / driver / list_all_files
thomas @ work computer: ~ $

As you say, the problem is with the camera :(

A question for Jasem.
Is there a way in Ekos to control an Arduino so that it triggers the camera via optocoupler / relay?
That would also solve the problem with mirror lock-up.
I think some older cameras have the problem, not just the Canon EOS350 (rebel xt)
The Arduino could handle the mirror lock-up and exposure time.
When the recording time is up, the Arduino sends a "done" and Ekos reads the image.
It's just an idea.

greeting
Thomas

Read More...

Hello Magnus

I'm German.

I can't do anything with the timer, I don't think I still have the old software. I built the timer 10-15 years ago.

If I understand you correctly, then you use a cable with a 2.5mm jack on the camera and an RS232 adapter on the other side which goes into the PC?

So you have 2 cables on the EOS?
One cable for USB data and one for triggering?
Which software do you use for the control, EKOS?

Please excuse the many questions, but you made me curious. :)

At the moment I can only record a maximum of 30 seconds. That is not a problem, but there is a lot of data. In addition, the mechanics of the camera will suffer over the years.

Thomas

Read More...

Hello Magnus
Yes, I once built one with an Atmega8, which also works with mirror release and has a timer.
But I can only use it locally in front of the telescope.

I actually wanted to save myself the additional effort and control the camera and telescope via Kstars / Ekos. :(
I read your thread a few years ago, it looks like you got stuck.

I know that it worked years ago with an old version of Gphoto. But that was certainly 10 years ago.

If the translation is a bit bumpy, I apologize.
I use google translate.

greeting
Thomas

Read More...

Good Morning

I have installed Kstars / Ekos under Kubuntu (20.04) and on the Raspian PI4, but I cannot expose for more than 30 seconds on both systems.

I do the following:
Start Kstars / Ekos
Connect the camera to the system (Kubuntu)
Switch on the camera, mode "M" and set the exposure time to "BULB"
Start the camera profile for my Canon in Ekos and start Indi.
Set an exposure time> 30 seconds.
The exposure starts and after 30 seconds the camera stops recording while EKOS counts down the remaining seconds.

As soon as I start recording via EKOS, the camera no longer shows BULB on the display, but rather 30 "

The indilog shows nothing conspicuous:

2020-09-29T08: 14: 05: [INFO] Exposure done, downloading image ...
2020-09-29T08: 13: 22: [INFO] Starting 40 seconds exposure.
2020-09-29T08: 09: 43: [INFO] Debug is disabled.
2020-09-29T08: 09: 43: [INFO] Debug is enabled.
2020-09-29T08: 09: 29: [INFO] Preset Bulb seconds selected.
2020-09-29T08: 09: 24: [INFO] World Coordinate System is enabled.
2020-09-29T08: 09: 24: [INFO] Device configuration applied.
2020-09-29T08: 09: 24: [INFO] Force BULB is enabled. All expsures shall be captured in BULB mode except for subsecond captures.
2020-09-29T08: 09: 24: [INFO] Upload settings set to client only.
2020-09-29T08: 09: 24: [INFO] Loading device configuration ...
2020-09-29T08: 09: 23: [INFO] Detected Canon EOS 350D DIGITAL Model Canon EOS 350D DIGITAL.
2020-09-29T08: 09: 23: [INFO] Canon DSLR Digital Rebel XT (normal mode) is online.

Jasem please help me.
I tried to find a solution to the problem in the forum. I found an entry that is more than 5 years old and a solution was not shown.

Best regards
Thomas



Read More...

hi Guys

I bought an EQ6 about 15 years ago and upgraded with Rajiva's MCU-Upgrade Kit.
If I run the EQ6 with Skychart the internal driver and the control of the mount works without problems.
If I use the Indiserver indi_lx200basic with Kstars then i've got the connection to the driver but more does not happen.

I can still remember a libindi version that worked. But that has been many years ago.
I have run on the server the latest PPA from Jasem and connect with Kstars from the client.

In the "sync" of an object, I see the cross for a second, but immediately disappears. If I want to "slew" on a object, nothing happens.

This is the Kstars Indi-Control output

2017-06-09T08:42:21: Object below the minimum elevation limit.
2017-06-09T08:42:21: Error Slewing to JNow RA 2:44:12 - DEC 3:18:21
2017-06-09T08:42:12: Synchronization successful.
2017-06-09T08:41:56: LX200 Basic is online.


What should I do to run the EQ6 with the Indi_lx200basic driver?
I would like to use ekos, but as long as the assembly does not work it is useless.

I have already read that many EQ6 users with MCU upgrade, have problems with this driver.

Is there a solution for this problem?
If there no driver specifically for the eq6 with mcu-upgrade kit?

If I can help to solve the problem, so let me know how i can help.

Sorry for my bad english but google ist my friend ;)

Best regards
Thomas

Read More...

hi Guys

I bought an EQ6 about 15 years ago and upgraded with Rajiva's MCU-Upgrade.
If I run the EQ6 with Skychart and the internal driver, then the control of the mount works without problems.
If I use the Indiserver indi_lx200basic with Kstars then he set the connection to the driver but more does not happen.

This is the Log from Indi-Kontroll in Kstars.

2017-06-09T07:05:21: LX200 Basic is offline.
2017-06-09T07:05:01: Object below the minimum elevation limit.
2017-06-09T07:05:01: Error Slewing to JNow RA 1:42:23 - DEC 10:00:04
2017-06-09T07:04:48: Synchronization successful.

In the "sync" of an object, I see the cross for a second, but immediately disappears. If I want to "slew" on a object happens nothing.

I can still remember on a libindi version that worked. But that has been many years ago.
I have run on the server the latest PPA from Jasem and connect with Kstars from the client.

What should I do to run the EQ6 with the Indi_lx200basic driver?
I would like to use ekos but as long as the assembly does not work it is useless.
I've already read that many EQ6 users with MCU upgrade, have problems with the driver.

Is there a solution for this?
Is there no EQ6 driver where fix this problem ?
If I can help solve the problem, so let me know.

Sorry for my bad english, but google Translate is my friend ;)

Best regards
Thomas

Read More...

Good Morning,

Please apologize if I can not always answer the same. I have family.

@KNRO
I have made 2 log files.
Indiserver -vv -l / home / thomas / indi_log indi_lx200basic
Indiserver -vvv -l / home / thomas / indi_log indi_lx200basic

"Sync" on Venus at "Slew" on Uranus. 2 times each.
I hope you can do something with it.
If you need other logs please tell it.

@NMAC
I have read your topic. I did not know you were still there. Is already a while ago
I would be glad if someone manages to get the thing to run.

I had already played with Kstars and Indi 15 years ago and it worked with this mount. Then there was a change in the libindi.
After that, nothing happened and I had to go to Skychart.

Somehow I had then Kontact to jasem and he has viewed with SSH the source from libindi. After that, it worked a while. At least until the first update but is certainly 6 years ago.

greeting
Thomas

Read More...

Hi Knro,

lx200 if you this mean.
See Screenshot.

Read More...

hi Guys

I bought an EQ6 about 15 years ago and upgraded with Rajiva's MCU-Upgrade Kit.
If I run the EQ6 with Skychart the internal driver and the control of the mount works without problems.
If I use the Indiserver indi_lx200basic with Kstars then i've got the connection to the driver but more does not happen.

I can still remember a libindi version that worked. But that has been many years ago.
I have run on the server the latest PPA from Jasem and connect with Kstars from the client.

In the "sync" of an object, I see the cross for a second, but immediately disappears. If I want to "slew" on a object, nothing happens.

This is the Kstars Indi-Control output

2017-06-09T08:42:21: Object below the minimum elevation limit.
2017-06-09T08:42:21: Error Slewing to JNow RA 2:44:12 - DEC 3:18:21
2017-06-09T08:42:12: Synchronization successful.
2017-06-09T08:41:56: LX200 Basic is online.


What should I do to run the EQ6 with the Indi_lx200basic driver?
I would like to use ekos, but as long as the assembly does not work it is useless.

I have already read that many EQ6 users with MCU upgrade, have problems with this driver.

Is there a solution for this problem?
If there no driver specifically for the eq6 with mcu-upgrade kit?

If I can help to solve the problem, so let me know how i can help.

Sorry for my bad english but google ist my friend ;)

Best regards
Thomas

Read More...