Date   

Re: Wireless controller

Taj Wurl-Koth
 

Hi Nels,

Years ago there was a bug in the handpad receiver firmware that would cause it to erase itself. If yours was purchased prior to mid 2015, then I would expect that is what happened to yours. If so, you can send it to us and we'll fix it at no cost. I'll email you our address


Re: Wireless controller

Nels Johansen
 

Don,
Battery is good. The lights on the controller are very dim, when a direction button is pushed on the hand pad one of the lights on the controller blinks. 
Nels


Re: Wireless controller

Don W
 

Hi Nels,

Power to the handpad is a 9 volt battery.  If it is dead, the handpad is dead, except when you plug in the cable direct to teh controller (as you said you did).  The radio handpad unit gets it's power through the cable connected to the controller.  The lights on the radio receiver must be on - showing power to the radio unit.  So both these power sources have to be working for the radio handpad to work.
Don W


Wireless controller

Nels Johansen
 

Hello everyone,
Our wireless hand pad stopped working suddenly, the hand pad works when  the controller is bypassed by plugging a wire into the handpad and to the servo 2.  Which to me indicates the controller is fried. Am I wrong to think this?  Do I need to buy a new wireless hand pad and controller?
Nels Johansen


Re: Nebulosity vs NINA

Ross Salinger
 

The problem that Don alludes to is that to drive any another imaging program like MaximDL you have to know a lot about how that program permits access to its camera control methods. It's got to be a lot of work and every time there is a release in the server side program you'd have to at least look at whether something needs to changed.  At the same time, every popular imaging program from the SKYX all the way to Voyager support any ASCOM camera that comes out immediately. When I got my new QHY600 camera I downloaded and installed the drivers (native and ASCOM) and was taking pictures, plate solving, etc. in minutes in both the SKYX and MaximDL.

So,  the conclusion that I would draw is that SiTech would be better off writing its own code to control ASCOM compatible cameras. That would make it independent of the imaging programs and future proof it against the day the MaximDL finally dies. Having said that, I don't code anymore so I don't know how practical that would be. It's just a suggestion. There are only a few things that SiTech would have to support in terms of camera control to make it work for 99 percent of users. There's no need to support flat frames or dark frames or bias frames, or regions of interest, camera modes, RBI, etc. It just needs to be able to take a picture and platesolve it etc.

Rgrds-Ross

On 9/29/2020 2:37 PM, Don W wrote:
Hi Jesse,

As nice as it would be, I don't think a "generic" camera control in SiTech is possible.  There are two levels of camera control overall as I see it.
First there are camera control software such as Maxim, AstroArt, Nebulosity, SGP, and many others.  Each of these have their own unique sets of commands, methodologies, and ways of communicating ( many use ASCOM, but Nebulosity uses the Clipboard and a separate "Listen" program).  These software have their own long list of cameras that they can control.  Controlling an older CCD vs a newer CMOS or DSLR takes many specific commands.

Second are a lot of cameras (many are small video cameras) that use ASCOM methods to connect.  These are mostly all available via the first software group, whether they could or should be controllable directly from SiTech is  possible, but many of these are very small cameras, suitable for Planetary Video and guiding, but not large enough for platesolving.

Don W


Re: Nebulosity vs NINA

Don W
 

Hi Jesse,

As nice as it would be, I don't think a "generic" camera control in SiTech is possible.  There are two levels of camera control overall as I see it.
First there are camera control software such as Maxim, AstroArt, Nebulosity, SGP, and many others.  Each of these have their own unique sets of commands, methodologies, and ways of communicating ( many use ASCOM, but Nebulosity uses the Clipboard and a separate "Listen" program).  These software have their own long list of cameras that they can control.  Controlling an older CCD vs a newer CMOS or DSLR takes many specific commands.

Second are a lot of cameras (many are small video cameras) that use ASCOM methods to connect.  These are mostly all available via the first software group, whether they could or should be controllable directly from SiTech is  possible, but many of these are very small cameras, suitable for Planetary Video and guiding, but not large enough for platesolving.

Don W


Re: Nebulosity vs NINA

jmgoldba
 

On Mon, Sep 28, 2020 at 12:02 AM, Don W wrote:
SiTech only controls the camera from the list of programs in CameraStuff in ChangeConfig.
I posted a request for a generic camera control option last April.

