I was playing with WXTide32 today and noticed a 1hour offset reported in WD when compared to the WXTide32 tide calendar output. See attached screenshot that I have annotated in red for the high/low tide times for my location. Note: this is the WXTide32 instance located in the wdisplay directory.
From the screenshot you can see that the WD time adjustment is left ‘as is’ so cannot understand where this offset has come from. Looking at another tide source for my location it looks like the WXTide32 output is correct compared to the WD +1hr adjustment. Also check the screenshot annotation in orange, could this be something to do with my problem?
Looking further in to this problem under the ‘Tide Prediction’ window (see attached) if I set the ‘Time Adjust’ options and press the 'View/reload the latest predictions: I get the following results:
Decrease by 1 hour = WXTide32 returns a list of command line switches i.e. WD issued an invalid command line to WXTide32.
Leave as is = WXTide32 returns a calendar of tides that both high and low tides are offset by +1hour.
Increase by 1 hour = WXTide32 returns a calendar of tides that are correct i.e. no low/high tide time offset - see screenshot.
This looks like a bug in the command line switches that WD issues to WXTide32
Is there a way of finding this out e.g. log file or some Windows method?
I also have just noticed a similar problem. I have the same setting “Leave as is” and the tide times are out by 1 hour. If I use the setting “Decrease by 1 hour”, I get the message “ERROR: I do not know what switch [21] means.”
Dalriadan can you select the ’ Increse by 1 hour’ option on the tides settings window as this strangely gives me the correct times for high/low tides and let me know the outcome.
I am guessing there is a bug in WD when it calls WXTide32 by passing the incorrect switches and in the case of the ‘Decrease by 1 hour’ option incorrect syntax to what WXTide32 is expecting.
I have the same problem too … I get around it by using a GMT offset and changing it by one hour when daylight savings happen. I noticed though that the GMT offset was wrong, I am normally GMT +10 however I have to use GMT -10 to get t to display the correct times.
This sounds like a different problem i.e. have you opened up WXTide32 independently of WD and checked the tide times displayed with your local port times?
If not check your location settings and timezone preferences within WXTide32.
This thread highlights an issue where WD does not fetch these correct times from WXTide32 even though both programs are setup correctly.
Just to say that for me on build 23 and ‘Leave As Is’ set I get correct times reported in the control panel and on the graph. I also run wxtide outside of WD to create my rolling year file for tides and all works fine as well. I wonder if this has anything to do with the settings on wxtide32? I also run WD and the PC on DST and wxtide32 shows correct times for the whole year without any alteration for DST.
Thanks Stuart, I am running the latest build. If I run the tides outside of WD they are correct but when run via WD with the time offset at leave as is I get this message.
Newburyport, Merrimack River, Massachusetts + Corrections: High(+1:00) Low(+1:00)
Newburyport, Merrimack River, Massachusetts
+ Corrections: High(+1:00) Low(+1:00)
If I select -1 hour I have this message
ERROR: I do not know what switch [21] means
Setting it to add 1 hour produces the same result as running the program outside of WD.
It is working, just was curious if Brian had found anything or if it might have been fixed.
Just a thought what version of wxtide are you running? There is a wxtide47.zip on the wxtide website at http://www.wxtide32.com/download.html, it might be worth downloading this and running it instead of the version on the WD download page. This is what I am running, both within WD and in a separate folder for my yearly file.
Hi, I tick leave as it is & then open tides by clicking on set the port location then file, then preferences, then system, then tick local, this gives me GMT + 1 hour ( BST ). Never could get +1 -1 hour to work. WD 10.37r b23.
if you set to reduce by 1 hour in WD
then WD passes in the command to wxtide32
-htoff -01:00 -ltoff -01:00
if you have set to increase by 1 hour then its
I have found the error, I think
was line of code
and was an experiemental code that broadstairs wanted (to work with the -thin switch)
but obviously only worked with his setup
use a new .zip update, ready now to remove that
