From ibcweb at mac.com Tue Apr 1 14:56:33 2008 From: ibcweb at mac.com (Travis Best) Date: Tue, 1 Apr 2008 14:56:33 -0400 Subject: [DogParkList] MacDoppler Message-ID: <4331B898-72F5-40C2-995B-401C2739343A@mac.com> Is mac Doppler able to set the uplink and downlink freq on a yaesu ft-857d? Thanks Travis From dagro at dogparksoftware.com Tue Apr 1 15:19:04 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Tue, 1 Apr 2008 15:19:04 -0400 Subject: [DogParkList] MacDoppler In-Reply-To: <4331B898-72F5-40C2-995B-401C2739343A@mac.com> References: <4331B898-72F5-40C2-995B-401C2739343A@mac.com> Message-ID: <457053C9-F9DD-44A0-82E9-841B8E18680B@dogparksoftware.com> Hi Travis, On Apr 1, 2008, at 14:56 , Travis Best wrote: > Is mac Doppler able to set the uplink and downlink freq on a yaesu > ft-857d? MacDoppler supports the FT-8x7 radios but a full duplex satellite radio like the TS-2000, FT-847 or IC-910 is recommended to take advantage of MacDoppler's capabilities. Why not download the free demo and try it ? 73 Don Agro VE3VRW From ke9v at mac.com Sat Apr 5 14:13:04 2008 From: ke9v at mac.com (Jeff Davis) Date: Sat, 5 Apr 2008 14:13:04 -0400 Subject: [DogParkList] Time? Message-ID: <8AD92DD5-48B3-4FDF-9085-5423C5189995@mac.com> Will apologize upfront for the seemingly silly question -- but I just upgraded to 4.3.4 about an hour before jumping into the QRP-ARCI Spring QSO Party and all of a sudden all my log times are in 12H (AM/ PM) format instead of UTC which I'm pretty sure was the setting before the upgrade -- or am I dreaming of something on a Windoze laptop somewhere? 73 de Jeff, KE9V From dagro at dogparksoftware.com Sat Apr 5 15:11:12 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Sat, 5 Apr 2008 15:11:12 -0400 Subject: [DogParkList] Time? In-Reply-To: <8AD92DD5-48B3-4FDF-9085-5423C5189995@mac.com> References: <8AD92DD5-48B3-4FDF-9085-5423C5189995@mac.com> Message-ID: <515C1B9D-DEAD-49D5-9DF2-E998F090F3C5@dogparksoftware.com> Hi Jeff, On Apr 5, 2008, at 14:13 , Jeff Davis wrote: > Will apologize upfront for the seemingly silly question -- but I > just upgraded to 4.3.4 about an hour before jumping into the QRP- > ARCI Spring QSO Party and all of a sudden all my log times are in > 12H (AM/PM) format instead of UTC which I'm pretty sure was the > setting before the upgrade -- or am I dreaming of something on a > Windoze laptop somewhere? The actual log entries in each row are always in 24 hour ADIF format, but how they are displayed in the Edit field depends on your system settings. 73 Don Agro VE3VRW From g.berges at bergesetco.com Sat Apr 5 16:38:09 2008 From: g.berges at bergesetco.com (Gustavo Berges) Date: Sat, 05 Apr 2008 16:38:09 -0400 Subject: [DogParkList] Question mark in CQ Zone Message-ID: Anyone found a way to disable the Alarm for a CQ Zone not in the log when the CQ field has a question mark? My alarm advises any time a question mark is in this field, even if I have the region zone confirmed. Thanks. -- Gustavo Berg?s, NU4L 1820 NE Jensen Beach Blvd. #623 Jensen Beach, Florida 34957 (772) 419 8015 Ph./(772) 382 0209 Fx -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From vk2cmp at optusnet.com.au Tue Apr 8 08:00:29 2008 From: vk2cmp at optusnet.com.au (Mick) Date: Tue, 8 Apr 2008 22:00:29 +1000 Subject: [DogParkList] MacDoppler hangs Message-ID: Hi there, has anyone experienced MacDoppler hanging when trying to command both the radio (IC910) and rotator (using kit (PIC) as per the ARRL link on the Dogpark site). I have used MacDoppler for years with no probs. Connected the rotator on the weekend and it works great. However the program continues to hang when I go to enable the radio or rotator. It has worked some times. I have a Keyspan 4 port convertor which has run MacDoppler and MacLogger for years as well. Any suggestions would be most appreciated cheers Mick VK2CMP From wa1oui at arrl.net Tue Apr 8 10:23:40 2008 From: wa1oui at arrl.net (David Kaplan) Date: Tue, 8 Apr 2008 10:23:40 -0400 Subject: [DogParkList] SRX, STX Strings on QSL References: <0D3D1FA0-6F35-4DB6-95B4-8D8AC4C95157@mac.com> Message-ID: <56F3D0D5-8F41-46CB-8C89-40131220BBAD@arrl.net> Attached is a QSL I was going to print. Luckily I looked at it carefully. Please note the CT, CT at the end of the "Please QSL" line. According to the manual these are the STX, SRX fields. I did have CT in the STX field, but the SRX field had "1000" in it. Here's the ADIF text: FN31nt9K2KWA1OUIAbdallah Hamad AL-Muzayan (&#1576;&#1608;&#1581;&#1605;&#183;)LL39xg2008030213053013053014.19970014.19970020MSSB348595915001000CT21 1) Is there a bug that STX is appearing twice? 2) It would be nice if there was a check box on the QSL page so that printing these is a choice. I really don't want to HAVE to send this information when I send a QSL. Thanks, David, WA1OUI -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: QSL.jpg Type: image/jpeg Size: 14062 bytes Desc: not available Url : From dagro at dogparksoftware.com Tue Apr 8 10:44:03 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Tue, 8 Apr 2008 10:44:03 -0400 Subject: [DogParkList] SRX, STX Strings on QSL In-Reply-To: <56F3D0D5-8F41-46CB-8C89-40131220BBAD@arrl.net> References: <0D3D1FA0-6F35-4DB6-95B4-8D8AC4C95157@mac.com> <56F3D0D5-8F41-46CB-8C89-40131220BBAD@arrl.net> Message-ID: Hi David, On Apr 8, 2008, at 10:23 , David Kaplan wrote: > > Attached is a QSL I was going to print. The attachment and email were bounced by the list software since it exceeds 40K but I received them. > Luckily I looked at it carefully. Please note the CT, CT at the end > of the "Please QSL" line. According to the manual these are the STX, > SRX fields. I did have CT in the STX field, but the SRX field had > "1000" in it. > > Here's the ADIF text: > FN31nt9K2KWA1OUI 78>Abdallah Hamad AL-Muzayan > (&#1576;&#1608;&#1581;&#1605;&#1 4>83;)LL39xg20080302 6>13053013053014.19970014.199700 3>20MSSB3485959 4>15001000CT21 > > 1) Is there a bug that STX is appearing twice? Yes, that has been fixed in 4.3.5b2, thanks for catching it. > 2) It would be nice if there was a check box on the QSL page so that > printing these is a choice. I really don't want to HAVE to send this > information when I send a QSL. That was put in at the request of several users and I have frozen the UI until I can finish MacLoggerDX for Cocoa, but I will keep it in mind for the new version. > Thanks, > > David, WA1OUI 73 Don Agro VE3VRW From wa6l at mac.com Wed Apr 9 13:17:43 2008 From: wa6l at mac.com (John Graf) Date: Wed, 9 Apr 2008 10:17:43 -0700 Subject: [DogParkList] K3 Power Out Message-ID: This last weekend I participated briefly in the ARCI QRP contest. I was using my new K3/100 and had the "report power" box checked in the preference pane. What I discovered is that when the K3 is dialed down to 5.0 watts, the reported power in MDLX shows up as 050 as opposed to 005. Is that a problem with MDLX or with the K3? Thanks, John, WA6L From rswickis at telus.net Wed Apr 9 13:21:12 2008 From: rswickis at telus.net (Roger Swickis) Date: Wed, 9 Apr 2008 10:21:12 -0700 Subject: [DogParkList] Logging from MacDoppler Message-ID: <4825E4A2-C2C5-4E84-A086-47C23231CD51@telus.net> I am a realatively new user to MacDoppler and MacLogger. I can't seem to make the interface from MacDoppler to MacLogger work. I have checked previous postings in the archive and they indicate that when I push the "Log it" button in the "Log Contact" window of MacD that a log entry should appear in the "MacDoppler File". I think then I should be able to find it (or at least put it in) the MacL preferences window under "Logs" and be able to callit up into MacLogger. However, nothing appears in the MacL preferences window under Log. I can't find a file where MacD has sent the log info. One post suggests to look in the "MacDoppler Folder". I do not have a "MacDoppler Folder". Am I supposed to create one? Does it happen automatically? If sohere might it be? I have used "Finder" to look for a fileor a folder , but can't find either. Can anyone help? Roger VA7MG/VE7BZR From dagro at dogparksoftware.com Wed Apr 9 13:44:47 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Wed, 9 Apr 2008 13:44:47 -0400 Subject: [DogParkList] Logging from MacDoppler In-Reply-To: <4825E4A2-C2C5-4E84-A086-47C23231CD51@telus.net> References: <4825E4A2-C2C5-4E84-A086-47C23231CD51@telus.net> Message-ID: <8135775C-45F6-41EE-922F-5E496BFB4994@dogparksoftware.com> Hi Roger, On 9-Apr-08, at 1:21 PM, Roger Swickis wrote: > However, nothing appears in the MacL preferences window under Log. > I can't find a file where MacD has sent the log info. One post > suggests to look in the "MacDoppler Folder". I do not have a > "MacDoppler Folder". Am I supposed to create one? Does it happen > automatically? If sohere might it be? log.dat is created in the same folder as MacDoppler once you log your first contact. Select the folder that MacDoppler is in from the MacLoggerDX preferences Files/ Logs popup "add" MacLoggerDX will then edit/add/display your satellite QSO's When you want to switch back to your HF contacts use the same popup. 73 Don Agro VE3VRW From M0XDF at Alphadene.co.uk Wed Apr 9 14:19:27 2008 From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF) Date: Wed, 9 Apr 2008 19:19:27 +0100 Subject: [DogParkList] K3 Power Out In-Reply-To: References: Message-ID: <2DCA3640-F67B-4F55-9A03-36E70431DB9D@Alphadene.co.uk> kinda both, its the way the K3 reports it and that MLDX doesn't expect a rig to report in decimals - Don is aware of it, but I don't remember his exact response to me. I said I didn't think it important enough to drag him away from the cocoa MLDX -- The secret of life is honesty and fair dealing. If you can fake that, you've got it made. -Groucho Marx On 9 Apr 2008, at 18:17, John Graf wrote: > > This last weekend I participated briefly in the ARCI QRP contest. I > was using my new K3/100 and had the "report power" box checked in > the preference pane. > > What I discovered is that when the K3 is dialed down to 5.0 watts, > the reported power in MDLX shows up as 050 as opposed to 005. Is > that a problem with MDLX or with the K3? From wa6l at mac.com Wed Apr 9 14:25:21 2008 From: wa6l at mac.com (John Graf) Date: Wed, 9 Apr 2008 11:25:21 -0700 Subject: [DogParkList] K3 Power Out In-Reply-To: <2DCA3640-F67B-4F55-9A03-36E70431DB9D@Alphadene.co.uk> References: <2DCA3640-F67B-4F55-9A03-36E70431DB9D@Alphadene.co.uk> Message-ID: <55C1F4B1-8A13-4B36-9755-53875C39F065@mac.com> Thanks, David. I agree with your analysis -- not terribly important! On Apr 9, 2008, at 11:19 AM, David Ferrington, M0XDF wrote: > kinda both, its the way the K3 reports it and that MLDX doesn't > expect a rig to report in decimals - Don is aware of it, but I don't > remember his exact response to me. > I said I didn't think it important enough to drag him away from the > cocoa MLDX > -- > The secret of life is honesty and fair dealing. If you can fake that, > you've got it made. -Groucho Marx > > On 9 Apr 2008, at 18:17, John Graf wrote: >> >> This last weekend I participated briefly in the ARCI QRP contest. >> I was using my new K3/100 and had the "report power" box checked in >> the preference pane. >> >> What I discovered is that when the K3 is dialed down to 5.0 watts, >> the reported power in MDLX shows up as 050 as opposed to 005. Is >> that a problem with MDLX or with the K3? > From lee at ww2dx.com Wed Apr 9 16:58:30 2008 From: lee at ww2dx.com (Lee (WW2DX)) Date: Wed, 9 Apr 2008 16:58:30 -0400 Subject: [DogParkList] MLDX Ideas for the future Message-ID: Hi All, been using MLDX for a while now and I have put together a list of observations thus far. Since I see see Don is working on a new cocoa version of MLDX ( yay) perhaps this is a good time to place some feedback. This list is in no particular order. I just added them when I thought or ran across them. Also I apologize up front if some of these features are already in MLDX and I just did not find them. Long Path Azimuth reading - Currently short path azimuth reading is shown when a call or prefix is looked up. Would be way cool to maybe click on the AZ box and have it switch to the LP AZ and highlight in some other color so you know it's LP. AWARDS: Track WAS by Band. Display shows when a new grid is being worked (call lookup lets you know its a new grid on that band) - I find that during a 6m opening I will do a call lookup of a distant station. I then have to navigate to awards -> VUCC -> then look and see if the grid is needed. Perhaps that when a lookup is done, and since the grid is shown in the lookup results, MLDX looks at the freq and then compares with the current grid worked data. If it is not in that list the Grid field changes color or some event happens to let you know instantly that it is a new one. Same for DXCC/WAS/ etc. I find that when I see a DX station come up on the cluster I have to go to Awards the enter the band and then search down the list to see if I have worked it and where I need it. It would be great if there was a field that in the main view where it showed what bands where needed for that entry. Way back in the day when I used hyperlog it had a nice band map that looked like something like this: - I would put his feature way up on my list of what I look for most. --------------------------------------- - 160 80 40 30 20 15 10 6 - ssb - C W - cw - C W C - -------------------------------------- WAC award tracking 5bwac WAS/WAC/DXCC by band 5BWAS/etc/etc/ WAZ / Track each WAZ award. http://www.cq-amateur-radio.com/wazrules.html It would be nice for all of us paper chasers :) - I don't know how popular award chasing is today. Use to be a big deal when I was a kid. As a paper chaser these are just things to keep me organized. DX Cluster: When a new or unconfirmed dxcc/state/vucc etc shows up mldx changes the color of the spot to let you know either not conformed or not worked depending on color. I don't know if this is possible, but I thought it would be sweet that as dx spots popped up, MLDX would grep the prefix and see if it is a new one. If so, some color for NEW and some other color for NOT confirmed. Other Features: Support for Icom 275H/475H When switching modes that require a particular RST have MLDX automatically change the RST appropriately. For instance, If you switch to CW change the RST field to 599/599, if you switch back to U/LSB auto change RST to 59/59. QSL SNT/RX I like the green/red but a 3rd color may be helpful when you RX a card but have not sent one yet. Electronic QSL services: The ability to automatically in real-time add QSO to eQSL and LOTW I believe eQSL does, not sure about LOTW. - Update, I think I have read someone here in the list that has a applescript to do this. Recording live QSO and saving to log: I know there are apple scripts but it would be cool to just click a record button in MLDX to start a recorder in the backgound then log the recording with the log entry. You could have a little play button in the log. Neat :) Multiple Rigs: Hot button on main page to switch to other rig. Also pre-set which rig gets which freq. Google Earth plotting. Have MLDX grep the LAT/LON from qrz and then be able to plot your Q's in Google Earth. I do this a lot for my VHF/UHF contests. For example: I had to export my log to Ham Radio Deluxe and use the export to google map function there (YUCK). http://www.ww2dx.com/Site/Blog/7539304B-36FA-4983-A9CE-659E0AD4C1A5.html Option to use Growl for DX cluster spots. Bug? Resizing the app after removing 23" cinema. - When I had one, there was a issue when I disconnected the cinema display the MLDX window stayed the same size on the native 15" TFT. I had to close and reopen MLDX to resize. OK, so that is what I have so far. I have to say that I really enjoy MLDX a lot. I also get countless compliments when I show the software to other non mac hams. Kudos to Don for a great software package and keeping with the true feel of what a MAC is and should be. Looking forward to the next release! I am open to any comments or thoughts anyone has about the above. 73 and CU in the pileups! de Lee WW2DX http://www.ww2dx.com MLDX/MBP/K3 - Does life get any better? :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From rprather at mac.com Wed Apr 9 18:08:05 2008 From: rprather at mac.com (Rick Prather) Date: Wed, 9 Apr 2008 15:08:05 -0700 Subject: [DogParkList] MLDX Ideas for the future In-Reply-To: References: Message-ID: <25353C5C-A3F2-4418-8452-8A46ACA372FA@mac.com> Lee, Your wants for cluster and database functions are nearly the same as mine. In my search for the functionality I want for my DXCC database I have looked in to several Windows logging programs (to quote you, YUCK) most of the OSX programs. I managed to find the LoTW and "need" aspects of most of what you want in a program called RUMLog by Tom DL2RUM. Since I am now using both RUMLog and MLDX I would be a very happy dude if Don is going to incorporate the database features that RUMLog has in to the new MLDX. The features I really enjoy are the "worked, confirmed" matrix that you mention but it also shows "worked, sent, exchanged status for not only paper QSL but also LoTW QSO's. At a glance you can see the status for both methods of QSL'ing in the three modes on all bands. Also, it has good LoTW integration in that you can generate a .tq8 file from any contact that shows worked but not sent. And, a feature I really like, you can have it check the ARRL server and download your confirmations and also change the status of the QSL automatically. A real time saver. I can also very easily generate reports of things like Countries confirmed on Paper only, on LoTW only or, my favorite, confirmed on LoTW only. As far as the cluster is concerned it's Telnet program is amazing. It will not only color code the countries you need or need confirmed but will also color code the mode and/ or band. So, in a separate window from the general minutia window you will see only the countries you are interested in with the mode/band/ or country in general indicated by color code. Very nice. Having said all, as I mentioned I now have to run both programs to get the functionality I want. MLDX is a much more complete and feature rich operating aid and also controls my rig. Whereas RUMLog is where I look for spots and award needs. Hence the rub, I constantly have to decide if I want the convenience of being able to double click a spot and have my radio go right to the Freq and mode or have the cluster sorting ability of RUMLog. For now I will use both and let my mood decide how to watch the cluster. Here's hoping that if Don hasn't already, he will take a look at Tom's logger and incorporate the best features of it in the new MLDX. Rick K6LE On Apr 9, 2008, at 1:58 PM, Lee (WW2DX) wrote: > > Hi All, been using MLDX for a while now and I have put together a > list of observations thus far. > Since I see see Don is working on a new cocoa version of MLDX ( yay) > perhaps this is a good time to > place some feedback. > > This list is in no particular order. I just added them when I > thought or ran across them. > Also I apologize up front if some of these features are already in > MLDX and I just did not find them. > > > > Long Path Azimuth reading > - Currently short path azimuth reading is shown when a call or > prefix is looked up. > Would be way cool to maybe click on the AZ box and have it switch > to the LP AZ and highlight in some other color > so you know it's LP. > > > AWARDS: > > Track WAS by Band. > > Display shows when a new grid is being worked (call lookup lets you > know its a new grid on that band) > - I find that during a 6m opening I will do a call lookup of a > distant station. I then have to navigate > to awards -> VUCC -> then look and see if the grid is needed. > Perhaps that when a lookup is done, > and since the grid is shown in the lookup results, MLDX looks at > the freq and then compares with > the current grid worked data. If it is not in that list the Grid > field changes color or some event happens > to let you know instantly that it is a new one. > > Same for DXCC/WAS/ etc. I find that when I see a DX station come up > on the cluster I have to go to > Awards the enter the band and then search down the list to see if I > have worked it and where I need it. > It would be great if there was a field that in the main view where > it showed what bands where needed for that entry. > Way back in the day when I used hyperlog it had a nice band map that > looked like something like this: > > - I would put his feature way up on my list of what I look for most. > > --------------------------------------- > - 160 80 40 30 20 15 10 6 - > ssb - C W - > cw - C W C - > -------------------------------------- > > > > WAC award tracking 5bwac > > WAS/WAC/DXCC by band 5BWAS/etc/etc/ > > WAZ / Track each WAZ award. > http://www.cq-amateur-radio.com/wazrules.html > It would be nice for all of us paper chasers :) > > - I don't know how popular award chasing is today. Use to be a big > deal when I was a kid. As a paper chaser > these are just things to keep me organized. > > DX Cluster: > When a new or unconfirmed dxcc/state/vucc etc shows up mldx changes > the color of the spot to let you know either not conformed or not > worked > depending on color. I don't know if this is possible, but I thought > it would be sweet that as dx spots popped up, MLDX would grep the > prefix and see if > it is a new one. If so, some color for NEW and some other color for > NOT confirmed. > > > Other Features: > > Support for Icom 275H/475H > > When switching modes that require a particular RST have MLDX > automatically change the RST appropriately. > For instance, If you switch to CW change the RST field to 599/599, > if you switch back to U/LSB auto change RST to 59/59. > > > QSL SNT/RX > I like the green/red but a 3rd color may be helpful when you RX a > card but have not sent one yet. > > > Electronic QSL services: > The ability to automatically in real-time add QSO to eQSL and LOTW > I believe eQSL does, not sure about LOTW. > > - Update, I think I have read someone here in the list that has a > applescript to do this. > > Recording live QSO and saving to log: > I know there are apple scripts but it would be cool to just click a > record button in MLDX to start a recorder in the backgound then log > the recording with the log entry. > You could have a little play button in the log. Neat :) > > > Multiple Rigs: > > Hot button on main page to switch to other rig. > Also pre-set which rig gets which freq. > > > Google Earth plotting. Have MLDX grep the LAT/LON from qrz and then > be able to plot your Q's in Google Earth. I do this a lot for my VHF/ > UHF contests. > For example: I had to export my log to Ham Radio Deluxe and use the > export to google map function there (YUCK). > > http://www.ww2dx.com/Site/Blog/7539304B-36FA-4983-A9CE-659E0AD4C1A5.html > > > Option to use Growl for DX cluster spots. > > > Bug? > > Resizing the app after removing 23" cinema. > - When I had one, there was a issue when I disconnected the cinema > display the MLDX window stayed the same size > on the native 15" TFT. I had to close and reopen MLDX to resize. > > > > OK, so that is what I have so far. I have to say that I really enjoy > MLDX a lot. I also get countless compliments when I show the > software to other non mac hams. Kudos to Don for a great software > package and keeping with the true feel of what a MAC is and should be. > > Looking forward to the next release! > > I am open to any comments or thoughts anyone has about the above. > > 73 and CU in the pileups! > > de Lee > WW2DX > http://www.ww2dx.com > > MLDX/MBP/K3 - Does life get any better? :) > > > > > > > _______________________________________________ > DogParkList mailing list > DogParkList at dogparksoftware.com > http://two.pairlist.net/mailman/listinfo/dogparklist -------------- next part -------------- An HTML attachment was scrubbed... URL: From greghemmings at hughes.net Wed Apr 9 18:08:35 2008 From: greghemmings at hughes.net (Greg Hemmings) Date: Wed, 9 Apr 2008 18:08:35 -0400 Subject: [DogParkList] MLDX Ideas Message-ID: <20080409180835871886.0d3c7427@hughes.net> Hi All, I love the ideas Lee submitted to Don. I would only add a request for some way to change the font size and color for those of us who wear bifocals! Seems like a small thing, but after hours of looking at that small type it really gets to me :)) Also, it would be REALLY cool to have a propagation button on MLDX that you could click and see forecast info relative to info in the station information box! Maybe work DXToolbox into MLDX somehow. Greg Hemmings N4WVE www.n4wve.com From EZRhino at fastmovers.biz Wed Apr 9 18:12:26 2008 From: EZRhino at fastmovers.biz (EZ Rhino) Date: Wed, 9 Apr 2008 16:12:26 -0600 Subject: [DogParkList] MLDX Ideas for the future Message-ID: <000f01c89a8e$cbdd4a50$0300a8c0@chriscomputer> Great suggestions, Lee. I second your thoughts, particularly the band/mode "graph". The google earth feature is really neat (I followed your link). Sometimes I look at the wonderful map built into MLDX and wish it was a political map, ie, shows country/state etc. borders. I'm sure greatful to Don for making such a good logging program, because if it wasn't there I would have had to buy a PC. :-) Chris KF7P ----- Original Message ----- From: Lee (WW2DX) To: DogParkList MacLogger Sent: Wednesday, April 09, 2008 2:58 PM Subject: [DogParkList] MLDX Ideas for the future Hi All, been using MLDX for a while now and I have put together a list of observations thus far. Since I see see Don is working on a new cocoa version of MLDX ( yay) perhaps this is a good time to place some feedback. This list is in no particular order. I just added them when I thought or ran across them. Also I apologize up front if some of these features are already in MLDX and I just did not find them. Long Path Azimuth reading - Currently short path azimuth reading is shown when a call or prefix is looked up. Would be way cool to maybe click on the AZ box and have it switch to the LP AZ and highlight in some other color so you know it's LP. AWARDS: Track WAS by Band. Display shows when a new grid is being worked (call lookup lets you know its a new grid on that band) - I find that during a 6m opening I will do a call lookup of a distant station. I then have to navigate to awards -> VUCC -> then look and see if the grid is needed. Perhaps that when a lookup is done, and since the grid is shown in the lookup results, MLDX looks at the freq and then compares with the current grid worked data. If it is not in that list the Grid field changes color or some event happens to let you know instantly that it is a new one. Same for DXCC/WAS/ etc. I find that when I see a DX station come up on the cluster I have to go to Awards the enter the band and then search down the list to see if I have worked it and where I need it. It would be great if there was a field that in the main view where it showed what bands where needed for that entry. Way back in the day when I used hyperlog it had a nice band map that looked like something like this: - I would put his feature way up on my list of what I look for most. --------------------------------------- - 160 80 40 30 20 15 10 6 - ssb - C W - cw - C W C - -------------------------------------- WAC award tracking 5bwac WAS/WAC/DXCC by band 5BWAS/etc/etc/ WAZ / Track each WAZ award. http://www.cq-amateur-radio.com/wazrules.html It would be nice for all of us paper chasers :) - I don't know how popular award chasing is today. Use to be a big deal when I was a kid. As a paper chaser these are just things to keep me organized. DX Cluster: When a new or unconfirmed dxcc/state/vucc etc shows up mldx changes the color of the spot to let you know either not conformed or not worked depending on color. I don't know if this is possible, but I thought it would be sweet that as dx spots popped up, MLDX would grep the prefix and see if it is a new one. If so, some color for NEW and some other color for NOT confirmed. Other Features: Support for Icom 275H/475H When switching modes that require a particular RST have MLDX automatically change the RST appropriately. For instance, If you switch to CW change the RST field to 599/599, if you switch back to U/LSB auto change RST to 59/59. QSL SNT/RX I like the green/red but a 3rd color may be helpful when you RX a card but have not sent one yet. Electronic QSL services: The ability to automatically in real-time add QSO to eQSL and LOTW I believe eQSL does, not sure about LOTW. - Update, I think I have read someone here in the list that has a applescript to do this. Recording live QSO and saving to log: I know there are apple scripts but it would be cool to just click a record button in MLDX to start a recorder in the backgound then log the recording with the log entry. You could have a little play button in the log. Neat :) Multiple Rigs: Hot button on main page to switch to other rig. Also pre-set which rig gets which freq. Google Earth plotting. Have MLDX grep the LAT/LON from qrz and then be able to plot your Q's in Google Earth. I do this a lot for my VHF/UHF contests. For example: I had to export my log to Ham Radio Deluxe and use the export to google map function there (YUCK). http://www.ww2dx.com/Site/Blog/7539304B-36FA-4983-A9CE-659E0AD4C1A5.html Option to use Growl for DX cluster spots. Bug? Resizing the app after removing 23" cinema. - When I had one, there was a issue when I disconnected the cinema display the MLDX window stayed the same size on the native 15" TFT. I had to close and reopen MLDX to resize. OK, so that is what I have so far. I have to say that I really enjoy MLDX a lot. I also get countless compliments when I show the software to other non mac hams. Kudos to Don for a great software package and keeping with the true feel of what a MAC is and should be. Looking forward to the next release! I am open to any comments or thoughts anyone has about the above. 73 and CU in the pileups! de Lee WW2DX http://www.ww2dx.com MLDX/MBP/K3 - Does life get any better? :) ------------------------------------------------------------------------------ _______________________________________________ DogParkList mailing list DogParkList at dogparksoftware.com http://two.pairlist.net/mailman/listinfo/dogparklist -------------- next part -------------- An HTML attachment was scrubbed... URL: From halmueller at mac.com Wed Apr 9 18:50:18 2008 From: halmueller at mac.com (Hal Mueller) Date: Wed, 9 Apr 2008 15:50:18 -0700 Subject: [DogParkList] font size (was Re: MLDX Ideas) In-Reply-To: <20080409180835871886.0d3c7427@hughes.net> References: <20080409180835871886.0d3c7427@hughes.net> Message-ID: You can zoom the screen by holding down the control key and moving your mouse scrollwheel up or down, or dragging up or down on the trackpad. You can also change the screen resolution to something coarser. Hal From M0XDF at Alphadene.co.uk Wed Apr 9 18:52:52 2008 From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF) Date: Wed, 9 Apr 2008 23:52:52 +0100 Subject: [DogParkList] MLDX Ideas In-Reply-To: <20080409180835871886.0d3c7427@hughes.net> References: <20080409180835871886.0d3c7427@hughes.net> Message-ID: I've asked Black Cat systems to provide AppleScript support in DXToolbox for that very purpose. -- Patience serves as a protection against wrongs as clothes do against cold. For if you put on more clothes as the cold increases, it will have no power to hurt you. So in like manner you must grow in patience when you meet with great wrongs, and they will then be powerless to vex your mind. -Leonardo da Vinci, painter, engineer, musician, and scientist (1452-1519) On 9 Apr 2008, at 23:08, Greg Hemmings wrote: > Hi All, > > I love the ideas Lee submitted to Don. I would only add a request > for some way to change the font size and color for those of us who > wear > bifocals! Seems like a small thing, but after hours of looking at > that > small type it really gets to me :)) > Also, it would be REALLY cool to have a propagation button on MLDX > that you could click and see forecast info relative to info in the > station information box! Maybe work DXToolbox into MLDX somehow. From rswickis at telus.net Thu Apr 10 18:52:14 2008 From: rswickis at telus.net (Roger Swickis) Date: Thu, 10 Apr 2008 15:52:14 -0700 Subject: [DogParkList] Using Two Callsigns Message-ID: <9FCCF3ED-7A0C-44BF-9AEF-5CEFCA042405@telus.net> Dear Folks, I purchased MacLogger with the understanding that it allowed the use of more than one callsign. My pre purchase concern related to the fact that (as I understand it) if I were to upload data from Maclogger to LoTW a callsign match would be done, using a call corresponding to my Macdoppler registered callsign. (The one appearing after the word "Registered" on the main page.) Presumably this could be a problem. Can anyone out there confirm that this is the case? I have already registered with one callsign, but unfortunately the information I would like to upload at the moment is contact information from my other callsign. Don Agro has advised that I merely have to change the information in the station info box to enable the other callsign, but it doesn't seem to be working that way for me. When I attempt to create another log with my alternate callsign I am immediately advised that my demonstration time has expired and I am asked if I would like to register. This happens even if I type in the other call and retype the registration number in the info panel. Am I the only one experiencing this problem? Does anyone out there have any suggestions? Thanks, Rog VA7MG/VE7BZR From rprather at mac.com Thu Apr 10 19:06:54 2008 From: rprather at mac.com (Rick Prather) Date: Thu, 10 Apr 2008 16:06:54 -0700 Subject: [DogParkList] Using Two Callsigns In-Reply-To: <9FCCF3ED-7A0C-44BF-9AEF-5CEFCA042405@telus.net> References: <9FCCF3ED-7A0C-44BF-9AEF-5CEFCA042405@telus.net> Message-ID: <9A8CA4CB-6787-4F7F-9853-4249CD93CB46@mac.com> Roger, The determining factor for the callsign that is used in LoTW is the callsign/location you sign the file with when generating the .tq8 file in TQSL for upload. I have MLDX registered using my current call but I extract QSO's for uploading to LoTW using four different callsigns from the past. I just have to make sure that any one upload file is for only one callsign. Rick K6LE On Apr 10, 2008, at 3:52 PM, Roger Swickis wrote: > Dear Folks, > > I purchased MacLogger with the understanding that it allowed the use > of more than one callsign. > > > My pre purchase concern related to the fact that (as I understand > it) if I were to upload data from Maclogger to LoTW a callsign match > would be done, using a call corresponding to my Macdoppler > registered callsign. (The one appearing after the word "Registered" > on the main page.) Presumably this could be a problem. Can anyone > out there confirm that this is the case? > > > > I have already registered with one callsign, but unfortunately the > information I would like to upload at the moment is contact > information from my other callsign. > > Don Agro has advised that I merely have to change the information in > the station info box to enable the other callsign, but it doesn't > seem to be working that way for me. > > When I attempt to create another log with my alternate callsign I am > immediately advised that my demonstration time has expired and I am > asked if I would like to register. This happens even if I type in > the other call and retype the registration number in the info panel. > > Am I the only one experiencing this problem? Does anyone out there > have any suggestions? > > Thanks, > > Rog VA7MG/VE7BZR > _______________________________________________ > DogParkList mailing list > DogParkList at dogparksoftware.com > http://two.pairlist.net/mailman/listinfo/dogparklist From dagro at dogparksoftware.com Thu Apr 10 19:08:35 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Thu, 10 Apr 2008 19:08:35 -0400 Subject: [DogParkList] Using Two Callsigns In-Reply-To: <9FCCF3ED-7A0C-44BF-9AEF-5CEFCA042405@telus.net> References: <9FCCF3ED-7A0C-44BF-9AEF-5CEFCA042405@telus.net> Message-ID: Hi Roger, On Apr 10, 2008, at 18:52 , Roger Swickis wrote: > I purchased MacLogger with the understanding that it allowed the use > of more than one callsign. As many on the list can attest, I routinely issue new registration numbers for changed/additional call signs, but it would probably better if you emailed me personally and asked for this courtesy. > My pre purchase concern related to the fact that (as I understand > it) if I were to upload data from Maclogger to LoTW a callsign match > would be done, using a call corresponding to my Macdoppler > registered callsign. (The one appearing after the word "Registered" > on the main page.) Presumably this could be a problem. Can anyone > out there confirm that this is the case? > > I have already registered with one callsign, but unfortunately the > information I would like to upload at the moment is contact > information from my other callsign. > > Don Agro has advised that I merely have to change the information in > the station info box to enable the other callsign, but it doesn't > seem to be working that way for me. No, you need a registration number or each call sign with the exception or /P /MM suffixes etc. > When I attempt to create another log with my alternate callsign I am > immediately advised that my demonstration time has expired and I am > asked if I would like to register. This happens even if I type in > the other call and retype the registration number in the info panel. > > Am I the only one experiencing this problem? Does anyone out there > have any suggestions? > > Thanks, > > Rog VA7MG/VE7BZR 73 Don Agro VE3VRW From rswickis at telus.net Thu Apr 10 23:55:48 2008 From: rswickis at telus.net (Roger Swickis) Date: Thu, 10 Apr 2008 20:55:48 -0700 Subject: [DogParkList] Two Callsigns Message-ID: Dear Don, On April 8 I did in fact send a message to you personally asking for information on how to handle two callsigns. You forwarded me the information on how to do this omitting the important fact that in order to do this I would require another registration number from you. I therefore thought that by carrying out your instructions and being unable to get the program to work as you described, that I must be doing something wrong. Only then did I forward a request to the mailing list for help. Now that I have ascertained that an additional registration number is required, and have now, as a result of my post to the mailing list, been forwarded one by you, I too can now attest that new registration numbers can be obtained for additional call signs. As for it being a 'courtesy', I recall being assured by you prior to my purchase of MacLogger that I could indeed use more than one callsign. I would thus call your giving me the necessary information for me to make that happen and to meet that commitment, to be part of the deal. 73, Rog VA7MG/VE7BZR From rswickis at telus.net Fri Apr 11 01:36:53 2008 From: rswickis at telus.net (Roger Swickis) Date: Thu, 10 Apr 2008 22:36:53 -0700 Subject: [DogParkList] Logging from MacDoppler Message-ID: Hello Folks, Re my earlier problem on Logging from MacDoppler. After much poking around I found that the 'log.dat' file created by MacDoppler does autuomatically save the file to 'the MacDoppler folder' as stated in the manual, but it saves it in my 'Applications Folder'. So, problem solved, sort of. I don't suppose there is a way of changing where MacDoppler puts that file, at least it's not evident to me. So I guess I'll hafta figure out a way to move the 'log.dat' file to a more logical location using OSX. Any suggestions? Rog VA7MG From rswickis at telus.net Fri Apr 11 01:48:32 2008 From: rswickis at telus.net (Roger Swickis) Date: Thu, 10 Apr 2008 22:48:32 -0700 Subject: [DogParkList] Fwd: Logging from MacDoppler References: Message-ID: <1EAC84C0-BC95-43EE-9F7F-1150FC89E5B6@telus.net> Corrected version > > Hello Folks, > > Re my earlier problem on Logging from MacDoppler. > > After much poking around I found that the 'log.dat' file created by > MacDoppler does NOT automatically save the file to 'the MacDoppler > folder' as stated in the manual, but it saves it in my > 'Applications Folder'. > > So, problem solved, sort of. > > I don't suppose there is a way of changing where MacDoppler puts > that file, at least it's not evident to me. So I guess I'll hafta > figure out a way to move the 'log.dat' file to a more logical > location using OSX. > > Any suggestions? > > Rog VA7MG > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dagro at dogparksoftware.com Fri Apr 11 06:01:30 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Fri, 11 Apr 2008 06:01:30 -0400 Subject: [DogParkList] Fwd: Logging from MacDoppler In-Reply-To: <1EAC84C0-BC95-43EE-9F7F-1150FC89E5B6@telus.net> References: <1EAC84C0-BC95-43EE-9F7F-1150FC89E5B6@telus.net> Message-ID: On Apr 11, 2008, at 01:48 , Roger Swickis wrote: > After much poking around I found that the 'log.dat' file created by > MacDoppler does NOT automatically save the file to 'the MacDoppler > folder' as stated in the manual, but it saves it in my 'Applications > Folder'. It saves it to the folder MacDoppler is in - in your case this happens to be the Applications folder but you could put it in any folder and that would then become the MacDoppler folder. The manual is correct, you just didn't understand it, and for that I apologize. 73 Don Agro VE3VRW From dagro at dogparksoftware.com Fri Apr 11 06:29:27 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Fri, 11 Apr 2008 06:29:27 -0400 Subject: [DogParkList] Fwd: Logging from MacDoppler In-Reply-To: <1EAC84C0-BC95-43EE-9F7F-1150FC89E5B6@telus.net> References: <1EAC84C0-BC95-43EE-9F7F-1150FC89E5B6@telus.net> Message-ID: On Apr 11, 2008, at 01:48 , Roger Swickis wrote: I don't suppose there is a way of changing where MacDoppler puts that file, at least it's not evident to me. So I guess I'll hafta figure out a way to move the 'log.dat' file to a more logical location using OSX. Simply "Add" your Applications folder to the "Files/Logs" popup in the MacLoggerDX Prefs panel and then use that popup to instantly switch between your HF and Satellite logs. 73 Don Agro VE3VRW From ki4gks at gmail.com Fri Apr 11 07:28:19 2008 From: ki4gks at gmail.com (Ed Tyler) Date: Fri, 11 Apr 2008 06:28:19 -0500 Subject: [DogParkList] Improvements to MacLoggerDX Message-ID: Don, I would like to see increased support for contesting. 1st adding features to support phone and cw and then rtty, psk31 and other digital modes. Support does not mean that it would need to directly support the mode but that it could capture necessary information from another software package and log it automatically. The first and most obvious portions of this support would be the ability to suppress the display of unnecessary information and provide some assistance and/or flexibility in logging exchanges. Much of this may already exist and I just don't know how to configure the software. Overall, having used some logging programs on windows units I truly beleive that MacLogger DX sells Macs to Amateur radio. My windows using Ham friends are always amazed at what functions MacLogger DX has and the stability of the program. ED -- KI4GKS Ed Tyler From g.berges at bergesetco.com Sat Apr 12 14:20:01 2008 From: g.berges at bergesetco.com (Gustavo Berges) Date: Sat, 12 Apr 2008 14:20:01 -0400 Subject: [DogParkList] Question mark in zone field Message-ID: Greetings and salutations: Does anyone know where the question mark is generated from in the zone field and if a script exists to tell MacLogger not to announce a zone as not in the log when there is a question mark in this field? If you set the DX Speech alarm for CQ Zone, and there?s a lot of activity, it?s always ?announcing? but in reality the zones are confirmed, it?s just that a question mark appears in the field. It?s still the greatest Mac program for this application in existence! -- Gustavo Berg?s, NU4L 1820 NE Jensen Beach Blvd. #623 Jensen Beach, Florida 34957 (772) 419 8015 Ph./(772) 382 0209 Fx -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From M0XDF at Alphadene.co.uk Sun Apr 13 04:35:19 2008 From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF) Date: Sun, 13 Apr 2008 09:35:19 +0100 Subject: [DogParkList] MLDX did not allow for BSt Message-ID: Is it possible that when we put our clocks forward, MLDX would not allow for that until it was restarted? I took a contest just after the weekend we put the clocks forward and I hadn't realised, all the logged QSOs where in BST and not UTC. But MLDX is showing UTC now (I've rebooted since the contest). So wondering if you need to restart MLDX after such a change? -- Now, here, you see, it takes all the running you can do, to keep in the same place. If you want to get somewhere else, you must run at least twice as fast as that! -Lewis Carroll, mathematician and writer (1832-1898) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dagro at dogparksoftware.com Sun Apr 13 10:10:48 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Sun, 13 Apr 2008 10:10:48 -0400 Subject: [DogParkList] MLDX did not allow for BSt In-Reply-To: References: Message-ID: <663D7CB5-181B-4D32-8A14-10DF3FC08109@dogparksoftware.com> Hi David, On Apr 13, 2008, at 04:35 , David Ferrington, M0XDF wrote: > Is it possible that when we put our clocks forward, MLDX would not > allow for that until it was restarted? MacLoggerDX always assumes that your System clock is set to the correct local time for your location and calculates UTC based on that. > I took a contest just after the weekend we put the clocks forward > and I hadn't realised, all the logged QSOs where in BST and not UTC. > But MLDX is showing UTC now (I've rebooted since the contest). > So wondering if you need to restart MLDX after such a change? 73 Don Agro VE3VRW D o g P a r k S o f t w a r e L t d . email: dagro at dogparksoftware.com www: http://www.dogparksoftware.com iChat AV:dogpark at mac.com From M0XDF at Alphadene.co.uk Sun Apr 13 14:19:02 2008 From: M0XDF at Alphadene.co.uk (David Ferrington, M0XDF) Date: Sun, 13 Apr 2008 19:19:02 +0100 Subject: [DogParkList] MLDX did not allow for BSt In-Reply-To: <663D7CB5-181B-4D32-8A14-10DF3FC08109@dogparksoftware.com> References: <663D7CB5-181B-4D32-8A14-10DF3FC08109@dogparksoftware.com> Message-ID: <9C851A78-204A-45A7-98AC-A39240E68E71@Alphadene.co.uk> It was and is set to correct local time etc - just that the logged QSOs were an hour out. -- Many ideas grow better when transplanted into another mind than in the one where they sprang up. -Oliver Wendell Holmes, Jr., US Supreme Court Justice (1841-1935) On 13 Apr 2008, at 15:10, Don Agro wrote: > Hi David, > > On Apr 13, 2008, at 04:35 , David Ferrington, M0XDF wrote: > >> Is it possible that when we put our clocks forward, MLDX would not >> allow for that until it was restarted? > > MacLoggerDX always assumes that your System clock is set to the > correct local time for your location and calculates UTC based on that. > >> I took a contest just after the weekend we put the clocks forward >> and I hadn't realised, all the logged QSOs where in BST and not >> UTC. But MLDX is showing UTC now (I've rebooted since the contest). >> So wondering if you need to restart MLDX after such a change? > > 73 Don Agro VE3VRW > > D o g P a r k S o f t w a r e L t d . > > email: dagro at dogparksoftware.com > www: http://www.dogparksoftware.com > iChat AV:dogpark at mac.com > _______________________________________________ > DogParkList mailing list > DogParkList at dogparksoftware.com > http://two.pairlist.net/mailman/listinfo/dogparklist From ea2ry at ea2ry.com Sun Apr 13 15:31:08 2008 From: ea2ry at ea2ry.com (Roberto) Date: Sun, 13 Apr 2008 21:31:08 +0200 Subject: [DogParkList] MLDX Without CAT Message-ID: Someone can explain how to use the MLDX without using the CAT of the transceiver? Is this possible? Because it does not mark the frequency or squeeze left hand. If possible I would like to know how it is To Don: You know if some day we may use the "?H Router" with MLDX? ;-) 73's de Roberto EA2RY FG/EA2RY CT9R EA2RY/HI7 S?1R 9X?R http://www.ea2ry.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dagro at dogparksoftware.com Sun Apr 13 15:48:20 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Sun, 13 Apr 2008 15:48:20 -0400 Subject: [DogParkList] MLDX Without CAT In-Reply-To: References: Message-ID: <6D1AE3BC-D2E8-4FEB-A3D4-B72B0CD4FE39@dogparksoftware.com> On Apr 13, 2008, at 15:31 , Roberto wrote: > To Don: You know if some day we may use the "?H Router" with > MLDX? ;-) It's not currently possible but may be in the cocoa version. 73 Don Agro VE3VRW -------------- next part -------------- An HTML attachment was scrubbed... URL: From dagro at dogparksoftware.com Sun Apr 13 16:21:10 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Sun, 13 Apr 2008 16:21:10 -0400 Subject: [DogParkList] Notes from the skunkworks - MacLoggerDX for Cocoa Message-ID: <0C10142A-0683-4135-B075-FEE14E67DFE1@dogparksoftware.com> Work on MacLoggerDX for Cocoa continues but still no release date. All the preliminary R&D has been done and coding begun some months ago. The current MacLoggerDX (v4.3.5 beta) is now feature and UI frozen but bugs will continue to be fixed and radio drivers added where possible. The reason for this freeze is that I am currently spending more than 95% of my time on supporting the existing products and this leaves very little time for me to work on the cocoa version. MacLoggerDX for cocoa will use the same radio drivers as the current MacLoggerDX but will use core data and SQL for the log database. This will allow much better response time for those really big logs. As soon as the prototype is feature complete some screen shots will be posted. Beta will be public and there will be an upgrade path for existing 3.5 registrations. To help me correlate feature requests for the new version please include "MacLoggerDX for Cocoa" in the subject line of your emails. Feel free to post them to either the dogpark list or the Yahoo group. I have no objection to animated discussions about these requests and I will be reading every one of them but due to time constraints won't be able to respond to them. I would also ask the more experienced users to continue the great job they have been doing helping the newer members on the lists. There is still a long way to go but I truly appreciate your continuing input and support. 73 Don Agro VE3VRW From dagro at dogparksoftware.com Sun Apr 27 10:59:34 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Sun, 27 Apr 2008 10:59:34 -0400 Subject: [DogParkList] MacDoppler for Cocoa 2.0.5 Released. Message-ID: <863831CF-279C-4290-BE0C-4088DCF7AD5C@dogparksoftware.com> MacDoppler for Cocoa 2.0.5 Released. Satellite tracking software for Macintosh. Dog Park Software is pleased to announce that version 2.0.5 MacDoppler for Cocoa has been released and a free demo can be downloaded from: --------------------------------------------------------------------------- What's New in this release ? * Full screen fixed for dual screen systems. * Fix for duplicated sats in AMSAT keps. * Alpha-Spid native 1.0 & 0.5 degree drivers added. * AO-16 Channel 1 mode fixed. * Added Rotor Command Delay. * Added M2 AzEl Driver. --------------------------------------------------------------------------- Screen shots: MacDoppler for Cocoa was re-written from the ground up to take full advantage of all the great Cocoa capabilities in OS X on PPC as well as Intel hardware. MacDoppler will provide any level of station automation you need from assisted Doppler Tuning and Antenna Pointing right on up to fully automated Satellite Gateway operation. MacDoppler for Cocoa carries on the rich tradition pioneered by MacDopplerPRO which is in use around the world by Amateur Radio operators, satellite spotters, educators and commercial customers from CBS News to the International Space Station Amateur Radio Hardware Management program, Delta Telemetry Tracking and Control at Integrated Defense Systems, Florida State University and the CalPoly CubeSat Project. MacDoppler features: * Runs under OS X 10.4 (Tiger) and 10.5 (Leopard) as a Universal Binary on Intel or PPC hardware. * Full 2D and 3D OpenGL projection model of earth. * Track List sorted in real-time order of next pass. * Full predictive dead spot crossing so that a pass is never interrupted by the beam heading passing a dead spot. * Speech advisory of next satellite AOS and Maximum Elevation. * Horizon Window shows elevation of upcoming passes on a time line. * Tuning Dial Tracking allows you to tune the downlink from your radio's front panel while MacDopplerPRO X automatically adjusts the uplink. --------------------------------------------------------------------------- MacDoppler for Cocoa must be registered for some features to work and to work beyond the 5 minute time limit. This is a free upgrade for all MacDoppler for Cocoa Registered users. --------------------------------------------------------------------------- 73 Don Agro VE3VRW D o g P a r k S o f t w a r e L t d . email: dagro at dogparksoftware.com www: http://www.dogparksoftware.com iChat AV:dogpark at mac.com From EZRhino at fastmovers.biz Fri May 9 11:32:43 2008 From: EZRhino at fastmovers.biz (EZ Rhino) Date: Fri, 9 May 2008 09:32:43 -0600 Subject: [DogParkList] CW keyer in MLDX Message-ID: Group: Anyone here use MLDX Keyer for CW? I have been messing around with it in prep for the FISTS spring sprint tomorrow. I can get it to work fine, except for one little thing. I created my own Macro in the CWMacros file to send the exchange. I use "@RST" to send the RST as it is typed in the field. But when I hit the CW button to send the exchange, the keyer function doesn't send the RST as it is entered. It sends the previous RST. So in other words, if I change the RST for the next contact, it doesn't change. I can hit "done" and close the keyer box, and reopen it, and it works, but then on the next contact it sends the previous RST. Any ideas? Chris KF7P From dagro at dogparksoftware.com Fri May 9 18:54:54 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Fri, 9 May 2008 18:54:54 -0400 Subject: [DogParkList] Dayton In-Reply-To: References: Message-ID: Hi Jeff, On May 9, 2008, at 18:13 , Swiger, Jeffrey M. wrote: > Thanks Don, I read the manual about the AWARD PANE, but missed this > one!.. Arghhh.... > Lots of manual stuff to do now and just got a package from the > bureau with 30+ cards today.. > My mistake in not reading, as the adage goes "RTFM"?.. No problem Jeff, there is a lot of stuff in there and I forget where some of it is sometimes :) > Hope to see you in Dayton this year also. I'll be there. Hopefully we can get our usual seats at the Pub Friday at 3:00 pm. Otherwise I will be at the AMSAT booth with MacDoppler Friday and Saturday at 2:00 pm. 73 Don Agro VE3VRW -------------- next part -------------- An HTML attachment was scrubbed... URL: From sjp at sjprior.fsnet.co.uk Sat May 31 05:10:39 2008 From: sjp at sjprior.fsnet.co.uk (Stephen Prior) Date: Sat, 31 May 2008 10:10:39 +0100 Subject: [DogParkList] Reading K3 mode in psk In-Reply-To: Message-ID: I don?t know whether I?m doing something wrong, but when I?m in Data A mode on the K3 (running psk31 for example from cocoamodem), MacloggerDX interprets this mode as CW-R. Now there may be something I can tweak somewhere in Maclogger but I haven?t found it! Thanks Stephen G4SJP -------------- next part -------------- An HTML attachment was scrubbed... URL: From ki4gks at gmail.com Sat May 31 10:18:29 2008 From: ki4gks at gmail.com (Ed Tyler) Date: Sat, 31 May 2008 09:18:29 -0500 Subject: [DogParkList] Posting to DX Clusters. Message-ID: Mac logger has all of the function necessary to allow an operator to post to a dx cluster in the terminal mode. Would it be possible to link the terminal input to the actual logging process so that they would be uploaded when the log entry was made? Ed -- KI4GKS Ed Tyler From nealk3nc at gmail.com Sat May 31 10:25:03 2008 From: nealk3nc at gmail.com (Neal Campbell) Date: Sat, 31 May 2008 10:25:03 -0400 Subject: [DogParkList] Posting to DX Clusters. In-Reply-To: References: Message-ID: <325413300805310725o3c4ce8e7t1ba3dae11cf3819@mail.gmail.com> Ed As a DXCluster sysop, I would not think that is such a great idea. More than likely, people work the stations that they see spotted so just automatically spotting them again would not be a good practise. 73 Neal k3nc On Sat, May 31, 2008 at 10:18 AM, Ed Tyler wrote: > Mac logger has all of the function necessary to allow an operator to > post to a dx cluster in the terminal mode. Would it be possible to > link the terminal input to the actual logging process so that they > would be uploaded when the log entry was made? > > Ed > > > -- > KI4GKS > Ed Tyler > _______________________________________________ > DogParkList mailing list > DogParkList at dogparksoftware.com > http://two.pairlist.net/mailman/listinfo/dogparklist > -- Neal Campbell Abroham Neal Software Programming Services for Windows, OS X and Linux (540) 242 0911 --------------------------------------------------------------------- Try Spot for OS X, the intelligent DXCluster Client at www.abrohamnealsoftware.com - introduction priced at $10.99 For a great dog book, visit www.abrohamneal.com From dagro at dogparksoftware.com Sat May 31 11:24:59 2008 From: dagro at dogparksoftware.com (Don Agro) Date: Sat, 31 May 2008 11:24:59 -0400 Subject: [DogParkList] Posting to DX Clusters. In-Reply-To: References: Message-ID: <60B05C8A-6FC2-4258-BD35-C7EB83CE4525@dogparksoftware.com> Hi Ed, On May 31, 2008, at 10:18 , Ed Tyler wrote: > Mac logger has all of the function necessary to allow an operator to > post to a dx cluster in the terminal mode. Would it be possible to > link the terminal input to the actual logging process so that they > would be uploaded when the log entry was made? > > Ed I have intentionally not implemented auto posting to avoid accidental QRM-ing of the clusters. 73 Don Agro VE3VRW From jawod at fuse.net Tue Jun 3 15:39:54 2008 From: jawod at fuse.net (John Wiener) Date: Tue, 3 Jun 2008 15:39:54 -0400 Subject: [DogParkList] Clueless with Echolink Message-ID: <5B6639FD-4E94-45FC-B59E-BE5F255C5505@fuse.net> Hi I have an iMac with EchoMac but I have no idea how to set it up. After reading something about UDP ports 5198 and 5199, I realize I am out of my element, Is there a step-by-step method to activate Echolink on my Mac? Thanks John AB8O From rprather at mac.com Tue Jun 3 16:02:21 2008 From: rprather at mac.com (Rick Prather) Date: Tue, 03 Jun 2008 13:02:21 -0700 Subject: [DogParkList] Clueless with Echolink In-Reply-To: <5B6639FD-4E94-45FC-B59E-BE5F255C5505@fuse.net> References: <5B6639FD-4E94-45FC-B59E-BE5F255C5505@fuse.net> Message-ID: <382892CA-F72F-4532-BE17-88A22904FB1A@mac.com> Are you using a router? A firewall? If so which ones? Rick K6LE On Jun 3, 2008, at 12:39 PM, John Wiener wrote: > Hi > > I have an iMac with EchoMac but I have no idea how to set it up. > After reading something about UDP ports 5198 and 5199, I realize I > am out of my element, > Is there a step-by-step method to activate Echolink on my Mac? > > Thanks > > John > AB8O > _______________________________________________ > DogParkList mailing list > DogParkList at dogparksoftware.com > http://two.pairlist.net/mailman/listinfo/dogparklist From jawod at fuse.net Tue Jun 3 23:11:50 2008 From: jawod at fuse.net (John Wiener) Date: Tue, 3 Jun 2008 23:11:50 -0400 Subject: [DogParkList] Echolink Message-ID: <50A478FC-BAA1-459C-90CB-0D9CC7E8A61A@fuse.net> "Some routers try to automatically configure this forwarding based on outgoing data the router has seen from each of the computers behind it. This is often referred to as port triggering. You can try configuring the router to forward UDP ports 5198 and 5199 to the computer that most recently sent UDP traffic to remote ports 5198 or 5199, or TCP traffic on port 5200. (The EchoMac client always initiates the TCP connection on port 5200, so typically no special router configuration is necessary.)" I have no idea how to do this. My router is Linksys befw 11s4 ver 3 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dogparklist at dogparksoftware.com Thu Jun 5 01:33:59 2008 From: dogparklist at dogparksoftware.com (VIAGRA INC) Date: Thu, 5 Jun 2008 01:33:59 -0400 (EDT) Subject: [DogParkList] SALE 82% OFF Message-ID: <20080605123402.3435.qmail@Agent_isb> An HTML attachment was scrubbed... URL: From jim at lexiann.com Thu Jun 5 22:07:48 2008 From: jim at lexiann.com (James Snider) Date: Thu, 05 Jun 2008 22:07:48 -0400 Subject: [DogParkList] Cable problem/question Message-ID: I just bought a CT-17 USB cable from Valley Enterprises (http://valley-ent.com) and was wondering if anyone has any experience getting it to work with MacloggerDX? My rig is a IC-703+ It came with a cd with Windows drivers but no Mac stuff. I also sent an e-mail to Valley Ent too. Thanks Jim W8BS -- Jim Snider W8BS jim at lexiann.com NAQCC # 2054 FPQRP # 1198 QRPARCI # 12270 SKCC # 4002 YL # 16027 10-10 # 63607 From jawod at fuse.net Fri Jun 6 08:54:42 2008 From: jawod at fuse.net (John Wiener) Date: Fri, 6 Jun 2008 08:54:42 -0400 Subject: [DogParkList] Echolink now functioning Message-ID: <003C706C-6051-4CD5-B557-F631026CD449@fuse.net> Thanks for all the help in setting up my router. PortForward.com did the trick. At first I didn't think it was working...no audio...but just not too many people on at 8:30 am EDT BTW...what does the orange highlight on the listings signify? Thanks again John AB8O From jim at lexiann.com Fri Jun 6 19:38:29 2008 From: jim at lexiann.com (James Snider) Date: Fri, 06 Jun 2008 19:38:29 -0400 Subject: [DogParkList] Cable problem/question In-Reply-To: Message-ID: I found a driver and got it to work! Jim W8BS On 6/5/08 10:07 PM, "James Snider" wrote: > > > I just bought a CT-17 USB cable from Valley Enterprises > (http://valley-ent.com) and was wondering if anyone has any experience > getting it to work with MacloggerDX? My rig is a IC-703+ It came with a cd > with Windows drivers but no Mac stuff. I also sent an e-mail to Valley Ent > too. > > > > > Thanks > > Jim W8BS > -- Jim Snider W8BS jim at lexiann.com NAQCC # 2054 FPQRP # 1198 QRPARCI # 12270 SKCC # 4002 YL # 16027 10-10 # 63607 From jim at lexiann.com Sun Jun 8 10:04:30 2008 From: jim at lexiann.com (James Snider) Date: Sun, 08 Jun 2008 10:04:30 -0400 Subject: [DogParkList] Posting a spot to DX cluster Message-ID: I know that this was talked about earlier this week but what if there were a quick key combo that would post to the cluster? Not an automatic post what we log, just if we hit a certain key combination. Jim W8BS -- Jim Snider W8BS jim at lexiann.com NAQCC # 2054 FPQRP # 1198 QRPARCI # 12270 SKCC # 4002 YL # 16027 10-10 # 63607