Date   

Re: LDMOS mounting inductance confusion.

alwyn.seeds1
 

Dear Chris,

Thanks for emphasising this point. I hear a number of amplifiers sold to amateurs that have bad radiated noise due to conversion from instabilities at out of band frequencies.

Amplifiers need to be tested over their full power range into mismatched loads at every frequency at which the active device can have gain.

I had one amplifier with a common mode instabilty, that was stable into a log periodic aerial, but grossly unstable into a Yagi.

Regards,

Alwyn
_____________________________________________________

Alwyn Seeds, Director
SynOptika Ltd.,
114 Beaufort Street,
London,
SW3 6BU,
England.


SynOptika Ltd., Registered in England and Wales: No. 04606737
Registered Office: 114 Beaufort Street, London, SW3 6BU, United Kingdom.
_____________________________________________________


Re: KST2ME Questino

Robin Szemeti - G1YFG
 

I did use Wireshark for initial testing, but once I had the TCP<->WebSocket bridge running and the raw protocol logged to the browser console output, it was no longer needed.   It is useful for examining low-level interactions though ...


On Mon, 27 Jul 2020 at 13:15, Andy <mm0fmf@...> wrote:
Which is why something like Wireshark is to be preferred. Capture *ALL* the traffic with Wireshark and analyse what was captured later with the nice plugins you can write for it.

73
Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 5:11 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
AH !!!!!!!!!!!!
Didn't know there was another interface, I thought it was only Telnet.
That explains to obvious disconnect when certain commands that might be expected to work don't



On Mon, 27 Jul 2020 at 13:08, Robin Szemeti - G1YFG <robin@...> wrote:
Just bear in mind that KST2ME does NOT use the telnet interface ... and the protocol is somewhat different.

I've been playing with this recently myself to add a "missed call" feature to my software (ie, if someone messages you while you are not connected, it will store the messages until such time as you do connect.

I am hesitant to criticise the protocol, as I appreciate the time and effort put in by the original author, for the benefit of the community. It is however lacking in some features that I think are needed and some of it is coded in a very odd way, but it is what it is ...

On Mon, 27 Jul 2020 at 12:58, Andy <mm0fmf@...> wrote:
What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.

Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 4:56 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Andy
 

Which is why something like Wireshark is to be preferred. Capture *ALL* the traffic with Wireshark and analyse what was captured later with the nice plugins you can write for it.

73
Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 5:11 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
AH !!!!!!!!!!!!
Didn't know there was another interface, I thought it was only Telnet.
That explains to obvious disconnect when certain commands that might be expected to work don't



On Mon, 27 Jul 2020 at 13:08, Robin Szemeti - G1YFG <robin@...> wrote:
Just bear in mind that KST2ME does NOT use the telnet interface ... and the protocol is somewhat different.

I've been playing with this recently myself to add a "missed call" feature to my software (ie, if someone messages you while you are not connected, it will store the messages until such time as you do connect.

I am hesitant to criticise the protocol, as I appreciate the time and effort put in by the original author, for the benefit of the community. It is however lacking in some features that I think are needed and some of it is coded in a very odd way, but it is what it is ...

On Mon, 27 Jul 2020 at 12:58, Andy <mm0fmf@...> wrote:
What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.

Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 4:56 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Robin Szemeti - G1YFG
 

yes, I love the "disconnect" feature ;) ... "received an odd command shall I : a) respond with an error code or b) stuff, it, just drop the connection silently" ...

Anyway, see PM.


On Mon, 27 Jul 2020 at 13:11, Andy G4JNT <andy.g4jnt@...> wrote:
AH !!!!!!!!!!!!
Didn't know there was another interface, I thought it was only Telnet.
That explains to obvious disconnect when certain commands that might be expected to work don't



On Mon, 27 Jul 2020 at 13:08, Robin Szemeti - G1YFG <robin@...> wrote:
Just bear in mind that KST2ME does NOT use the telnet interface ... and the protocol is somewhat different.

I've been playing with this recently myself to add a "missed call" feature to my software (ie, if someone messages you while you are not connected, it will store the messages until such time as you do connect.

I am hesitant to criticise the protocol, as I appreciate the time and effort put in by the original author, for the benefit of the community. It is however lacking in some features that I think are needed and some of it is coded in a very odd way, but it is what it is ...

On Mon, 27 Jul 2020 at 12:58, Andy <mm0fmf@...> wrote:
What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.

Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 4:56 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Andy G4JNT
 

