CoMoMap: Yet another navigation software (V1.3.2)

[Bre901]

Version V1.1 of CoMoMap is available at https://condorutill.fr/index_fr.php
Main new feature: display of other gliders if cunimb is enabled on the server
A number of instabilities have been fixed
For more information, see the file CoMoMap_README.txt

[Bre901]

Some users have asked me how to configure VSPE if one one wants to use both CoMoMap and another app (eg. XCSoar or LK8000)

For that you will need a port splitter.
The "splitted" port (COM8 in the pic below) may be shared by CoMoMap and other app(s)

Splitter_EN_crop.jpg (34.49 KiB) Viewed 1009 times

Hint : in the Splitter creation window, the Source (COM7 here) is on the right and the destination (COM8) on the left

The manual has been updated accordingly, it is available on the website.
No need to reinstall CoMoMap, click on the "More..." link to access the CoMoMap page

[h.kreso]

Hi,
I try to run the program but it just closes after the NMEA counter. Debug log attached

[Bre901]

Version 1.2 is available from my webpage: https://condorutill.fr/index.php

Many thanks to the beta-testers

As usual taking a look at the manual is more than recommended

New features:
- Finish line (180° and 360°) and 360° sector TPs : optimised target point (display and calculations)
- Cunimb: hide tracks in thermal mode view (optional)
- Keyboard hook periodical restart (optional)
- Glider data auto update (optional)
- Total energy available now computed according to best GR speed at current W/L
- More VR friendly

Bug fixes:
- Detection of window-type start sector
- DDH: incorrect value after next TP
- some more instabilities fixed (hopefully including the problem mentioned in the post above above)

[Bre901]

A user has encountered problems with the Podkarpackie landscape: CoMoMap crashes on startup

The problem does not come from CoMoMap but from the landscape, more precisely from the RUZSOMBEROK coordinates in the .apt file
41 RAZNANY 49.0769005 21.0995007
42 RUZSOMBEROK 49.0852661 19368260.0
The dot (decimal separator) was probably forgotten when entering the data.

The new version of CoMoMap (1.2.0.3) which manages incorrect coordinates is available

It's not essential to download it, unless you want to fly Podkarpacie (or another equally good landscape) before the landscape is corrected (I've contacted the landscape creator).

[h.kreso]

I acknowledge the error, I had to use XCSoar again yesterday. The program did not crash, it was just that there was no landscape

[sasa]

Is it possible to use CoMoMap on a laptop that does not have Condor installed, in a similar way as we use other glider computer applications (XCSoar, TopHat, LK8000, ...) ?

[Bre901]

I guess it would be possible if you manage to forward a COM port to the other PC

For the UDP port, it should work seamlessly as Condor (or CoTASA) support forwarding to another IP address

[sasa]

In order for CoMoMap to work, in addition to COM and UDP port redirection, is it necessary to copy something else from Condor (eg .trn files, maps, ...)?
If it needs to be copied, where should it be put?

[Bre901]

CoMoMap has been designed to run on the same PC as Condor, I'm not sure it will work on another PC and I'm sorry I have no time to experiment with that.

It requires some workarounds, including setting a registry key. If you are not comfortable with regedit, be careful !

You should try the following:

Theoretically you could specify the path to the Condor root folder on the Condor PC in the .ini file if it is shared on the local network but I'm not sure this works

Alternatively I would recommend creating a dummy Condor installation on the CoMoMap PC with a Landscapes folder containing the desired landscape folder(s) in which you copy the .trn file(s) and .bmp map(s), then specify the path to the (dummy) Condor root folder in the .ini file

If this doesn't work, start Regedit and add a registry key: HKEY_CURRENT_USER\SOFTWARE\Condor2\InstallDir, value=the path to the dummy Condor installation folder

You will also need to specifiy the current flightplan, the easiest way is to disable Wait in the .ini file and start CoMoMap from a command prompt window with the name of the flightplan on the command line:
> CoMoMap PATH_TO_MY_FLIGHTPLAN.fpl

Or, if the flight plan file is always the same, create a shortcut with the same syntax

Hope this helps

[kalorama]

I tried this and it worked a few times, but now I routinely get a message popping up in condor (at start of flight) that NEMA could not be initialized. Any thoughts?

Geoffrey

[Bre901]

I tried this and it worked a few times, but now I routinely get a message popping up in condor (at start of flight) that NEMA could not be initialized. Any thoughts?

Geoffrey

Is it systematic ?
I also get that message from time to time with CoMoMap running on the same PC, using VSPE as a COM port emulator

[kalorama]

It does seem to be systematic. Once it started happening I stopped being able to use CoMoMap -- rebooting didn't help.
Geoffrey

[BONANZA3188]

