Thanks for checking and suggesting the option changes Hy.
It was the "Remember job progress" that was tripping me up. The sequence ran once then refused to run again. Sorted now.
Udo you're right, you can have the same name for jobs but I had to unselect the option "Sort Jobs by Alt & Prio".
I remember as a kid being allowed to control one of the smaller radio antenna (a 5m dish IIRC) at a visit to Jodrell Bank. I'll never forget it. Perhaps we can let young visitors to the stand pick a star in Kstars and we'll have the OTA slew to it. Unending possibilities.
So, Happy Bunny and thanks for your help
Thanks for your replies. I had unset all constraints.
The demo is on 18th Sep from 10:30am - 5pm GMT. Location is 51N 1.5W.
I'll attach the two files.
I was already editing the XML as you typed that. Thanks.
Also fixed the options as you mentioned.
Still having problems with it.
Not sure whether I can have several jobs with same name so have numbered them.
Executing the jobs now fails as all are in state idle and there is apparently nothing more to do.
Will need to site down with the manual for a while.
Thanks for your super-quick reply Udo.
I did try all of those options - especially the repeat until terminated.
I think though your suggestion has helped.
It appears that the Job Completion Options apply to each job, not the list of defined jobs. So the first job had no end time because I created it with the Job Completion option set to repeat until terminated. If I set that first (and subsequent jobs) to Sequence Completion, then it works.
So as you say, it appears I can define jobs here but I cannot run the whole sequence multiple times. If true then that would be an issue for this demo.
We'll be running a stand at an event next week and would like to have one scope slewing too different parts of the sky every minute. This will be during the day so it's just a demo for the interest of visitors.
I tried configuring the scheduler by adding 4 locations with RA and DEC. Manually slewing to them works fine. Putting them into the scheduler allows the first then any subsequent target is marked as invalid.
The error is "Warning: Job 'Demo Slew' cannot start because its previous sibling has no completion time, marking invalid."
I'm using a sequence file that just takes one 60s light frame at bin4, which will be ignored.
Any ideas how to get around this please, or is there a better way to do this ?
It's painful to redo but worth a try.
I also noticed that your install string is different.
sudo apt-get install indi-full kstars-bleeding
but yours is:
sudo apt-get install indi-full gsc
I don't know what the package gsc is but I didn't use it. Also you''re missing the kstars package, which contains EKOS.
I also do an update after adding Jasem's PPA.
If all else fails you could try my method and see if you fare any better.
Ubuntu 20.04 works fine with this as I understand 22 does.
After you install the OS and before you clone Jasem's PPA, did you run the following to update to latest packages ?
sudo apt-get update
sudo apt-get upgrade
Then do the indi / kstars stuff.
You didn't say whether you've read the link I sent. That link shows chapter and verse the method to install with Ubuntu 20.04.
That said, your success with the command to fix "broken install" shows that something was not right in the back end.
The crash log is created locally. You'll need to upload it as a zip or similar for anyone to comment.
Thanks for the tip Andrew.
I found it in the INDI Setup once EKOS was running.
Reduced from 255 to 20
Did you see this post John ?
When I set up each time, I do a rough PA using the built-in reticule on the HEQ5 Pro.
When it's connected to EKOS it seems the LED that lights up the reticule is on full.
Instead I connected the handset to the mount and dialled down the brightness to 2% and it does indeed dim it.
When I restart everything and connect again via INDI it's back at 100%.
Is there a setting in INDI to dim this please ?