Date   
Re: EGC decoding improvement - Multipsk test version 6

Patrick Lindecker
 

Hello Paul,

 

>One question, if I press the "urgencies with positions" button the map opens ok, up but within that map window if I press the Goggle Earth. In fact, I forgot this panel which is not related to the EGC needs. There is no interest to open GE as the position is very approximate (one degree of accuracy). I will hide the majority of the buttons of this panel. Thanks for the remark.

 

At the moment, I know that there was a bug on these positions (bug fixed now in my local version). I wil propose a test version 7 (the last I hope).

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Paul Gulliver
Envoyé : samedi 15 juin 2019 18:20
À : multipsk@groups.io
Objet : Re: [multipsk] EGC decoding improvement - Multipsk test version 6

 

Hi Patrick.

 

I've been running test ver 6 for a few hours on 4A-F4 and all seems fine, no unknown messages.

One question, if I press the "urgencies with positions" button the map opens ok, up but within that map window if I press the Goggle Earth button nothing happens - I do have GE installed on the computer. Does GE only open if there is a position to display or should it open regardless?

 

Cheers

 

Paul

 

On 14/06/2019 at 21:14, Patrick Lindecker <f6cte@...> wrote:

Hello to all,

 

Here is the Multipsk test version 6 which improves EGC decoding : http://f6cte.free.fr/MULTIPSK_4_39_1_test_version_6.zip

 

Paste this address in your Internet Explorer or equivalent. Download the file.
First, make a copy of the your Multipsk folder, in case of…

Extract the Multipsk.exe file (+ manual files + files for interfaces) and replace the “official” Multipsk.exe (+ manual files) with these test version files.

 

This test version decodes BD/BE messages and reassembles them (apparently always in messages packets B1 or B2). All the unknown messages EGC are decoded except the “85” one which remains a mystery.

 

I added a packet selection “Urgencies with position” but I did not decode Urgencies messages so I have not been able to test this function: display of the urgencies messages with indication of the position on the world map (with a red dash). So thanks for reports about this function.

 

I added, for information, the number of the decoded frame (there is a new one each 8.64 s).

 

The EGC frequencies are:

4-F3 EGC 1537.7000

3-F5 EGC 1541.4500 

4-F1 EGC 1541.4500

4A-F4 EGC 1537.1000 

 

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: EGC decoding improvement - Multipsk test version 6

Paul Gulliver
 

Hi Patrick.

I've been running test ver 6 for a few hours on 4A-F4 and all seems fine, no unknown messages.
One question, if I press the "urgencies with positions" button the map opens ok, up but within that map window if I press the Goggle Earth button nothing happens - I do have GE installed on the computer. Does GE only open if there is a position to display or should it open regardless?

Cheers

Paul


On 14/06/2019 at 21:14, Patrick Lindecker <f6cte@...> wrote:

Hello to all,

 

Here is the Multipsk test version 6 which improves EGC decoding : http://f6cte.free.fr/MULTIPSK_4_39_1_test_version_6.zip

 

Paste this address in your Internet Explorer or equivalent. Download the file.
First, make a copy of the your Multipsk folder, in case of…

Extract the Multipsk.exe file (+ manual files + files for interfaces) and replace the “official” Multipsk.exe (+ manual files) with these test version files.

 

This test version decodes BD/BE messages and reassembles them (apparently always in messages packets B1 or B2). All the unknown messages EGC are decoded except the “85” one which remains a mystery.

 

I added a packet selection “Urgencies with position” but I did not decode Urgencies messages so I have not been able to test this function: display of the urgencies messages with indication of the position on the world map (with a red dash). So thanks for reports about this function.

 

I added, for information, the number of the decoded frame (there is a new one each 8.64 s).

 

The EGC frequencies are:

4-F3 EGC 1537.7000

3-F5 EGC 1541.4500 

4-F1 EGC 1541.4500

4A-F4 EGC 1537.1000 

 

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: EGC decoding improvement - Multipsk test version 6

Patrick Lindecker
 

Hello Fred,

 

>TV6 installed and working nicely.  Thank you,
Nice, but it is not the final version as I just see that the Urgencies function does not work (I just received  an Urgency message and the boat in difficulties is shown in plain Finland…).

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Fred Albertson
Envoyé : samedi 15 juin 2019 00:11
À : multipsk@groups.io
Objet : Re: [multipsk] EGC decoding improvement - Multipsk test version 6

 

Hi Patrick,

TV6 installed and working nicely.  Thank you,

Fred




Avast logo

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


Re: EGC decoding improvement - Multipsk test version 6

Fred Albertson
 

Hi Patrick,

