Communication with Al Lai, Wintec-TW

    Hi Jan,


    Yes this is exactly the same I was thinking about and another GPS have this funtion there you can see the actual track and are able to go back in that track if you need. No possibuilities to move cursor but the screen moves depending on your position.


    [Blockierte Grafik: http://se-bilder.se/tracker_back%20navigation.jpg]


    //Stefan

    Hi,
    Some small observations I wonder if any other have faced this after upgrade to 1.0.0.4


    1.
    In menu C1 it always state "No Fix" even if the GPS have a 2D or 3D fix, in the C2 menu it state what type of Fix the GPS have.


    2.
    In the Jurney function (B3) I from time to time got a maximum speed that are way out of what I've been traveling, last time it was 190 Km/h when the maximum speed has been around 110 km/h.


    //Stefan


    Dear Jan, dear Al
    In my opinion this would be a perfect match!
    Maybe we can vote for an update/upgrade in this direction.


    But I also have to come back to #1 the URTM /MGRS issue. As UTM-Grid-Referencing bases on the WGS84-Model conversion is possible - Al, what do you think!?
    For an example for conversional rules ready to implement see:
    http://www.ottmarlabonde.de/L1/UTMBeispielRechnung.htm
    and
    http://www.mucl.de/~hharm/files/utm.doc


    Hallo Jan, Hallo Al
    Meiner Meinung nach würde das eine perfekte Kombination für das Gerät sein! Ich habe normalerweise genug andere wissenschaftliche Geräte um mich herum, umso besser wäre die Implementation dieser Funktionen in ein Gerät.


    Trotzdem nochmal auf UTM und MGRS hingewiesen: Da UTM auf der WGS84-Projektion basiert gibt es diverse Umrechnungsmodelle - die relativ leicht so implementieren wären. Ist das irgendwie möglich darüber mal abzustimmen? (Siehe Links als Beispiel)


    Henri


    Hi,


    I think it is not even necessary to implement a conversion, as the GPS chip can be enabled to output the nmea PUBX 01 record, which is UTM data (not UTMREF /MGRS)


    Deutsch (und etwas ausführlicher)
    Der GPS-Chip kann den nmea PUBX 01 Datensatz ausgeben, welcher UTM Koordinaten in Form der Meridianzone sowie der Northing- und Easting-Werte und der Hemisphäre enthält (und zusätzlich noch diverse andere Angaben), deshalb muß eine Umrechnung von WGS84 eigentlich gar nicht mehr eingebaut werden.
    Was er nicht leistet, ist die Angabe von gitterfeldbasierten UTMREF/MGRS Koordinaten (Zone 32U Planquadrat ND Northing..., Easting...)


    Sascha


    Hallo Al,


    i've installed TMX270 and FW1004.


    In TMX i can't see Temp and Pressure, i think we must i have a new TMX, is'nt it??


    Please give us a new Filedescription, we have only WBT201_technical_document_2_Logdata.pdf and in this TrackFlag is old. Not for WSG1000 with Temp and Pressure.


    In deutsch und etwas ausführlöicher, da ich engl. nur ganz einfache Sätze bilden kann und die vermutlich noch grammatikalisch falsch sind:


    Ich nutze TMX 270 und die FW 1004. In TMX kann ich Temperatur und Druck (barometrisch) nicht sehen, ich vermute, dass hierzu eine angepasste TMX notwendig ist.


    Bitte gebe uns eine neue (passende) Filebeschreibung von TK1, wir haben nur .....Logdata.pdf (der WBT201) und darin sind Temperatur und Druck nicht spezifiziert. Die Daten sind sicher in den 2 Bytes des TrackFlag, die Werte nachzuempfinden ist mir bislang aber nicht gelungen.

    Einmal editiert, zuletzt von karomue ()


    Hi,
    Is problem still being?
    Some time when you set some limit of navigation out put filter(such as PDOP, TDOP) will lead to No fix, but you could see there still have some satellites in calculate for positioning (in GPGSA).


    Zitat

    Original von Stefan
    This meeans that the WSG-1000 just can output this data to a USB connected device and not to any type wireless navigating system that's more suitable in the field.


    How did you solved this with the WBT-100 since that one was capable of supporting this data via Bluetooth and was a less advanced unit. Does you have any product after WBT-100 that are able to support compass heading information via Bluetooth since I've not been able to find any other.


    I am sorry that is impossible send out log data and sensor information via Bluetooth due to WSG-1000s architecture.
    But WBT100 is different to WSG-1000.
    We are going to develop WBT101. But that need 3~6 month for waiting GPS chipsets.


    Zitat

    Original von Stefan
    As a last point I think it would be good that you add a extra notice on your product pages for WSG-1000 that this feture of compass heading information are not possible via Bluetooth, this so people who plan to use it for this doesn't buy and become un-pleased with your product.´


    Thanks, I will push our colleague to add this notice..

    Zitat

    Original von Stefan
    Except for this, it's a great product with the display and functions for active people - and if you don't need to received the compass data to other attached units. I've send in a question to Wintec there I suggested possible additional visual track back functionality (as a track on the display if you got lost when you are out) but have not heard anything about that.


    Regarding the visual track back function.
    In fact, I implemented it in initial developing stage.
    But performance is bad and that makes big CPU loading and occupies large code size.
    However, we will try to implement it. But I not sure we could success or not.



    Zitat

    Original von Jan
    I noticed some problem with the GPS altitude. Yesterday, I was in another town with altitude about 71m. Today, I turned on the WSG-1000 here at an altitude of about 240m. First, the WSG showed the old altitude and only after a while reached the true altitude. So this is also a problem for calibration of the altimeter. Did anybody else notice this? Log mode was bike.
    further, I also hat the impression that getting a fix is slower...
    Regards,
    Jan


    Hi Jan,
    The altitude of GPS is absolute and different to relative altitude of altimeter.
    GPSs altitude is calculated by satellites.
    And altimeters altitude is calculated by air pressure.
    So we could reason some points.
    1. GPS altitude is accuracy than altimeter if GPS could got good signal.
    2. Altimeter is stable than GPS in measure altitude variation.
    3. Altimeter is untrusting during sharp change in weather.(such as typhoon)
    4. .
    5. ..


    Dear Stefan,
    Did you have config gps parameters by u-center?




    we are attempting convert WSG-84 to UTM and show to screen.
    But that need considerable code size.
    the WSG-1000 surplus of code size just 3%, currently.
    That mean we have to reduce code or some function.
    We are going to reduce icon first.
    We could do it perfect.


    Zitat

    Original von karomue
    i've installed TMX270 and FW1004.
    In TMX i can't see Temp and Pressure, i think we must i have a new TMX, is'nt it??


    The TMX270 can support show Temp and pressure.
    But you should update WSG-1000 firmware first. then using new firmware to logging data.


    About format all command is same with WBT201.
    It's WSG-1000 device, that keyword is "CX01" when you send " @AL,8,1\r\n".
    And Log version become "2.0" when you send " @AL,8,3\r\n"


    The WSG-1000 not support function of password, auto sleep and over speed marked in log.


    The WSG-1000 logger support record temperature and air pressure in log since version 1.0.0.4.
    The structure of log package define as
    typedef struct
    {
    unsigned short bTrackStart:1;
    unsigned short bPushToLog:1;
    unsigned short temperature:5;// new feature
    unsigned short air_pressure:9; // new feature
    }__Status;


    //int temperature_degreeC=(2*temperature)-10;
    //int air_pressure_hPa=air_pressure+589;

    Hallo frame-dragging,


    die Produktbeschreibung verspricht das Blaue vom Himmel.
    "Alle nötigen Daten können über [...] Bluetooth ausgelesen werden."
    Und was ist mit den Log-Files? Ha-ha.




    The product specification of Wintec seems to be a pack of lies.
    "All necessary data can be gained from the device by bluetooth".
    And what about the log-files? Ha-ha.

    Zitat

    Original von Allai




    //int temperature_degreeC=(2*temperature)-10;
    //int air_pressure_hPa=air_pressure+589;


    Dear Al,


    thank you very mutch, that was it!


    But, i've Problems with T and P.


    In my File, Temp. and Pressure are include.


    I've TMX 270 and after start it, in the TrackEditor/Report I can see T and P also. If I double-click my File, T and P disappears.


    Where is my Mistake?


    D:
    Ich habe ein Problem in TMX Temp. und Druck anzuzeigen.


    Nach Start von TMX270 ist in TrackEditor/Report Temp. und Druck zu sehen, nach Doppelklick verschwinden aber beide. Im TK2-File sind die Werte vorhanden.


    Wo liegt der Fehler?


    You should set f32LogVersion to 2.0 in struct of tk2 header.
    typedef struct
    {
    char pHeader[16];
    float f32LogVersion;//set to 2.0 if you have T and P
    float f32SWVersion;
    float f32HWVersion;
    .........................
    ............................
    ...............

    }_TK2_STURCT_;


    Sorry Al,


    I do'nt understand this.


    I generate a log with WSG1000/FW1004, then read it with TMX270. Generate a TK2, go to LogEditor, double-click the TK2 and ca'nt see T+P. ??????


    I havn't programmed with C, C++ or so.... (or other Program, only WSG1000 -> TMX270).


    D:
    Kann das mal jemand versuchen nachzuempfinden:


    Im log TK2 ist eindeutig T+P enthalten. Wenn man mit TMX270 aus einem TK1 ein TK2 erzeugt, dann wie beschrieben über LogEditor dieses TK2 sehe ich weder T noch P doppel-klickt im Report. ????


    Could you give me your a tk2 file for test?


    Dear Al,
    thanks for your explanation, but my problem was different. I had the impression that the GPS altitude was stuck at the altitude of the old fix (71m), although I had a 3D fix in a city at 240m. So it was not the usual noise in the GPS altitude, but it was either a problem of the GPS to find the altitude (although it stated 3D fix) or it was a problem at the way from the GPS chipset to the WSG firmware. On the other hand, the two positions were more than 300 km away, this might also be a reason.
    The remark about the barometer was just a side note. A hot start then usually solves the problem...
    The last three days I also noticed another strange behaviour (which could also be caused by my lack of knowledge about the exact way GPS works): I turned it on inside a hotel room (yes, I know that inhouse GPS is a bad idea). No satellites were found. But when I came from outside, it saw many satellites, and could even get a fix when I held it at the right position, so I don't know why it didn't see the sats in the first place...
    Maybe there is some misconfiguration, I did a factory reset, but it seems that this does not reset all configuration items, many things remain in memory. Do you have a GPS settings file for u-center with recommended settings which I could upload?


    Another point: Since you and Charly were talking about the file format and code extensions, there are three more ideas which I had. Two of these ideas are probably easy to implement and would help to become independent of a PC for configuring the WSG. The third idea would allow people to log only what they want, or to trade the number of logged track points against the number of logged data items. It would probably mean changing the data format, but it would give experts maximum flexibility. I have attached three images to show what I mean.


    Best regards,
    Jan