In the beginning there was MaxIm for camera control and MaxIm camera drivers.
Nowadays there's a plethora of camera control software using ASCOM drivers.
ASCOM won't go into what I call the last mile of camera control which involves writing
the image obtained from the camera to a FITS file so here we are.

I wonder whether SiTech scripts really need that last mile to do what they do?

Jesse


Re: What happened to Lenord?

Ned Smith
 

I have two Delrin worm gears of his that I would like to sell. Contact me off list.


On Tue, Sep 29, 2020 at 8:15 AM Mark Navarro <star.hunter777@...> wrote:
Leonard got out of the telescope mount  business a few years back.

On Sun, Sep 27, 2020, 11:50 PM Mike Colyar <mike@...> wrote:
Leonard Stage isn't answering emails or voice mails. Has he closed his business or having problems?



--
Ned Smith


Re: What happened to Lenord?

Mark Navarro
 

Leonard got out of the telescope mount  business a few years back.


On Sun, Sep 27, 2020, 11:50 PM Mike Colyar <mike@...> wrote:
Leonard Stage isn't answering emails or voice mails. Has he closed his business or having problems?


Re: Nebulosity vs NINA

David Newbury
 

I am very interested in hearing that you are using N.I.N.A. with your SiTech controller.
I am currently using the old SGPro V2. with my MESU 200. I was waiting for V4 to be released as I was lead to believe it will support dual camera's. However, I have since found that new versions of SGPro will be subscription only! Bye Bye SGPro for me. I will go down "free" to use N.I.N.A. route instead. As I know N.I.N.A does support dual rigs and has a control setting to allow dither when neither camera is imaging. 
I have imaged with N.I.N.A but not setup a full control imaging session, as of yet. Exciting times ahead :)

Thanks

Dave.


On Monday, 28 September 2020, 14:49:43 BST, moofrost@... <moofrost@...> wrote:


Hi. I use NINA exclusively with Sitech. Never an issue. Through Ascom. Multiple plate solves when framing etc. Actually runs smooth as butter.

 How are you set up?


Re: What happened to Lenord?

Mike Colyar
 

Web sites live on forever I guess. I just wanted to ask him a few questions about plastic worm wheels. I’ll just cut a couple and test them.

Thanks,

Mike


On Sep 28, 2020, at 9:42 AM, Taj Wurl-Koth <twurlkoth@...> wrote:

Hi Mike,

Lenord closed shop several years ago. 2013 by my records. What do you need? We may be able to help.


Re: Stand alone operation with an Alt/Alt

Mike Colyar
 

Dunno why I didn’t thnk of that way of looking at it. Or I could move to Equador and simplify the problem. That one anyway.

Mike


On Sep 28, 2020, at 8:50 AM, Dan Gray <grayarea@...> wrote:

I'm not 100% sure, but I think if you change your latitude to zero (using Servo config) and then use either the slewNTrack or DragNTrack, it may work.  Better make it just a bit more than zero, say 0.1 degs north.
Dan

On Sun, Sep 27, 2020 at 1:05 PM Mike Colyar <mike@...> wrote:
Hi Russel,

I remember reading that. It made sense to me, sort of. Thanks for reminding me though.

What I’m hopeing to do is run a mount in standalone mode for public star parties and one of the needs is to minimize the amount of equipment to haul around. This includes a laptop and cameras and the like. Easy to do in Alt/Az and Equatorial but not obvious to me in Alt/Alt.

Probably Dan has this all sorted out or will have a solution in mind. He’s always been about three jumps ahead of me.

Mike


On Sep 27, 2020, at 12:15 PM, Russell R via groups.io <rem.64@...> wrote:

Hi Mike,

Going to add to what Don said.

I did this a while back with a mount that can move from equatorial to Alt/Alt by just turning a crank.  Easier to initialize than an equatorial.  In my case, just align mount axis with NCP and get fairly level.  Then do photo int. followed by a mount model.  I did some testing at what degrees I could tilt the axis using PXP.  It went all the way to 11.3° before the mount model blew up.  However some things happen along the way.  When a mount model is built by the script, it places calibration points right on the edge of the horizon file boundary.  When you start to "tilt" the axis, some of these calibration points are moved out of the boundary and PXP won't included them anymore.  I was impressed by how far it did work.  For chasing satellites it is great, but for imaging, you would probably need a rotator.  