TV6 installed and working nicely.  Thank you,

Fred

EGC decoding improvement - Multipsk test version 6

Patrick Lindecker
 

Hello to all,

 

Here is the Multipsk test version 6 which improves EGC decoding : http://f6cte.free.fr/MULTIPSK_4_39_1_test_version_6.zip

 

Paste this address in your Internet Explorer or equivalent. Download the file.
First, make a copy of the your Multipsk folder, in case of…

Extract the Multipsk.exe file (+ manual files + files for interfaces) and replace the “official” Multipsk.exe (+ manual files) with these test version files.

 

This test version decodes BD/BE messages and reassembles them (apparently always in messages packets B1 or B2). All the unknown messages EGC are decoded except the “85” one which remains a mystery.

 

I added a packet selection “Urgencies with position” but I did not decode Urgencies messages so I have not been able to test this function: display of the urgencies messages with indication of the position on the world map (with a red dash). So thanks for reports about this function.

 

I added, for information, the number of the decoded frame (there is a new one each 8.64 s).

 

The EGC frequencies are:

4-F3 EGC 1537.7000

3-F5 EGC 1541.4500 

4-F1 EGC 1541.4500

4A-F4 EGC 1537.1000 

 

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: Multipsk vs Display Launcher

Operarore1426
 

Hi Mario, 
Thanks so much for informations
I'll try 
73's Maurizio 

Re: Multipsk vs Display Launcher

Patrick Lindecker
 

Hello Mario,

 

The first line of characters are here without meaning but I can’t know if the data has a meaning or not. So the data are displayed in Hexa and in ASCII/ANSI, the user will see if it is text or not.

 

For the second it is  _+CHR(127) (the meaning follows)

 

>I wanted to ask you which buttons to keep pressed in the "Frames Display" field, I keep pressed the I/UI and XID buttons.

It’s up to you. Look at the hint associated with each button (stay with the mouse one second over each one)

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de MarioLuciano
Envoyé : mercredi 12 juin 2019 12:55
À : multipsk@groups.io
Objet : Re: [multipsk] Multipsk vs Display Launcher

 

Hi Patrick, very kind of you.

I discovered it after many attempts with Display Launcher. Now it looks like all Launcher Display modules are working properly. Patrick, I wanted to ask you a question: when I decode signals in VDL2, strange characters are recorded in the Multipsk QSO file, especially in the "Message type" field, and then Display Launcher interprets them incorrectly. I wanted to ask you which buttons to keep pressed in the "Frames Display" field, I keep pressed the I/UI and XID buttons. I'll attach a screenshot of the QSO file. Thank you and see you soon.

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


Re: Multipsk vs Display Launcher

MarioLuciano
 

Hi Patrick, very kind of you.

I discovered it after many attempts with Display Launcher. Now it looks like all Launcher Display modules are working properly. Patrick, I wanted to ask you a question: when I decode signals in VDL2, strange characters are recorded in the Multipsk QSO file, especially in the "Message type" field, and then Display Launcher interprets them incorrectly. I wanted to ask you which buttons to keep pressed in the "Frames Display" field, I keep pressed the I/UI and XID buttons. I'll attach a screenshot of the QSO file. Thank you and see you soon.

73

Mario

Re: Multipsk vs Display Launcher

MarioLuciano
 

Hi Maurizio, the Multipsk settings are those indicated in the Display Launcher Help and are:

1) For Multipsk: set the GMDSS/ATIS mode, the frequency is one of those indicated in the context help of Multipsk, and then set the backup time by going to "QSO -> Regular Backup -> and putting 20 seconds through the buttons with the arrow symbol. Then press the Return button and return to the RX-TX screen. Put the listening frequency in the upper left box otherwise the QSO file is a wrong report, do not activate the zero button crossed out in the lower left, AGC and AFC I leave them active and at this point you should be able to decode the various messages of the ships. Now start Display Launcher.

2) In Display Launcher select GMDSS Display mode, when you start the screen where there will be then the grid where the listens will be reported, press the Options button and select the path to the QSO file of Mutipsk, confirm it and you will return again to the screen where there is the grid. Now press the Start button of Display Launcher and you should see the various messages received from the Multipsk appear.

73's Mario

Re: Multipsk vs Display Launcher

agene
 

Hi Mario (and others),

I have checked the code in Display-Launcher, and the only module in the 'European' version of Display-Launcher which did not correctly handle the character "Ø" in Display-Launcher is the Aero-Display module, all the others automatically converted 'Ø' to '0' . I have modified AERO_Display.exe to do the same. You can download it from

