Portsdown 4 with Pluto - Things to Remember

[G8GKQ]

I have been doing some experiments with the Portsdown 4 and Pluto. Some points to note:

As recently pointed out by G4FRE, carrier mode is not available when using a Pluto with the Portsdown. You can achieve the same result after a lot of waiting for Pluto reboots and button presses by using the Portsdown Signal Generator to drive the Pluto, but the level needs to be set correctly and it is hardly something that is easy to do in a portable situation. Incidentally, the need for Pluto reboots is why I have not coded it as an option from the Portsdown menu.

The Pluto is fussy about the callsign string. It cannot contain any slashes, otherwise your Service ID will be displayed as Service01. So, if you are operating portable, enter your callsign in the form G8GKQ-P, rather than G8GKQ/P. The LimeSDR accepts slashes, but neither device is well behaved if you try to include spaces.

Dave, G8GKQ

[F4DVK]

Hello Dave,

I managed to get it to work with "/P".

I modified:
rtmp://$PLUTOIP:7272/,$FREQ_OUTPUT,$MODTYPE,$CONSTLN,$SYMBOLRATE_K,$PFEC,-$PLUTOPWR,nocalib,800,32,/,$CALL,

Like this (,/,):
rtmp://$PLUTOIP:7272/,$FREQ_OUTPUT,$MODTYPE,$CONSTLN,$SYMBOLRATE_K,$PFEC,-$PLUTOPWR,nocalib,800,32,//,$CALL,

We would have to experiment, but it works for me with or without "/P".

Stephane

[G8GKQ]

Thanks Stephane

That worked for me! I had tried many "escape" codes, but not thought of doing that.

Unless you can see any downsides, I'll incorporate it in the next update.

Dave, G8GKQ

[F4DVK]

You can integrate it, I only did tests.

Stephane