n5pwp
Member
I just started monitoring ALE on HF. The COTHEN frequencies seem to give the most activity (Haven't found a single Ham ALE transmission). I use both PC-ALE and MARS-ALE and monitor using an RTL-SDR. So I receive only. I've noticed several times a conversation like this:
[01/09/2017][05:22:59][FRQ 05732000][MONITOR: MONITOR CALL HEARD - DEFAULT - FORCED RESUME SCAN - Tell N2CKH/NNN0WWL]
[01/09/2017][05:56:40][FRQ 05732000][MONITOR: MONITOR IDLE - FRAME NOT FOR ME 10000]
[01/09/2017][05:56:40][FRQ 05732000][MONITOR: MONITOR CALL HEARD - FRAME NOT FOR ME 15000]
I have a few questions about this exchange.
1. Why do I only see this in the MARS-ALE receive window and not in the PC-ALE window? Does the program filter it out since it is not Amateur Radio transmissions? It allows the SND transmissions.
2. Did the receiver of the message actually get a message meant for someone else and it kicked it back out?
3. Is there a document that explains what typical exchanges would be? Or what these MONITOR: messages are?
4. Why does one end with 10000 and the other with 15000?
To answer those that reply with "Google is your friend". I have already done that. I have spent the last several days crawling all over ALE in Google. I have found several good resources for decoding the addresses.
Anyway, I'm hoping to see something more interesting than the SND frames and the "Frame not for me" messages.
Oh yeah, one more question. I'm using a virtual audio cable so I can run several pieces of software to decode other digital signals on the same frequencies. Is there a way when a voice call comes I can pass the audio through to listen to the voice or do I have to use the Stereo mixer in Windows and listen to all the ALE digital signals and wait for a voice signal to come through?
It occurs to me that maybe this is the way ALE works. They find a good frequency and then when they connect then they go to voice? I thought there would be some traffic passed as text. Is that not how ALE is supposed to work?
Enough questions for now. I look forward to chatting with others that have more experience with the mode.
Thanks.
Mike
[01/09/2017][05:22:59][FRQ 05732000][MONITOR: MONITOR CALL HEARD - DEFAULT - FORCED RESUME SCAN - Tell N2CKH/NNN0WWL]
[01/09/2017][05:56:40][FRQ 05732000][MONITOR: MONITOR IDLE - FRAME NOT FOR ME 10000]
[01/09/2017][05:56:40][FRQ 05732000][MONITOR: MONITOR CALL HEARD - FRAME NOT FOR ME 15000]
I have a few questions about this exchange.
1. Why do I only see this in the MARS-ALE receive window and not in the PC-ALE window? Does the program filter it out since it is not Amateur Radio transmissions? It allows the SND transmissions.
2. Did the receiver of the message actually get a message meant for someone else and it kicked it back out?
3. Is there a document that explains what typical exchanges would be? Or what these MONITOR: messages are?
4. Why does one end with 10000 and the other with 15000?
To answer those that reply with "Google is your friend". I have already done that. I have spent the last several days crawling all over ALE in Google. I have found several good resources for decoding the addresses.
Anyway, I'm hoping to see something more interesting than the SND frames and the "Frame not for me" messages.
Oh yeah, one more question. I'm using a virtual audio cable so I can run several pieces of software to decode other digital signals on the same frequencies. Is there a way when a voice call comes I can pass the audio through to listen to the voice or do I have to use the Stereo mixer in Windows and listen to all the ALE digital signals and wait for a voice signal to come through?
It occurs to me that maybe this is the way ALE works. They find a good frequency and then when they connect then they go to voice? I thought there would be some traffic passed as text. Is that not how ALE is supposed to work?
Enough questions for now. I look forward to chatting with others that have more experience with the mode.
Thanks.
Mike