Please note that Display-Launcher only works with the English language version of MultiPSK, it does not work with the French or Spanish language versions except for HFDL-Display which does have the option to handle the French version of MultiPSK.

Regards, Mike Simpson
South Penrith, NSW, Australia


Re: Multipsk vs Display Launcher

Patrick Lindecker
 

Hello Mario,

 

>the number 0 is set as crossed out (Ø)

Of course, you can cancel the transformation of “0” to “Ø” by extracting the button “Ø” (at least when you use Display Launcher).

 

73

Patrick

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de MarioLuciano
Envoyé : dimanche 9 juin 2019 12:33
À : multipsk@groups.io
Objet : [multipsk] Multipsk vs Display Launcher

 

Hi all,

I am an Italian SWL (IZ1067SWL) and always follow with great interest the discussions of this group. I wanted to report an anomaly between the Display Launcher software and the Multipsk software: if in the Multipsk reports (QSO file) the number 0 is set as crossed out (Ø) the Display Launcher software does not read the QSO file of Mutipsk, and does not even update in real time. Maybe it was already reported, but I couldn't find it. I hope I've been useful.

Mario

P.S. sorry if my English translation is imprecise, but I know little about English and have translated everything with an online translator.

My equipment:

S.O. Windows 7 64 bit
Radio: ICOM IC-R8600
Antenna: Wellbrook ALA 1530 S+
Software: Multipsk vers.4.39 and Display Launcher European version




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 vs Display Launcher

Operarore1426
 

Thanks for the useful information.
How did you set MultiPSK and Display Launcher? Thank you
 
I also use the translator to do fast.

73's Maurizio

Multipsk vs Display Launcher

MarioLuciano
 

Hello, everyone,
I am an Italian SWL (IZ1067SWL) and always follow with great interest the discussions of this group. I wanted to report an anomaly between the Display Launcher software and the Multipsk software: if in the Multipsk reports (QSO file) the number 0 is set as crossed out (Ø) the Display Launcher software does not read the QSO file of Mutipsk, and does not even update in real time. Maybe it was already reported, but I couldn't find it. I hope I've been useful.
Mario

P.S. sorry if my English translation is imprecise, but I know little about English and have translated everything with an online translator.

My equipment:

S.O. Windows 7 64 bit
Radio: ICOM IC-R8600
Antenna: Wellbrook ALA1530 S+
Software used: Multipsak vers.4.39 and Display Launcher European version

Re: MultiPSK and DISPLAY LAUNCHER #aero

Operarore1426
 

Hi, Patrick,
I did that. On Display lancher instead I have to select the MultiPSK patch with the right QSO folder?


Il giorno dom 9 giu 2019 alle ore 23:34 Patrick Lindecker <f6cte@...> ha scritto:

Maurizio,

 

There is no more that what was said by Mike:

 

In MultiPSK, click on the QSO button and click 'Regular back-up' in the bottom left corner and set the time there to 20 sec.

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Operarore1426
Envoyé : dimanche 9 juin 2019 23:19
À : multipsk@groups.io
Objet : Re: [multipsk] MultiPSK and DISPLAY LAUNCHER #aero

 

Hi Patrik

thanks a lot for informations

What parameters and where should I put them on MultiPSK to get the data back to Display Luncher?

Regard, Maurizio

 

 

 

Il giorno dom 9 giu 2019 alle ore 23:10 Patrick Lindecker <f6cte@...> ha scritto:

Hello Paul and Mauricio,

 

As said by Mike, the TCP/IP link is no more used, so there is no link between Multipsk and Display-Launcher. Display-Launcher uses the QSO files.

 

73

patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Paul Gulliver
Envoyé : dimanche 9 juin 2019 19:53
À : multipsk@groups.io
Objet : Re: [multipsk] MultiPSK and DISPLAY LAUNCHER #aero

 

Sorry, I mis-understood, I thought you had Multipsk working and decoding but unable to link to Display Launcher.

 

Perhaps Patrick will come up and help you

 

Paul

 

On 09/06/2019 at 18:37, Operarore1426 <operatore1426@...> wrote:

I'm trying. I reinstall the program and try again. From MultiPSK no TCP port? I enclose the MultiPSK setup
Regards, Maurizio

 

 


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 and DISPLAY LAUNCHER #aero

Operarore1426
 

Thanks for the valuable information. I reinstall it as told by you.
Good listening
73's Maurizio

Il giorno lun 10 giu 2019 alle ore 01:51 MadMike <virtualtrains@...> ha scritto:
Hi Maurizio,

1. Display-Launcher should NOT be installed in c:\program files (x86) - due to Windows 10 security features, some options in Display-Launcher will not work if in that folder. I suggest you place it somewhere like C:\Radio Utilities\Display-Launcher

