开云体育

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the aprsisce group. File : /APRSISCE.TXT Uploaded by : ldeffenb <kj4erj@...> Description : APRS-IS Client Introduction You can access this file at the URL: http://groups.yahoo.com/group/aprsisce/files/APRSISCE.TXT To learn more about file sharing for your group, please visit: http://help.yahoo.com/l/us/yahoo/groups/original/members/web/index.htmlfiles Regards, ldeffenb <kj4erj@...>

Hey I have installed your software on my IPAQ 514 device (Windows mobile 6), the software runs and can contact the server to send and receive data. The GPS however is not built in on this device and I'm not able to get my bluethooth version working. How are the GPS handled in your software? Is it internally connected to a serialport or is there another solution? Kind regards David - SM3ULU

Hello OMs Is there aprsis for Blackberry? 73 de Wisnu YB0AZ Sent from my BlackBerry? smartphone from Sinyal Bagus XL, Nyambung Teruuusss...!

Hello, I recently had to reload everything and couldn't find my code. Was wondering if moderator could resend it to my email. Thank you, Michael KE5EUA

Greetings, Currently on my phones (all in family) the internet connection has been disabled. This has been doen to eliminate costs involved with general run-of-the-mill stuff like surfing, downloading songs, etc. I am curious if anyone knows the cost breakdown for running this software. Obvious the cost varies, so I guess I am really looking for how much data is passed/received per month. Thanks! Best regards, Fred

Just wanted to say hi to everyone and thanks for letting me join. Dave N8PU

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the aprsisce group. File : /APRSISCE6P090805.zip Uploaded by : ldeffenb <kj4erj@...> Description : Latest release with OpenStreetMap.org MAPS! You can access this file at the URL: http://groups.yahoo.com/group/aprsisce/files/APRSISCE6P090805.zip To learn more about file sharing for your group, please visit: http://help.yahoo.com/l/us/yahoo/groups/original/general.htmlfiles Regards, ldeffenb <kj4erj@...>

