Remote Turn On/Off 10Micron GM1000 HPS · Jerry Gerber · ... · 52 · 1424 · 8

jsg 9.55
Topic starter
...
· 
·  2 likes
·  Share link
All good.  I got some help from Chris, the chief tech at DSP Remote.  He's sharp and very generous with his time and expertise.  I now have the capacity to turn on and off all gear from my desktop browser at home–without losing my remote connection.

Now on to the next problem….

Thank you all for your help and sharing your experience!

Jerry
www.youtube.com/@astromusicvideo
Like
AccidentalAstronomers 18.64
...
· 
·  Share link
John Hayes:
I was going to make this same point.  For observatories that run from solar recharged batteries, you should completely power your equipment down each day to reduce the load on the electrical system.  And after a long stretch of cloudy weather, leaving equipment on 24/7 will just draw the power down until the sun comes back out.  This happens about once per year at Obstech in Chile and the administrators have to  ask everyone to power their equipment down until they can bring everything back on line.

John


Hey John:

What did you do when you were at DSW--especially during the summer "monsoon" season? I've found that it's not unusual to have stretches of cloudy, rainy weather where humidity climbs into the 80s and 90s at night. Looks like we might be headed for a stretch of that this week:

image.png

When I first got out to DSW last July, I used to turn everything off every morning or for days at a time during long stretches of rain. I went out there about a month later to deal with a camera issue, and the weather was wet and humid at the time. When I uncovered my OTA, I saw that water had accumulated inside the dew shield next to the objective (thankfully, it wasn't quite deep enough to have reached the glass yet). That was when I decided it might be best to stay powered up through such periods. And Lloyd told me he would just leave everything powered up all the time 24/7/365. I haven't seen any more water accumulating since I have kept everything on. DSW is a very different environment from Obstech, both weather-wise, and also from the standpoint of how the observatory is powered.

Since you're the guy who literally wrote the manual on best practices for remote imaging (an incredible document, btw), I'm definitely interested in your thoughts on an environment like DSW. I'm still relatively new to all this, so my opinions and practices are not even remotely steeped in experience or deep knowledge and should always be taken for what they're worth, which ain't a whole lot.

I do have more than 40 years' experience in IT, managing businesses with large server rooms and the like. At one point, we had an old Novell server that had been up and operating continuously for more than 14 years. And any time our servers had power turned off for any reason, it was an all-hands-on-deck moment. So I know that electronics can be designed to stay up and running continuously for years, if not decades. That makes me tend toward what Ed Thomas says in the 10u forum thread @Ruediger posted about power cycling things. Still, a dedicated server room in a secure facility with its own HVAC system and power fail-safes is one thing. An unsealed metal Quonset hut sitting in the New Mexico desert is quite another.

CS,
Tim
Like
jsg 9.55
Topic starter
...
· 
·  Share link
Timothy Martin:
John Hayes:
I was going to make this same point.  For observatories that run from solar recharged batteries, you should completely power your equipment down each day to reduce the load on the electrical system.  And after a long stretch of cloudy weather, leaving equipment on 24/7 will just draw the power down until the sun comes back out.  This happens about once per year at Obstech in Chile and the administrators have to  ask everyone to power their equipment down until they can bring everything back on line.

John


Hey John:

What did you do when you were at DSW--especially during the summer "monsoon" season? I've found that it's not unusual to have stretches of cloudy, rainy weather where humidity climbs into the 80s and 90s at night. Looks like we might be headed for a stretch of that this week:

image.png

When I first got out to DSW last July, I used to turn everything off every morning or for days at a time during long stretches of rain. I went out there about a month later to deal with a camera issue, and the weather was wet and humid at the time. When I uncovered my OTA, I saw that water had accumulated inside the dew shield next to the objective (thankfully, it wasn't quite deep enough to have reached the glass yet). That was when I decided it might be best to stay powered up through such periods. And Lloyd told me he would just leave everything powered up all the time 24/7/365. I haven't seen any more water accumulating since I have kept everything on. DSW is a very different environment from Obstech, both weather-wise, and also from the standpoint of how the observatory is powered.

Since you're the guy who literally wrote the manual on best practices for remote imaging (an incredible document, btw), I'm definitely interested in your thoughts on an environment like DSW. I'm still relatively new to all this, so my opinions and practices are not even remotely steeped in experience or deep knowledge and should always be taken for what they're worth, which ain't a whole lot.

I do have more than 40 years' experience in IT, managing businesses with large server rooms and the like. At one point, we had an old Novell server that had been up and operating continuously for more than 14 years. And any time our servers had power turned off for any reason, it was an all-hands-on-deck moment. So I know that electronics can be designed to stay up and running continuously for years, if not decades. That makes me tend toward what Ed Thomas says in the 10u forum thread @Ruediger posted about power cycling things. Still, a dedicated server room in a secure facility with its own HVAC system and power fail-safes is one thing. An unsealed metal Quonset hut sitting in the New Mexico desert is quite another.

CS,
Tim

It seems there are both advantages and disadvantages of turning gear off and on and the same for leaving it on 24-7.   Is heat worse than humidity?  I guess that depends upon how much heat for how long and how much humidity for how long.   

At DSP Remote I don't think the humidity gets very high, but I could be wrong.  I was told I would not even need dew heaters, but that may be only for summer months. Here's a chart showing highest humidity in August reaching around 56%.

Screenshot 2024-07-07 at 11-48-41 Animas NM Climate.png
Edited ...
Like
AnaTa 3.34
...
· 
·  Share link
Timothy Martin:
John Hayes:
I was going to make this same point.  For observatories that run from solar recharged batteries, you should completely power your equipment down each day to reduce the load on the electrical system.  And after a long stretch of cloudy weather, leaving equipment on 24/7 will just draw the power down until the sun comes back out.  This happens about once per year at Obstech in Chile and the administrators have to  ask everyone to power their equipment down until they can bring everything back on line.

John


Hey John:

What did you do when you were at DSW--especially during the summer "monsoon" season? I've found that it's not unusual to have stretches of cloudy, rainy weather where humidity climbs into the 80s and 90s at night. Looks like we might be headed for a stretch of that this week:

image.png

When I first got out to DSW last July, I used to turn everything off every morning or for days at a time during long stretches of rain. I went out there about a month later to deal with a camera issue, and the weather was wet and humid at the time. When I uncovered my OTA, I saw that water had accumulated inside the dew shield next to the objective (thankfully, it wasn't quite deep enough to have reached the glass yet). That was when I decided it might be best to stay powered up through such periods. And Lloyd told me he would just leave everything powered up all the time 24/7/365. I haven't seen any more water accumulating since I have kept everything on. DSW is a very different environment from Obstech, both weather-wise, and also from the standpoint of how the observatory is powered.

Since you're the guy who literally wrote the manual on best practices for remote imaging (an incredible document, btw), I'm definitely interested in your thoughts on an environment like DSW. I'm still relatively new to all this, so my opinions and practices are not even remotely steeped in experience or deep knowledge and should always be taken for what they're worth, which ain't a whole lot.

I do have more than 40 years' experience in IT, managing businesses with large server rooms and the like. At one point, we had an old Novell server that had been up and operating continuously for more than 14 years. And any time our servers had power turned off for any reason, it was an all-hands-on-deck moment. So I know that electronics can be designed to stay up and running continuously for years, if not decades. That makes me tend toward what Ed Thomas says in the 10u forum thread @Ruediger posted about power cycling things. Still, a dedicated server room in a secure facility with its own HVAC system and power fail-safes is one thing. An unsealed metal Quonset hut sitting in the New Mexico desert is quite another.

CS,
Tim

**Any server is not astrophotography rig. They have to run non-stop. Question is that do people leave professional telescopes and associated rigs powered up 24/7? 
CS!

Armen
Like
AccidentalAstronomers 18.64
...
· 
·  Share link
Jerry Gerber:
At DSP Remote I don't think the humidity gets very high, but I could be wrong.  I was told I would not even need dew heaters, but that may be only for summer months. Here's a chart showing highest humidity in August reaching around 56%.


Interesting that it would be that different for you from what I see. But I guess being 200 miles north of you up on a mesa in the mountains is a significant shift. As you can see from the chart above, we're expecting over 90% humidity at around 1:00am early tomorrow morning. Again, I kind of go back to what your DSP guy, Ed Thomas, said in that thread--that power cycling electronics is generally harder on it than running it all the time. But your ambient temps during the summer may also be higher than mine, too, which is definitely a consideration. I think the lesson in all this is that if you ask five people this question, you'll get forty-three different opinions. I haven't yet seen anything in this thread that compels me to make a change from what I'm doing. But my mind is open. Time will tell.
Like
jsg 9.55
Topic starter
...
· 
·  Share link
Timothy Martin:
Jerry Gerber:
At DSP Remote I don't think the humidity gets very high, but I could be wrong.  I was told I would not even need dew heaters, but that may be only for summer months. Here's a chart showing highest humidity in August reaching around 56%.


Interesting that it would be that different for you from what I see. But I guess being 200 miles north of you up on a mesa in the mountains is a significant shift. As you can see from the chart above, we're expecting over 90% humidity at around 1:00am early tomorrow morning. Again, I kind of go back to what your DSP guy, Ed Thomas, said in that thread--that power cycling electronics is generally harder on it than running it all the time. But your ambient temps during the summer may also be higher than mine, too, which is definitely a consideration. I think the lesson in all this is that if you ask five people this question, you'll get forty-three different opinions. I haven't yet seen anything in this thread that compels me to make a change from what I'm doing. But my mind is open. Time will tell.

Maybe Ed is right, but it may be different for different situations.  I've managed an electronic music studio for decades and always shut everything off before going to bed.   On average my DAW (digital audio workstation) runs flawlessly for 8-10 years, as does all the other peripheral equipment, and that's with daily power-up and power-down cycles.  But the equipment is always indoors with almost always very mild temperatures. 

Chris, the chief tech at DSP Remote, says he leaves everything on and never powers down and he's had no problems, although I don't know for how long he's been doing that.   Temperatures are getting hotter and hotter, and scarier too, we were supposed to go imaging north of San Francisco this past Friday for 3 days but we cancelled the trip as the temperatures there were up to 114F.  Palm Springs, California got up to 124F the other day.   And it's going to continue to get hotter as the fossil fuels companies (and all of us, really) are continuing to thicken the atmosphere.
Like
AccidentalAstronomers 18.64
...
· 
·  Share link
Jerry Gerber:
Maybe Ed is right, but it may be different for different situations.  I've managed an electronic music studio for decades and always shut everything off before going to bed.


Doing my part to contribute to the climate change! I've had a project studio in my house for decades as well. I never turn off my computers. I've had more than my share of computer issues over the years, but I can't say they were ever related leaving stuff on.
Like
jhayes_tucson 26.84
...
· 
·  1 like
·  Share link
Timothy Martin:
John Hayes:
I was going to make this same point.  For observatories that run from solar recharged batteries, you should completely power your equipment down each day to reduce the load on the electrical system.  And after a long stretch of cloudy weather, leaving equipment on 24/7 will just draw the power down until the sun comes back out.  This happens about once per year at Obstech in Chile and the administrators have to  ask everyone to power their equipment down until they can bring everything back on line.

John


Hey John:

What did you do when you were at DSW--especially during the summer "monsoon" season? I've found that it's not unusual to have stretches of cloudy, rainy weather where humidity climbs into the 80s and 90s at night. Looks like we might be headed for a stretch of that this week:

image.png

When I first got out to DSW last July, I used to turn everything off every morning or for days at a time during long stretches of rain. I went out there about a month later to deal with a camera issue, and the weather was wet and humid at the time. When I uncovered my OTA, I saw that water had accumulated inside the dew shield next to the objective (thankfully, it wasn't quite deep enough to have reached the glass yet). That was when I decided it might be best to stay powered up through such periods. And Lloyd told me he would just leave everything powered up all the time 24/7/365. I haven't seen any more water accumulating since I have kept everything on. DSW is a very different environment from Obstech, both weather-wise, and also from the standpoint of how the observatory is powered.

Since you're the guy who literally wrote the manual on best practices for remote imaging (an incredible document, btw), I'm definitely interested in your thoughts on an environment like DSW. I'm still relatively new to all this, so my opinions and practices are not even remotely steeped in experience or deep knowledge and should always be taken for what they're worth, which ain't a whole lot.

I do have more than 40 years' experience in IT, managing businesses with large server rooms and the like. At one point, we had an old Novell server that had been up and operating continuously for more than 14 years. And any time our servers had power turned off for any reason, it was an all-hands-on-deck moment. So I know that electronics can be designed to stay up and running continuously for years, if not decades. That makes me tend toward what Ed Thomas says in the 10u forum thread @Ruediger posted about power cycling things. Still, a dedicated server room in a secure facility with its own HVAC system and power fail-safes is one thing. An unsealed metal Quonset hut sitting in the New Mexico desert is quite another.

CS,
Tim

Hi Tim,
As I'm sure you know, I was out at DSW for nearly 5 years but I never had an issue with water actually pooling anywhere.  This might be an argument for always parking the telescope horizontally.   If this were an ongoing problem, I'd suggest drilling small (~ 1/16") drain holes in strategic positions and always parking horizontally.  Dew and frost are definitely a very real problems at DSW.  I built my own Arduino controlled anti-dew system that worked amazingly well so dew and frost never formed when I was running.  I suppose that if you were getting dew when the roof was closed, that you might want to keep your anti-dew system powered up all the time as Lloyd suggested.  My C14 was wrapped in Reflextix with two heater straps on the dew shield and one strap just behind the corrector plate.  The Arduino controller simply measured the temperature-dew point spread and turned on a Dew Buster controller when the spread went below a fixed threshold value (~4-5 degrees).

Since DSW is on the power grid, leaving your stuff on 24/7 isn't the kind of concern that it might be if the main power came from solar cells and batteries.  I always shut my system down every morning and powered it back up at night and I still do that in Chile.  I've heard the argument that temperature cycling the PC (and other gear) might cause more wear and tear than just leaving it on; but, I don't really buy into that argument.  I use industrial level, wide temperature range PCs that are rated for operation from -25C to 70C (!) and so far, they have served me well.  One downside to leaving the camera on all the time is that the fans accumulate dust at a rate proportional to how long the fans run so leaving the cameras on all the time will eventually completely clog up cooling system with dust.  This might be an issue where there are a lot of opinions but not much actually data.  I've noticed that roughly half of the operators at both observatories that I've been at leave all of their equipment running 24/7 so it must be fine.

BTW, dew is also an issue at Obstech.  It is not at all uncommon during certain times of the year to find everything absolutely soaked by midnight.  Even my MacBook Pro got pretty wet on a few nights while I was setting up my ASA600.  That's why I was so concerned that ASA doesn't supply their scopes with any internal heaters for dew protection.  I've discovered that the fans are so effective that they work well to prevent dew on the optics--at least so far.


John
Like
Supro 4.37
...
· 
·  Share link
i may be late to the party, but finally got Digital Logger Pro to do everything I want. Getting Wake-On-Lan going was critical. Even if I leave the PC on mostly, I want to be able to shut it down in the summer months if I can. 

And regardless, turning it back on remote is sort of important. 

After setting Wake-on-Lan in BIOS and within Windows Network Adapter settings...I got Digital Loggers script going through that web interface. It seems fairly robust as I've been testing for a bit now. Here's the snippet below. 

-- Send WOL to outlet 8
function WOL_outlet8()
        WOL("11:AA:11:aa:23:gf") -- your MAC here       
        log.notice("Wake On Lan command issued")
end

image.png

I know i'm about the 4995th person to circumnavigate this, but just in case its helpful...
Like
jhayes_tucson 26.84
...
· 
·  Share link
Nick Grundy:
i may be late to the party, but finally got Digital Logger Pro to do everything I want. Getting Wake-On-Lan going was critical. Even if I leave the PC on mostly, I want to be able to shut it down in the summer months if I can. 

And regardless, turning it back on remote is sort of important. 

After setting Wake-on-Lan in BIOS and within Windows Network Adapter settings...I got Digital Loggers script going through that web interface. It seems fairly robust as I've been testing for a bit now. Here's the snippet below. 

-- Send WOL to outlet 8
function WOL_outlet8()
        WOL("11:AA:11:aa:23:gf") -- your MAC here       
        log.notice("Wake On Lan command issued")
end

image.png

I know i'm about the 4995th person to circumnavigate this, but just in case its helpful...

I must be missing something.  I use a Digital Loggers IP power switch as well but I don't understand why is this needed?  I just set my PC to boot on power up in the BIOS so that when I turn on the power through the IP switch, it boots.  When I'm done, I shut it down from Windows.  My IP power switch isn't affected by a loss of power--other than it simply reverts to everything off.  I just have to connect to it to turn everything on when the power comes back on and I'm ready.

John
Like
Supro 4.37
...
· 
·  Share link
John Hayes:
why is this needed?


I assume you have your PC set to turn on in the event of power loss? 

In testing, and what I'm anticipating for remote, just turning power on to the outlet won't get the PC to start if I shut it down at the end of the session. 
  1. End imaging session
  2. Transfer data and Shutdown PC via Windows
  3. Power down outlets via Digital Loggers web interface (or script)
  4. ....next evening....
  5. Access and Power on outlets via Digital Logger web interface
  6. Send Wake-on-Lan to PC via script
  7. Access PC, connect, etc.


@John Hayes It sounds like you have it set up so #6 is unecessary? (that's what the function above does)
Like
bdm201170 8.64
...
· 
·  Share link
Jerry Gerber:
All good.  I got some help from Chris, the chief tech at DSP Remote.  He's sharp and very generous with his time and expertise.  I now have the capacity to turn on and off all gear from my desktop browser at home--without losing my remote connection.

Now on to the next problem....

Thank you all for your help and sharing your experience!

Jerry
www.youtube.com/@astromusicvideo

hi

this one working perfect and not expensive ( around $ 200 dollars )

netBooter NP-0201DU  

CS, Brian
Like
Reg_00 9.14
...
· 
·  Share link
Nick Grundy:
John Hayes:
why is this needed?


I assume you have your PC set to turn on in the event of power loss? 

In testing, and what I'm anticipating for remote, just turning power on to the outlet won't get the PC to start if I shut it down at the end of the session. 
  1. End imaging session
  2. Transfer data and Shutdown PC via Windows
  3. Power down outlets via Digital Loggers web interface (or script)
  4. ....next evening....
  5. Access and Power on outlets via Digital Logger web interface
  6. Send Wake-on-Lan to PC via script
  7. Access PC, connect, etc.


@John Hayes It sounds like you have it set up so #6 is unecessary? (that's what the function above does)

I do the same as John. If I need to cold boot my PC I just cycle that outlet on the Digital Logger. Most mini PCs can be set to power on when power is lost then restored. You can script the digital logger to cycle a port at any interface if you want to automate this task.
Edited ...
Like
jhayes_tucson 26.84
...
· 
·  1 like
·  Share link
Nick Grundy:
John Hayes:
why is this needed?


I assume you have your PC set to turn on in the event of power loss? 

In testing, and what I'm anticipating for remote, just turning power on to the outlet won't get the PC to start if I shut it down at the end of the session. 
  1. End imaging session
  2. Transfer data and Shutdown PC via Windows
  3. Power down outlets via Digital Loggers web interface (or script)
  4. ....next evening....
  5. Access and Power on outlets via Digital Logger web interface
  6. Send Wake-on-Lan to PC via script
  7. Access PC, connect, etc.


@John Hayes It sounds like you have it set up so #6 is unecessary? (that's what the function above does)

Yes...as I said, I set the BIOS so that the PC will boot when power is applied and I've been running that way for about 7 years of remote imaging without any problem.  If what you are doing works, that's great but I think that if you simply do the same thing that I'm doing (it's actually what everyone does), it will work just fine and you won't need any code or scripts at all.  Keep it simple!

Do you know how to get into the BIOS on your PC?  The boot on power up is an option on every machine that I've seen.

John
Edited ...
Like
Supro 4.37
...
· 
·  Share link
John Hayes:
PC will boot when power is applied


yup, I've gotten in and done the boot settings. 

What I hit was that when i shutdown the PC gracefully, even when power was reapplied, it wouldn't start. I didn't test that a lot though and just assumed I needed something to do WakeOnLan. 

I'm trying to think if there'd ever be a scenario where i'd want to wait and start the PC via the script (instead of just start on its own like you have it). Can't think of any. I guess its good to have options though. 

If i wanted simple, I think I picked the wrong hobby :-)
Like
Rowan.Prangley 0.00
...
· 
·  Share link
Howdy,

I use a Primalucelab Eagle 4 Pro as my main drive and from here, use WakeOnLan (WOL) commands via MountWizzard4 (MW4) to start my 10Micron.

By toggling the Eagle PC to wake when power is turned on via relay - I believe this is a Windows setting - it has been very straightforward to start the mount and the whole process can be scripted in Voyager or similar observatory software if needed.

Best,

Rowan
Like
Supro 4.37
...
· 
·  Share link
Rowan Prangley:
t has been very straightforward to start the mount and the whole process can be scripted in Voyager or similar observatory software if needed.


so, is everything shut down at some point? 

do you use VPN, then send the Wake command to the eagle pro from home?
Like
Rowan.Prangley 0.00
...
· 
·  1 like
·  Share link
Nick Grundy:
Rowan Prangley:
t has been very straightforward to start the mount and the whole process can be scripted in Voyager or similar observatory software if needed.


so, is everything shut down at some point? 

do you use VPN, then send the Wake command to the eagle pro from home?

To wake my Eagle, I use a nifty free software (I think it's called "WakeOverLan" or "WakeMeLan"... Something like that) then use Windows Remote Desktop to access via my home network (a touch easier then full remote location) but you can use others systems like Chrome Remote desktop which works via the browser or, if you are a Starkeeper Voyager user, you can script the full automation including mount shutdown using Voyager's web access 

Shutting down the mount is easy with MW4 as this will send the commend to the mount. If you don't want to use MW4 to shutdown the mount, a simple method is the 10Micron virtual keypad 👍
Like
DarkStar 18.93
...
· 
·  1 like
·  Share link
Nick Grundy:
Rowan Prangley:
t has been very straightforward to start the mount and the whole process can be scripted in Voyager or similar observatory software if needed.


so, is everything shut down at some point? 

do you use VPN, then send the Wake command to the eagle pro from home?

Hello all,

First: wake-on-LAN over VPN does not work by default, since WOL is a network broadcast (at least the most common variant of it). Broadcasts are neither forwarded by any router, nor any VPN. If you want this, the service provider (or you) have to configure a multicast proxy. These is something where you need profound network knowledge and administrative access to all network infrastructure in between.

Second: the switches in between must either be configured for WOL to have static ARP table entries, or you have the risk, that after a reboot of the switch, it does not know anymore the MAC of the computer an will not deliver the WOL package. As consequence you cannot wake up the target. Or you have very dump, simple one which works sometimes without config. 

These are reasons why WOL never was seriously used in professional environment. To make it reliable a lot of effort and suitable hardware is required. To use WOL in remote destinations is an unacceptable risk. I can only second to John: keep it simple and fail safe. E.g. boot on power resume and get IP controlled power sockets. You should be capable to reset the complete environment to a well defined reset state without dependencies, where you can power up everything in a planned sequence. WOL should never ever be considered as a reliable - or even worse: depended - option. 

CS
Rüdiger

note: to overcome first handicap you can deploy a simple device e.g. a RasPi (they boot on power up)  in the target network and log into it via SSH over VPN. From there you can send a WOL packet to target. But again: an additional point of failure and does not handle second limitation. 😞
Edited ...
Like
Supro 4.37
...
· 
·  Share link
i'm definitely against additional points of failure. 

I am right to assume most to the remote facilities provide you some sort of VPN access mechanism? 

If that is the case, you would have some sort of switch or device you keep online all the time? (from which you wake other devices) no?

@Rowan Prangley it sounded like you are on the same network (observatory at home?)

@John Hayes  your remote setup has something you log in to first? the switch? or PC?
Like
DarkStar 18.93
...
· 
·  Share link
Hi Nick,

though not being asked directly a can bring some clarity to it.

Many use tools like Team Viewer. in simple words: These tools connect from client side to the service provider e.g. Team Viewers cloud and propagate their address and listen permanently on an incoming connection. When you try to access your pc, TV is also connecting to the cloud and the cloud forwards you to the requested client. This is very much simplified, but all these solutions work with a broker in between. 

But now you see the problem: This is not a fully transparent VPN connection. It is more or less a KVM (keyboard video mouse) solution with some add ons. 

From an admins view, these solutions cause head ache.

1. They punch holes in the firewall from inside. A professional admin would block that, but unfortunately they tunnel via https which is open and required.
2. You are dependent on the service provider. Sometimes you have to pay.
3. It is not a transparent connection. It is only KVM (keyboard, video, mouse). SSH of files transfer and other services will not work (I know some have a file feature by transfer over https. But this is very inefficient).

Real VPN connections need a VPN endpoint, VPN client software and a static public address on the observatory side. They require effort, knowledge and money. Therefore they are not offered afaik and the observatories run at very low security level and over only KVM via 3rd party tools.
Edited ...
Like
Rowan.Prangley 0.00
...
· 
·  2 likes
·  Share link
Nick Grundy:
i'm definitely against additional points of failure. 

I am right to assume most to the remote facilities provide you some sort of VPN access mechanism? 

If that is the case, you would have some sort of switch or device you keep online all the time? (from which you wake other devices) no?

@Rowan Prangley it sounded like you are on the same network (observatory at home?)

@John Hayes  your remote setup has something you log in to first? the switch? or PC?

Yes! Observatory at home and on same network. Sorry, I should have read the thread from the start to better provide input
Like
jhayes_tucson 26.84
...
· 
·  1 like
·  Share link
Nick Grundy:
@John Hayes  your remote setup has something you log in to first? the switch? or PC?

The Data Loggers IP power switch plugs into a UPS, which is plugged into the observatory line power so it’s on full time.  The PC is on a switched outlet and it boots when power is applied.   The UPS is there just to insure that a momentary power glitch won’t crash the whole system.  That’s more important for a place like DSW that runs on the power grid than it is at Obstech, which runs from batteries—sort of like a giant UPS.  If the observatory power goes down for any reason, the IP switch just comes back on line when the power is restored and I’m back in business.  The only log in required is for Windows when it boots.

John


PS  I should also mention that in Chile, the connection is made through a password protected VPN so log in is required for that.  I also have to log in to CRD to mirror my PC screen so there are ultimately multiple passwords needed to get into the system.
Edited ...
Like
Wjdrijfhout 6.78
...
· 
·  1 like
·  Share link
Nick Grundy:
I am right to assume most to the remote facilities provide you some sort of VPN access mechanism?

No VPN access in the remote site I’m using, for the reasons mentioned by Ruediger. If VPN is important to you, you may want to check out ZeroTier. This is a virtual VPN system and can easily be setup at a remote site on your own remote PC without interfering with the remote networking environment. It works great if you need IP-access to a software server on your remote PC. I use it for example for some of the remote tools that Voyager offers, which need to connect to the Voyager server on the remote PC. It can give you direct file access as well, for example using an FTP client. It only works on PC’s, phones, tablets etc., as you need to install some software. You will not be able to access your mount this way.

As for WOL, I have always stayed away from it for reasons mentioned above. Also, my understanding is that WOL for the 10Micron mount only works as long as it remains powered. In case of a power loss, you have to physically press the switch again. The best way to power on these mounts remotely is with a relay switch of sorts.

Besides the Screen/keyboard/mouse access of the remote PC (Team Viewer, Splashtop, etc), there are many other options to interact with your equipment on-site, and without a VPN. But they all work with some intermediary cloud-based service like Ruediger described. For my system for example such accesses are:
- Shelly Pro 4 PM (IP switch), via Shelly Cloud
- File exchange, via Box
- Camera access and switch monitoring, via the UniFi (UI) site manager
- UPS, via Schneider Electric cloud service  

Willem Jan.
Like
FraaRog 1.20
...
· 
·  Share link
Any tips on getting Tailscale installed on the WPS? I followed the faq on the WPS site, but it installs an ancient version, and all my attempts to update it fail in tedious ways. 

That is, Tailscale is installed on my WPS, but it's complaining that the version is very old and wants me to update with a newer Tailscale. Were you able to update your version, or are you living with the one it complains about?

Thanks!
Like
 
Register or login to create to post a reply.