We seek to understand and document all radio transmissions, legal and otherwise, as part of the radio listening hobby. We do not encourage any radio operations contrary to regulations. Always consult with the appropriate authorities if you have questions concerning what is permissable in your locale.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Token

Pages: 1 ... 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 ... 144
646
Somebody yelling at WDDR between cuts on the freq.  I think he might be saying high to ya WDDR.


(edit)  SSTV images.




T!

647
Conditions not great tonight, weak signal, sometimes usable but not often.



T!

648
Usable but not strong here in the Mojave Desert.  Will probably improve over time since we are still a good bit before sundown.

T!

649
HF Beacons / Windy 4102.74 kHz 1300 UTC May 20 2017
« on: May 20, 2017, 1323 UTC »
The newer format Windy beacon is booming this morning, 1300 UTC, May 20, 2017.  4102.74 kHz but with some sag, so I expect it will drift with either temp or battery voltage.

No wind in the High Desert this morning, no dits between the W's, it is sending:
W
W
W
W
W
TMP 74
B 127

Entire cycle takes about 1 min 31 seconds.

You can tell when the sun hit the sensor, temp shot up 6 degrees in under 5 minutes.

T!

650
Yes, YHWH has been on since at least 0315 UTC May 20.  It sounded like he was going to sign off at about the time you heard the msuic, but then he restarted one of the CDs.

T!

651
Some kind of odd digital image mode on the waterfall, 0330 UTC, 20 May, 2017.  Freq was about 6960 kHz.  Unfortunately I was not recording when it happened.



T!

652
General Radio Discussion / Re: Tragedy at Honda
« on: May 18, 2017, 1804 UTC »
I just finished a book about this astounding event: https://en.wikipedia.org/wiki/Honda_Point_disaster. The book is "Tragedy at Honda", published by Naval Institute Press.

It's about a destroyer fleet that ran aground during the 20s, whilst making a fast run along the California coast from San Francisco to San Diego. The book goes into detail about the disaster, as well as about the subsequent Navy trials of the officers in charge of the fleet. Basically, they were playing follow the leader, and the leader turned left into the coastal rocks due to navigational errors. The rest of the fleet just followed the leader into the rocks, causing nine of the ships to run aground. Seven sank, and the other two were badly damaged but managed to extricate themselves. It remains one of the worst naval disasters in US peacetime Naval history.

This event, and lessons learned from it, is one that was hammered into us when preparing to become qualified to con a ship.

The ships were in line astern or column formation, and following the flagship (the entire formation was 14 ships of Destroyer Squadron 11, the USS Delphy was the flagship).  This was a standard formation for some operations, including high speed transit of a relatively narrow channel.

The Commodore (Cpt Edward Watson) treated the transit as a training opportunity and directed the evolution to be conducted under simulated wartime conditions.  He also ordered all ships to stay in close formation, probably to maintain visual separation in the fog.

Yeah, a high speed transit through a designated channel, in the fog.  It sounds stupid, but believe it or not sometimes Navy vessels have to do such things, and you have to practice at some point.

Although the Commodore ordered the formation and the ships were following the flagship, so the flagship navigation was at fault, each skipper has a responsibility to the safety of his own ship.  So almost all of the ships commanders were court-martialed, although the Commodore accepted responsibility for the event.

The issues at the trials included whether a major earthquake in Japan a few days earlier altered currents on the California coast to such an extent that "dead reckoning", which was being used by many of the ships, was "fooled". I think that this is very unlikely, but at the time it gained some credence.

Dead reckoning was standard operating procedure at the time when there were no visual sightings or queues, such as at night or during fog.  Of course sight lines to known points were preferred, but if you can’t see them you can’t take such lines.

This was a transitional Navy, technology was just starting to provide navigation aids that could see in the dark, and most Captains and navigators had little confidence in them, particularly smaller ships like destroyers.  It is easy to look back at it in hind-sight and say this was stupid, but now we trust the tech.  This was 1923, and the first US Navy navigational radiobeacons went in in 1921.  However RDF had been on some US Navy ships since the USS Lebenon in 1906.  For most of the Captains of the ships involved they had been using other than radio techniques as primary sources the vast majority of their careers.  Remember, these were all destroyer drivers, and the habit of the day was that once an officer entered the destroyer fleet he stayed there.  Since RDF was in most common use on larger vessels (cruisers and battleships) the majority of the skippers probably had little confidence in such things.