Beta Testers, Here's a stream of consciousness (actually a brain dump from my version control system) of what's new since January in APRSISCE (for Windows Mobile). 1) It generates a date/time-stamped CSV file in your Documents folder with all of the transmitted coordinates. It does this even if you have APRS-IS disabled. I used this to track myself when I was out of the country without phone/Internet services. Some day I'll make it an Enable. 2) If you add any b/Buddies to your filter text, they will be reverse-video'd when scrolling in the recent station list. 3) I now notice that the tracking in general is NEW! All stations that move will leave a single width black line behind themselves. You clear these with Menu/Clear Track or double-click the Odometer. 4) Secondary symbol table symbols now do overlays if specified by the client. This is NOT restricted to the subset that is documented, but is displayed on any symbol if so configured by the remote station. 5) Your last known good position is saved when the client is closed and recalled when you run it again. This means that the map will be displayed along with other stations' relative positions even before you get a new fix. 6) Scale factors have changed due to the OpenStreetMap implementation. You can actually zoom further out than before and if you zoom too far in, the maps will disappear and the circle will come back. The circle is also displayed if there are no maps currently loaded for the selected zoom level. Maps will appear when they finally begin arriving. 7) Objects are tracked by the originating call sign in addition to the object name itself. This helps avoid object ID collisions in a close geographic area, but it can generate extra objects if ownership is intentionally changed. 8) The path of the most recently heard packet for a station is remembered and displayed on the station popup. Object owners also appear here along with your configured APRS-IS server name if you click your own icon in the center. 9) Several packet parser corrections have been implemented. Some packets that were previously considered bad parses will now be properly displayed. 10) The javAPRSsrvr # heartbeat is no longer considered to be a received packet. This means that the activity timer may expire more often than it has before causing Force Disconnects. If you get an inordinate number of these, increase your Quiet Time configuration parameter. This was done because some APRS-IS servers seem to go dumb and quit transmitting packets but continue to transmit the heartbeats. 11) Station Icons will fade away as they age. The XML configuration file lets you specify a minimum and maximum station age (in minutes). Stations will stay 100% for the minimum time and will then fade until the maximum time at which point they are deleted. Any message from a station will restore it to full brightness. (Note: a bug was just reported in the left/right arrow map fade controls. If you decrease it below zero with the left arrow, it will wrap back up to 100%. This will get fixed, but I probably won't bother with a new release for it). 12) The station popup (click on the map icon or the recent station list) has been streamlined to remove information that is empty and add new additional information. It will show some or all of the following: Title bar shows station and IGate (this is APRS-IS after all) Sym: Symbol name and overlay (if any) Rng: miles @ bearing (if you have a fix) n/m Tracks (mKB) (if you've moved) Last known coordinates in APRS format Last heard timestamp (yyyy-mm-dd hh:mm:ss) Path (if not empty between tocall and qXX,Igate) 13) Zoom factors are now different due to OpenStreetMap tile scaling 14) Circle no longer rotates, but North is always up. I need to make OSM an enable to restore the old rotating circle behavior. Or just restore rotation if you crank the visibility down to 0%? 15) Statistics display (double-click the split station/memory bar) shows both your and total track counts and memory consumption. I hope to add network traffic counters and Tile "disk" and memory consumption

Beta Testers, I just posted the first new release of APRSISCE (for Windows Mobile) to the Yahoo group Files section. You can find it there as: APRSISCE6P090805.zip There's lots of little stuff in there, but the big thing is... IT DOES MAPS! It hooks into OpenStreetMap.org's servers and dynamically loads maps in the background and displays them on your phone. Left/Right arrows will decrease/increase the density (transparency) of the maps in 5% increments. If you take it down to zero, the maps will disappear and the old circle will come back. Before copying this onto your phone, please make a copy of the version you've been using, just in case something goes worng! Please post feedback here to the group with comments, successes, and (hopefully not) failures of this new version. Lynn (D) - KJ4ERJ - Author of APRSISCE PS. Oh, it also does Overlay characters on the Icons! Even the really tiny ones! PPS. It also tracks (and draws) every station that moves, so expect lots of lines if you view an active APRS area. To clear the lines, double-click the Odometer. The first confirm is for your track (if you have any) and the second confirm is for the other stations' tracks (if there are any).

Greetings, I'm taking some abuse from my son about what the up/+ and down/- should do with respect to zooming the map, so I'm throwing it out to the group to help me make the client mostly intuitive for most of the people. Things I'd like you to consider before voting are: Showing more or less map area Showing more or less map detail Showing more or fewer stations Notice how I'm NOT using the word zoom in these, because there are no "in" or "out" keys on the keyboard. What does in and out mean anyway? So, the poll link below asks what the Up/+ should do. Give me your group opinion and I'll make it so. http://groups.yahoo.com/group/aprsisce/surveys?id=2216634 Lynn (D) - KJ4ERJ - Author of APRSISCE

(The poll is now open for voting. I may know about APRS-IS and Windows Mobile programming, but Yahoo Group management goes beyond my abilities! Thanks for letting me know!) Greetings, I'm taking some abuse from my son about what the up/+ and down/- should do with respect to zooming the map, so I'm throwing it out to the group to help me make the client mostly intuitive for most of the people. Things I'd like you to consider before voting are: Showing more or less map area Showing more or less map detail Showing more or fewer stations Notice how I'm NOT using the word zoom in these, because there are no "in" or "out" keys on the keyboard. What does in and out mean anyway? So, the poll link below asks what the Up/+ should do. Give me your group opinion and I'll make it so. http://groups.yahoo.com/group/aprsisce/surveys?id=2216634 Lynn (D) - KJ4ERJ - Author of APRSISCE

Group, There's another new version of APRSISCE for Windows Mobile just posted to the Files section. I discovered a fairly serious resource consumption that causes Windows Mobile to run out of resources and lock up if you drive around at a low zoom level causing lots of OpenStreetMap files to paint. This resource leak has been fixed along with the following changes. 1) Reworked the APRS-IS network handling to improve responsiveness and reduce load on the device. 2) Double-clicking the "APRS OK" window no longer brings up a series of network devices, but instead shows traffic statistics for the APRS-IS connection including packets and bytes sent and received for this session. 3) Reworked where stations are painted on the OSM tiles. They weren't quite landing on streets at larger zoom levels. It uses the old way until all tiles have been filled in, so don't be alarmed if you see the stations "jump" right after the map completes. You should only see this the first time you're in an area while the OSM tiles are loading from the network instead of from the cache. 4) The OSM map is now clipped to the old circle and doesn't overflow around and behind the various other windows. 5) Double-clicking an empty space on the map will popup OpenStreetMap tile statistics if any tiles have been loaded in that session. Eventually, I hope to also show the status of the on-device cache of tiles by zoom level. 6) Increased the available zoom levels. On my 320x240 AT&T Tilt, I can now zoom out to 524 miles instead of the old 256. 7) Reworked how tiles are cached on CE. You might want to locate the OSMTiles folder (probably in the root of your device) and delete it and all files within it. The new caching layer uses directories that exactly mirror OSM's URLs. 8) To store the OSM cache on a Storage Card (assuming you have one), close APRSISCE and edit the APRSISCE.xml file that should have synced to your desktop. Locate the <OSM.Path> argument and set it to <OSM.Path>/Storage Card/OSMTiles/</OSM.Path>. Save the file and wait for it to sync back to your device before running APRSISCE. You should then see an OSMTiles folder on your Storage Card. 9) The OSM Tile Cache now prefetches tiles in anticipation of your movement or zooming. It fetchs one tile out in each ordinal direction from the screen along with all tiles one closer zoom below and one further zoom above. 10) While APRSISCE is fetching OSM tiles, you'll see a yellow circle expanding from the center of the map. Each jump is one tile. When it reaches the outer circle, it has worked off all queued prefetches. It prioritizes the queue, so it'll still get the missing visible tiles first. Let me know what you think and let me know what you'd like to see enhanced and/or changed, especially if you encounter any bugs! Lynn (D) - Author of APRSISCE - (APRS message me at KJ4ERJ-12)

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the aprsisce group. File : /APRSISCE6P090811.zip Uploaded by : ldeffenb <kj4erj@...> Description : New Station Info (Comment, PHG, cse/spd), Logon fix, OSM prefetcher fix & expansion You can access this file at the URL: http://groups.yahoo.com/group/aprsisce/files/APRSISCE6P090811.zip To learn more about file sharing for your group, please visit: http://help.yahoo.com/l/us/yahoo/groups/original/general.htmlfiles Regards, ldeffenb <kj4erj@...>

