Hello, We just released the new version of the HamWAN.org <http://www.HamWAN.org/> website. This represents a substantial effort which had us start by creating a new content management system with focus on ease of use and security, and then a translation process of all the old content to the new system format. Please let me know if you find any problems. I already know about the broken SVG issues on the LAN Integration page, and that Capitol Peak links aren't reporting their link status correctly on the map (it's due to this RouterOS "feature" <https://ciscodude.net/2015/01/19/mikrotik-snmp-oddity/>). We haven't addressed the need to re-arrange and edit much of the site information in this transition. This was mostly a technical migration due to hackers exploiting our old website's code. If that's not exciting enough, we've also deployed our first HamWAN Cam! You can access it with IE or Safari or Firefox by going here: http://ptz.baldi.hamwan.net/ The login and password are hamwan. The streaming isn't perfect yet, but it's good enough for folks to play with. You can choose between the "Main Stream" which is a 2Mbit 1080p 30fps feed, or the "Sub Stream" which is a 160kbit 480p 10fps feed. Click and hold the motion controls to move the cam. And oh yeah, we also upgraded the microwave links to Baldi. They're both MIMO now. --Bart
We’ve had some folks have problems reaching the new site. This is due to your computer caching the old site. Please try clearing your cache if you’re having a problem reaching hamwan.org. Additionally, I’d like to thank Bart and Tom for their *significant* time investment in getting the site rebuilt. It’s much appreciated. Thanks, Nigel
On Sep 5, 2016, at 16:07, Bart Kus <me@bartk.us> wrote:
Hello,
We just released the new version of the HamWAN.org <http://www.hamwan.org/> website. This represents a substantial effort which had us start by creating a new content management system with focus on ease of use and security, and then a translation process of all the old content to the new system format. Please let me know if you find any problems. I already know about the broken SVG issues on the LAN Integration page, and that Capitol Peak links aren't reporting their link status correctly on the map (it's due to this RouterOS "feature" <https://ciscodude.net/2015/01/19/mikrotik-snmp-oddity/>).
We haven't addressed the need to re-arrange and edit much of the site information in this transition. This was mostly a technical migration due to hackers exploiting our old website's code.
If that's not exciting enough, we've also deployed our first HamWAN Cam! You can access it with IE or Safari or Firefox by going here:
http://ptz.baldi.hamwan.net/ <http://ptz.baldi.hamwan.net/>
The login and password are hamwan. The streaming isn't perfect yet, but it's good enough for folks to play with. You can choose between the "Main Stream" which is a 2Mbit 1080p 30fps feed, or the "Sub Stream" which is a 160kbit 480p 10fps feed. Click and hold the motion controls to move the cam.
And oh yeah, we also upgraded the microwave links to Baldi. They're both MIMO now.
--Bart
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
The plugin doesn't seem to install :( On Mon, Sep 5, 2016 at 6:02 PM, Nigel Vander Houwen <nigel@nigelvh.com> wrote:
On Sep 5, 2016, at 16:07, Bart Kus <me@bartk.us> wrote:
If that's not exciting enough, we've also deployed our first HamWAN Cam! You can access it with IE or Safari or Firefox by going here:
-- ------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 <http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
For those with plugin problems, we are restreaming at http://stream.tukwila.hamwan.net:8081/baldi.ogg <http://stream.tukwila.hamwan.net:8081/baldi.ogg> ^ Works in Chrome, Firefox, and Opera Note that this is just a restream, you can’t control the camera through it. Nigel
On Sep 5, 2016, at 23:11, John D. Hays <john@hays.org> wrote:
The plugin doesn't seem to install :(
On Mon, Sep 5, 2016 at 6:02 PM, Nigel Vander Houwen <nigel@nigelvh.com <mailto:nigel@nigelvh.com>> wrote:
On Sep 5, 2016, at 16:07, Bart Kus <me@bartk.us <mailto:me@bartk.us>> wrote:
If that's not exciting enough, we've also deployed our first HamWAN Cam! You can access it with IE or Safari or Firefox by going here:
--
John D. HaysK7VE
PO Box 1223, Edmonds, WA 98020-1223 <http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
It's dark out :) On Mon, Sep 5, 2016 at 11:25 PM, Nigel Vander Houwen <nigel@nigelvh.com> wrote:
For those with plugin problems, we are restreaming at http://stream.tukwila.hamwan.net:8081/baldi.ogg
^ Works in Chrome, Firefox, and Opera Note that this is just a restream, you can’t control the camera through it.
Nigel
On Sep 5, 2016, at 23:11, John D. Hays <john@hays.org> wrote:
The plugin doesn't seem to install :(
On Mon, Sep 5, 2016 at 6:02 PM, Nigel Vander Houwen <nigel@nigelvh.com> wrote:
On Sep 5, 2016, at 16:07, Bart Kus <me@bartk.us> wrote:
If that's not exciting enough, we've also deployed our first HamWAN Cam! You can access it with IE or Safari or Firefox by going here:
--
------------------------------ John D. Hays K7VE
PO Box 1223, Edmonds, WA 98020-1223 <http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
-- ------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 <http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
On 9/6/16 2:59 AM, John D. Hays wrote:
It's dark out :)
Need an IR illuminator. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
Nice job. It would be nice -- someday -- if the "red" coverage shading was actually changed to be color coded for which site is illuminating a given area. When I see "red" somewhere, I don't know which site is supposedly covering it and where to aim the dish... Some areas are covered by more than one site in which case the colors would overlap, but that's definitely nice to know too...
On Tue, Sep 6, 2016 at 12:18 AM, Ed Morin <edmorin.jr@gmail.com> wrote:
Nice job.
It would be nice -- someday -- if the "red" coverage shading was actually changed to be color coded for which site is illuminating a given area. When I see "red" somewhere, I don't know which site is supposedly covering it and where to aim the dish...
Some areas are covered by more than one site in which case the colors would overlap, but that's definitely nice to know too...
Ed, This is on the roadmap, but as far as I know, I'm our only javascript developer and I've been busy with other projects this summer (new website, Baldi camera, Gold, and Capitol Peak deploys, among other things). If you are any good at javascript, you could take a stab at it. The source data can all be gleaned by reading the current map.js file and once you have the new map code working we can swap it in. I've found that knowing which site *should* be strongest at a particular location is not terribly relevant in the real world. For example, the computer models show that Baldi, ETiger, and Gold should all be reachable from my house. When I do a sweep with the dish, I see beacon packets from ETiger and Gold. Nothing from Baldi. Oh well, what matters here is reality, not what the model shows. Tom
Tom, Are the models combined into a single image overlay? If not, an easy way to implement this might be turning individual cells or sectors on and off. Something like "Show only the coverage for this cell" would allow someone to see which one is covering their area through experimentation. It would even allow us to use the more detailed heatmaps that would show where the weaker signals might go and not just show a single color for > -70. Of course, it might be quite a bit more difficult, but I think the ideal interface would allow someone to choose a specific point on the map and get a report of sectors that can reach that location from different angles and what the estimated signals would be from each one using various standard antennas at various heights. On Tue, Sep 6, 2016 at 9:11 AM, Tom Hayward <tom@tomh.us> wrote:
On Tue, Sep 6, 2016 at 12:18 AM, Ed Morin <edmorin.jr@gmail.com> wrote:
Nice job.
It would be nice -- someday -- if the "red" coverage shading was actually changed to be color coded for which site is illuminating a given area. When I see "red" somewhere, I don't know which site is supposedly covering it and where to aim the dish...
Some areas are covered by more than one site in which case the colors would overlap, but that's definitely nice to know too...
Ed,
This is on the roadmap, but as far as I know, I'm our only javascript developer and I've been busy with other projects this summer (new website, Baldi camera, Gold, and Capitol Peak deploys, among other things). If you are any good at javascript, you could take a stab at it. The source data can all be gleaned by reading the current map.js file and once you have the new map code working we can swap it in.
I've found that knowing which site *should* be strongest at a particular location is not terribly relevant in the real world. For example, the computer models show that Baldi, ETiger, and Gold should all be reachable from my house. When I do a sweep with the dish, I see beacon packets from ETiger and Gold. Nothing from Baldi. Oh well, what matters here is reality, not what the model shows.
Tom _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
Most of the models are per-cell. I'd like to be able to turn them on and off, but the javascript to do this has not been written. I'd also like to be able to generate spot models for a given point, like you suggest, but this will require automating Radio Mobile or Splat!. I haven't had time to work on this myself. Tom On Tue, Sep 6, 2016 at 9:27 AM, Cory (NQ1E) <cory@nq1e.hm> wrote:
Tom,
Are the models combined into a single image overlay? If not, an easy way to implement this might be turning individual cells or sectors on and off. Something like "Show only the coverage for this cell" would allow someone to see which one is covering their area through experimentation. It would even allow us to use the more detailed heatmaps that would show where the weaker signals might go and not just show a single color for > -70.
Of course, it might be quite a bit more difficult, but I think the ideal interface would allow someone to choose a specific point on the map and get a report of sectors that can reach that location from different angles and what the estimated signals would be from each one using various standard antennas at various heights.
On Tue, Sep 6, 2016 at 9:11 AM, Tom Hayward <tom@tomh.us> wrote:
On Tue, Sep 6, 2016 at 12:18 AM, Ed Morin <edmorin.jr@gmail.com> wrote:
Nice job.
It would be nice -- someday -- if the "red" coverage shading was actually changed to be color coded for which site is illuminating a given area. When I see "red" somewhere, I don't know which site is supposedly covering it and where to aim the dish...
Some areas are covered by more than one site in which case the colors would overlap, but that's definitely nice to know too...
Ed,
This is on the roadmap, but as far as I know, I'm our only javascript developer and I've been busy with other projects this summer (new website, Baldi camera, Gold, and Capitol Peak deploys, among other things). If you are any good at javascript, you could take a stab at it. The source data can all be gleaned by reading the current map.js file and once you have the new map code working we can swap it in.
I've found that knowing which site *should* be strongest at a particular location is not terribly relevant in the real world. For example, the computer models show that Baldi, ETiger, and Gold should all be reachable from my house. When I do a sweep with the dish, I see beacon packets from ETiger and Gold. Nothing from Baldi. Oh well, what matters here is reality, not what the model shows.
Tom _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
What are the parameters you have for Radio Mobile for each site's coverage map generation? (At least Haystack and Tiger.) I'd like to at least do a manual map for each... On Tue, Sep 6, 2016 at 9:32 AM, Tom Hayward <tom@tomh.us> wrote:
Most of the models are per-cell. I'd like to be able to turn them on and off, but the javascript to do this has not been written.
I'd also like to be able to generate spot models for a given point, like you suggest, but this will require automating Radio Mobile or Splat!. I haven't had time to work on this myself.
Tom
On Tue, Sep 6, 2016 at 9:27 AM, Cory (NQ1E) <cory@nq1e.hm> wrote:
Tom,
Are the models combined into a single image overlay? If not, an easy way to implement this might be turning individual cells or sectors on and off. Something like "Show only the coverage for this cell" would allow someone to see which one is covering their area through experimentation. It would even allow us to use the more detailed heatmaps that would show where the weaker signals might go and not just show a single color for > -70.
Of course, it might be quite a bit more difficult, but I think the ideal interface would allow someone to choose a specific point on the map and get a report of sectors that can reach that location from different angles and what the estimated signals would be from each one using various standard antennas at various heights.
On Tue, Sep 6, 2016 at 9:11 AM, Tom Hayward <tom@tomh.us> wrote:
On Tue, Sep 6, 2016 at 12:18 AM, Ed Morin <edmorin.jr@gmail.com> wrote:
Nice job.
It would be nice -- someday -- if the "red" coverage shading was actually changed to be color coded for which site is illuminating a given area. When I see "red" somewhere, I don't know which site is supposedly covering it and where to aim the dish...
Some areas are covered by more than one site in which case the colors would overlap, but that's definitely nice to know too...
Ed,
This is on the roadmap, but as far as I know, I'm our only javascript developer and I've been busy with other projects this summer (new website, Baldi camera, Gold, and Capitol Peak deploys, among other things). If you are any good at javascript, you could take a stab at it. The source data can all be gleaned by reading the current map.js file and once you have the new map code working we can swap it in.
I've found that knowing which site *should* be strongest at a particular location is not terribly relevant in the real world. For example, the computer models show that Baldi, ETiger, and Gold should all be reachable from my house. When I do a sweep with the dish, I see beacon packets from ETiger and Gold. Nothing from Baldi. Oh well, what matters here is reality, not what the model shows.
Tom _______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
On Tue, Sep 6, 2016 at 10:22 AM, Ed Morin <edmorin.jr@gmail.com> wrote:
What are the parameters you have for Radio Mobile for each site's coverage map generation? (At least Haystack and Tiger.) I'd like to at least do a manual map for each...
Here is my network file. I believe all the .ants are on the website. Tom
Holy mackerel it's Raining up there! On 9/5/2016 5:07 PM, Bart Kus wrote:
Hello,
We just released the new version of the HamWAN.org <http://www.HamWAN.org/> website. This represents a substantial effort which had us start by creating a new content management system with focus on ease of use and security, and then a translation process of all the old content to the new system format. Please let me know if you find any problems. I already know about the broken SVG issues on the LAN Integration page, and that Capitol Peak links aren't reporting their link status correctly on the map (it's due to this RouterOS "feature" <https://ciscodude.net/2015/01/19/mikrotik-snmp-oddity/>).
We haven't addressed the need to re-arrange and edit much of the site information in this transition. This was mostly a technical migration due to hackers exploiting our old website's code.
If that's not exciting enough, we've also deployed our first HamWAN Cam! You can access it with IE or Safari or Firefox by going here:
The login and password are hamwan. The streaming isn't perfect yet, but it's good enough for folks to play with. You can choose between the "Main Stream" which is a 2Mbit 1080p 30fps feed, or the "Sub Stream" which is a 160kbit 480p 10fps feed. Click and hold the motion controls to move the cam.
And oh yeah, we also upgraded the microwave links to Baldi. They're both MIMO now.
--Bart
_______________________________________________ PSDR mailing list PSDR@hamwan.org http://mail.hamwan.net/mailman/listinfo/psdr
-- 73 Lee W5LMM http://w5lmm.us QRZ: http://qrz.com/db/W5LMM Where am I? look no further than http://aprs.fi/#!mt=roadmap&z=11&call=a%2FW5LMM-1&timerange=3600&tail=3600 "The best number is 73. Why? 73 is the 21st prime number. Its mirror, 37, is the 12th and its mirror, 21, is the product of multiplying 7 and 3... and in binary 73 is a palindrome, 1001001, which backwards is 1001001." --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
participants (8)
-
Bart Kus -
Bryan Fields -
Cory (NQ1E) -
Ed Morin -
John D. Hays -
Lee Maisel -
Nigel Vander Houwen -
Tom Hayward