2. Your options file paths should only show paths to MultiPSK\QSO folders. Do not include the Display launcher paths in the file paths.



Regards, Mike Simpson
South Penrith, NSW, Australia


Re: MultiPSK and DISPLAY LAUNCHER #aero

agene
 

Hi Maurizio,

1. Display-Launcher should NOT be installed in c:\program files (x86) - due to Windows 10 security features, some options in Display-Launcher will not work if in that folder. I suggest you place it somewhere like C:\Radio Utilities\Display-Launcher

2. Your options file paths should only show paths to MultiPSK\QSO folders. Do not include the Display launcher paths in the file paths.



Regards, Mike Simpson
South Penrith, NSW, Australia


Re: MultiPSK and DISPLAY LAUNCHER #aero

Patrick Lindecker
 

Maurizio,

 

There is no more that what was said by Mike:

 

In MultiPSK, click on the QSO button and click 'Regular back-up' in the bottom left corner and set the time there to 20 sec.

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Operarore1426
Envoyé : dimanche 9 juin 2019 23:19
À : multipsk@groups.io
Objet : Re: [multipsk] MultiPSK and DISPLAY LAUNCHER #aero

 

Hi Patrik

thanks a lot for informations

What parameters and where should I put them on MultiPSK to get the data back to Display Luncher?

Regard, Maurizio

 

 

 

Il giorno dom 9 giu 2019 alle ore 23:10 Patrick Lindecker <f6cte@...> ha scritto:

Hello Paul and Mauricio,

 

As said by Mike, the TCP/IP link is no more used, so there is no link between Multipsk and Display-Launcher. Display-Launcher uses the QSO files.

 

73

patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Paul Gulliver
Envoyé : dimanche 9 juin 2019 19:53
À : multipsk@groups.io
Objet : Re: [multipsk] MultiPSK and DISPLAY LAUNCHER #aero

 

Sorry, I mis-understood, I thought you had Multipsk working and decoding but unable to link to Display Launcher.

 

Perhaps Patrick will come up and help you

 

Paul

 

On 09/06/2019 at 18:37, Operarore1426 <operatore1426@...> wrote:

I'm trying. I reinstall the program and try again. From MultiPSK no TCP port? I enclose the MultiPSK setup
Regards, Maurizio

 

 


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 and DISPLAY LAUNCHER #aero

Operarore1426
 

Hi Patrik
thanks a lot for informations
What parameters and where should I put them on MultiPSK to get the data back to Display Luncher?
Regard, Maurizio



Il giorno dom 9 giu 2019 alle ore 23:10 Patrick Lindecker <f6cte@...> ha scritto:

Hello Paul and Mauricio,

 

As said by Mike, the TCP/IP link is no more used, so there is no link between Multipsk and Display-Launcher. Display-Launcher uses the QSO files.

 

73

patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Paul Gulliver
Envoyé : dimanche 9 juin 2019 19:53
À : multipsk@groups.io
Objet : Re: [multipsk] MultiPSK and DISPLAY LAUNCHER #aero

 

Sorry, I mis-understood, I thought you had Multipsk working and decoding but unable to link to Display Launcher.

 

Perhaps Patrick will come up and help you

 

Paul

 

On 09/06/2019 at 18:37, Operarore1426 <operatore1426@...> wrote:

I'm trying. I reinstall the program and try again. From MultiPSK no TCP port? I enclose the MultiPSK setup
Regards, Maurizio

 




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 and DISPLAY LAUNCHER #aero

Patrick Lindecker
 

Hello Paul and Mauricio,

 

As said by Mike, the TCP/IP link is no more used, so there is no link between Multipsk and Display-Launcher. Display-Launcher uses the QSO files.

 

73

patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Paul Gulliver
Envoyé : dimanche 9 juin 2019 19:53
À : multipsk@groups.io
Objet : Re: [multipsk] MultiPSK and DISPLAY LAUNCHER #aero

 

Sorry, I mis-understood, I thought you had Multipsk working and decoding but unable to link to Display Launcher.

 

Perhaps Patrick will come up and help you

 

Paul

 

On 09/06/2019 at 18:37, Operarore1426 <operatore1426@...> wrote:

I'm trying. I reinstall the program and try again. From MultiPSK no TCP port? I enclose the MultiPSK setup
Regards, Maurizio

 




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 and DISPLAY LAUNCHER #aero

Operarore1426
 

On Sun, Jun 9, 2019 at 07:52 PM, Paul Gulliver wrote:
Perhaps Patrick will come up and help you
Ok Thanks a lot Paul