David Allmon replied to the topic 'INTRA-focal or EXTRA-focal' in the forum. 2 months ago

On my system in takes you intrafocal, but that is because I sat and watched as I pushed the in button to see which direction it went. It turned out that one of my focusers, an EAF, was backwaards, so I set it to reversed in the settings. The other, a Pegasus FocusCube, turned out to be correct. It is just the side of the focuser I put it on that made the difference.
Hope that helps a little.

Read More...

David Allmon replied to the topic 'Per driver configurable delay?' in the forum. 3 months ago

Jasem,

One question...If it is indiserver doing this, is it reading the local database, and does that mean if I set it up on the Raspberry Pi it will still work if I connect remotely?

Read More...

David Allmon replied to the topic 'Per driver configurable delay?' in the forum. 3 months ago

Jasem,

It was "Auto Connect". I had it turned off because I normally need to initialize the LX600. It worked perfectly. It ran the script and initialized the scope, then attached tthe driver.

Thank you for your work on this. I think it is a worthwhile addition. I've attached the log file in case you want to look it over after your additional logging.

File Attachment:

File Name: log_07-16-38.txt
File Size: 70 KB


Read More...

David Allmon replied to the topic 'Per driver configurable delay?' in the forum. 3 months ago

Jasem,

Sorry it took so long, but I I had to build Kstars, indi, and the 3rd party drivers. It takes a while on the Raspberry Pi.

Editing the lx200autostar, I put a 30 second pre delay, then a bash script, with no post delay. It seems by the log file that it waited 30 seconds and then loaded the lx200autostar and the other 7 drivers. I'm not sure if that is what it is supposed to do.

Then I added a 10 second delay with no script to the pegasus_flatmaster driver, leaving the 30 second delay in the lx200autostar. That changed the load order, but not the behavior. It loaded the pegasus_flatmaster driver after 10 seconds, but also loaded the other drivers in the same second. It was as if the only delay it was seeing was the shortest one. I'm going by the log file - I can't actually verify that the 30 second delay did or did not happen. I also can't verify that the script actually ran. Does it wait until the script finishes before loading the driver?

I have attached the log file from the run where the Raspberry Pi was running Kstars and the indiserver.

File Attachment:

File Name: log_15-31-41.txt
File Size: 27 KB


Read More...

David Allmon replied to the topic 'Per driver configurable delay?' in the forum. 3 months ago

Jasem,

I pulled the source and compiled libev, indi, indi-3rdparty, and kstars. Everything seems to run, but I don't see where the config for the delay is.

Read More...

Thanks for the tip, but I already tried that. It is correct there, but just shows the city name and the country on the weather box. It's California - I'm in Arizona.



Thanks!

Read More...

David Allmon replied to the topic 'Per driver configurable delay?' in the forum. 3 months ago

Jasem,

That would cover all of my use cases. I'm not familiar enough with the code to say where I think it should live.

Thanks,

Read More...

David Allmon replied to the topic 'Per driver configurable delay?' in the forum. 3 months ago

Jasem,

There have been many times that I could use something like that. Like for Arduino based projects, which reset when the port is opened, then haven't finished initializing before the driver sends a software handshake. Twice I've had to modify hardware to compensate for that.

I have an LX600 with a bad GPS. When it boots, it is set to go to the daylight savings prompt and wait for the date and time. That takes 20 to 30 seconds. The lx200autostar knows nothing about this process, so I can't load indi until after I have powered on, and run a program to initialize the date and time on the scope. It would be really nice to have a driver that could power up a device, delay some amount (like the 20-30 second initialization time of an unattended LX600), and run a script to initiailize it correctly before the LX200driver attaches and hogs the port.

I built an 8-port switchable power box that is used for that now, but I have a separate python app that has checkboxes to power on each port. I would much rather have a driver that I could interface the box with that would do what you have suggested.

Thanks,

Read More...

Hi,

This is a minor problem, but I thought I would bring it up, to see if anyone has a fix. The weather section of the Stellarmate dashboard says "Glendale, USA", but there are three Glendales I am aware of: Glendale California, Glendale Arizona, and Glendale Pennsylvania. The weather is for Glendale Claifornia. I don't live there. The GPS coordinates are correct for my location.



