Lady Heather v6 Beta for Windows .exe

[linux_user]

I suggest using github. Seems odd that we have to wait for mods. Just let me download the current master branch. I'll grab the updates when those are tested and merged... 

[texaspyro]

Updated attachment and links in the first post to v6.14 Beta.   There is also a link to download the source code.

This version has a few fixes and cosmetic changes,  support for very small (480x320 screens),  support for the Samsung UCCM type GPSDOs, and support for Trimble RT17 format survey receivers like the NetRS.

[softfoot]

I just upgraded from Version 6.08 Beta - Aug  1 2018 16:31:34 to the latest and it doesnt initialize my ublox 4 anymore.
I do use some commands that rely on the previous beta :-

# Kludge to force GPS module to use 115200 and LH from the default 9600
@!x115200

# Kludge to set TP5
@TA2SW
@#
@PA 10e6 0.5
@PA 10e6 0.5
# End of kludge

Have you disabled anything that may affect this ?

Dave

[texaspyro]

Have you disabled anything that may affect this ?

No...

[KE5FX]

Hello Mark,

is there a particular reason, or did I miss something on time-nuts, that you don't publish LH on John Miles pages, KEF5FX, anymore?

Frank

The slow update rate on that page is more my fault than Mark's.  Every so often I'll update it when I have time, but I've been utterly swamped lately.  Ultimately it would be best to migrate it to Github or another site where an active development process can be more easily supported.

[texaspyro]

The slow update rate on that page is more my fault than Mark's.  Every so often I'll update it when I have time, but I've been utterly swamped lately.  Ultimately it would be best to migrate it to Github or another site where an active development process can be more easily supported.

Actually,  I didn't want to put beta level code on your site.   

I have been meaning to put it on Github.

[ArthurDent]

I initially got the same error messages "w32sal.dll missing" and "winvfx16.dll missing" until I paid more attention and put the new beta file in the same folder with the rest of the Lady Heather files.

I haven't tried it with all my GPSDOs but did first run it with my NTPB15AA unit that I modified to have a display and built-in power supply. My display has a rollover problem as you can see but LH worked well as you can see from the graph. 

[texaspyro]

And oh, so sexy hands on Heather's new analog clock display!  Hovering the mouse over a satellite/sun/moon will show info about that satellite/sun/moon.

BTW, the GLP keyboard command will hide the location of your evil-mad-scientist secret volcano lair.

[ArthurDent]

I forgot to blank the location so I did it in photoshop.

[Helix70]

Just thought I would report that with a 4K display on a 13 inch laptop, Windows 10 sets the scaling to 300% by default so programs are big enough to see and click buttons on. With Lady Heather v5 and v6beta, Scaling doesn't work well and all of the writing turns into a bit of a mess. I have tried all the different sizes and font sizes, they all look like this.

I have a multi screen setup, a 1920x1200 monitor and the laptop 4K display, and when Heather opens on the 4K display, this is the result, even if you move it to the HD screen. When it starts on the HD screen, it is ok.

I am happy to help test this if the developer wants to correct it. This isn't the only program that faces this issue, but i think as hardware evolves, more of us will have 4K displays.

[texaspyro]

In v6 try using the scaled vector fonts.  $q from the keyboard or /vq=# from the command line,  where # is the desired scale factor in percent (50-500).  /vq sets 150%

[Helix70]

Thanks texaspyro, that cleans it up nicely. /vq=0 looks the nicest, still uses the good font. When you use scaled, is there any control over the window size?

Thanks,

Josh

[texaspyro]

Thanks texaspyro, that cleans it up nicely. /vq=0 looks the nicest, still uses the good font. When you use scaled, is there any control over the window size?

Strange, /vq=0 just sets the font back to the normal dot matrix font... it should not do anything different.

Scaled vector fonts work with whatever window size you select.   Larger scaled font sizes may cause parts of the image to fall outside of the screen window.

Note the the WINVFX library that Heather uses to draw to the screen will scale the drawn image by dropping lines and/or horizontal pixels if you select an image size larger than the monitor size... that causes rather ugly screen output.

[Helix70]

This is the result of /vq=0.