There is a drawback however to doing this which caused issues switching back and forth.  Here is what Dan told me.  
From Dan Gray:
Yes, changing types of scopes will completely mess up the parking and everything.
I suggest you get everything working (inlcuding any homes or parks) in the alt/alt format, then go to the SiTechExe->Config ->ChangeConfig ->Misc
Save a backup named "Alt_Alt.cfg".
Ok, now close SiTechExe, always recommended if changing mount types.
 
Go to the SiTechData folder
Copy any and all the ParkPointXP files and the HomePointXP files to same with a prefix of Alt_Alt_
 
Ok, restart SiTechExe, change the mount to GEM or Equatorial, "OK", then exit SiTechExe again.
Now restart SiTechExe, and load models, set your home and/or park positions, etc.
Now, again, go to the SiTechExe->Config ->ChangeConfig ->Misc
Save a backup named "Equatorial.cfg".
 
Ok, exit SiTechExe,
Copy any and all the ParkPointXP files and the HomePointXP files to same with a prefix of Equ_
 
Now make yourself a batch file that copies the appropriate Alt_Alt files and overwrite the existing files without the prefixes.
 
Make another batch file that copies the appropriate Equ_ files and overwrite the existing files without the prefixes.
 
OR, use a different computer for the two types of mounts.
Dan

Hope this helps some.
Russell R.





Re: What happened to Lenord?

Taj Wurl-Koth
 

Hi Mike,

Lenord closed shop several years ago. 2013 by my records. What do you need? We may be able to help.


Re: Stand alone operation with an Alt/Alt

Dan Gray
 

I'm not 100% sure, but I think if you change your latitude to zero (using Servo config) and then use either the slewNTrack or DragNTrack, it may work.  Better make it just a bit more than zero, say 0.1 degs north.
Dan


On Sun, Sep 27, 2020 at 1:05 PM Mike Colyar <mike@...> wrote:
Hi Russel,

I remember reading that. It made sense to me, sort of. Thanks for reminding me though.

What I’m hopeing to do is run a mount in standalone mode for public star parties and one of the needs is to minimize the amount of equipment to haul around. This includes a laptop and cameras and the like. Easy to do in Alt/Az and Equatorial but not obvious to me in Alt/Alt.

Probably Dan has this all sorted out or will have a solution in mind. He’s always been about three jumps ahead of me.

Mike


On Sep 27, 2020, at 12:15 PM, Russell R via groups.io <rem.64@...> wrote:

Hi Mike,

Going to add to what Don said.

I did this a while back with a mount that can move from equatorial to Alt/Alt by just turning a crank.  Easier to initialize than an equatorial.  In my case, just align mount axis with NCP and get fairly level.  Then do photo int. followed by a mount model.  I did some testing at what degrees I could tilt the axis using PXP.  It went all the way to 11.3° before the mount model blew up.  However some things happen along the way.  When a mount model is built by the script, it places calibration points right on the edge of the horizon file boundary.  When you start to "tilt" the axis, some of these calibration points are moved out of the boundary and PXP won't included them anymore.  I was impressed by how far it did work.  For chasing satellites it is great, but for imaging, you would probably need a rotator. 

There is a drawback however to doing this which caused issues switching back and forth.  Here is what Dan told me.  
From Dan Gray:
Yes, changing types of scopes will completely mess up the parking and everything.
I suggest you get everything working (inlcuding any homes or parks) in the alt/alt format, then go to the SiTechExe->Config ->ChangeConfig ->Misc
Save a backup named "Alt_Alt.cfg".
Ok, now close SiTechExe, always recommended if changing mount types.
 
Go to the SiTechData folder
Copy any and all the ParkPointXP files and the HomePointXP files to same with a prefix of Alt_Alt_
 
Ok, restart SiTechExe, change the mount to GEM or Equatorial, "OK", then exit SiTechExe again.
Now restart SiTechExe, and load models, set your home and/or park positions, etc.
Now, again, go to the SiTechExe->Config ->ChangeConfig ->Misc
Save a backup named "Equatorial.cfg".
 
Ok, exit SiTechExe,
Copy any and all the ParkPointXP files and the HomePointXP files to same with a prefix of Equ_
 
Now make yourself a batch file that copies the appropriate Alt_Alt files and overwrite the existing files without the prefixes.
 
Make another batch file that copies the appropriate Equ_ files and overwrite the existing files without the prefixes.
 
OR, use a different computer for the two types of mounts.
Dan

Hope this helps some.
Russell R.


Re: Nebulosity vs NINA

Eric Walden
 

