Date   

ICOM 7600 SETUP?

Dan Coleman
 

I searched but did not see this topic so I am posting the question. I am sure someone out there is using their ICOM 7600 with MultiPSK. I have a USB to serial adapter etc. connected to the ACC1 port and now I am wondering if someone has information as to what I do next go get it all working. With this setup, I had it working about a year ago but I had a computer crash and can't see to get back. Any help would be greatly appreciated.
73, Dan, W8KMX, South Carolina, USA


Multipsk 4.39.4 translated to Spanish

Patrick Lindecker
 

Hello to all Spanish native speakers,

 

The 4.39.4 version of Multipsk has been completely translated to Spanish by Joachin (EA4ZB), from French. The links to the translation file and to the manual (AIDE_PSK.CHM) in Spanish are on my Web site (http://f6cte.free.fr/Translation_files.htm).

 

Note that for a new CHM file (as here the AIDE_PSK.CHM file):

 

"

Sometimes .CHM files are flagged (by Windows) as downloaded from an untrusted source such as the Internet.

 

To resolve this issue, carry out the following steps:

 

1.       Right-click the .CHM file and choose Properties

 

2.       On the General tab, click the button labeled "Unblock"

 

3.       Click OK

"

 

73

Patrick

 

 




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com



Re: new user with a few question

Patrick Lindecker
 

Hello,

 

>what do i need to do sdrplay tcp?

I’m  not sure to understand the question.  SDRplay is a receiver and tcp-ip is the link between Multipsk and the SDRplay server.

 

>can i close tx window ?
By clicking on the <RX> button or <ESC>.


>where is frequency list button ?

Click on the “QRGs” button.

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Beau Thompson
Envoyé : mardi 16 juillet 2019 14:11
À : multipsk@groups.io
Objet : [multipsk] new user with a few question

 

Hi All,

as a new user i have a few questions

1 what do i need to do sdrplay tcp?

2 can i close tx window ?


3 where is frequency list button ?

Thanks Beau n9mfk




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com



Re: How do I do unproto mode in ALE? #ALE #multipsk

Patrick Lindecker
 

Hello,

 

Unproto was not used at all. It has been removed from the 4.34 Multipsk. I will not put it back.

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de benhut1@...
Envoyé : lundi 15 juillet 2019 09:24
À : multipsk@groups.io
Objet : [multipsk] How do I do unproto mode in ALE? #ALE #multipsk

 

I used to be able to activate unproto mode which would bypass ARQ mode, and would also bypass some of the more advanced unconnected modes of ALE, and let me use ALE like a normal digital mode like RTTY45. That feature is missing now. Or else I just can't find it in the new version of the software. Please tell me how to find it, if it still exists. If it doesn't still exist, please put it back in.




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com



How do I do unproto mode in ALE? #ALE #multipsk

benhut1@...
 

I used to be able to activate unproto mode which would bypass ARQ mode, and would also bypass some of the more advanced unconnected modes of ALE, and let me use ALE like a normal digital mode like RTTY45. That feature is missing now. Or else I just can't find it in the new version of the software. Please tell me how to find it, if it still exists. If it doesn't still exist, please put it back in.


new user with a few question

Beau Thompson <n9mfk9@...>
 

Hi All,

as a new user i have a few questions

1 what do i need to do sdrplay tcp?

2 can i close tx window ?


3 where is frequency list button ?

Thanks Beau n9mfk


Re: Update shipdata.txt?

Patrick Lindecker
 

Nice Bob.

73
Patrick

-----Message d'origine-----
De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Bob
Envoyé : lundi 15 juillet 2019 22:05
À : multipsk@groups.io
Objet : Re: [multipsk] Update shipdata.txt?


On 7/14/2019 4:12:56 PM, Patrick Lindecker (f6cte@free.fr) wrote:
Hello Bob,
For test, I have inserted "316018616,ALGOMA SPIRIT,,Cargo " in the
Shipdata.txt file:

If I simulate the reception of the MMSI 316018616, it is displayed
after the
MMSI:
"(ALGOMA SPIRIT, Cargo - Canada)"
So it works.
I stared at the text file for the longest time and I saw nothing but CR LF
at the end of every line, no obvious missing "," characters and so forth so
I did a clean full install into a different folder and slowly started adding
active vessels in my area to that text file. It works fine, so I'll just
overwrite this file into the other folder. Odd, and no doubt a syntax error
somewhere from me typing too fast. Oh well!

Cheers!

Bob





---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


Re: Update shipdata.txt?

Bob
 

On 7/14/2019 4:12:56 PM, Patrick Lindecker (f6cte@free.fr) wrote:
Hello Bob,
For test, I have inserted "316018616,ALGOMA SPIRIT,,Cargo " in the
Shipdata.txt file:

If I simulate the reception of the MMSI 316018616, it is displayed after the
MMSI:
"(ALGOMA SPIRIT, Cargo - Canada)"
So it works.
I stared at the text file for the longest time and I saw nothing but CR LF at the end of every line, no obvious missing "," characters and so forth so I did a clean full install into a different folder and slowly started adding active vessels in my area to that text file. It works fine, so I'll just overwrite this file into the other folder. Odd, and no doubt a syntax error somewhere from me typing too fast. Oh well!

Cheers!

Bob


Re: ShipData txt file

Patrick Lindecker
 

Hello Mario,

 

I don’t use files which belong to other programs.

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de MarioLuciano
Envoyé : lundi 15 juillet 2019 11:56
À : multipsk@groups.io
Objet : [multipsk] ShipData txt file

 

Hi Patrick,

I'm gonna hook into Bob's topic. I wanted to ask you if you can exchange the YADD "YADD_MMSI_SHIP.txt" file with the MultiPsk ShipData.txt file, renaming it. Thank you.

73
Mario




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com



ShipData txt file

MarioLuciano
 

Hi Patrick,

I'm gonna hook into Bob's topic. I wanted to ask you if you can exchange the YADD "YADD_MMSI_SHIP.txt" file with the MultiPsk ShipData.txt file, renaming it. Thank you.

73
Mario


Re: Update shipdata.txt?

Patrick Lindecker
 

Hello Bob,

For test, I have inserted "316018616,ALGOMA SPIRIT,,Cargo " in the
Shipdata.txt file:

316018477,ALGOMA DISCOVERY,CFK9796,Cargo
316018616,ALGOMA SPIRIT,,Cargo
316019016,FJORD ETERNITE,CFN5465,

If I simulate the reception of the MMSI 316018616, it is displayed after the
MMSI:
"(ALGOMA SPIRIT, Cargo - Canada)"
So it works.

73
Patrick

-----Message d'origine-----
De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Bob
Envoyé : dimanche 14 juillet 2019 12:51
À : multipsk@groups.io
Objet : Re: [multipsk] Update shipdata.txt?

On 7/13/2019 4:51:52 PM, Patrick Lindecker (f6cte@free.fr) wrote:
Hello Bob,
316018616,ALGOMA SPIRIT,,Cargo
The format seems correct.
But the line must be located so as to respect an MMSI increasing order
(i.e with the others "316..." MMSIs).
The line must be finished with a CHR(13) (not a CHR(10)).
The number of lines of the file must not pass 50000.
Thanks Patrick, I'll check the CHR(13) situation. Otherwise the MMSI values
are incremental and the total is under 40000 lines.

Cheers!

Bob





---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


Re: help

Patrick Lindecker
 

RR for the solution.

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Christian VIRENQUE
Envoyé : dimanche 14 juillet 2019 15:51
À : multipsk@groups.io
Objet : Re: [multipsk] help

 

Hello Patrick,

 

Many thanks for explanation.

 

The problem is just solved.

 

I download and install a new package!

 

73

Christian

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Patrick Lindecker
Envoyé : dimanche 14 juillet 2019 10:33
À : multipsk@groups.io
Objet : Re: [multipsk] help

 

Hello Christian,

 

This error 10061 means

«Connection refused. You will usually see this error when a server refuses a connection from a client, because the server is not listening on that port.” 

 

The server here is the “rsc_tcp.exe” file. I don’t know why the connection is refused. Perhaps a bit error during the downloading (?), but it can also be a problem in the TCP/IP link of your PC (perhaps a resident program in your PC prevents the TCP/IP use).

 

You could try to download another time the Multipsk package and install it.

 

Have you tried a RTL dongle using rtl_tcp.exe? At least you will know if the origin of the problem is the TCP/IP link.

 

73

Patrick

 

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Christian VIRENQUE
Envoyé : samedi 13 juillet 2019 23:39
À : multipsk@groups.io
Objet : [multipsk] help

 

Since today when i launch SDRPlay, i have the message:

Fichier RSP_TCP exe détecté, connexion TCP/IP en cours

 

but no connexion is made.

 

When i relaunch MSK, i have:

Récepteur SDRplay detect et connexion TCP/IP faite

and immédiatly i have:

 

Echec de la liaison TCP/IP, le récepteur SDRplay n'est probablement pas connectée.

 

 

Une demande de connexion déjà acceptée n'a pas pu être achevée.

Erreur de socket n°10061 : Connexion refusée. Vous verrez cette erreur

 

On another computer, all is OK

 

Thanks for  help

 

CV

 

Image supprimée par l'expéditeur.

Garanti sans virus. www.avast.com


Re: help

Christian VIRENQUE
 

Hello Patrick,

 

Many thanks for explanation.

 

The problem is just solved.

 

I download and install a new package!

 

73

Christian

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Patrick Lindecker
Envoyé : dimanche 14 juillet 2019 10:33
À : multipsk@groups.io
Objet : Re: [multipsk] help

 

Hello Christian,

 

This error 10061 means

«Connection refused. You will usually see this error when a server refuses a connection from a client, because the server is not listening on that port.” 

 

The server here is the “rsc_tcp.exe” file. I don’t know why the connection is refused. Perhaps a bit error during the downloading (?), but it can also be a problem in the TCP/IP link of your PC (perhaps a resident program in your PC prevents the TCP/IP use).

 

You could try to download another time the Multipsk package and install it.

 

Have you tried a RTL dongle using rtl_tcp.exe? At least you will know if the origin of the problem is the TCP/IP link.

 

73

Patrick

 

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Christian VIRENQUE
Envoyé : samedi 13 juillet 2019 23:39
À : multipsk@groups.io
Objet : [multipsk] help

 

Since today when i launch SDRPlay, i have the message:

Fichier RSP_TCP exe détecté, connexion TCP/IP en cours

 

but no connexion is made.

 

When i relaunch MSK, i have:

Récepteur SDRplay detect et connexion TCP/IP faite

and immédiatly i have:

 

Echec de la liaison TCP/IP, le récepteur SDRplay n'est probablement pas connectée.

 

 

Une demande de connexion déjà acceptée n'a pas pu être achevée.

Erreur de socket n°10061 : Connexion refusée. Vous verrez cette erreur

 

On another computer, all is OK

 

Thanks for  help

 

CV

 

Image supprimée par l'expéditeur.

Garanti sans virus. www.avast.com


Re: Update shipdata.txt?

Bob
 

On 7/13/2019 4:51:52 PM, Patrick Lindecker (f6cte@free.fr) wrote:
Hello Bob,
316018616,ALGOMA SPIRIT,,Cargo
The format seems correct.
But the line must be located so as to respect an MMSI increasing order (i.e
with the others "316..." MMSIs).
The line must be finished with a CHR(13) (not a CHR(10)).
The number of lines of the file must not pass 50000.
Thanks Patrick, I'll check the CHR(13) situation. Otherwise the MMSI values are incremental and the total is under 40000 lines.

Cheers!

Bob


Re: help

Patrick Lindecker
 

Hello Christian,

 

This error 10061 means

«Connection refused. You will usually see this error when a server refuses a connection from a client, because the server is not listening on that port.” 

 

The server here is the “rsc_tcp.exe” file. I don’t know why the connection is refused. Perhaps a bit error during the downloading (?), but it can also be a problem in the TCP/IP link of your PC (perhaps a resident program in your PC prevents the TCP/IP use).

 

You could try to download another time the Multipsk package and install it.

 

Have you tried a RTL dongle using rtl_tcp.exe? At least you will know if the origin of the problem is the TCP/IP link.

 

73

Patrick

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Christian VIRENQUE
Envoyé : samedi 13 juillet 2019 23:39
À : multipsk@groups.io
Objet : [multipsk] help

 

Since today when i launch SDRPlay, i have the message:

Fichier RSP_TCP exe détecté, connexion TCP/IP en cours

 

but no connexion is made.

 

When i relaunch MSK, i have:

Récepteur SDRplay detect et connexion TCP/IP faite

and immédiatly i have:

 

Echec de la liaison TCP/IP, le récepteur SDRplay n'est probablement pas connectée.

 

 

Une demande de connexion déjà acceptée n'a pas pu être achevée.

Erreur de socket n°10061 : Connexion refusée. Vous verrez cette erreur

 

On another computer, all is OK

 

Thanks for  help

 

CV

 

Garanti sans virus. www.avast.com


help

Christian VIRENQUE
 

Since today when i launch SDRPlay, i have the message:

Fichier RSP_TCP exe détecté, connexion TCP/IP en cours

 

but no connexion is made.

 

When i relaunch MSK, i have:

Récepteur SDRplay detect et connexion TCP/IP faite

and immédiatly i have:

 

Echec de la liaison TCP/IP, le récepteur SDRplay n'est probablement pas connectée.

 

 

Une demande de connexion déjà acceptée n'a pas pu être achevée.

Erreur de socket n°10061 : Connexion refusée. Vous verrez cette erreur

 

On another computer, all is OK

 

Thanks for  help

 

CV


Garanti sans virus. www.avast.com


Re: Update shipdata.txt?

Patrick Lindecker
 

Hello Bob,

Is it possible to edit/expand the shipdata.txt file for AIS reception?
Yes it is.

316018616,ALGOMA SPIRIT,,Cargo
The format seems correct.
But the line must be located so as to respect an MMSI increasing order (i.e
with the others "316..." MMSIs).
The line must be finished with a CHR(13) (not a CHR(10)).
The number of lines of the file must not pass 50000.

73
Patrick



-----Message d'origine-----
De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Bob
Envoyé : samedi 13 juillet 2019 17:51
À : multipsk@groups.io
Objet : [multipsk] Update shipdata.txt?

Hi Patrick,

Is it possible to edit/expand the shipdata.txt file for AIS reception? I've
edited the file using plain old Windows Notepad, adding Canadian and
American ships here on the Great Lakes but none of the ship names ever
appear in MultiPSK or on Google Earth when their MMSI data is received via
AIS decoding.

Here's a received message as displayed in MultiPSK.

Message: 1 / MMSI: 316018616 (Canada) / Status: under way using engine /
Course over ground: 181.6° / Position: 079°47.82' W 43°16.61' N / 15:41:52

My edited shipdata.txt file contains this line:

316018616,ALGOMA SPIRIT,,Cargo

but only the MMSI appears as you see above. It doesn't look like there
should be any spaces between the fields and only a single comma is used as
the delimiter between each field so that's how I've been adding additional
lines. I used 2 commas ",," between fields 2 and 4 as I don’t have data for
field 3.

Cheers!

Bob





---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus


Update shipdata.txt?

Bob
 

Hi Patrick,

Is it possible to edit/expand the shipdata.txt file for AIS reception? I've edited the file using plain old Windows Notepad, adding Canadian and American ships here on the Great Lakes but none of the ship names ever appear in MultiPSK or on Google Earth when their MMSI data is received via AIS decoding.

Here's a received message as displayed in MultiPSK.

Message: 1 / MMSI: 316018616 (Canada) / Status: under way using engine / Course over ground: 181.6° / Position: 079°47.82' W 43°16.61' N / 15:41:52

My edited shipdata.txt file contains this line:

316018616,ALGOMA SPIRIT,,Cargo

but only the MMSI appears as you see above. It doesn't look like there should be any spaces between the fields and only a single comma is used as the delimiter between each field so that's how I've been adding additional lines. I used 2 commas ",," between fields 2 and 4 as I don’t have data for field 3.

Cheers!

Bob


Re: Multipsk stopped working after upgrad

Patrick Lindecker
 

Hello Dennis,

 

 

>Also, I know there is still is a sequence/combination of steps/changes that will throw the MultiPSK application into an endless error >message cycle. It has only happened very occasionally and the sequence to reproduce it is still a mystery and not nailed down. I will let >you know if I figure out the right combinations to cause it.

It is possible. I hope you can reproduce it so that I can fix it.

 

73

Patrick

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Dennis Schendel via Groups.Io
Envoyé : vendredi 5 juillet 2019 10:10
À : multipsk@groups.io
Objet : Re: [multipsk] Multipsk stopped working after upgrad

 

Hello Patrick,

 

Thank you very much for your quick response, analysis and fixes to the issues reported. The MultiPSK 4.39.4 TEST 1 VERSION is working much better with both the RTL-SDR.COM V3 dongle and SDRPlay RSP1A device.

 

I did a fair amount of test sequences in an attempt to identify some of the anomalies I was experiencing, primarily when switching between VDL2 and ADS-B modes and frequencies. While working on this I finally realized that the VFO-x buttons also store the Modulation selection settings for the last frequency setting loaded in it. So that oversight had led to some of the issues that I observed where the Modulations settings were “unexpectedly” changing when the frequency was changed.

 

I realized that when using preloaded VFO-x buttons to change the frequencies to switch between the VDL2 and ADS-B modes (or other modes for that matter), I needed to select the appropriate VFO first/before changing the Mode. This has helped avoid some of the unpredicted Modulation setting combinations that I encountered before.

 

However, there still remains some situation (sequence of changes) where the Modulations settings are still being set to unexpected settings. This seems to be more prevalent when switching into the ADS-B mode where the USB Modulations setting is occasionally being selected. I will continue to investigate this as I have time. But for now, it is quite easy to work around.

 

Also, I know there is still is a sequence/combination of steps/changes that will throw the MultiPSK application into an endless error message cycle. It has only happened very occasionally and the sequence to reproduce it is still a mystery and not nailed down. I will let you know if I figure out the right combinations to cause it.

 

Thank you again!

 

73

Dennis

 

 

From: multipsk@groups.io [mailto:multipsk@groups.io] On Behalf Of Patrick Lindecker
Sent: Thursday, July 04, 2019 10:50
To: multipsk@groups.io
Subject: Re: [multipsk] Multipsk stopped working after upgrad

 

Hello Dennis,

 

>In the following screenshot, the lower/narrower waterfall portion is an FM station, and when I change the frequency to 1090 MHz I still >hear the FM station but the waterfall shows the upper/wider waterfall image.

You are right. It is a regression bug following the SDRplay addition. Now fixed.

 

>As shown below, USB is enabled and selected when it should be PPM that is enabled and selected.

I agree, it is not normal, but I have not been able to reproduce this. I have always “PPM” when I switch to ADS-B… Do you remember how do you get this?

 

>In addition, with V4.39.3 and the RTL-dongle, sometimes when I change the receive Frequency, I will get endless error messages like this:

I have never seen this (and it seems independent from the 4.39.3 version). It will be to confirm in the next version (4.39.4).

 

>And after I finally get the MultiPSK instance/session shutdown/terminated ... then the next time I start MultiPSK, I might get a message like this:

It means that due some unknown error, the mode and the modulation managed to the SDR VFO B have been altered, and they have been replaced by default parameters: i.e. here BPSK31 and USB. Surely due to the forced shutdown. Seeing this is not a problem. It’s just an information that some parameters have been altered and that the system returns to default parameters for few ones.

 

>After clicking OK ... it may come up just fine or it might go into the endless error messages again ... especially if it is in “Open RX/TX screen after start up” ... which it will sometimes switch to on its own.

I never have experimented this.  Perhaps a consequence of the forced stop.

 

>BTW: I do have an SDRPlay RSP1A device. When trying to use it, on the Configuration settings window, I have found out that the “RTL >key/DLL” button and the “SDRplay” button can both be in the enabled/depressed position at the same time.

You are right. I fixed this.

Note: however it is not a professional program and all possibilities of errors by the user are directly be addressed. For example, if you click on a first interface and if, during the connection with the first one, you select another interface, the result is uncertain…

 

TKS for the remarks.

 

73

Patrick

 

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Dennis Schendel via Groups.Io
Envoyé : mercredi 3 juillet 2019 11:49
À : multipsk@groups.io
Objet : Re: [multipsk] Multipsk stopped working after upgrad

 

Hi Patrick,

 

I have also been having a similar problems/issues as Mike with the RTL-dongle (V3) when using MultiPSK v4.39.3. (The original V4.39, before SDRplay was added worked well.) Wasn’t sure at first if it was unique to me, but now that others seem to be experiencing similar issues it’s time to submit what I am seeing.

 

Here are a couple more twists I have observed with the latest version of MultiPSK when switching between different modes and frequencies ... for example, between the VDL2, ADS-B and FM/RDS modes and their corresponding frequencies.

 

When using a RTL.SDR.COM dongle (e.g. V3), I have found that when I change the receive Frequency in the transceiver window (via either VFO-A/B or Other frequencies or the QRGs), the frequency displayed changes but it is not actually being changed in the RTL-dongle. (This is most observable when changing from a FM station to different mode frequency ... I am still hearing/receiving the original FM station.) In the following screenshot, the lower/narrower waterfall portion is an FM station, and when I change the frequency to 1090 MHz I still hear the FM station but the waterfall shows the upper/wider waterfall image.

 

 

Then, when I change the mode to ADS-B to receive the digital ADS-B transmission on 1090 MHz ... the presets for the Modulations buttons at the bottom of the transceiver window don’t always show and/or get set correctly. As shown below, USB is enabled and selected when it should be PPM that is enabled and selected. (BTW: This kind of thing happens with some of the other Modes as well. And it has been happening on older versions of MultiPSK.)

 

 

From what I have seen in the past, isn’t this what it is supposed to look like for ADS-B mode?:

 

 

In addition, with V4.39.3 and the RTL-dongle, sometimes when I change the receive Frequency, I will get endless error messages like this:

 

 

And after I finally get the MultiPSK instance/session shutdown/terminated ... then the next time I start MultiPSK, I might get a message like this:

 

After clicking OK ... it may come up just fine or it might go into the endless error messages again ... especially if it is in “Open RX/TX screen after start up” ... which it will sometimes switch to on its own.

 

I am experiencing similar problems/issues when I try to switch to VDL2 or FM mode on an associated frequency such as 136.975 MHz, etc.

 

NOTE: The only way I can consistently get MultiPSK v4.39.3 to start and run as it should is to pre-set the Mode and corresponding Frequency and the shut MultiPSK completely down (terminated) And when it is restarted, it will come up and run correctly (until I change something as described above).

 

 

BTW: I do have an SDRPlay RSP1A device. When trying to use it, on the Configuration settings window, I have found out that the “RTL key/DLL” button and the “SDRplay” button can both be in the enabled/depressed position at the same time.

 

I don’t expect that was intended to happen or be allowed.

 

And when the “RX/TX screen” button is clicked, that causes the following endless error messages to occur:

 

 

I can get the SDRPlay RSP1A device to work by pre-setting everything and then doing the full restart of the MultiPSK v4.39.3 application. But after that, changing any of the settings, especially the receive Frequency will put things into the endless error messages condition again.

 

Hope this helps identify and isolate some of the issues.

 

Regards,

Dennis

 

From: multipsk@groups.io [mailto:multipsk@groups.io] On Behalf Of MadMike
Sent: Tuesday, July 02, 2019 17:14
To: multipsk@groups.io
Subject: Re: [multipsk] Multipsk stopped working after upgrad

 

Hi Patrick,

 

Sorry, I can confirm the RTL-dongle works OK with VDL2, it is while using the RSP1 or RSP2 that the problem occurs. The attached images show the received signal with v43.9.2 and v43.9.3 the v43.9.3 just shows a constant vertical red line in the centre of the display. The earlier v43.9.2 works fine.

 

 

 

Regards, Mike Simpson

South Penrith, NSW, Australia

 

 

Attachments:

 


Image removed by sender. Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com

 


Re: Multipsk stopped working after upgrad

Dennis Schendel
 

Hello Patrick,

 

Thank you very much for your quick response, analysis and fixes to the issues reported. The MultiPSK 4.39.4 TEST 1 VERSION is working much better with both the RTL-SDR.COM V3 dongle and SDRPlay RSP1A device.

 

I did a fair amount of test sequences in an attempt to identify some of the anomalies I was experiencing, primarily when switching between VDL2 and ADS-B modes and frequencies. While working on this I finally realized that the VFO-x buttons also store the Modulation selection settings for the last frequency setting loaded in it. So that oversight had led to some of the issues that I observed where the Modulations settings were “unexpectedly” changing when the frequency was changed.

 

I realized that when using preloaded VFO-x buttons to change the frequencies to switch between the VDL2 and ADS-B modes (or other modes for that matter), I needed to select the appropriate VFO first/before changing the Mode. This has helped avoid some of the unpredicted Modulation setting combinations that I encountered before.

 

However, there still remains some situation (sequence of changes) where the Modulations settings are still being set to unexpected settings. This seems to be more prevalent when switching into the ADS-B mode where the USB Modulations setting is occasionally being selected. I will continue to investigate this as I have time. But for now, it is quite easy to work around.

 

Also, I know there is still is a sequence/combination of steps/changes that will throw the MultiPSK application into an endless error message cycle. It has only happened very occasionally and the sequence to reproduce it is still a mystery and not nailed down. I will let you know if I figure out the right combinations to cause it.

 

Thank you again!

 

73

Dennis

 

 

From: multipsk@groups.io [mailto:multipsk@groups.io] On Behalf Of Patrick Lindecker
Sent: Thursday, July 04, 2019 10:50
To: multipsk@groups.io
Subject: Re: [multipsk] Multipsk stopped working after upgrad

 

Hello Dennis,

 

>In the following screenshot, the lower/narrower waterfall portion is an FM station, and when I change the frequency to 1090 MHz I still >hear the FM station but the waterfall shows the upper/wider waterfall image.

You are right. It is a regression bug following the SDRplay addition. Now fixed.

 

>As shown below, USB is enabled and selected when it should be PPM that is enabled and selected.

I agree, it is not normal, but I have not been able to reproduce this. I have always “PPM” when I switch to ADS-B… Do you remember how do you get this?

 

>In addition, with V4.39.3 and the RTL-dongle, sometimes when I change the receive Frequency, I will get endless error messages like this:

I have never seen this (and it seems independent from the 4.39.3 version). It will be to confirm in the next version (4.39.4).

 

>And after I finally get the MultiPSK instance/session shutdown/terminated ... then the next time I start MultiPSK, I might get a message like this:

It means that due some unknown error, the mode and the modulation managed to the SDR VFO B have been altered, and they have been replaced by default parameters: i.e. here BPSK31 and USB. Surely due to the forced shutdown. Seeing this is not a problem. It’s just an information that some parameters have been altered and that the system returns to default parameters for few ones.

 

>After clicking OK ... it may come up just fine or it might go into the endless error messages again ... especially if it is in “Open RX/TX screen after start up” ... which it will sometimes switch to on its own.

I never have experimented this.  Perhaps a consequence of the forced stop.

 

>BTW: I do have an SDRPlay RSP1A device. When trying to use it, on the Configuration settings window, I have found out that the “RTL >key/DLL” button and the “SDRplay” button can both be in the enabled/depressed position at the same time.

You are right. I fixed this.

Note: however it is not a professional program and all possibilities of errors by the user are directly be addressed. For example, if you click on a first interface and if, during the connection with the first one, you select another interface, the result is uncertain…

 

TKS for the remarks.

 

73

Patrick

 

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Dennis Schendel via Groups.Io
Envoyé : mercredi 3 juillet 2019 11:49
À : multipsk@groups.io
Objet : Re: [multipsk] Multipsk stopped working after upgrad

 

Hi Patrick,

 

I have also been having a similar problems/issues as Mike with the RTL-dongle (V3) when using MultiPSK v4.39.3. (The original V4.39, before SDRplay was added worked well.) Wasn’t sure at first if it was unique to me, but now that others seem to be experiencing similar issues it’s time to submit what I am seeing.

 

Here are a couple more twists I have observed with the latest version of MultiPSK when switching between different modes and frequencies ... for example, between the VDL2, ADS-B and FM/RDS modes and their corresponding frequencies.

 

When using a RTL.SDR.COM dongle (e.g. V3), I have found that when I change the receive Frequency in the transceiver window (via either VFO-A/B or Other frequencies or the QRGs), the frequency displayed changes but it is not actually being changed in the RTL-dongle. (This is most observable when changing from a FM station to different mode frequency ... I am still hearing/receiving the original FM station.) In the following screenshot, the lower/narrower waterfall portion is an FM station, and when I change the frequency to 1090 MHz I still hear the FM station but the waterfall shows the upper/wider waterfall image.

 

 

Then, when I change the mode to ADS-B to receive the digital ADS-B transmission on 1090 MHz ... the presets for the Modulations buttons at the bottom of the transceiver window don’t always show and/or get set correctly. As shown below, USB is enabled and selected when it should be PPM that is enabled and selected. (BTW: This kind of thing happens with some of the other Modes as well. And it has been happening on older versions of MultiPSK.)

 

 

From what I have seen in the past, isn’t this what it is supposed to look like for ADS-B mode?:

 

 

In addition, with V4.39.3 and the RTL-dongle, sometimes when I change the receive Frequency, I will get endless error messages like this:

 

 

And after I finally get the MultiPSK instance/session shutdown/terminated ... then the next time I start MultiPSK, I might get a message like this:

 

After clicking OK ... it may come up just fine or it might go into the endless error messages again ... especially if it is in “Open RX/TX screen after start up” ... which it will sometimes switch to on its own.

 

I am experiencing similar problems/issues when I try to switch to VDL2 or FM mode on an associated frequency such as 136.975 MHz, etc.

 

NOTE: The only way I can consistently get MultiPSK v4.39.3 to start and run as it should is to pre-set the Mode and corresponding Frequency and the shut MultiPSK completely down (terminated) And when it is restarted, it will come up and run correctly (until I change something as described above).

 

 

BTW: I do have an SDRPlay RSP1A device. When trying to use it, on the Configuration settings window, I have found out that the “RTL key/DLL” button and the “SDRplay” button can both be in the enabled/depressed position at the same time.

 

I don’t expect that was intended to happen or be allowed.

 

And when the “RX/TX screen” button is clicked, that causes the following endless error messages to occur:

 

 

I can get the SDRPlay RSP1A device to work by pre-setting everything and then doing the full restart of the MultiPSK v4.39.3 application. But after that, changing any of the settings, especially the receive Frequency will put things into the endless error messages condition again.

 

Hope this helps identify and isolate some of the issues.

 

Regards,

Dennis

 

From: multipsk@groups.io [mailto:multipsk@groups.io] On Behalf Of MadMike
Sent: Tuesday, July 02, 2019 17:14
To: multipsk@groups.io
Subject: Re: [multipsk] Multipsk stopped working after upgrad

 

Hi Patrick,

 

Sorry, I can confirm the RTL-dongle works OK with VDL2, it is while using the RSP1 or RSP2 that the problem occurs. The attached images show the received signal with v43.9.2 and v43.9.3 the v43.9.3 just shows a constant vertical red line in the centre of the display. The earlier v43.9.2 works fine.

 

 

 

Regards, Mike Simpson

South Penrith, NSW, Australia

 

 

Attachments:

 


Image removed by sender. Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com



2841 - 2860 of 4916