probleme twonav Cross version 5.3
-
Bonjour,
J'ai un twonav cross première version et je constate beaucoup de défauts comparativement à mon anima+ (moindre sensibilité, positionnement très fluctuant à l'arrêt...)
Surtout lorsque je fais une randonnée, le totalisateur est toujours faux alors que lorsque je regarde le fichier gpx tracklog il est assez près de la vérité.
exemple:
aujourdhui randonnée 8.2km
sur anima+ (ma référence) : 8,196km 141 denivelé
su cross lorsque je regarde l'activité du jour : 6,369 km 125 de dénivelé
sur le fichier tracklog téléchargé dans land du cross : 8.3km 142m de dénivelé.
Merci de me dire si je fais une mauvaise utilisation du cross.
-
Le problème que je rencontre ne se situe pas sur le fichier dans le dossier tracklog mais bien sur l'affichage dans le gps (sur mes activités enregistrées) et sur l'affichage lorsque je marche avec une route pré-tracée . La distance n'est pas correcte et toujours inférieure à la réalité (dans ce cas 6,39km alors que la réalité est 8.3km)
Lorsque je télécharge le fichier enregistré (2023-01-03-134916.....trk) dans le PC avec LAND les valeurs sont bonnes (8.3km) et identiques à celui enregistré sur anima+.
J'en déduis donc qu'il y a un bug dans le logiciel. -
Strange, mine is working fine (Cross SW 5.3). My guess you choose the wrong field definition (2D versus 3D). Need to see your gps*.ini file for the activity to check it further.
PS: Writing in English since my French is nonexistent and google often changes the translation.
-
"J'en déduis donc qu'il y a un bug dans le logiciel."
Non, sans doute pas, sinon, on aurait tous remarqué la même chose.
Très probablement, vous avez des réglages (les filtres, les seuils, ...) qui ne sont pas corrects dans le profil utilisé. Ou bien vous n'utilisez pas le bon profil peut-être ?
Cordialement,
-
Bonjour,
ci joint les fichiers écrans sur cross, pc avec land et le gps.ini
Si quelqu'un peut me dire d'ou vient l'erreur je suis preneur.
Merci par avance
[Registro]
Nom_Usuario=Market
DeviceId=6383-4DMD-CD4P-6947*35
[Directorios]
dir_fonts_extended2=/root/TwoNavData/AppData
Recorded_Tracks4=/root/TwoNavData/Data/Tracklog/
Temporal=/tmp/twonav//
SpeedCams=/root/TwoNavData/Radars/
CacheWebMaps=/tmp/twonav/cache/
IgnoreStoredMD5RemoteData=0
Maps2=/root/TwoNavData/Maps
Data=/root/TwoNavData/Data/
Maps4=/root/TwoNavData/Maps
Data3=/root/TwoNavData/Data/
Recorded_Tracks7=/root/TwoNavData/Data/Tracklog/
Temporal2=/tmp/twonav//
SpeedCams2=/root/TwoNavData/Radars/
CacheWebMaps3=/tmp/twonav/cache/
Maps6=/root/TwoNavData/Maps
Data4=/root/TwoNavData/Data/
Maps6*1=/root/TwoNavData/Maps
Temporal2*2=/tmp/twonav//
[General]
dir_go_amazon=/root/TwoNavData/Data/
IsANTPlus=1
num_idioma=2
GO_Amazon=0
MyTwoNavUser=yves.andre3@orange.fr
MyTwoNavPass=A04C51F72AFFE356C97641AB272D305E24DE5B697497AA7247D4A3D793347F3F
MyTwoNavToken=
MyTwoNavName=yves andre
dir_go_amazon2=/root/TwoNavData/Data/
ActivitiesDoneCounter=2
[TiempoReal]
SetDefaultProfiles4=0
Total_Odometer=701314.6875000000
Total_Odometro_B=701227.0625000000
Append_Odometros=0;701314.7;701227.1;0;0;481585.7;
CompassCalibration=-1262336.0,-2900512.0,961088.0,-47152.0,37344.0,-13040.0,0,0,0,
Edad_Piloto=71
Peso_Piloto=84
HRM_Rest_Piloto=60
LocalTimeBias=-3600
TracklogName=/root/TwoNavData/Data/Tracklog/2023-01-03_193544.trk
LastGPSPosition=A,45.73631331ºN,3.18891166ºE
Sea_Level_Pressure_INV=0.0009618746
Sea_Level_Pressure_INV_LastTime=03-JAN-2023 17:02:31
GpsMode=3
IsRoutingNow=
Journey_Identifier=7
Append_Altura_Maxima=0.0000000000
Append_Velocidad_Maxima=0.0000000000
Activated_Alarms=317,21,306,59,383,41,124,650,651,661,652,396,381,397,237,47,
Color_Lineas_Aux_MovingMap=0x0000FFFF
Profile=3
Modo_Altura_Grabacion=3
HRM_Manual_MaxRest=0
[Vistas]
SeeMe=1, 00000,20240628,
WifiNetworksList=1
Broadcast2=v1.1,1,30000,0,
Volumen_Mute=0
SeeMeDontAskAgainActivated=1
BrightnessAuto=1
Brightness=90
[GPRS]
M2M=v1.0,300000,1,m2m.orange.es,,,1,
[Graficas]
ParamX_Graficas=1
[Windows]
UIWindowsScale=2.0000000000
UIWindowsWidth=480
UIWindowsHeight=800
UIPageInitialSteps8=stepShowPageIdioma:never,stepConnectGps,stepConfigureConnectivity:never,stepShowWelcomePage:never,stepShowCompassCalibration:never
ScreenSaveBatsTimer=0
Vision_Nocturna=0
[Balizas]
Name_Active_WPT_File=Waypoints.wpt
[Mapa]
LastTime_Scan_forMaps=05-JAN-2023 13:08:32
Show_All_Maps=1
Scan_forMaps_NextTime=0
DrawMapsShadingRelief=1
[Files]
Recent=/root/TwoNavData/Data/Tracklog/TALLENDE1.trk,/root/TwoNavData/Maps/FranceTopo.imp,/root/TwoNavData/Data/Tracklog/2023-01-03_134916--TALLENDE.trk,/root/TwoNavData/Data/TALLENDE.gpx,/root/TwoNavData/Maps/Spain_OSM_21q2.vmap,/root/TwoNavData/Data/Lanzarote/circuit park.gpx,/root/TwoNavData/Data/lebroc.gpx,/root/TwoNavData/Maps/lan17.rmap,/root/TwoNavData/Maps/cournon.rmap,/root/TwoNavData/Data/ravel.gpx
Last_Maps=/root/TwoNavData/Maps/FranceTopo.imp
Last_Track=/root/TwoNavData/Data/Tracklog/TALLENDE1.trk
[Com]
ActivateGps=1
[Sensors]
SensorsList3=0*0,1,2070,0,50754,1,%
[ConnectDevices]
PeripheralActivated=0
DevicePaired=0
ShowNotifications=1
ShowNotification_LostCall=1
ShowNotification_SMS=1
[DEM]
Pintar_Grid_Todo__DEM=1
Pintar_Curvas_Nivel_DEM=1
Sombreado_Todo_DEM=0
Salto_Color_Todo_DEM=500.0000000000
[Navigation]
WifiActiveBeforeNavigating=0
[Coordenadas]
Modo_Grados_Min_Seg=2
[Keys]
ZoomOnPhysicalKeys=2
KeyPagePreviousShortPress=197.0
KeyPowerShortPress=551.0
KeyPageNextShortPress=193.0
KeyZoomInShortPress=-1.0
[3D]
Mode3Dbutton3=1
[Units]
Unidad_Distancia=0
[Colores]
Hypsometric_Colors=lowcontrast.hipcolrs
[Campos]
Colorear_2=6
[Tracks]
Navigated_Track_2Colors=1
Navigated_Track_Int_Color -
Hi to all! I have a similar situation. I tested using my Cross Plus 5.3 fw and Coros Vertih 2 watch. Coros was on my left hand, and Cross Plus was on my chest. Here are both gxp files. The one from Coros is the right one (because I know the route and used Garmin GPSMAP 66st to check earlier) and the one from Cross Plus is the problematic one. On Cross Plus I used GPS+Glonass satellite systems.
Regards Goran.
-
Hi, here it is
https://go.twonav.com/public/shared/2023-01-01-104349-trk-13382668/
Goran.
-
Hello,
Monday I did a hike where there is also a distance incident, I miss 2 km..
1 km after the start, I realized that the location accuracy was bad, which is not usual.
Looking at the status of the satellites, I noticed that the GPS was tracking more Glonass satellites and Gallileo, only one GPS Satellite, was being tracked which is not normal.
Following this observation, I reset the tracking of the satellites, the GPS returned to a situation of mainly tracking the satellites of the GPS constellation. Following this action, the accuracy which had slipped to 35 m for no apparent reason returned to 7 to 8 m.
Usually the accuracy is under 5 m.
Let's hope it's not a consequence of the conflict in Ukraine.
This did not happen again on the next activity in Trail mode, although the accuracy did not return below 5m
This is a case to follow.
Best regards
-
Hello,
On the image below two identical traces recorded one on Monday, the other on Tuesday.
Recorded during tests that I do, to understand the behavior of the GPS when following a complex road book, in this case there are 5 loops. So I follow strictly the same itinerary, the Road Book having been designed differently, I still have two tries to do.
On the first, the mileage count is wrong, 1.5 km are missing.
The question why?
One track was run in hiker mode and the other in runner mode, so the main difference is speed.
In hiking mode the speed is always relatively low, and according to the recording configuration the GPS considers that there is no more movement below a speed threshold and it forces the speed to 0 (There are many points in this type of trace which have zero speed)
I therefore compared the number of points at zero speed on the two recorded traces.
The GPS was held all the way, in the open air and the top of the screen towards the sky (the antenna is at the top), so the GPS can see the sky perfectly.
The hike was done at a brisk pace.
In the case of hiking, 365 records out of 2988 have zero speed, (12.2%)
In the case of the "race" only 8 points out of 1556 have zero speed (0.5%)
The difference in the number of recordings is explained by the configuration of the recording of the trace which is different between the two configurations.
The difference in distance is 14%, which supports the hypothesis that this difference in distance display is probably due to not taking into account points with zero speed.
Best Regards
-
Hi Thierry,
It was on my chest (in the pocket of my running backpack). Sometimes, it was upside down, and sometimes with Twonav description upwards. I run in a small forest. But my Coros watch track was perfect, and its antenna was much smaller than Cross Plus's. Regards, Goran.
-
Hi, Goran
I'm not saying the opposite, it seems that the CROSS has a weakness on this side (sensitivity).
Either you deal with this weakness or you have to get closer to the after-sales service.
Here in the user space the goal is to try to propose solutions.
All GPS providers, regardless, recommend keeping the GPS in view of the sky.
The signal received by the antenna of a GPS is extremely weak, it does not take much for it to lose contact.
On your second track it could not follow the satellites correctly there must have been a big mask "all the same", on the other hand on your first track it can be interesting to observe how many points were recorded at zero speed.
I also have a "watch" but the track of my Trail 2 is always more accurate than that of the watch.
CDLT
CDLT
-
I tried it with a track recorded on sunday and it recorded fine (7km, Walking). Land differed probably 100m, depending on the Land version I use.
Please upload the 2 differing tracks (Anima+&Cross) to let us have a look at it.
Regarding the gps*.ini:
I meant the inifile which is corresponding to the activity you used.
gps00.ini is the first activity ini file, gps003.ini ist the fourth activity ini file. Please delete your logindata und your serial from the gps.ini you uploaded here, since this could be used to hack you account:
MyTwoNavUser=
MyTwoNavPass=PS: I know there is a significant glitch in the trackrecording of the newer Twonav versions (4-5), which only affects activites with slow speed. Some filters like record every x seconds or every x meters are not reliable used by the device if the speed is under 6km/h (I think). This was reported to Twonav but I'm not sure if and when they will repair it. And without a look at your tracks I can't tell if this bug is related to yours. But the bug I'm writing about results in recording longer distances compared to tracks recorded with older versions.
Vous devez vous connecter pour laisser un commentaire.
Commentaires
20 commentaires