Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

stargazine_ep24_banner.thumb.jpg.56e65b9c9549c15ed3f06e146fc5f5f1.jpg

HN50

Members
  • Content Count

    138
  • Joined

  • Last visited

Community Reputation

67 Excellent

2 Followers

About HN50

  • Rank
    Star Forming

Profile Information

  • Gender
    Not Telling
  • Location
    Surrey
  1. I went back and re-read how your set up works, that combination of mechanical and electronic is fascinating, I could not have come up with that myself. Is it all working as expected now? Did you leave it on 24 hour per .jpg? It has been a bit of a heavy work week so unfortunately I have not done a whole lot myself. Yesterday I sat down and amended the Arduino code to measure the minimum signal strength at the same time as I am currently measuring the average. The idea is that the transmitter should be detectable anyway however sudden jumps in signal strength due to noise from lightning strikes will effectively be ignored. So far it looks quite similar to the average but I will be interested to see the difference when there is a flare as that 'C' class flare on the 29th May caused the signal strength on my setup to drop. So I would expect the min signal to respond to a sudden drop more than the average. It occurs to me though that it won't respond to a sudden increase in signal strength and so you would only see that in the next minute. Swings and roundabouts. I will just leave it accumulating data to see what happens. Otherwise that is it, bit of a nothing post today I am afraid! I did get time yesterday to order the first set of components for the Muon detector so am hoping they should arrive this coming week. I will start a new thread in this section. Thanks for reading, Dave I also changed my report so that I get a plot of the last 4 weeks. I can't figure out why but PowerBI is determined that 12:08 on 13/09/2020 is two weeks ago and not one. SQL query is correct but I can't work out why it is plotting wrong. A week tomorrow it falls off the end of my report anyway so I might just chalk it up to 'just one of those things'... There has been a bit of an uptick in activity throughout the day as recorded by the GOES data. Will keep an eye on that.
  2. Miles Dyson didn't quite appreciate what he had built in that film so be careful if you try and switch it off..! * That is weird, I wonder why that happened? The light on the MKR flashes every time I take a measurement when running under USB power, but when under external power flashes once as expected and then stays on permanently. I have added the command to turn it off but it does exactly 3/8 of nothing... With work over the last week or so I have not done that much, but I got round to checking the data today. Helpfully the transmitter is back up and running after that interruption last week. The signal strength has gone up again after the maintenance period on the 10th so I wonder if they are transmitting at a greater power. More helpfully though I have been able to see the effect that my change in sampling has had (i.e. 1000 reads over 30 seconds rather than 1). It isn't scientific but I took two of the same day of the week n either side of my change to compare. Dark blue is with the longer sample window. It certainly looks smoother so I think is working though time will tell if it smooths out real fluctuations and unhelpfully the GOES data shows the sun has not been up to much. UKRAA suggested I could take the minimum value over the sample period as well so I might change the code to record that as well. So as ever I will leave it and watch. Otherwise I need to get ordering the Muon detector components. Thanks for reading, Dave * there will be no more film references. I only know the Terminator films and I don't see how Jurassic Park is relevant.
  3. Hi, Thank you for posting that is really useful to know, your plot looks similar to mine. So I think my radio is working properly but the transmitter isn't. I have turned logging on again so will see how this pans out. Thanks, David
  4. The code change has worked, analysis with Mk 1 eyeball seems to suggest a smoother output, time will tell if that also smooths out real events. Although I am not entirely keen on the plot today; I hope that a) the transmitter has been offline for an extended period rather than b) something is wrong with my radio...
  5. The transmitter seems to be down today so there is not much to see. As a result I have been making some code changes instead. I have simplified it by removing the alarm and pin interrupt. When I have finished taking measurements/sending to the MQTT broker I check the time and the number of seconds past the minute, subtract from 60 and send the Arduino to sleep for that amount of time. Not sure why I have not thought about this before, I think the low power library used with the MKR 1010 is a bit more flexible and the sleep time is variable. I have also changed how I am sampling data. Previously I was taking an average of 1000 measurements, each with 1ms between them (i.e. all done in 1 second). I mailed UKRAA and they suggested I might take measurements over a longer time to reduce lightning interference. So now I am taking 1000 with an interval of 30ms (i.e. over 30 seconds). I will be interested to see how this affects my results so as ever I will leave it running and see what happens. A bit early to tell and it would be good to see the affect on a 'normal' day. Thanks for reading, Dave
  6. Hi, That is where I went, I looked around in the UK but went for the one I found on Ebay. Seller was really helpful, I bought a block and the optical grease and with p&p it came to about £40. I did however get stung £14 for import duty. Dave
  7. Activity so far today seems more stable. Dave
  8. Hi, The last week has been pretty quiet, yesterday there seemed to be quite a bit of activity with the transmitter going on and off, and a few days before that the signal strength seemed to jump somewhat but is back down again. There was about half an hour on the 27th from about 18:30 when I stopped receiving data at IoT hub but I will just keep an eye on that, 35 minutes over about three weeks isn't too bad. I have been tinkering a bit with Azure behind the scenes but otherwise not so much on the radio. I might change the sampling when I make a measurement as I take 1000 over the course of a second so I might spread it out a bit more over maybe 20 seconds to try and reduce the noise. I have set up my own Github account for storing source code as my laptop seems to be becoming a little temperamental and so far I have been e-mailing code to myself. The pcb for the Muon detector arrived in a week; I was expecting it in 3 so I need to start sourcing parts. Dave
  9. I am not saying that it is all perfectly matching but having loaded the last 24 hours of GOES data more than a few of the downward ticks in my VLF data correlate with a spike in X-ray flux...
  10. Thanks for posting your data. I am not quite sure what that hump is I was getting between about 16:00 and 19:00 is but I am not sure it was a flare - the sharp end of day peak does match what you got. Today seems more settled too (there seemed a lot of transmitter downtime yesterday); Over the last couple of hours I have noticed a few downward ticks in the line though that happen around jumps in the GOES data. Though they do also tally with apparent temperature jumps in the project box that the Arduino is enclosed in...
  11. Cool, am interested to see what was detected by your system.
  12. Just had a quick look at the dashboard while passing (I am not obsessed) and the end of day peak appears to appearing several hours ahead of normal. I pulled in the last few hours of NOAA data and there is something happening at the moment - the start of the peak was ahead of the event but there is something happening, even if it is small. The start of the peak does coincide with a jump in temperature up in my roof (first screenshot) thinking back the weather changed abruptly and went from being cold to full sunshine. I don’t know if that would explain the earlier part of the peak (it is only about 3 degrees change). Anyway, will keep watching.
  13. Hi, Looking good, is the new timing unit working as you hoped? I have noticed a few sudden drops in signal strength myself so had wondered if the transmitter had stopped transmitting momentarily. And that peak is interesting, very regular, very abrupt and yet not obvious what it is..? There was a C class flare yesterday but I did not register it, I don't know if that is because the radio is not sensitive enough or if it was pointing away from Earth. But it is good to know that some solar activity is happening. I used the NOAA data I had imported to tweak my dashboard. Not done too much myself, on a tangent I have been exploring KiCAD with a view to trying to make either another VLF radio (basically a copy of one I have made before on stripboard) or a bat detector. I have also downloaded the Muon detector and am looking to get the pcb made for me. Thanks for reading, Dave
  14. The scintillator and optical grease arrived the other day, will start looking at the PCB in KiCAD so hopefully will make a start soon. Not quite sure which subject it would go under though? My progress... I am on holiday at the moment and I spent yesterday making some back-end changes. Rather than logging the date and time as one column, I have reduced them to two numbers - for date an integer in the format YYYYMMDD *, and for time the number of minutes past midnight. I did this as I would like to bring in additional data (the proposed Muon detector, GOES x-ray data from NOAA, maybe another VLF radio...) and I want to have common date and time calendar tables in the database to join to them all to. That should make them easier to plot together. I also removed the in-Arduino moving average as it was not calculating and in any case that could be calculated in the database. Date table looks like (I have it going to 2040); Time table looks like; If I need them together I can then create a view over both that joins on DateKey and TimeKey. I have also been practicing Power BI more and have been able to replicate the charts I have been running in LibreOffice. I found the breadth of choices available within charts slightly narrower in Power BI but the big difference is now how much faster I can display data without having to shuffle columns around in LibreOffice. I have loaded into the database some GOES X-ray flux data to see how easy it is to display it alongside my data. The feed isn't automatic so I will have to think about how I do this as it too gets updated every minute. I also discovered Power BI exports dashboards to a nice pdf as well. So not a bad bit of work today. Thanks for reading. Dave * On reflection it could have just been YYMMDD. I am not convinced I will be working on this project in 2120 when the datekeys start being reused.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.