Re: DX-World DXpedition list
Makes no difference here
73
Jan
PA4JJ
Op 1-12-2024 om 12:48 schreef Andrea
via groups.io:
I think this has something to do with windows regional
setting.
I changed to English (United States) and it's working fine.
Maybe is the date/hour format?
73
Andrea
Il giorno dom 1 dic 2024 alle
ore 12:46 Jan via <hamlogger= [email protected]> ha
scritto:
I have the same issue
7Q8P should be in bold or am I mistaken?
Op 1-12-2024 om 11:20 schreef Andrea via :
I changed it to period but same issue
Il giorno dom 1 dic 2024 alle ore 10:44 ja1nlx via
<ayoshida0205@...> ha scritto:
Your decimal symbol is comma ?
If so, temporarily change to period.
73 de aki
JA1NLX
On 2024-12-01 日 18:33:59, Andrea via <fuffa2k5@...> wrote:
Hi Aki san.
I did that and now I can see the DXpeditions 12.txt" file.
However the DXpedition call is not bolt and the right-click option
"Get DXpedition info" is grayed out, see attached screenshot.
Il giorno dom 1 dic 2024 alle ore 10:21 ja1nlx via
ha scritto:
Click Setup in the main menu.
Click Update.
Enable automatic download of DX-World DXpedition list.
Delete DXpedition 0.txt.
Close/Run Logger32.
73 de aki
JA1NLX
On 2024-12-01 日 18:14:49, Andrea via wrote:
I'm trying this new feature (thanks Bob and to the rest of the dev team).
This is a great feature, as so far I did it manually inserting dxped
calls in call alert list.
But, it seems I have an issue and is not working. I cannot see any
call in bold or italic.
Looking at the dxpediton file its name is "DXpeditions 0.txt".
Is this right or as today is first December (at least in my timezone)
it should be "DXpeditions 12.txt"?
Thanks
73 de IZ2LSC
--
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 77.174.195.163 port 7300
NO FT8/FT4 spots on pa4jj-3 77.174.195.163 port 7388
--
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 77.174.195.163 port 7300
NO FT8/FT4 spots on pa4jj-3 77.174.195.163 port 7388
|
Version 4.0.330 does not appear to calculate grid squares confirmed correctly.
I did recalculate statistics? after installation of the new version. (did this twice)
With the previous version I had 1228 grid squares confirmed. This agreed with the VUCC award on LOTW.
Version 4.0.330 shows only 1224 grids confirmed. The total grids worked,1279, agreed with the previous version.
73, Terry N4TB
|
Re: DX-World DXpedition list
I think this has something to do with windows regional setting. I changed to English (United States) and it's working fine. Maybe is the date/hour format?
73 Andrea
Il giorno dom 1 dic 2024 alle ore 12:46 Jan via <hamlogger= [email protected]> ha scritto:
I have the same issue
7Q8P should be in bold or am I mistaken?
Op 1-12-2024 om 11:20 schreef Andrea
via :
I changed it to period but same issue
Il giorno dom 1 dic 2024 alle ore 10:44 ja1nlx via
<ayoshida0205@...> ha scritto:
Your decimal symbol is comma ?
If so, temporarily change to period.
73 de aki
JA1NLX
On 2024-12-01 日 18:33:59, Andrea via <fuffa2k5@...> wrote:
Hi Aki san.
I did that and now I can see the DXpeditions 12.txt" file.
However the DXpedition call is not bolt and the right-click option
"Get DXpedition info" is grayed out, see attached screenshot.
Il giorno dom 1 dic 2024 alle ore 10:21 ja1nlx via
ha scritto:
Click Setup in the main menu.
Click Update.
Enable automatic download of DX-World DXpedition list.
Delete DXpedition 0.txt.
Close/Run Logger32.
73 de aki
JA1NLX
On 2024-12-01 日 18:14:49, Andrea via wrote:
I'm trying this new feature (thanks Bob and to the rest of the dev team).
This is a great feature, as so far I did it manually inserting dxped
calls in call alert list.
But, it seems I have an issue and is not working. I cannot see any
call in bold or italic.
Looking at the dxpediton file its name is "DXpeditions 0.txt".
Is this right or as today is first December (at least in my timezone)
it should be "DXpeditions 12.txt"?
Thanks
73 de IZ2LSC
--
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 77.174.195.163 port 7300
NO FT8/FT4 spots on pa4jj-3 77.174.195.163 port 7388
|
Re: DX-World DXpedition list
I have the same issue
7Q8P should be in bold or am I mistaken?
Op 1-12-2024 om 11:20 schreef Andrea
via groups.io:
I changed it to period but same issue
Il giorno dom 1 dic 2024 alle ore 10:44 ja1nlx via groups.io
<ayoshida0205@...> ha scritto:
Your decimal symbol is comma ?
If so, temporarily change to period.
73 de aki
JA1NLX
On 2024-12-01 日 18:33:59, Andrea via groups.io <fuffa2k5@...> wrote:
Hi Aki san.
I did that and now I can see the DXpeditions 12.txt" file.
However the DXpedition call is not bolt and the right-click option
"Get DXpedition info" is grayed out, see attached screenshot.
Il giorno dom 1 dic 2024 alle ore 10:21 ja1nlx via groups.io
ha scritto:
Click Setup in the main menu.
Click Update.
Enable automatic download of DX-World DXpedition list.
Delete DXpedition 0.txt.
Close/Run Logger32.
73 de aki
JA1NLX
On 2024-12-01 日 18:14:49, Andrea via groups.io wrote:
I'm trying this new feature (thanks Bob and to the rest of the dev team).
This is a great feature, as so far I did it manually inserting dxped
calls in call alert list.
But, it seems I have an issue and is not working. I cannot see any
call in bold or italic.
Looking at the dxpediton file its name is "DXpeditions 0.txt".
Is this right or as today is first December (at least in my timezone)
it should be "DXpeditions 12.txt"?
Thanks
73 de IZ2LSC
--
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 77.174.195.163 port 7300
NO FT8/FT4 spots on pa4jj-3 77.174.195.163 port 7388
|
Hi?! ? Nice feature Bob?!!?? ? You’re near what i’ve asked several times?! Now you can improve this with a little check box option saying?:? SHOW ONLY DXWORLD EXPED SPOTS in the DX spots windows. (checkbox in the DXworld windows) ? And as we can check what DXped we want, the new feature i asked is near the goal, (as i’ve asked to make this feature with one call, whatever what is it) ? If you add this, after, i can do the feature i want if i edit the TXT file and add manualy the call i just want to see in the DXspot windows…boring to edit but….interesting… ? And i have only one call spots showed in the DXspots windows?! DX spots filters don’t make this. ? Thanks for improving L32?!! ? Ciao 73 Olivier F4FQH ? ? This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
|
Re: DX-World DXpedition list
I changed it to period but same issue Il giorno dom 1 dic 2024 alle ore 10:44 ja1nlx via groups.io <ayoshida0205@...> ha scritto:
Your decimal symbol is comma ?
If so, temporarily change to period.
73 de aki
JA1NLX
On 2024-12-01 日 18:33:59, Andrea via groups.io <fuffa2k5@...> wrote:
Hi Aki san.
I did that and now I can see the DXpeditions 12.txt" file.
However the DXpedition call is not bolt and the right-click option
"Get DXpedition info" is grayed out, see attached screenshot.
Il giorno dom 1 dic 2024 alle ore 10:21 ja1nlx via groups.io
ha scritto:
Click Setup in the main menu.
Click Update.
Enable automatic download of DX-World DXpedition list.
Delete DXpedition 0.txt.
Close/Run Logger32.
73 de aki
JA1NLX
On 2024-12-01 日 18:14:49, Andrea via groups.io wrote:
I'm trying this new feature (thanks Bob and to the rest of the dev team).
This is a great feature, as so far I did it manually inserting dxped
calls in call alert list.
But, it seems I have an issue and is not working. I cannot see any
call in bold or italic.
Looking at the dxpediton file its name is "DXpeditions 0.txt".
Is this right or as today is first December (at least in my timezone)
it should be "DXpeditions 12.txt"?
Thanks
73 de IZ2LSC
|
Re: DX-World DXpedition list
Your decimal symbol is comma ? If so, temporarily change to period.
On 2024-12-01 日 18:33:59, Andrea via groups.io <fuffa2k5@...> wrote: Hi Aki san.
I did that and now I can see the DXpeditions 12.txt" file.
However the DXpedition call is not bolt and the right-click option
"Get DXpedition info" is grayed out, see attached screenshot.
Il giorno dom 1 dic 2024 alle ore 10:21 ja1nlx via groups.io
ha scritto:
>
> Click Setup in the main menu.
> Click Update.
> Enable automatic download of DX-World DXpedition list.
> Delete DXpedition 0.txt.
> Close/Run Logger32.
>
> 73 de aki
> JA1NLX
>
> On 2024-12-01 日 18:14:49, Andrea via groups.io wrote:
>
> I'm trying this new feature (thanks Bob and to the rest of the dev team).
> This is a great feature, as so far I did it manually inserting dxped
> calls in call alert list.
> But, it seems I have an issue and is not working. I cannot see any
> call in bold or italic.
> Looking at the dxpediton file its name is "DXpeditions 0.txt".
> Is this right or as today is first December (at least in my timezone)
> it should be "DXpeditions 12.txt"?
>
> Thanks
> 73 de IZ2LSC
>
>
>
>
>
>
|
Re: DX-World DXpedition list
Hi Aki san. I did that and now I can see the DXpeditions 12.txt" file. However the DXpedition call is not bolt and the right-click option "Get DXpedition info" is grayed out, see attached screenshot. Il giorno dom 1 dic 2024 alle ore 10:21 ja1nlx via groups.io <ayoshida0205@...> ha scritto:
Click Setup in the main menu.
Click Update.
Enable automatic download of DX-World DXpedition list.
Delete DXpedition 0.txt.
Close/Run Logger32.
73 de aki
JA1NLX
On 2024-12-01 日 18:14:49, Andrea via groups.io <fuffa2k5@...> wrote:
I'm trying this new feature (thanks Bob and to the rest of the dev team).
This is a great feature, as so far I did it manually inserting dxped
calls in call alert list.
But, it seems I have an issue and is not working. I cannot see any
call in bold or italic.
Looking at the dxpediton file its name is "DXpeditions 0.txt".
Is this right or as today is first December (at least in my timezone)
it should be "DXpeditions 12.txt"?
Thanks
73 de IZ2LSC
|
Re: DX-World DXpedition list
Click Setup in the main menu. Click Update. Enable automatic download of DX-World DXpedition list. Delete DXpedition 0.txt.
On 2024-12-01 日 18:14:49, Andrea via groups.io <fuffa2k5@...> wrote: I'm trying this new feature (thanks Bob and to the rest of the dev team).
This is a great feature, as so far I did it manually inserting dxped
calls in call alert list.
But, it seems I have an issue and is not working. I cannot see any
call in bold or italic.
Looking at the dxpediton file its name is "DXpeditions 0.txt".
Is this right or as today is first December (at least in my timezone)
it should be "DXpeditions 12.txt"?
Thanks
73 de IZ2LSC
|
I'm trying this new feature (thanks Bob and to the rest of the dev team).
This is a great feature, as so far I did it manually inserting dxped
calls in call alert list.
But, it seems I have an issue and is not working. I cannot see any
call in bold or italic.
Looking at the dxpediton file its name is "DXpeditions 0.txt".
Is this right or as today is first December (at least in my timezone)
it should be "DXpeditions 12.txt"?
Thanks
73 de IZ2LSC
|
Re: Logger32 v4.0.330 auto-update is on-line
I think you have a serious problem ... everything works normally! Try to redo the recalculation of the statistics.
Good luck
Hello.
Thanks for this new release.
I found some that is not more working.on this release.
Insert a partial callsing in the Logbook Entry Window, then in the Worked/Confirmed Window we can see the status of that Country/DXCC on all Bands/Modes.
When I click on a Mode of an only Worked slot for that Band, the new Windoow that open does not more show the QSO (or QSOs) made with that Country/DXCC on that specific Band/Mode.
So we cannot know what is (or what are) the callsing/cllsigns we worked (before) on that specific Band/Mode.
See here:
I inserted "9H" and I ciicked on "CW" cell on the CW/15m, the new window open but des not show the prevoius QSOS/QSOs made with all "9H" on 15m CW.
For test I clicked also on the combination "PHO" on the cell 20m (confirmed) and this is the result:
So it looks like now we can see only the confimred QSOs and not also the Worked ones.
I already did recalculate statistics.
Thanks.
On Sunday, December 1, 2024 at 01:21:18 AM GMT+1, Bob via groups.io <k4cy@...> wrote:
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
Re: Logger32 v4.0.330 auto-update is on-line
Hello. Thanks for this new release. I found some that is not more working.on this release.
Insert a partial callsing in the Logbook Entry Window, then in the Worked/Confirmed Window we can see the status of that Country/DXCC on all Bands/Modes. When I click on a Mode of an only Worked slot for that Band, the new Windoow that open does not more show the QSO (or QSOs) made with that Country/DXCC on that specific Band/Mode. So we cannot know what is (or what are) the callsing/cllsigns we worked (before) on that specific Band/Mode.
See here:
I inserted "9H" and I ciicked on "CW" cell on the CW/15m, the new window open but des not show the prevoius QSOS/QSOs made with all "9H" on 15m CW.
For test I clicked also on the combination "PHO" on the cell 20m (confirmed) and this is the result:
So it looks like now we can see only the confimred QSOs and not also the Worked ones. I already did recalculate statistics.
Thanks.
On Sunday, December 1, 2024 at 01:21:18 AM GMT+1, Bob via groups.io <k4cy@...> wrote:
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
Re: Logger32 v4.0.330 auto-update is on-line
.? Sorry for the slight delay.? I was out logging ... with a chainsaw, not a keyboard.
Hey I noticed that there have been no ?for a couple of years.? Would anyone care to update the world on all the sexy new features Bob has added recently??
73 Gary? ?beater/tester &?
Honor Roll &? checker
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
Logger32 v4.0.330 auto-update is on-line
This release includes the following changes -
Changes made to the Previous QSO Window so that a left click on either the BAND or MODE column header sorts the previous QSOs by Band or Mode.
Fixed a referential integrity bug with WAZ and WAS award statistics. After installing this update, you must recalculate the statistics for all your logbooks.
A new feature has been added to highlight (in bold letters and color of your choice) DX Spots of DXpeditiions listed by DX-World at
Look at sections 14.2.3 and 14.4 of the help file for details. This is all new code, expect teething problems.
?
Enjoy, 73.
|
woow ... thank you so much Bob, very kind
73, IS0GQX Bruno
Il 30/11/2024 17:40, Bob via groups.io
ha scritto:
toggle quoted message
Show quoted text
I have
increased the max command line length?from 150 to 200
characters. SeventyThree(s).
On 11/30/2024 10:55 AM EST IS0GQX Bruno via groups.io
<is0gqx@...> wrote: ?
?
Hi Bob,
I am connected on HA8TKS (dxcluster.ha8tks.hu - port 7373),
for now I manually send and accept these 2 strings:
set dx filter cty=IS or (cont<>EU and
comment<>*beaco* and comment<>*ncdxf* and
comment<>*RTTY* and (spottercty<>k or
cty<>k) and (spottercty<>JA or cty<>JA) and
not skimmer)
and
set dx filter cty=IS or (cont<>EU and
comment<>*beaco* and comment<>*ncdxf* and
comment<>*RTTY* and (spottercty<>k or
cty<>k) and (spottercty<>JA or cty<>JA))
?
as you can see it is truncated:
?
?
thank you very much for your
attention
73, IS0GQX Bruno
?
?
Il 30/11/2024 15:37, Bob via
groups.io ha scritto:
As a test, I mase a Telnet shortcut called Too Long. The
command was 100 characters long. Like this - 111111111
222222222 333333333 444444444 555555555 666666666 777777777
888888888 999999999 0000000000
?
I sent the command to Telnet. Here is what I see in the
Telnet window
?
DX de LZ5DI-#: 28033.0 OH6NVC
CW 21 dB 27 WPM CQ 1425Z
111111111 222222222 333333333
444444444 555555555 666666666 777777777 888888888
999999999 0000000000
111111111 222222222 333333333
444444444 555555555 666666666 ... command error
?
The 100 character shortcut is
sent. The cluster didn't like the command, and appears to
reject anything more than 60 characters.
?
What do you see with a valid
command that is longer than 60 characters?
SeventyThree(s).
On 11/30/2024 3:50 AM EST IS0GQX Bruno via groups.io
< is0gqx@...>
wrote: ?
?
Hello,
I have recently connected to an AR Cluster with some
rules and filters,
I wanted to insert these strings in the convenient
"Telnet shortcuts"
menu to be easily recalled and sent to the Cluster
according to my
needs, but their length exceeds the length of the
space dedicated to the
"Command line" field and is truncated.
I thank you for your attention, especially Bob to whom
I ask if it was
possible to increase the length of the entry dedicated
to the command to
be sent.
Best regards and have a good weekend everyone.
?
73, IS0GQX Bruno
?
?
?
?
|
Hi Bob,
many thanks, for now I leave the insertion directly in the
configuration file (Logger32.ini), I will try not to enter the
graphical menu for further changes in order not to truncate the
strings.
Thanks again
73, IS0GQX Bruno
Il 30/11/2024 15:37, Bob via groups.io
ha scritto:
toggle quoted message
Show quoted text
As a test, I mase a Telnet shortcut called Too Long. The
command was 100 characters long. Like this - 111111111 222222222
333333333 444444444 555555555 666666666 777777777 888888888
999999999 0000000000
?
I sent the command to Telnet. Here is what I see in the Telnet
window
?
DX de LZ5DI-#: 28033.0 OH6NVC CW
21 dB 27 WPM CQ 1425Z
111111111 222222222 333333333
444444444 555555555 666666666 777777777 888888888 999999999
0000000000
111111111 222222222 333333333
444444444 555555555 666666666 ... command error
?
The 100 character shortcut is
sent. The cluster didn't like the command, and appears to
reject anything more than 60 characters.
?
What do you see with a valid
command that is longer than 60 characters? SeventyThree(s).
On 11/30/2024 3:50 AM EST IS0GQX Bruno via groups.io < is0gqx@...>
wrote: ?
?
Hello,
I have recently connected to an AR Cluster with some rules
and filters,
I wanted to insert these strings in the convenient "Telnet
shortcuts"
menu to be easily recalled and sent to the Cluster
according to my
needs, but their length exceeds the length of the space
dedicated to the
"Command line" field and is truncated.
I thank you for your attention, especially Bob to whom I
ask if it was
possible to increase the length of the entry dedicated to
the command to
be sent.
Best regards and have a good weekend everyone.
?
73, IS0GQX Bruno
?
?
?
|
I have increased the max command line length?from 150 to 200 characters. SeventyThree(s).
On 11/30/2024 10:55 AM EST IS0GQX Bruno via groups.io <is0gqx@...> wrote:
?
?
Hi Bob,
I am connected on HA8TKS (dxcluster.ha8tks.hu - port 7373), for now I manually send and accept these 2 strings:
set dx filter cty=IS or (cont<>EU and comment<>*beaco* and comment<>*ncdxf* and comment<>*RTTY* and (spottercty<>k or cty<>k) and (spottercty<>JA or cty<>JA) and not skimmer)
and
set dx filter cty=IS or (cont<>EU and comment<>*beaco* and comment<>*ncdxf* and comment<>*RTTY* and (spottercty<>k or cty<>k) and (spottercty<>JA or cty<>JA))
?
as you can see it is truncated:
?
?
thank you very much for your attention
73, IS0GQX Bruno
?
?
Il 30/11/2024 15:37, Bob via groups.io ha scritto:
As a test, I mase a Telnet shortcut called Too Long. The command was 100 characters long. Like this - 111111111 222222222 333333333 444444444 555555555 666666666 777777777 888888888 999999999 0000000000
?
I sent the command to Telnet. Here is what I see in the Telnet window
?
DX de LZ5DI-#: 28033.0 OH6NVC CW 21 dB 27 WPM CQ 1425Z
111111111 222222222 333333333 444444444 555555555 666666666 777777777 888888888 999999999 0000000000
111111111 222222222 333333333 444444444 555555555 666666666 ... command error
?
The 100 character shortcut is sent. The cluster didn't like the command, and appears to reject anything more than 60 characters.
?
What do you see with a valid command that is longer than 60 characters? SeventyThree(s).
On 11/30/2024 3:50 AM EST IS0GQX Bruno via groups.io < is0gqx@...> wrote:
?
?
Hello,
I have recently connected to an AR Cluster with some rules and filters,
I wanted to insert these strings in the convenient "Telnet shortcuts"
menu to be easily recalled and sent to the Cluster according to my
needs, but their length exceeds the length of the space dedicated to the
"Command line" field and is truncated.
I thank you for your attention, especially Bob to whom I ask if it was
possible to increase the length of the entry dedicated to the command to
be sent.
Best regards and have a good weekend everyone.
?
73, IS0GQX Bruno
?
?
?
?
|
... or look at section 13.4.3 (page 296) of the help file for details on how to send long/complex commands to a Telnet cluster. SeventyThree(s).
On 11/30/2024 9:37 AM EST Bob <k4cy@...> wrote:
?
?
As a test, I mase a Telnet shortcut called Too Long. The command was 100 characters long. Like this - 111111111 222222222 333333333 444444444 555555555 666666666 777777777 888888888 999999999 0000000000
?
I sent the command to Telnet. Here is what I see in the Telnet window
?
DX de LZ5DI-#: 28033.0 OH6NVC CW 21 dB 27 WPM CQ 1425Z
111111111 222222222 333333333 444444444 555555555 666666666 777777777 888888888 999999999 0000000000
111111111 222222222 333333333 444444444 555555555 666666666 ... command error
?
The 100 character shortcut is sent. The cluster didn't like the command, and appears to reject anything more than 60 characters.
?
What do you see with a valid command that is longer than 60 characters? SeventyThree(s).
On 11/30/2024 3:50 AM EST IS0GQX Bruno via groups.io < is0gqx@...> wrote:
?
?
Hello,
I have recently connected to an AR Cluster with some rules and filters,
I wanted to insert these strings in the convenient "Telnet shortcuts"
menu to be easily recalled and sent to the Cluster according to my
needs, but their length exceeds the length of the space dedicated to the
"Command line" field and is truncated.
I thank you for your attention, especially Bob to whom I ask if it was
possible to increase the length of the entry dedicated to the command to
be sent.
Best regards and have a good weekend everyone.
?
73, IS0GQX Bruno
?
?
?
|
Hi Bob,
I am connected on HA8TKS (dxcluster.ha8tks.hu - port 7373), for
now I manually send and accept these 2 strings:
set dx filter cty=IS or (cont<>EU and
comment<>*beaco* and comment<>*ncdxf* and
comment<>*RTTY* and (spottercty<>k or cty<>k)
and (spottercty<>JA or cty<>JA) and not skimmer)
and
set dx filter cty=IS or (cont<>EU and
comment<>*beaco* and comment<>*ncdxf* and
comment<>*RTTY* and (spottercty<>k or cty<>k)
and (spottercty<>JA or cty<>JA))
as you can see it is truncated:
thank you very much for your attention
73, IS0GQX Bruno
Il 30/11/2024 15:37, Bob via groups.io
ha scritto:
toggle quoted message
Show quoted text
As a test, I mase a Telnet shortcut called Too Long. The
command was 100 characters long. Like this - 111111111 222222222
333333333 444444444 555555555 666666666 777777777 888888888
999999999 0000000000
?
I sent the command to Telnet. Here is what I see in the Telnet
window
?
DX de LZ5DI-#: 28033.0 OH6NVC CW
21 dB 27 WPM CQ 1425Z
111111111 222222222 333333333
444444444 555555555 666666666 777777777 888888888 999999999
0000000000
111111111 222222222 333333333
444444444 555555555 666666666 ... command error
?
The 100 character shortcut is
sent. The cluster didn't like the command, and appears to
reject anything more than 60 characters.
?
What do you see with a valid
command that is longer than 60 characters? SeventyThree(s).
On 11/30/2024 3:50 AM EST IS0GQX Bruno via groups.io < is0gqx@...>
wrote: ?
?
Hello,
I have recently connected to an AR Cluster with some rules
and filters,
I wanted to insert these strings in the convenient "Telnet
shortcuts"
menu to be easily recalled and sent to the Cluster
according to my
needs, but their length exceeds the length of the space
dedicated to the
"Command line" field and is truncated.
I thank you for your attention, especially Bob to whom I
ask if it was
possible to increase the length of the entry dedicated to
the command to
be sent.
Best regards and have a good weekend everyone.
?
73, IS0GQX Bruno
?
?
?
|
As a test, I mase a Telnet shortcut called Too Long. The command was 100 characters long. Like this - 111111111 222222222 333333333 444444444 555555555 666666666 777777777 888888888 999999999 0000000000
?
I sent the command to Telnet. Here is what I see in the Telnet window
?
DX de LZ5DI-#: 28033.0 OH6NVC CW 21 dB 27 WPM CQ 1425Z
111111111 222222222 333333333 444444444 555555555 666666666 777777777 888888888 999999999 0000000000
111111111 222222222 333333333 444444444 555555555 666666666 ... command error
?
The 100 character shortcut is sent. The cluster didn't like the command, and appears to reject anything more than 60 characters.
?
What do you see with a valid command that is longer than 60 characters? SeventyThree(s).
On 11/30/2024 3:50 AM EST IS0GQX Bruno via groups.io < is0gqx@...> wrote:
?
?
Hello,
I have recently connected to an AR Cluster with some rules and filters,
I wanted to insert these strings in the convenient "Telnet shortcuts"
menu to be easily recalled and sent to the Cluster according to my
needs, but their length exceeds the length of the space dedicated to the
"Command line" field and is truncated.
I thank you for your attention, especially Bob to whom I ask if it was
possible to increase the length of the entry dedicated to the command to
be sent.
Best regards and have a good weekend everyone.
?
73, IS0GQX Bruno
?
?
?
|
Jan
Stefano Zoli
ZL2iFB