Prior to 1917 only the largest ships had RDF systems, but in 1917, as a result of German U-boat activity, all destroyer and larger combatants could be so equipped (Model DA).  But it was not until the development of the Model DB system in 1922 that people really started to trust them for navigation.

As for the earthquake causing issues, it is undeniable that there was some influence from the earth quake on the local currents.  The steamship SS Cuba ran aground in the same area the same day, and potentially suffered the same issue.  I have seen the impact of a remote large earthquake on local currents myself, while navigating coastal waters.  Small, but there, and back in the day if they had been running DR for a couple of days that small error may have become large.  Not sure I really buy it myself, but it is not without some validity.

T!

653
Yeah, the Bearcat name goes back to at least the mid / early 70's, and probably a bit before.  I think it was originally used by Electra Scanner Company for their police scanners, and then the line was sold to Uniden at some point, maybe the mid 1980's?

I know I have a crystal controlled Electra scanner that has the Bearcat name and paw print from maybe 1973 or so.  I used to have a Bearcat 4 channel scanner that was an 8 track plug in.  A scanner built into a body that could be plugged into an 8 track player, then the audio played through the 8 track player speakers.

T!

654
If I am not mistaken I think the “Beartracker” feature, and scanners bearing that name, goes back to at least the mid 1980’s, and maybe before that.  The feature has a couple of dedicated priority channels (it hits them every couple seconds, regardless of what else it is doing) that are specific to police vehicles being close by.  For example in the past you could scan 154.905 MHz and if you got a hit there you knew a CHP was within a couple of miles, this being the frequency of the mobile extender that allowed the Hi- VHF hand held on the officers hip to be cross banded to the Lo-VHF CHP dispatch frequency.

As for the cost of $450, that really is not too bad.  The scanner is full featured, digital modes, trunking, GPS enabled (to automatically select frequencies in your are), etc.  If you were to grab any scanner with these features it would be in the $400 area anyway.  So the addition of a CB, and the convenience of a single unit to do both jobs, for $50 or a little more does not seem excessive.

T!

655
I moved this thread from the "Spy Numbers" to "Utility" forum.  In general coded military messages, such as those on the HF-GCS network, are not considered "numbers" stations.

T!

657
2nd and 4th Thursday of the month (in March and April) on 5934 kHz at 1830z.  Now that it is May (and until August) the frequency on these days and in this time slot will be 6887 kHz.  2nd and 4th Fridays at 1930z will be on 5943 kHz from now until August.

T!

658
Didn't he also use this freq 4 or 6 months ago?  I am sure I have a recording around someplace.

T!

659
HF Beacons / Re: 7.509.3MHz Astrakhan...
« on: May 02, 2017, 2024 UTC »
"L" St Petersburg on 8.495.2MHz CW quite strong 529 report.

8495.2 kHz should have been F, not L.

T!



It is interesting that F and L are just 1 KHz apart

F is on 8494.200 KHz at Vladisvostok

L is on 8495.200 KHz at Saint Petersburg






Yep, my bad.  I saw 8495.2 and read it to myself as 8494.2.

T!

660
Utility / Re: CAP Net 7615 USB 0105 UTC 29 Apr 2017
« on: May 02, 2017, 1757 UTC »
Ouch, YHWH has been using that freq for his pirate transmissions regularly.

I thought the same thing, although I have yet to copy a CAP net during the hours YHWH prefers, so he may be getting lucky. Wasn't he in the ham bands before his bust?

Both ham bands and aviation bands.  Not sure what one got him on the FCC's radar, although locally here the important ones that noticed (the ones that might maake the most noise) saw the aviation freqs incursion. 

T!

Pages: 1 ... 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 ... 144

Item image   Radiation Detection and Measurement by Knoll, Glenn F

 $49.95