AH !!!!!!!!!!!!
Didn't know there was another interface, I thought it was only Telnet.
That explains to obvious disconnect when certain commands that might be expected to work don't



On Mon, 27 Jul 2020 at 13:08, Robin Szemeti - G1YFG <robin@...> wrote:
Just bear in mind that KST2ME does NOT use the telnet interface ... and the protocol is somewhat different.

I've been playing with this recently myself to add a "missed call" feature to my software (ie, if someone messages you while you are not connected, it will store the messages until such time as you do connect.

I am hesitant to criticise the protocol, as I appreciate the time and effort put in by the original author, for the benefit of the community. It is however lacking in some features that I think are needed and some of it is coded in a very odd way, but it is what it is ...

On Mon, 27 Jul 2020 at 12:58, Andy <mm0fmf@...> wrote:
What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.

Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 4:56 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Andy G4JNT
 

PowerBasic code,  using the following:

    THREAD CREATE CheckInput(ix&) TO idThread&
    TCP OPEN PORT 23000 AT "www.on4kst.info" AS #1
    SLEEP (200)                   '200ms delay to allow a response
    TCP PRINT #1, Username$
    SLEEP (200)
    TCP PRINT #1, Password$
    SLEEP (200)
    TCP PRINT #1, "3"       '3 = Microwave Chat
             then send any text I want to using TCP PRINT #3

and in a separate thread, looking for input :
    DO
        TCP LINE INPUT #1, RawMessage$
                ............. all the string processing on RawMessage$   needed to do what's wanted
                         including looking for Username$ in there 
    LOOP

Andy


On Mon, 27 Jul 2020 at 12:58, Andy <mm0fmf@...> wrote:
What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.

Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 4:56 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Robin Szemeti - G1YFG
 

Just bear in mind that KST2ME does NOT use the telnet interface ... and the protocol is somewhat different.

I've been playing with this recently myself to add a "missed call" feature to my software (ie, if someone messages you while you are not connected, it will store the messages until such time as you do connect.

I am hesitant to criticise the protocol, as I appreciate the time and effort put in by the original author, for the benefit of the community. It is however lacking in some features that I think are needed and some of it is coded in a very odd way, but it is what it is ...


On Mon, 27 Jul 2020 at 12:58, Andy <mm0fmf@...> wrote:
What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.

Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 4:56 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Andy
 

What are using to view the socket data? I normally rely on Wireshark (Windows and Linux) for this kind of thing.

Andy
(the other one)


From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> on behalf of Andy G4JNT <andy.g4jnt@...>
Sent: Monday, July 27, 2020 4:56 AM
To: UK Microwaves groups.io <UKMicrowaves@groups.io>
Subject: Re: [UKMicrowaves] KST2ME Questino
 
At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Andy G4JNT
 

At least in KST2ME the second type is highlighted, and you can change the .WAV file associated with it to anything you like (even meep.wav if you wanted to) and teh colour of teh highlight.

But Robin and I are still puzzled over the actual coding over air that differentiates a /CQ from the callsign alone





On Mon, 27 Jul 2020 at 12:51, Pete - GM4BYF via groups.io <gm4byf=blueyonder.co.uk@groups.io> wrote:

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Pete - GM4BYF
 

The meep meep is when someone definitely messages you using the /cq. The  dind sound is when somebody doesn't use the /cq - in normal use of KST, that message may easily not be seen as it isn't highlighted.

73
Pete GM4BYF
On 27/07/20 12:27, Andy G4JNT wrote:

Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 

Andy

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com

--
vry 73
Pete GM4BYF


Re: KST2ME Questino

Andy G4JNT
 

Well.
Interesting.   The window on the left is my software that shows everything that arrives via the Telnet interface - the raw message.   If the user call appears in te message, it shows highlighted in green.   All other messages are black on white (it was quiet, there was little othe traffic)
Window on the right is KST2ME  also logged in as G8IMR, so both respond to the same messages

The using the main ON4KST web interface logged in as 'JNT  I sent the following to get the results shown
   g8imr no preamble, just callsign  
   /cq g8imr with slash seek you
   (g8imr) in brackets
The results you can see in the KST2ME window.
The first one (at 1129)  triggered a magenta highlight and a polite ding
The second one a raucous meep-meep and orange.   
As  a raw message the callsign appears in brackets, coded as a "trigger CQ meep etc"
But any attempt to type brackets fails to do any triggering, hence no KST2ME filtered response to this.  In spite of my own prog highlighting since teh callsign appears in the message
SO there's definitely some other coding going on over air that is telling  KST2ME its a /CQ entry as opposed to just a callsign in the string.  As RObin intimated