Is there a place to edit that information to correct it?

Thanks,

Read More...

I built a profile having just the telescope simulator, CCD simulator, and the Pegasus Flatmaster. Then I built a sequence using default time and count to take a light frame, and added a sequence to take a dark frame, and one to make a flat field frame. When I clicked the play button the first sequence ran, and as soon as the second started, the program asked me if the simulator had a shutter. I said yes, and Indi Control Panel, Ekos, and Kstars all went away. I looked at the indi server and, although it was running, it had printed the following:

2022-06-06T01:34:25: startup: indiserver indi_simulator_ccd indi_simulator_telescope indi_pegasus_flatmaster 
2022-06-06T01:34:25: Driver indi_simulator_telescope: HaAxis: TrackRate 1, trackingRateDegSec 15.041067 arcsec
2022-06-06T01:42:05: Client 0: XML error: Line 5: Bogus end tag char <
2022-06-06T01:42:05: Client 0: XML read: 
  <oneSwitch name='FLAT_LIGHT_OFF'>
      On
  </oneSwitch>
</newSwitchVector>
<newSwitchVector device='Pegasus FlatMaster' name='FLAT_LIGHT_CONTROL'>
  <oneSwitch name='FLAT_LIGHT_OFF'>
      On
  </oneSwitch>
</newSwitchVector>

It printed the <oneSwitch... part about 100 times, and ended on a partial block. I've seen that kind of thing happen before. indiserver is still running.
It doesn't seem to matter what the frames are - dark light or flat, as long as you go from one with the light off to one with the llight on, or vice versa. It blows up about every time, providing you disconnect from the server between attempts. Occasionally it takes out indiserver as well. The indi logs show as above _or_ "connection reset by peer". I attached the Kstars log. It shows startup to starting the second sequence and then nothing.

File Attachment:

File Name: log_19-23-19.txt
File Size: 30 KB


Also, out of the blue, the flatmaster driver blurted out this message I've never seen before:
2022-06-06T02:24:45: Driver indi_pegasus_flatmaster: indi_pegasus_flatmaster dispatch error: Property FLAT_LIGHT_C is not defined in Pegasus FlatMaster.

Any help would be appreciated.

Read More...

Ken,

Its togling the RTS line. I built one a few years back using a USB to serial converter. It was for the shutter release on a Nikon camera. Only the RTS and ground were used. If you have one lying around, you could test it to see if that works. Wouldn't be as much fun as playing with an ATtiny85.

Dave

Read More...

Hi,

This is on Stellarmate, but isn't a Stellarmate problem. I'm using KStars 3.5.9 stable on an Ubuntu 20.4 system. Indi 1.9.6 is running on the Raspberry Pi with Stellarmate OS 1.7.1 32-bit. After upgrading to Stellarmate, and when I have these devices running:

indi_sbig_ccd
indi_asi_ccd
indi_asi_focuser
indi_pegasus_focuscube
indi_pegasus_flatmaster
indi_qhycfw2_wheel
indi_lx200autostar
indi_gpsd

and I start a run of flats, Ekos and Kstars and any fits viewer windows I have open go away. Loading KStars again, and starting Ekos, brings me back to where I was when I started the flat process - 1 second exposure time, wrong directory, count of 1, etc. Usually the flatmaster driver on Indi Control Panel is blank. I have to restart Indi on the Raspberry Pi.
I got around it (sort of) by building 2 shell scripts - one to load everything except flatmaster, and one to load these devices:
indi_sbig_ccd
indi_simulator_telescope
indi_qhycfw2_wheel
indi_pegasus_flatmaster

When I do imaging, I run the first script, "indi", and when I do flats, I run the second "flats" script. That resolves it, but won't really do for a solution. I will try to see if there is a combination that won't work together. In the mean time, has anyone seen such an interaction with the FlatMaster driver..?

The attached log shows the problem happening at 2022-06-03T21:17:45.493 (around line 134).

File Attachment:

File Name: log_21-15-59.txt
File Size: 271 KB


Thanks,

Read More...