Testers, There's yet another release of APRSISCE available (APRSISCE6P090811.zip)! Here's a short list of what's new and different. Lynn (D) - KJERJ 1) Station comments are now displayed in the station popup. 2) Station course and speed are parsed and displayed in the station popup (ONLY if provided by remote station, not "guessed" at by distance/time). (Thanks to John N8JJ) I'm thinking about providing a scaled arrow (short and thick for slow, long and thin for fast) in the course direction in the future, thoughts? Also, should I think about calculating course and speed, even though this can result in strange answers? 3) Station PHGR (Power/Height/Gain/Range) is parsed, calculated, and displayed, including the Beacon Rate (per hour) if provided. 4) Rng: (Range) has changed to Pos: (Position) in the station popup and the bearing is now displayed in 16 compass point text, not degrees. (16 points are also used for the course if displayed) 5) Corrected the logon string's Version content so we should quit getting the "adjunct HH:MM Missing filter keyword" complaint at login (most of you have probably never noticed anyway). 6) No longer display the Pos: 0 @ 0 if you station pop-up "ME". 7) Screens bigger than 320x240 in size will increase the displayed icon size as you zoom in. This looked better than I expected. I just need to figure out a graceful scale also. 8) Station popup coordinates no longer display table/icon information, but use spaces. The coordinates are now more readable and the selected icon's name is displayed anyway. 9) Double-clicking an empty map space now displays OSM Tile fetcher queue information and doesn't say (1 failed) while it is actively downloading a tile. 10) The OSM Tile prefetcher now pulls all outward-zooming parent tiles whenever a lower level tile is retrieved. This makes zooming out faster. It is smart enough to stop when it encounters a tile that's already been loaded. 11) Corrected a timing issue that could cause the tile pre-fetcher to access non-allocated memory. I have no idea what the user-side of this would have looked like, but it probably would NOT have been pretty. 12) TCP communication errors are now forced into APRSISCE.log, even if Debug Logging is not enabled. 13) The forecast range red dot is now 100% opaque again to avoid the square background it had at 50%. I need to get fade and transparency working together for the station icons. 14) Double-clicking where a rectangle overlaps the circle should now honor the top rectangle, this was really strange for a while! Known Issues: 1) I had the tile prefetcher lock up last night during testing. I ran out of data coverage range and it just stopped fetching tiles. Closing and restarting the client corrected the situation. 2) If a corrupted OSM tile is fetched (web server error during the fetch, for instance), that tile file is detected as corrupt but not removed from the device. This means you'll have a permanent map "hole" there at a single zoom level until I get this fixed. To Dos: (Incomplete) Parse and display Frequency object information Delete bad PNGs to allow refetch Support larger Icons (complements Noel W8TVI) Fix up fonts for VGA (640x480) devices (test with Noel W8TVI) Allow configuration of location for OSMTiles cache (w/o editing XML) Allow configuration of date/time display & GMT vs local (Dave N8PU) Allow configurable removal of some screen elements (Satellites, John N8JJ) Optimize circle redraws for off-screen stations Track selected station (in center of screen) Pan (Drag) screen for browsing the map Record/Recall last DNS/IP for OSM/APRS-IS (faster reconnect) Asynchronous TCP/IP connections & reading (solves hangs) Timeout on OSM Tile fetcher (solves stalls) Implement whatever results from the Zoom +/- Poll Win32 client only for the following: Simultaneously track multiple targets in separate circles Support NMEA GPS

