Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
Re: PropView 1.0.2 settings not saved between sessions
Ron Eberson
No dave with the last update all are great no problem.
sorry to tell you not before. -----Oorspronkelijk bericht----- Van: Dave Bernstein [mailto:dhb@...] Verzonden: donderdag 5 april 2001 17:18 Aan: dxlab@... Onderwerp: [dxlab] Re: PropView 1.0.2 settings not saved between sessions Ron, are you still having problems with PropView settings like Power and TakeOff not being saved between sessions? Is anyone else encountering this? 73, Dave, AA6YQ --- In dxlab@y..., "Ron Eberson" <zx@c...> wrote: YES HE WORKS DAVE thanks for it.antenna? Also on the fig you can see not the top of the 7 from 17 meters.see the both DXView and Porpview on the screen compleet?- it will update your online help and install PropView102.exe, which To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to |
|
Re: PropView 1.0.2 settings not saved between sessions
Dave Bernstein
Ron, are you still having problems with PropView settings like Power
and TakeOff not being saved between sessions? Is anyone else encountering this? 73, Dave, AA6YQ --- In dxlab@y..., "Ron Eberson" <zx@c...> wrote: YES HE WORKS DAVE thanks for it.antenna? Also on the fig you can see not the top of the 7 from 17 meters.see the both DXView and Porpview on the screen compleet?- it will update your online help and install PropView102.exe, which |
|
Re: PropView
Dave Bernstein
To get full interoperability between DXView and PropView, you should
toggle quoted message
Show quoted text
be running DXView 1.2.6 -- sorry for not making this explicit. 73, Dave, AA6YQ --- In dxlab@y..., "Richard B Drake" <rich@w...> wrote:
Robin, |
|
Interesting observation with PathView
I just worked BX7AA on 21.016. I ran the propagation forecast for
him using the current solar flux of 228 (not too shabby) and it showed that I should have propagation but it was between the 10% and 50% MUF lines. I managed to work him but the interesting thing was that the charts showed that propagation to him on that frequency should improve over the next two hours and then begin to drop off. Of course there is no guarantee that he would still be there in two hours but the message to me was that if I had trouble working him at this time I should keep trying because the conditions should be improving. Nice job Dave, this is really useful! ----- 73, Rich - W3ZJ www.w3zj.com |
|
Re: PropView
Robin,
toggle quoted message
Show quoted text
PathView does access the prefix database in DXView. All you should need to do is have both programs running and when you lookup a prefix in DXView the resulting Lat/Lon information automatically appears in PathView. If yours is not doing this then perhaps there is some problem. ---- 73, Rich - W3ZJ -----Original Message----- |
|
PropView
Hi Dave,
Have just started using PropView and it seems to work well at this QTH. What would make it very quick to use would be the ability to use Country prefixes instead of Latitude and Longitude. All of that information must exist already in DXView...is there any way in which PropView could access that database? Robin gw3zcf |
|
DXKeeper 1.1.9 is available
Dave, AA6YQ
This release
toggle quoted message
Show quoted text
- adds an "Import from MMTTY" checkbox to the Import tab, which when checked extracts transmit and receive sequence numbers from imported RST sent and rcvd fields respectively - adds a "Start" button to the QSO Capture window, which when activated designates the QSO start time When you click the Start button, it is replaced by a display of the QSO start time. Clicking the Log or Clear buttons un-hides the Start button. When the QSO Capture window's Callsign textbox has focus, striking the "Insert" key is equivalent to clicking the Start button. Clicking the Lookup button no longer designates the QSO start time. If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.9 by downloading and then running -- your online help will be updated by this process. 73, Dave, AA6YQ -----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...] Sent: Thursday, March 29, 2001 1:31 AM To: dxlab@... Subject: [dxlab] DXLab 1.1.8 is available This release - corrects a defect that produced a crash if you tried to close DXKeeper while it was iconified - in the QSO Capture window, clearing all fields leaves the text entry cursor in the callsign field If you've already installed DXKeeper 1.1.1 or later, you can upgrade to version 1.1.8 by downloading and then running www.qsl.net/dxkeeper/DXKeeper118Update.exe -- your online help will be updated by this process. 73, Dave, AA6YQ Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. |
|
Re: PropView
Dave, AA6YQ
When PropView starts, it initializes the Time field to the then current UTC
toggle quoted message
Show quoted text
time. This won't change unless you change it -- either by double-clicking (to set the current time), or by keying in a time. Clicking the "Predict" button does not update the time to the current time, as that would preclude times other than the current time. Since time doesn't play a role in the computation -- its just used to position the vertical time bar -- perhaps it would be more useful to eliminate the "Time" text box (in the Conditions panel of the Parameters tab) and instead make the vertical time bar in the Prediction display "draggable". A prediction would initially position the vertical time bar to the current time, but one could drag it around to serve as an index. Double-clicking the vertical time bar would return it to the current time. Note that a prediction could be for some day other than today, in which case double-clicking the vertical time bar would be positioning it to "the current time on that day". Comments? Better ideas? IonCAP does not consider geomagnetic conditions in its prediction computation. I'm currently scanning the literature for the statistical relationship between the K index and the dimensions of the auroral oval, which would enable DXView to plot the oval and report the extent to which a path experiences polar absorption. I know of at least one propagation program that does this, and therefore assume that documentation of the relationship exists. If anyone is has this information or a reference to it, please send it my way. 73, Dave, AA6YQ -----Original Message-----
From: Richard B Drake [mailto:rich@...] Sent: Wednesday, April 04, 2001 19:14 PM To: Dxlab Subject: [dxlab] PathView Dave, Now that the solar flare activity seems to have settled a bit, PathView is providing some very nice and accurate information. I think however that it is not always reading the clock. When I first bring it up and do a prediction it shows the vertical time bar in the correct location. However, it never seems to change as I do more predictions at a later time unless I close and reopen it again. ----- 73, Rich - W3ZJ www.w3zj.com Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. |
|
PathView
Dave,
Now that the solar flare activity seems to have settled a bit, PathView is providing some very nice and accurate information. I think however that it is not always reading the clock. When I first bring it up and do a prediction it shows the vertical time bar in the correct location. However, it never seems to change as I do more predictions at a later time unless I close and reopen it again. ----- 73, Rich - W3ZJ www.w3zj.com |
|
Re: Callsign lookup
Dave,
toggle quoted message
Show quoted text
As you probably know, some countries (the UK for example) still require logging of both start and stop times. Here, we can do what we want including nothing. But, QSLing dictates that we record times as accurately as we can so that we can reasonably confirm a contact. Thus, this is the reason for even being very concerned about it. Most loggers record only one time and there has been a big discussion lately on the OnLineQSL reflector as to whether to record the start or the stop time. Interestingly, it splits about 50/50 among users and people have reasons that they consider important for doing it one way or the other. DXKeeper is one of the few loggers that records both the start and stop times so this becomes an important feature of the program. I think your idea of providing a separate button specifically for noting start time is the best. No one will be confused about it and it provides complete control over it. My suggestion would be that it not be a required entry and if the user doesn't select it you record the time of entry into the log (basically the end time of the QSO) in both time fields. This will work out well for those quick DX and contest contacts where start and stop times differ only by a few seconds and also provides rag chewers with a way to record both times on a long QSO when they want it. ---- 73, Rich - W3ZJ -----Original Message----- |
|
Re: PropView 1.0.2 is available
Dave, AA6YQ
By "save some settings", I assume you mean between PropView sessions. Power
toggle quoted message
Show quoted text
and WaveAngle are saved between sessions -- I checked this on both US and European configurations. When you close PropView, is it terminating normally or are you seeing an error message? Perhaps PropView is terminating abnormally before it saves your modified settings. The frequency display is dynamic -- when the range of frequencies is large, the ham bands get scrunched together and the labels overlap, resulting in the problem you noticed with the 7 in 17 meters. Perhaps there's a way to miminize this by making the labels alternate positions -- I'll think about it... DXView's and PropView's windows are as compressed as I know how to make them without sacrificing useability. The only way to make them smaller would be to adopt a smaller font size, which I'm reluctant to implement given the periodic comments I get about the fonts already being too small. The more DXLab applications you run, the more screen space you need; I don't know how to work around this without making the applications much harder to use; the good news is that higher-resolution display systems (1024x768, 1280x1024, 1600x1200) have gotten a lot less expensive over the past few years. Alternate suggestions would be appreciated. 73, Dave, AA6YQ -----Original Message-----
From: Ron Eberson [mailto:zx@...] Sent: Wednesday, April 04, 2001 1:32 AM To: dxlab@... Subject: RE: [dxlab] PropView 1.0.2 is available YES HE WORKS DAVE thanks for it. Is it posible to save some settings like power and wave angel of antenna? Also on the fig you can see not the top of the 7 from 17 meters. Can we change the size of the window from Propview so that you can see the both DXView and Porpview on the screen compleet? Thanks in advance and the time you take for all of us. -----Oorspronkelijk bericht----- Van: Dave Bernstein [mailto:dhb@...] Verzonden: woensdag 4 april 2001 7:23 Aan: dxlab@... Onderwerp: [dxlab] PropView 1.0.2 is available This release corrects the runtime error occuring on systems with a locale that doesn't use the period character as a decimal separator. (Ron, this should correct the problem you are encountering with 1.0.1). If you already have PropView 1.0.1 installed, you can upgrade by downloading and running www.qsl.net/propview/PropView102Update.exe -- it will update your online help and install PropView102.exe, which you can then run. 73, Dave, AA6YQ To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to Yahoo! Groups Sponsor Click here for Business information To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. |
|
Re: Callsign lookup
Ron Eberson
A button so that we can make a choce in it than we can use it also for
contests. my opinion Ron -----Oorspronkelijk bericht----- Van: Dave, AA6YQ [mailto:dhb@...] Verzonden: woensdag 4 april 2001 7:39 Aan: dxlab@... Onderwerp: RE: [dxlab] Callsign lookup We can certainly change "?" from "check for previous QSOs" to "check for previous QSOs and lookup DXInfo but don't set the start time". Seems a little complicated to remember. Or we could modify the "lookup" button to not set the start time, perhaps making start time the same as end time for all QSOs logged throught the capture window. Or should I add a "start QSO" button to record the start time? Which would be more intuitive and/or convenient? Is there a better idea? 73, Dave, AA6YQ -----Original Message----- From: Richard B Drake [mailto:rich@...] Sent: Tuesday, April 03, 2001 23:40 PM To: Dxlab Subject: [dxlab] Callsign lookup Dave, Entering a callsign in DXKeeper's capture window and clicking on the question mark next to it causes the callsign to be placed into the filter window and looked up. If the callsign exists in the log, the information is also transferred to DXView which then provides beam heading and progress information. However, if the callsign does not exist in the log, nothing goes to DXView. I could click "lookup" to get the call into DXView but that does other things including noting the start time and I haven't started a QSO yet. ----- 73, Rich - W3ZJ www.w3zj.com Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to |
|
Re: Callsign lookup
Dave, AA6YQ
We can certainly change "?" from "check for previous QSOs" to "check for
toggle quoted message
Show quoted text
previous QSOs and lookup DXInfo but don't set the start time". Seems a little complicated to remember. Or we could modify the "lookup" button to not set the start time, perhaps making start time the same as end time for all QSOs logged throught the capture window. Or should I add a "start QSO" button to record the start time? Which would be more intuitive and/or convenient? Is there a better idea? 73, Dave, AA6YQ -----Original Message-----
From: Richard B Drake [mailto:rich@...] Sent: Tuesday, April 03, 2001 23:40 PM To: Dxlab Subject: [dxlab] Callsign lookup Dave, Entering a callsign in DXKeeper's capture window and clicking on the question mark next to it causes the callsign to be placed into the filter window and looked up. If the callsign exists in the log, the information is also transferred to DXView which then provides beam heading and progress information. However, if the callsign does not exist in the log, nothing goes to DXView. I could click "lookup" to get the call into DXView but that does other things including noting the start time and I haven't started a QSO yet. ----- 73, Rich - W3ZJ www.w3zj.com Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. |
|
Re: PropView 1.0.2 is available
Ron Eberson
YES HE WORKS DAVE thanks for it.
Is it posible to save some settings like power and wave angel of antenna? Also on the fig you can see not the top of the 7 from 17 meters. Can we change the size of the window from Propview so that you can see the both DXView and Porpview on the screen compleet? Thanks in advance and the time you take for all of us. -----Oorspronkelijk bericht----- Van: Dave Bernstein [mailto:dhb@...] Verzonden: woensdag 4 april 2001 7:23 Aan: dxlab@... Onderwerp: [dxlab] PropView 1.0.2 is available This release corrects the runtime error occuring on systems with a locale that doesn't use the period character as a decimal separator. (Ron, this should correct the problem you are encountering with 1.0.1). If you already have PropView 1.0.1 installed, you can upgrade by downloading and running www.qsl.net/propview/PropView102Update.exe -- it will update your online help and install PropView102.exe, which you can then run. 73, Dave, AA6YQ To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to |
|
PropView 1.0.2 is available
Dave Bernstein
This release corrects the runtime error occuring on systems with a
locale that doesn't use the period character as a decimal separator. (Ron, this should correct the problem you are encountering with 1.0.1). If you already have PropView 1.0.1 installed, you can upgrade by downloading and running www.qsl.net/propview/PropView102Update.exe -- it will update your online help and install PropView102.exe, which you can then run. 73, Dave, AA6YQ |
|
Callsign lookup
Dave,
Entering a callsign in DXKeeper's capture window and clicking on the question mark next to it causes the callsign to be placed into the filter window and looked up. If the callsign exists in the log, the information is also transferred to DXView which then provides beam heading and progress information. However, if the callsign does not exist in the log, nothing goes to DXView. I could click "lookup" to get the call into DXView but that does other things including noting the start time and I haven't started a QSO yet. ----- 73, Rich - W3ZJ www.w3zj.com |
|
Re: PropView 1.0.1
Dave Bernstein
Thanks, Ron. "98" and "Dutch version" was what I needed to know. I'll
get on it this evening. 73, Dave, AA6YQ --- In dxlab@y..., "Ron Eberson" <zx@c...> wrote: Dave he give's also in the window error 134.0, 98SE, and Win2K. My guess is that you are running a Europeanversion, and that one of PropView's date or time routines is failing in thissure why PropView is failing, but will look into it. |
|
Re: PropView 1.0.1
Ron Eberson
Dave he give's also in the window error 13
type mismatch is this a info for you? -----Oorspronkelijk bericht----- Van: Dave Bernstein [mailto:dhb@...] Verzonden: dinsdag 3 april 2001 20:54 Aan: dxlab@... Onderwerp: [dxlab] Re: PropView 1.0.1 Ron, I tested this release on three different versions of windows: NT 4.0, 98SE, and Win2K. My guess is that you are running a European version, and that one of PropView's date or time routines is failing in this environment and creating the runtime error. Please tell me what version of Windows you are running, and which European locale you have chosen. Hopefully I can replicate and then repair the problem tonite. PropView uses the same Help viewing mechanism as the other DXLab applications -- in fact it uses the same code module. So I'm not sure why PropView is failing, but will look into it. 73, Dave, AA6YQ --- In dxlab@y..., "Ron Eberson" <zx@c...> wrote: show: Error 13 Run time error.must put a filename????? To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to |
|
Re: PropView 1.0.1
Ron Eberson
I have the 98 version normal type only dutch version.
The help is working not more a dos screen now. I have reinstal it and restart the comp. 700 MHz and 64MB memory i do not know yje version se or so how can i see this??? -----Oorspronkelijk bericht----- Van: Dave Bernstein [mailto:dhb@...] Verzonden: dinsdag 3 april 2001 20:54 Aan: dxlab@... Onderwerp: [dxlab] Re: PropView 1.0.1 Ron, I tested this release on three different versions of windows: NT 4.0, 98SE, and Win2K. My guess is that you are running a European version, and that one of PropView's date or time routines is failing in this environment and creating the runtime error. Please tell me what version of Windows you are running, and which European locale you have chosen. Hopefully I can replicate and then repair the problem tonite. PropView uses the same Help viewing mechanism as the other DXLab applications -- in fact it uses the same code module. So I'm not sure why PropView is failing, but will look into it. 73, Dave, AA6YQ --- In dxlab@y..., "Ron Eberson" <zx@c...> wrote: show: Error 13 Run time error.must put a filename????? To unsubscribe from this group, send an email to: dxlab-unsubscribe@... Your use of Yahoo! Groups is subject to |
|
Re: Interpreting PropView Graphs
Dave,
toggle quoted message
Show quoted text
I had figured that out, but it took a while. I think that is an excellent explanation. However, I assume that this all means nothing with record breaking solar flares, geomagnetic storm conditions and proton bombardment. Honestly, we have the best solar flux of cycle 23 and we are being simultaneously attacked by band closing sun monsters :-) ----- 73, Rich - W3ZJ -----Original Message----- |
to navigate to use esc to dismiss