Menu
▾
▴
wsjt-devel
|
From: Marco C. <PY...@ou...> - 2025-05-11 16:19:52
Attachments:
OpenPGP_signature.asc
OpenPGP_0x38215F3BB231677C.asc
|
Hello, I started to use MSK144 and among other things, I'm not understanding if I'm doing something wrong that prevents my CW-ID to be sent every time-frame I selected. Are there some details that I'm missing? How could I verify the CW-ID transmission? These are my current settings: I've tried 1, and 7 as well but I never noticed CW-ID being sent. Thanks! --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Andrew N. <ka...@ya...> - 2025-05-12 12:06:59
|
Marco is referring I think only to the use of the cw ID while using the short message format on 2 meter msk144. On that band/mode operators do not exchange signal reports and turn to the short message format (known as Sh) to complete a meteor scatter qso with quickly decaying meteor trails. Time is of the essence. However, a monitoring station often can not decode the callsigns of stations using the Sh format. With this in mind, two meter meteor scatter operators, when involved in a particularly long qso, will use the cw-id to identify their station to comply with regulations. Meteor scatter contacts on 2 meters can take a long time, I've seen them last a hour or more. Sometimes the use of the SWL format, (ticking the SWL box in MSK144) will reveal the callsign of the station using the Sh format, but sometimes it does not. Hence he use of the cw-ID. 73,Andy, ka2uqw |
|
From: Marco C. <PY...@ou...> - 2025-05-12 21:24:58
Attachments:
OpenPGP_signature.asc
OpenPGP_0x38215F3BB231677C.asc
|
Hi Andy! In reality I was asking in general the correct usage of CW-ID, which at least here it seems is not working. Then I would like to get the confirmation about it. Best regards, Marco, PY1ZRJ Il 12/05/25 09:05, Andrew Neumeier via wsjt-devel ha scritto: > Marco is referring I think only to the use of the cw ID while using > the short message format on 2 meter msk144. On that band/mode > operators do not exchange signal reports and turn to the short message > format (known as Sh) to complete a meteor scatter qso with quickly > decaying meteor trails. Time is of the essence. However, a > monitoring station often can not decode the callsigns of stations > using the Sh format. With this in mind, two meter meteor scatter > operators, when involved in a particularly long qso, will use the > cw-id to identify their station to comply with regulations. Meteor > scatter contacts on 2 meters can take a long time, I've seen them last > a hour or more. > > Sometimes the use of the SWL format, (ticking the SWL box in MSK144) > will reveal the callsign of the station using the Sh format, but > sometimes it does not. Hence he use of the cw-ID. > > 73, > Andy, ka2uqw > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Reino T. <rei...@ko...> - 2025-05-13 19:05:04
|
Hi Marco, I set up v2.7.0 GA (latest version) and selected in General the CW ID interwall to ‘1’. I listened to the audio and there is my CW id once a minute! When I set T/R to 5 s, then the CW ID replaces the first MSK144 transmission. When the T/R period is longer, then the last 5 s of the transmission is replaced. If I also select CW ID after 73, then the last 5 s of the ‘73’ message is stolen for the CW ID. The once a minute CW ID transmission may not be the first time of the minute. At least with 10 s T/R sends it at 45 seconds mark. At T/R 5 s the whole ‘73’ message is stolen and no ’73’ is sent (may be a bug). The CW ID seems to work. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...> Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li... Cc: Marco Calistri <PY...@ou...> Subject: Re: [wsjt-devel] CW-ID is not being sent Hi Andy! In reality I was asking in general the correct usage of CW-ID, which at least here it seems is not working. Then I would like to get the confirmation about it. Best regards, Marco, PY1ZRJ |
|
From: Marco C. <PY...@ou...> - 2025-05-13 19:23:26
|
Hello Reino! Thanks for the time you spent for the tests! The main issues, IMHO are: what are the correct parameters both for the CW id time interval and the MSK T/R seconds? Since it's not much worth that CW-ID being working only with few parameters combination that we can't use for normal MSK144 mode. For example here in Brazil the T/R is normally set to 30 s. Best regards, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Reino Talarmo <rei...@ko...> Sent: Tuesday, May 13, 2025 4:04:51 PM To: PY...@ou... <PY...@ou...>; 'WSJT software development' <wsj...@li...> Subject: RE: [wsjt-devel] CW-ID is not being sent Hi Marco, I set up v2.7.0 GA (latest version) and selected in General the CW ID interwall to ‘1’. I listened to the audio and there is my CW id once a minute! When I set T/R to 5 s, then the CW ID replaces the first MSK144 transmission. When the T/R period is longer, then the last 5 s of the transmission is replaced. If I also select CW ID after 73, then the last 5 s of the ‘73’ message is stolen for the CW ID. The once a minute CW ID transmission may not be the first time of the minute. At least with 10 s T/R sends it at 45 seconds mark. At T/R 5 s the whole ‘73’ message is stolen and no ’73’ is sent (may be a bug). The CW ID seems to work. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...> Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li... Cc: Marco Calistri <PY...@ou...> Subject: Re: [wsjt-devel] CW-ID is not being sent Hi Andy! In reality I was asking in general the correct usage of CW-ID, which at least here it seems is not working. Then I would like to get the confirmation about it. Best regards, Marco, PY1ZRJ |
|
From: Reino T. <rei...@ko...> - 2025-05-14 05:41:56
|
Hello Maco! Of course there are no global "correct" parameter values. User Guide sets the T/R to 15 s, but any value would work except the same T/R value and the same Tx even/1st value and then both stations would send and receive at the same timeslots! The CW ID is really a matter of local regulations. E.g. in Finland we don't need to send it at all as the monitoring station could decode MSK144 at a short range better than any CW, typically no human listening needed. The same with FT8. In many regions 10 minutes is set in the regulations and so the CW ID should be set to 10 and possibly activate the 'CW ID after 73' as it could be the last transmission. The CW ID is intended for a strong signal identification and your QSO partner normally would not hear it, just short pings. For the regulation purposes the CW ID is working as it should. For QSO point of view it may steal your '73' if you send it only once and you are using T/R 5s. 73, Reino OH3mA From: Marco Calistri <PY...@ou... <mailto:PY...@ou...> > Sent: Tuesday, May 13, 2025 10:23 PM To: Reino Talarmo <rei...@ko... <mailto:rei...@ko...> >; 'WSJT software development' <wsj...@li... <mailto:wsj...@li...> > Subject: Re: [wsjt-devel] CW-ID is not being sent Hello Reino! Thanks for the time you spent for the tests! The main issues, IMHO are: what are the correct parameters both for the CW id time interval and the MSK T/R seconds? Since it's not much worth that CW-ID being working only with few parameters combination that we can't use for normal MSK144 mode. For example here in Brazil the T/R is normally set to 30 s. Best regards, Marco PY1ZRJ Inviato da Outlook per Android <https://aka.ms/AAb9ysg> _____ From: Reino Talarmo <rei...@ko... <mailto:rei...@ko...> > Sent: Tuesday, May 13, 2025 4:04:51 PM To: PY...@ou... <mailto:PY...@ou...> <PY...@ou... <mailto:PY...@ou...> >; 'WSJT software development' <wsj...@li... <mailto:wsj...@li...> > Subject: RE: [wsjt-devel] CW-ID is not being sent Hi Marco, I set up v2.7.0 GA (latest version) and selected in General the CW ID interwall to '1'. I listened to the audio and there is my CW id once a minute! When I set T/R to 5 s, then the CW ID replaces the first MSK144 transmission. When the T/R period is longer, then the last 5 s of the transmission is replaced. If I also select CW ID after 73, then the last 5 s of the '73' message is stolen for the CW ID. The once a minute CW ID transmission may not be the first time of the minute. At least with 10 s T/R sends it at 45 seconds mark. At T/R 5 s the whole '73' message is stolen and no '73' is sent (may be a bug). The CW ID seems to work. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li... <mailto:wsj...@li...> Cc: Marco Calistri <PY...@ou... <mailto:PY...@ou...> > Subject: Re: [wsjt-devel] CW-ID is not being sent Hi Andy! In reality I was asking in general the correct usage of CW-ID, which at least here it seems is not working. Then I would like to get the confirmation about it. Best regards, Marco, PY1ZRJ |
|
From: Marco C. <PY...@ou...> - 2025-05-14 15:04:17
|
That's all right Reino! The inconvenience is that here I wasn't able to notice my CW-ID emission, despite of the several settings I have tried. Best regards! Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Reino Talarmo via wsjt-devel <wsj...@li...> Sent: Wednesday, May 14, 2025 2:41:43 AM To: 'WSJT software development' <wsj...@li...> Cc: Reino Talarmo <rei...@ko...> Subject: [wsjt-devel] FW: CW-ID is not being sent Hello Maco! Of course there are no global “correct” parameter values. User Guide sets the T/R to 15 s, but any value would work except the same T/R value and the same Tx even/1st value and then both stations would send and receive at the same timeslots! The CW ID is really a matter of local regulations. E.g. in Finland we don’t need to send it at all as the monitoring station could decode MSK144 at a short range better than any CW, typically no human listening needed. The same with FT8. In many regions 10 minutes is set in the regulations and so the CW ID should be set to 10 and possibly activate the ‘CW ID after 73’ as it could be the last transmission. The CW ID is intended for a strong signal identification and your QSO partner normally would not hear it, just short pings. For the regulation purposes the CW ID is working as it should. For QSO point of view it may steal your ‘73’ if you send it only once and you are using T/R 5s. 73, Reino OH3mA From: Marco Calistri <PY...@ou...<mailto:PY...@ou...>> Sent: Tuesday, May 13, 2025 10:23 PM To: Reino Talarmo <rei...@ko...<mailto:rei...@ko...>>; 'WSJT software development' <wsj...@li...<mailto:wsj...@li...>> Subject: Re: [wsjt-devel] CW-ID is not being sent Hello Reino! Thanks for the time you spent for the tests! The main issues, IMHO are: what are the correct parameters both for the CW id time interval and the MSK T/R seconds? Since it's not much worth that CW-ID being working only with few parameters combination that we can't use for normal MSK144 mode. For example here in Brazil the T/R is normally set to 30 s. Best regards, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Reino Talarmo <rei...@ko...<mailto:rei...@ko...>> Sent: Tuesday, May 13, 2025 4:04:51 PM To: PY...@ou...<mailto:PY...@ou...> <PY...@ou...<mailto:PY...@ou...>>; 'WSJT software development' <wsj...@li...<mailto:wsj...@li...>> Subject: RE: [wsjt-devel] CW-ID is not being sent Hi Marco, I set up v2.7.0 GA (latest version) and selected in General the CW ID interwall to ‘1’. I listened to the audio and there is my CW id once a minute! When I set T/R to 5 s, then the CW ID replaces the first MSK144 transmission. When the T/R period is longer, then the last 5 s of the transmission is replaced. If I also select CW ID after 73, then the last 5 s of the ‘73’ message is stolen for the CW ID. The once a minute CW ID transmission may not be the first time of the minute. At least with 10 s T/R sends it at 45 seconds mark. At T/R 5 s the whole ‘73’ message is stolen and no ’73’ is sent (may be a bug). The CW ID seems to work. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li...<mailto:wsj...@li...> Cc: Marco Calistri <PY...@ou...<mailto:PY...@ou...>> Subject: Re: [wsjt-devel] CW-ID is not being sent Hi Andy! In reality I was asking in general the correct usage of CW-ID, which at least here it seems is not working. Then I would like to get the confirmation about it. Best regards, Marco, PY1ZRJ |
|
From: Marco C. <PY...@ou...> - 2025-05-27 10:14:18
|
Hi Reino, list! I need to correct my previous message, since I have been able to hear my CW-ID when using MSK144 mode. Then this feature is still working on latest WSJTX version! So far so good 😊 73 de Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ Da: Marco Calistri via wsjt-devel <wsj...@li...> Inviato: Mercoledì, Maggio 14, 2025 12:09:27 PM A: WSJT software development <wsj...@li...> Cc: Marco Calistri <PY...@ou...> Oggetto: Re: [wsjt-devel] FW: CW-ID is not being sent That's all right Reino! The inconvenience is that here I wasn't able to notice my CW-ID emission, despite of the several settings I have tried. Best regards! Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Reino Talarmo via wsjt-devel <wsj...@li...> Sent: Wednesday, May 14, 2025 2:41:43 AM To: 'WSJT software development' <wsj...@li...> Cc: Reino Talarmo <rei...@ko...> Subject: [wsjt-devel] FW: CW-ID is not being sent Hello Maco! Of course there are no global “correct” parameter values. User Guide sets the T/R to 15 s, but any value would work except the same T/R value and the same Tx even/1st value and then both stations would send and receive at the same timeslots! The CW ID is really a matter of local regulations. E.g. in Finland we don’t need to send it at all as the monitoring station could decode MSK144 at a short range better than any CW, typically no human listening needed. The same with FT8. In many regions 10 minutes is set in the regulations and so the CW ID should be set to 10 and possibly activate the ‘CW ID after 73’ as it could be the last transmission. The CW ID is intended for a strong signal identification and your QSO partner normally would not hear it, just short pings. For the regulation purposes the CW ID is working as it should. For QSO point of view it may steal your ‘73’ if you send it only once and you are using T/R 5s. 73, Reino OH3mA From: Marco Calistri <PY...@ou...<mailto:PY...@ou...>> Sent: Tuesday, May 13, 2025 10:23 PM To: Reino Talarmo <rei...@ko...<mailto:rei...@ko...>>; 'WSJT software development' <wsj...@li...<mailto:wsj...@li...>> Subject: Re: [wsjt-devel] CW-ID is not being sent Hello Reino! Thanks for the time you spent for the tests! The main issues, IMHO are: what are the correct parameters both for the CW id time interval and the MSK T/R seconds? Since it's not much worth that CW-ID being working only with few parameters combination that we can't use for normal MSK144 mode. For example here in Brazil the T/R is normally set to 30 s. Best regards, Marco PY1ZRJ Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Reino Talarmo <rei...@ko...<mailto:rei...@ko...>> Sent: Tuesday, May 13, 2025 4:04:51 PM To: PY...@ou...<mailto:PY...@ou...> <PY...@ou...<mailto:PY...@ou...>>; 'WSJT software development' <wsj...@li...<mailto:wsj...@li...>> Subject: RE: [wsjt-devel] CW-ID is not being sent Hi Marco, I set up v2.7.0 GA (latest version) and selected in General the CW ID interwall to ‘1’. I listened to the audio and there is my CW id once a minute! When I set T/R to 5 s, then the CW ID replaces the first MSK144 transmission. When the T/R period is longer, then the last 5 s of the transmission is replaced. If I also select CW ID after 73, then the last 5 s of the ‘73’ message is stolen for the CW ID. The once a minute CW ID transmission may not be the first time of the minute. At least with 10 s T/R sends it at 45 seconds mark. At T/R 5 s the whole ‘73’ message is stolen and no ’73’ is sent (may be a bug). The CW ID seems to work. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> Sent: Tuesday, May 13, 2025 12:25 AM To: wsj...@li...<mailto:wsj...@li...> Cc: Marco Calistri <PY...@ou...<mailto:PY...@ou...>> Subject: Re: [wsjt-devel] CW-ID is not being sent Hi Andy! In reality I was asking in general the correct usage of CW-ID, which at least here it seems is not working. Then I would like to get the confirmation about it. Best regards, Marco, PY1ZRJ |
|
From: Patrick 9. <pat...@gm...> - 2025-05-11 16:33:54
|
CW id was used b4 in past on old modes. Not sure if is still used nowdays. JT65a, JT6M had CW ID. ned, 11. svi 2025. 18:28 Marco Calistri via wsjt-devel < wsj...@li...> je napisao: > Hello, > > I started to use MSK144 and among other things, I'm not understanding if > I'm doing something wrong that prevents my CW-ID to be sent every > time-frame I selected. > > Are there some details that I'm missing? > > How could I verify the CW-ID transmission? > > These are my current settings: > > > > I've tried 1, and 7 as well but I never noticed CW-ID being sent. > > Thanks! > --- > > *73 de Marco, PY1ZRJ (former IK5BCU) * > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Marco C. <PY...@ou...> - 2025-05-11 16:55:35
Attachments:
OpenPGP_signature.asc
OpenPGP_0x38215F3BB231677C.asc
|
Thanks Patrick! I'm using latest WSJT-X version and I was expecting to see the CW-ID during MSK144 operation. 73 de Marco PY1ZRJ Il 11/05/25 13:33, Patrick 9A5CW ha scritto: > > CW id was used b4 in past on old modes. Not sure if is still used nowdays. > JT65a, JT6M had CW ID. > > > ned, 11. svi 2025. 18:28 Marco Calistri via wsjt-devel > <wsj...@li...> je napisao: > > Hello, > > I started to use MSK144 and among other things, I'm not > understanding if I'm doing something wrong that prevents my CW-ID > to be sent every time-frame I selected. > > Are there some details that I'm missing? > > How could I verify the CW-ID transmission? > > These are my current settings: > > > > I've tried 1, and 7 as well but I never noticed CW-ID being sent. > > Thanks! > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* > ** > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > EFE62hMo0AA5GaSX.jpeg > > > ZpqOWexRd030VPJP.png > --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Reino T. <rei...@ko...> - 2025-05-11 17:37:55
Attachments:
image001.jpg
image002.png
|
Marco, I am not an expert, but I assume that you need to select ‘ID CW dopo 73’ for the activation. I read is so that the CW ID is sent in your settings only after every third sending of the ‘73’. It may be so that it will be sent only as a part of QSOs, not otherwise. I have not used it as it is not a mandatory issue in Finland. 73, Reino OH3mA From: Marco Calistri via wsjt-devel <wsj...@li...> Sent: Sunday, May 11, 2025 7:55 PM To: Patrick 9A5CW <pat...@gm...>; WSJT software development <wsj...@li...> Cc: Marco Calistri <PY...@ou...> Subject: Re: [wsjt-devel] CW-ID is not being sent Thanks Patrick! I'm using latest WSJT-X version and I was expecting to see the CW-ID during MSK144 operation. 73 de Marco PY1ZRJ Il 11/05/25 13:33, Patrick 9A5CW ha scritto: CW id was used b4 in past on old modes. Not sure if is still used nowdays. JT65a, JT6M had CW ID. ned, 11. svi 2025. 18:28 Marco Calistri via wsjt-devel <wsj...@li... <mailto:wsj...@li...> > je napisao: Hello, I started to use MSK144 and among other things, I'm not understanding if I'm doing something wrong that prevents my CW-ID to be sent every time-frame I selected. Are there some details that I'm missing? How could I verify the CW-ID transmission? These are my current settings: I've tried 1, and 7 as well but I never noticed CW-ID being sent. Thanks! --- 73 de Marco, PY1ZRJ (former IK5BCU) _______________________________________________ wsjt-devel mailing list wsj...@li... <mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel EFE62hMo0AA5GaSX.jpeg ZpqOWexRd030VPJP.png --- 73 de Marco, PY1ZRJ (former IK5BCU) |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X