The following aprsisce poll is now closed. Here are the final results: POLL QUESTION: Which way should the zoom up/down +/- work? CHOICES AND RESULTS - Up/+ should show more area/stations, 3 votes, 50.00% - Up/+ should show more detail, 3 votes, 50.00% For more information about this group, please visit http://groups.yahoo.com/group/aprsisce For help with Yahoo! Groups, please visit http://help.yahoo.com/l/us/yahoo/groups/original/general.html

Lynn, Are there any plans on adding an option to be able to change your own icon? Thanks, Jason, K2ENG

Lynn, I try to open APRSISCE6P.exe on both my laptop and my Samsung phone and I get an error that APRSISCE6P.exe is not a valid Win32 app. 73, Dan AI4GK

Lynn KJ4ERJ, Maybe I haven’t paid enough attention but I’ll ask anyway, I’m wondering if we (the user) can change the interval the program updates while we are using it. The reason I ask there has been a couple of times I was tracking a user (from my home computer) and noticed that it seem like there is a randomness to the updates; sometimes it’ll update 2 or 3 times within a short distance like when you would be slowing down for a turn or accelerating away from a turn but if you are on a mostly strait road it seems to take much longer for the updates. I’m aware we can ‘force’ an update but that’s not what I’m talking about. Thanks, Dave N8PU

Dave, I've extended on the concept of SmartBeaconing (TM by the HamHud developers, google it to find out) and call it Genius Beaconing. You can configure the parameters via the Configuration dialog and clicking on the big Genius button. It offers the following parameters: Min Time - Minimum time between beacons in seconds (driving a circle) Max Time - Maximum time between beacons in minutes (sitting still) Bearing Change - Beacon if bearing changes by this many degrees (or more) Forecast Error - in 0.10 miles (see discussion below) Max Distance - In 0.10 miles (see discussion below) The last two parameters are what makes up my Genius Beaconing. APRSISCE keeps track of what was sent in the most recent beacon, particularly the speed and bearing component. If an outside observer was to extrapolate the last position by the speed and bearing for the time since the beacon, they would think you were somewhere. The local GPS knows where you actually are. When the difference between these two points is more than the Forecast Error, a beacon is generated. The forecast position is shown in the circle by that little red dot that moves outwards from the center. When it reaches the circle, the beacon is generated. This parameter will tend to generate beacons for slight turns that don't trigger the Bearing Change as well as generating beacons when your speed changes (faster or slower) by a substantial amount. Because the forecast error won't generate beacons in steady non-turning motion, there's also the Max Distance parameter. Even if the forecast error is keeping pretty close to where you actually are, if you've traveled more than the Max Distance, a beacon will be generated anyway. When you're sitting still, the Max Time applies. This is designed to be very long just to keep the system current while you're parked. The Min Time is used to prevent lots of small changes (like driving in circles) from triggering a bunch of updates. APRSISCE will hold off any beacons for at least this time after a beacon was last sent. It shows this in one of the small red lines in the APRS OK box at the top center of the screen. There are actually three small color bars at the bottom of the box above the top edge of the circle. These three bars show (not sure which is which right now, but if you watch them, you'll soon see which is which): 1) Time since last reception from APRS-IS. This extends from left to right until it reaches the configured Quiet Time maximum at which point APRSISCE will force a disconnect on the assumption that the connection has died in a non-detectable fashion. This is the bar that disappears the instant the stations list scrolls with a new update. 2) Transmit "Pressure". Given the different parameters that can trigger a beacon, APRSISCE shows this bar to give you an idea how long it will be until the next beacon. The line below APRS OK shows which parameter is reaching what percentage of threshold currently driving towards a beacon. This bar grows from left to right and disappears when a beacon is actually sent. 3) Min Time. This bar counts down from right to left as APRSISCE is enforcing the Min Time configuration. Even if the Pressure exceeds 100%, APRSISCE will not issue a beacon until this bar disappears to the left. This is the bar that appears suddenly red and then shrinks down through yellow to green until it disappears until the next beacon. So, you can tweak the Max Time and Forecast/distance parameters to generate more beacons, but I'd encourage you to consider the effects on APRS-IS and what you're actually gaining by transmitting more frequently, especially if you are having your beacons gated to RF. Once you inform the observers that they can rely on your speed and bearing and elapsed time to place you within X (Forecast Error) miles of where you actually are, you probably don't need to beacon any faster. The only parameter I sometimes think about decreasing is the Max Time to something like 10 minutes while parked instead of the 30 minutes that mine is currently set to (I don't remember what the defaults are). Hope

Greetings all, as I replace my HTC TyTN II (AT&T Tilt unbranded with front camera), I am getting a I-Mate Ultimate 8502. Has anybody ran APRS-IS CE on this hardware? Thank you, Michael KE5EUA