Tuto pour COMOMAP en réseau sur un 2eme PC
Il s'agit d'envoyer, vers un deuxième PC, par le réseau Ethernet, les données Condor (port COM NMEA et Port UDP infos) exploitées par le logiciel COMOMAP
Procédure :
Sur le PC CONDOR :
- Sans COTASA :
CONDOR envoie les données du vol par ETHERNET sur le port UDP 55278
- Avec COTASA actif, COTASA utilise le port 55278 et le renvoie sur le port 55279 à mettre dans le fichier :
C:\Users\Michel\Documents\CoTASA\Settings\CoTASA.ini
voici les lignes concernées :
# UDP port to listen to (Condor default is 55278)
Port=55278
# UDP Port forwarding (default= none)
Forward Port=55279
# UDP Port forwarding IP address (default : 127.0.0.1 = localhost)
Forward Address=192.168.1.202 #(adresse IP du 2eme PC à mettre ici)

vérifier que le fichier C:\Condor2\Settings\UDP.ini comporte ceci :
[General]
Enabled=1
[Connection]
Host=127.0.0.1
Port=55278
[Misc]
SendIntervalMs=25
ExtendedData=0
ExtendedData1=1
LogToFile=0

CONDOR envoie les positions du planeur sur un port COM indiqué dans le setup de Condor onglet option case cochée et port COM, celui mis dans VSPE à voir ci-après.

VSPE est un logiciel gratuit qui permet de créer des ports COM virtuels et de les partager ou de faire des passerelles TCP ou UDP.
sur le PC CONDOR :
Charger VSPE : https://eterlogic.com/Downloads.html et l'installer.
Faire un port COM virtuel partagé, pour cela, faire une paire (fonction "Pair") avec un port com existant ou faire un nouveau (fonction "Connector"),
puis faire un splitter pour créer un port partagé
puis faire un envoie des données du port com via TCPserver. (Sauvegarder cette config dans un fichier de nom "VSPE" avec le menu VSPE "File" "Save as").

Comomap utilise les fichiers Logfile.txt et Flightplan.fpl de Condor, il faut donc les copier sur le 2eme PC après que CONDOR ait démarré :
Partager, sur le 2eme PC les répertoires ou sont ces fichiers, exemple :
\\MICHEL-PC2\Condor2\Logs répertoire à créer pour le pour le fichier Logfile.txt et
\\MICHEL-PC2\Users\Michel2\Documents\Condor\Pilots\Bigand_Michel-BI répertoire à créer pour le fichier Flightplan.fpl

faire un fichier "comomap reseau.bat" contenant :
copy C:\Condor2\Logs\Logfile.txt \\MICHEL-PC2\Condor2\Logs\Logfile.txt
copy C:\Users\Michel\Documents\Condor\Pilots\Bigand_Michel-BI\Flightplan.fpl \\MICHEL-PC2\Users\Michel2\Documents\Condor\Pilots\Bigand_Michel-BI\Flightplan.fpl

Il faut l'executer après que CONDOR soit démarré, en vol ou au sol.

Sur le deuxième PC :
La réception des données Condor en UDP 55279 qui arrivent par réseau Ethernet, sont exploitées par COMOMAP directement
La réception des positions Condor sont converties de TCP en port com local.
Il faut que les deux PC communiquent, qu'ils soient dans le même réseau avec accès de l'un à l'autre pour les flux Ethernet et pour le partage de répertoires.
Installer COMOMAP dans le répertoire "Mes Documents"
Installer et lancer VSPE et
faire un nouveau port COM virtuel (fonction "Connector"),
puis faire une réception des données TCP vers un port com via TCPclient. (Sauvegarder cette config dans un fichier de nom "VSPE" avec le menu VSPE "File" "Save as")

dans le fichier de config COMOMAP (comomap.ini dans le répertoire COMOMAP sur le 2eme PC, il faut mettre le numéro de port UDP en réception :
# UDP port to listen to (Condor default is 55278)
Port=55279
# UDP Port forwarding (default= none)
Forward Port=
# UDP Port forwarding IP address (default : 127.0.0.1 = localhost)
Forward Address=

C'est tout pour la configuration.

Pour l'utilisation :
Sur le PC Condor :
1 - Lancer VSPE sur le PC Condor
2 - Lancer COTASA si besoin
3 - Lancer Condor jusqu'au menu breefing "Flight planner"

Sur le 2eme PC :
1 - Lancer VSPE
2 - Lancer COMOMAP
3 - Lancer la simulation Condor par "Start flight"
Ne rien faire pendant que CONDOR se lance. Dès qu'on est dans le planeur,
sur le PC Condor :
lancer l'utilitaire que vous avez créé "comomap reseau.bat"

Enjoy
Michel 188

[Bre901]

As I was a bit in a hurry to finalise the manual for the release of version 1.3, I haven't described some new options which may improve performance:

1 - If you are using Condor 3 and have enough memory, you may safely increase Airspace_mem_size to 256 MB or even higher, this will increase memory usage and pre-computing time but performance will be improved

2 - CoMoMap now supports local grid refinement (finer grid closer to the glider)
recommended grid settings are:
Grid_size=1
Max_Grid_size=3
Local_Grid_refining=1

I would recommend experimenting a bit with those settings before using them in a competition on which your (Condor) life depends