I have also been using NINA exclusively with Scitech on my Mesu 200 Mk2. I haven’t built a pointing model. Just use plate solve and sync. Works perfectly almost all the time. Have been having a few crashing issues in NINA recently but not sure if that is a product of it or my setup.


Re: Nebulosity vs NINA

paul K
 

Hi Chris, have you looked at Sequence generator pro? It integrates really well with sitech and many other ascom compliant devices. 
Best wishes
Paul

On Mon, 28 Sep 2020, 08:02 Don W, <westergren@...> wrote:
 

Hello

I guess I should start a new question,if I could find out how to,but here goes.

 

If I replace Nebulosity with NINA as the telescope control program can I build a plate solve mount model?

OR

how do you keep Nebulosity in listen mode for more than a few plate solves?

Chris

Hi Chris,
Sorry but NINA is not supported by SiTech at this time.  I don't know why Nebulosity drops out of listening mode.

There is a cumbersome way to use Nina, by modifying the script to develop a PXP model to pause and manually take a Fits image in NINA and save it to the default.fit location, then let SiTech run Platesolve 2 or 3 for that PXP point, then move to the next point.

SiTech only controls the camera from the list of programs in CameraStuff in ChangeConfig.
Don W




Re: Nebulosity vs NINA

moofrost@...
 

Hi. I use NINA exclusively with Sitech. Never an issue. Through Ascom. Multiple plate solves when framing etc. Actually runs smooth as butter.

 How are you set up?


Re: Nebulosity vs NINA

Che
 

I used to have problems with Nebulosity dropping out of listening mode with my QHY8 and QHY 10 cams.  When put the cams into fast download mode the problem went away.  I may have binned as well I am not sure.  It was taking too long to download and Nebulosity would drop out.  Not sure what cam you are using but you might give that a try.  Would be nice if Dan could implement NINA support as it is awesome and growing rapidly in number of users.

Che

On 9/28/2020 1:12 AM, Chris Waters wrote:

OK,

Thanks Don, seems like I persevere with Nebulosity.

Chris

On 28/9/20 3:02 pm, Don W wrote:
 

Hello

I guess I should start a new question,if I could find out how to,but here goes.

 

If I replace Nebulosity with NINA as the telescope control program can I build a plate solve mount model?

OR

how do you keep Nebulosity in listen mode for more than a few plate solves?

Chris

Hi Chris,
Sorry but NINA is not supported by SiTech at this time.  I don't know why Nebulosity drops out of listening mode.

There is a cumbersome way to use Nina, by modifying the script to develop a PXP model to pause and manually take a Fits image in NINA and save it to the default.fit location, then let SiTech run Platesolve 2 or 3 for that PXP point, then move to the next point.

SiTech only controls the camera from the list of programs in CameraStuff in ChangeConfig.
Don W




Re: Nebulosity vs NINA

Chris Waters
 

OK,

Thanks Don, seems like I persevere with Nebulosity.

Chris

On 28/9/20 3:02 pm, Don W wrote:
 

Hello

I guess I should start a new question,if I could find out how to,but here goes.

 

If I replace Nebulosity with NINA as the telescope control program can I build a plate solve mount model?

OR

how do you keep Nebulosity in listen mode for more than a few plate solves?

Chris

Hi Chris,
Sorry but NINA is not supported by SiTech at this time.  I don't know why Nebulosity drops out of listening mode.

There is a cumbersome way to use Nina, by modifying the script to develop a PXP model to pause and manually take a Fits image in NINA and save it to the default.fit location, then let SiTech run Platesolve 2 or 3 for that PXP point, then move to the next point.

SiTech only controls the camera from the list of programs in CameraStuff in ChangeConfig.
Don W




Nebulosity vs NINA

Don W
 

 

Hello

I guess I should start a new question,if I could find out how to,but here goes.

 

If I replace Nebulosity with NINA as the telescope control program can I build a plate solve mount model?

OR

how do you keep Nebulosity in listen mode for more than a few plate solves?

Chris

Hi Chris,
Sorry but NINA is not supported by SiTech at this time.  I don't know why Nebulosity drops out of listening mode.

There is a cumbersome way to use Nina, by modifying the script to develop a PXP model to pause and manually take a Fits image in NINA and save it to the default.fit location, then let SiTech run Platesolve 2 or 3 for that PXP point, then move to the next point.

SiTech only controls the camera from the list of programs in CameraStuff in ChangeConfig.
Don W



2061 - 2080 of 33961