Why was it written with such a clumsy interface and coding?



image.png


On Mon, 27 Jul 2020 at 12:27, Andy Talbot <andy.g4jnt@...> wrote:
Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


Re: KST2ME Questino

Andy G4JNT
 

Main issue solved.  I logged into the dreaded ON4KST actual chat facility as G8IMR   and into KST2ME with G4JNT

Sent a message prefaced only with the call,    no /CQ or anything
Result, a polite dind sound and my filtered message highlighted in magenta

Then in ON4KST typed "/cq G8imr ... etc"    and got a loud raucous mepp-meep sound and the message highlighted in orange.  

SO that's answered for-sure my original query.    Now to find the over-the-air difference between the two messages.
That's going to require a bit of playing around



On Sun, 26 Jul 2020 at 22:21, Robin Szemeti - G1YFG <robin@...> wrote:
I was unable to work that out either.

If you send /CQ <$callsign> <msg> the KST server will send out the message with the <to> field populated with <$callsign> 

In the protocol there is a "highlight" field that can be either 0,1 or 2 ... but I was unable to discover when or why it changed.  I ignored it completely and simply looked at the <to> field and triggered the sound with a regex if it matched my call.

On Sun, 26 Jul 2020 at 16:04, Andy G4JNT <andy.g4jnt@...> wrote:
No, doesn't help.  That sets up the sounds for two apparently different message types.  It has two options,  CQ sound and Preamble sound

When is a message a CQ and when a preamble?  Looking at the raw over-air message contents there seems no obvious difference.   Although a few callsigns appear in brackets - is that it ?

I've never used the actual KST web interface, but understand that in there you have to type some daft entity prefaced by "/CQ" i.  Is that the difference?  In which case I'm going to have to wait for a quiet period on KST and use the web interface to send some  G8IMR <> G4JNT test messages.

Want to know the raw over-air format and its options, coz I have an idea for using KST reporting for something different.




On Sun, 26 Jul 2020 at 15:52, Paul Selwood G3YDY via groups.io <g3ydy=blueyonder.co.uk@groups.io> wrote:

Hi Andy,

 

Tools/Setup/Sounds  - you will see it all.

 

73

 

Paul

 

G3YDY

 

 

From: UKMicrowaves@groups.io <UKMicrowaves@groups.io> On Behalf Of Andy G4JNT
Sent: 26 July 2020 15:34
To: UK Microwaves groups.io <ukmicrowaves@groups.io>
Subject: [UKMicrowaves] KST2ME Questino

 

Using KST2Me  , messages sent to me come up with either an orange or magenta background in the lower window, both accompanied by a sound.    Orange a  'meep' sound,  magenta a 'ding'

 

What's the difference between the two colours + sounds?

 


This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com


Re: Nokia boards ...

geoffrey pike
 



this has some info on the subject 
cheers
Geoff
GI0GDP

On Monday, 27 July 2020, 11:22:55 BST, Timestep <help@...> wrote:


 
 
Hi Geoff
 
Could you give me a link to the mods please.  I have one here just waiting !
 
73  Dave  G4IUG


Re: Nokia boards ...

Dave Cawley G4IUG
 


 
 
Hi Geoff
 
Could you give me a link to the mods please.  I have one here just waiting !
 
73  Dave  G4IUG


Re: Nokia boards ...

Steve G4HTZ
 

I bought one already modified off of eBay ...never used ...meant to give out over 100w + with about 50-100mw drive....never tried or used it ....
--
Steve G4HTZ 
JO01JN60
Great Wakering, Essex 
24ghz 1.8w 80cm dish 

also known to be active occasionally on 70cms DATV 


Siemens W30861-Q4160-X-5 "13cm PA" wanted

Phil Guttridge G3TCU
 

Hi all,

I bought one of these from a UK rally a couple of years ago and have finally mounted it in a box with an SG-labs Xvtr, PSUs etc.

I carried out mods originally posted by IZ4BEH (there is similar info by DK5FA on the Amsat-DL site).  I'm sure it is not yet 'optimised' but I measure about 150W out on 2320.
BTW: comments on Amsat-DL suggest that these units are pretty hopeless at 2400.

