Jump to content

SkySurveyBanner.jpg.21855908fce40597655603b6c9af720d.jpg

TimBrandt

New Members
  • Posts

    15
  • Joined

  • Last visited

Reputation

1 Neutral

Profile Information

  • Gender
    Male
  • Interests
    Astrophotography, landscape photography, aviation photography, history, spacefight....
  • Location
    Somerset

Recent Profile Visitors

427 profile views
  1. Thanks all for your advice. Rebuilt using Wago capsule box and lots of Plastidip. So far so good. As always, second time round is much easier. Tim
  2. Thanks too, len. I think if I mount the BME280 with some internal shielding I can keep effective airflow but divert any splashes from rain. I'll try goretex if I'm still having problems. I used a Wago Capsule Box for the allsky - I may look at the same again but with some through vents for the BME280. Thanks again, Tim
  3. Hi Will, thank you for a very comprehensive and useful answer. I'll do as you suggest. I can print up a small inter cover for the light/temp sensors with vent holes. I used a resistor chain to heat an allsky enclosure but had not thought of one for the SQM. All the best Tim
  4. Hi, all, I'm after some advice,please. I recently built a version of Rob Brown's DIY SQM. I mounted the main electronics box in my observatory, with the main sensors in a modified weather station cover outside, on the end of a 1m cable. The sensors I used were a BME280 pressure and temp sensor, an MLX90614 to measure sky temperature and a TSL2591 to measure lux. The cover is a TFA Dostman weather station cover which stops direct rain and sun, but allows airflow to the sensors. The TSL2991 is protected under a plastic lens, and the IR thermometer can is sealed and itself waterproof, but the rest of the board is not. The sensors are connected by STEMM QT connectors. After 3 weeks, I have extensive water damage to the sensor boards, with corroded components. The problem is humidity, and the boards are wet at least some of the time. I had expected some problems from this, as I live in the UK, but the damage has been greater/faster than I anticipated. My question is what I can do to fix this in a rebuild? I can replace the QT connectors with soldered connections, but what can I do to protect the boards? Potting seems an obvious solution, but what would be suitable? Also, how can I protect the BME280 and the TSL2591, given that these need the active sensors to be exposed? I realise the question is pretty basic, but my previous experience of electronics was in aviation, where the cost is several orders of magniture greater, but buys better spec'ed items. Any advice gratefully received. Tim
  5. Hi Lars, I know this was posted some time ago but very interesting. but thanks for sharing. It has been a big help in reassuring me on some vignetting I'm experiencing with a Williams Optics GT81 and a ZWO ASI2600 APS-C camera. Kind regards Tim
  6. I've tried PHP, nodejs and python, but for what I want to do nodejs works nicely with sockets.io to link to the client. My other webservers use nodejs, so I can reuse most of the code - much of which has been derived from stuff posted online by those who know much more. I'm also trying to keep my options open to add INDI support and also to bring together my "distributed" observatory control system into a single cabinet at some point. At present I've several control boxes containing RPis and arduinos spread around the place as I've tackled different aspects of remote control. Regards Tim
  7. Hi James, I've been trying to set up a webserver on my NAS to try your idea, but can't get all the javascript plugins to work and I don't want to use PHP. I've ordered another Raspberry Pi, as I know how to make them work and will try again. I think you may be correct as the problems with access control seem to be browser related and should be bypassed by the server. I'll let you know how I fare! Regards Tim
  8. James, thanks. I tried a local copy of jQuery as you suggested , but the same result. I think the CORS error is because I'm trying to do a GET from a different server (the switch), which does not explicitly allow the access . I have tried both straight javascript and jQuery, and get the same error. On the other points, this is very much a test fragment;. if I can get it to work then I'll create the webserver itself - I'm already using others to control the 12V supply relays to the mount and the roof. I've also spent a lot of time on the browser console debugging the other servers... Any other ideas gratefully received! Thanks Tim
  9. Hi James, thanks for replying. The switch has an HTTP command format "http://login:password@ipaddress/set.cmd?cmd=setpower+switchnumber=1" ( for on or 0 for off) . The read command is of tthe format "http://login:password@ipaddrss:port/set.cmd?cmd=getpower". Both should return a string. If used in a straight browser window, the get power command generates a string like "p61=1,p62=0 etc". I'd tried several approaches, mostly with Javascript and jQuery. Simply sending a window.open command with the url turns the switch on and of ok, but opens a new window with the response code rather than returning it (no surprise). Using an "HTTP get" command gives me a CORS access error and a 401 error. If I suppress CORS protection in the browser (which is not long-term viable on my system) I still get a 401 error. I am out past the boundary of my IT knowledge and after several days of trying would be really grateful for a steer. The code which gave me the latest CORS and 401 errors was: <html> <head> <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js"></script> <script> $(document).ready(function(){ $("button").click(function(){ $.get("http://[user]:[password]@192.168.178.76/set.cmd?cmd=getpower", function(data, status){ alert("Data: " + data + "\nStatus: " + status); }); }); }); </script> </head> <body> <button>Button</button> </body> </html> Thanks, Tim
  10. Hi all, I'm hoping someone can help. I'm just finishing a DIY obsy, and trying to wrap up the various control packages. For mains power control I'm using an IP 9258 remote switch from IP Power. It works, but the supplied web management software is very poor and I cannot integrate it with the rest of the obsy's control software which is largely based on 3 LAN webservers (Raspberry Pis). I have produced a simple LAN server-hosted web page to switch it on and off - but cannot read the resulting on/Off state of the switches (I think largely for reasons linked to cross-server security which are way ahead of my IT skills). I can't get at the firmware for the box. I don't like controlling switches "blind", and unless I can find a software solution I may have to build a new Arduino controlled switch. Has anyone produced a web-based front end for the IP 9258 switch that reads the switch state that I could please copy or at least learn how from? Thanks in advance Tim Brandt
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.