[EOC_Jason]

I'm trying to get LH to work with an old Axiom Sandpiper (SiRF) GPS module (it supposedly can output raw data, which I'm hoping to eventually write to rinex and do post-processing, that's why I'm messing with it).

Anyhow, LH will detect it as sirf, but then the screen just stays blank (see attached). It initially flashes "NO COM1 SERIAL PORT DATA SEEN" quickly (I had to restart the program several times to catch what it said). I've tried several baud rates, it always auto-detects just fine, but then does nothing. Data is good as I can view it in SIRFDEMO... If I switch to NMEA it displays everything in LH just fine.

Any help would be appreciated.

[texaspyro]

It probably uses a early version of the Sirf protocol that Heather know nothing about.  I have found no manual on the Sandpiper.  What I have seen says it speaks NMEA and no mentions of raw data.

[EOC_Jason]

I managed to find *one* site that had some old PDF manuals & html pages that looks like they archived it from another site (that is no longer up).

http://gps.0xdc.ru/static/sirf/doc/SirfStar/gpsd.berlios.de/vendor-docs/axiom/

It's not a big deal, just kind of got sidetracked doing one thing, which led to another, and we all know where that rabbit hole leads to... 

[texaspyro]

Ok,  the problem is the Axion outputs the NAV2 message and newer ones output the NAV message that Heather supports.   The NAV messages contain the time and that is used to drive the screen updates.

I tricked up some code to use NAV2 if NAV is not available and it works... except the Axiom does not output the UTC offset value (number of leap seconds difference between UTC and GPS time that the receiver sends).   You would need to manually set that value.

As far as the RAW data...  the documentation does not have enough info to figure out how to it.

[tkamiya]

This is a result from the latest code (as of today) using Tremble Resolution T.  The clock update happens every 3 seconds and as such, red line appears at the top.  (tick mark?)  Also, saw tooth continues forever.  Latter, I think might be irrelevant as this is just a receiver.  It is not disciplining anything.

Only thing a bit unusual about this setup is COM3 is a USB/serial adapter at TTL level, and TR-T is 3.3V, so there is a level converter in the middle.  TXD and RXD is connected, CTS and RTS is unconnected.  According to Trimble, this receiver does not do any kind of flow control, including Xon Xoff.

I also tried configuration/display software from Trimble.  It updates every second.  I don't know if this is coming from the GPS.  Using terminal, I see data coming every second but it's binary, so I can't tell its content.

Notice run time is short.  But I had this running for 6 hours at one point and result was identical.

I noted format changed.  Display area below digital clock is smaller

[texaspyro]

The original model Res-T has a firmware bug.  If certain message requests are sent, it takes the device 3 seconds to respond.   Try starting Heather with the /rxr or /rxr=1 or /rt=1 command line options.  This will tell Heather that the device is the old model and not to issue requests that can hose up the receiver.

[tkamiya]

Thank you.  I had /rxr=2.  Changed it to /rxr=1 and red ticks went away.  Clock update is timely as well.

What do you make of saw tooth though?  Period is longer but it is still there.

[texaspyro]

What do you make of saw tooth though?  Period is longer but it is still there.

If you are talking about the magenta trace, that is not sawtooth correction data.  That is the "clock bias" value... I'll leave it to you to figure out exactly what that is...  the docs don't really talk about it.   The sawtooth plot  control command is GD.  It defaults to OFF since it is mostly a noisy looking plot that can obscure other plots.

[tkamiya]

Thank you.  I spent two days with this new board to get this far.

[tkamiya]

Everything I read basically says it is a drift of clock and in over-determined mode, this is one of the value to correct 1 pps.  What concerns me is this is very periodic.  I used the word to describe the shape.  It looks more like a graph of periodic function.  Every screen shots I see, including my other receivers, this is more of a noise like graph that drifts up and down randomly.

All of my Prsolution-T is like this, and all of my GPSTM isn't like this.

Does this indicate a problem with my receiver?

[texaspyro]

What the various plots are used for is determined by the receiver type.   GP is usually a PPS related plot.  GO is usually an oscillator related plot.   Note: usually, but not always...