Now I have put this effort into making use of this lump, I'd like to get hold of a spare, just in case I ever have a mishap with this one!

I'd be grateful if anyone knows of a source of supply.

Thanks & 73, Phil G3TCU











Re: LDMOS mounting inductance confusion.

Chris Bartram G4DGU
 

Hello Ian,

Am I missing something, or what's wrong with bolting the PCB flat down onto the spreader and filling the gap between the gate leads and the topside of the board with honest, reliable metal?
Certainly, with a balanced amplifier, the whole point is to present the correct differential impedance to the devices. That will be present at the device terminals even if the microstripline groundplane is 'floating'.

Connecting the groundplane firmly to ground will make little difference to the differential impedance, but will - if the 'designer' has even thought about the problem - cause a significant change in the common-mode impedance presented to the devices. That could, in turn, lead to 'parallel-mode' instabilities.

What's missing in your analysis is the change of characteristic impedance presented in both common and differential mode impedances by changing the effective thickness of the tracks. Conductor thickness is a significant factor when designing microstriplines.

The lossy nature of many components at RF, and particularly microwaves, can hide many potential problems!

If I seem a little jaundiced regarding the design of amateur amplifiers, I am! However, I'm not prepared to discuss details in public ...

73

Chris G4DGU

73

Chris G4DGU


Re: Nokia boards ...

Robin Szemeti - G1YFG
 

Better add one to the collection then ...

On Mon, 27 Jul 2020 at 10:40, geoffrey pike via groups.io <gi0gdp=yahoo.co.uk@groups.io> wrote:
Hi Robin,
NO, and these boards have been detailed on AMSAT DL.
Problems (because they have been pulled) are resistor failure.
They easily give 50 dBm for about 17 dBm or less in.
Biggest problem is connectors so just remove the old ones, anyway heaps of info available
The single biggest improvement at 2,405 GHz is the lowering of the line Z on the driver stage, all documented.
For 2.3 GHz you dont need to do much at all
cheers
Geoff
GI0GDP

On Monday, 27 July 2020, 10:33:47 BST, Robin Szemeti - G1YFG <robin@...> wrote:


Sorry, a photo would help:

image.png


On Mon, 27 Jul 2020 at 10:32, Robin Szemeti <robin@...> wrote:
I've seen some Nokia PA boards for sale, are these the same as the ones that were offered through the chipbank?

Has anyone had success with this type ?

--
Best regards,

Robin Szemeti

Redpoint Consulting Limited

E: robin@...
T: +44 (0) 1299 405028
M: +44 (0) 7971 883371

CONFIDENTIALITY NOTICE
The information contained in this e-mail is intended only for the
confidential use of the above named recipient. If you are not the
intended recipient or person responsible for delivering it to the
intended recipient, you have received this communication in error
and must not distribute or copy it.
Please accept the sender's apologies, notify the sender immediately
by return e-mail and delete this communication.

Thank you.


Re: Nokia boards ...

geoffrey pike
 

Hi Robin,
NO, and these boards have been detailed on AMSAT DL.
Problems (because they have been pulled) are resistor failure.
They easily give 50 dBm for about 17 dBm or less in.
Biggest problem is connectors so just remove the old ones, anyway heaps of info available
The single biggest improvement at 2,405 GHz is the lowering of the line Z on the driver stage, all documented.
For 2.3 GHz you dont need to do much at all
cheers
Geoff
GI0GDP

On Monday, 27 July 2020, 10:33:47 BST, Robin Szemeti - G1YFG <robin@...> wrote:


Sorry, a photo would help:

image.png


On Mon, 27 Jul 2020 at 10:32, Robin Szemeti <robin@...> wrote:
I've seen some Nokia PA boards for sale, are these the same as the ones that were offered through the chipbank?

Has anyone had success with this type ?

--
Best regards,

Robin Szemeti

Redpoint Consulting Limited

E: robin@...
T: +44 (0) 1299 405028
M: +44 (0) 7971 883371

CONFIDENTIALITY NOTICE
The information contained in this e-mail is intended only for the
confidential use of the above named recipient. If you are not the
intended recipient or person responsible for delivering it to the
intended recipient, you have received this communication in error
and must not distribute or copy it.
Please accept the sender's apologies, notify the sender immediately
by return e-mail and delete this communication.

Thank you.


Re: Nokia boards ...

militaryoperator
 

I have one of these, hoping to get it on 2320 at some time. 

Ben G4BXD 

image.png



5741 - 5760 of 62956