Jump to content


+Premium Members
  • Posts

  • Joined

  • Last visited

Everything posted by binzi

  1. Inspired by the Wherigo based GPSr submitted by Geofellas I developed my own cartridge adding some functionality for runners to the Oregon and other devices having a Wherigo Player: Oregon Runner at Wherigo.com It keeps track of your time and distance and offers a Virtual Training Partner as well as an AutoLap Function. That is, you may run against a virtual partner who runs a given distance in a given time/at a given speed. Thereby the cartridge automatically keeps track of your last lap. The cartridge may be played anywhere. When you start it you should find a GPSr in your inventory. Currently it offers the following options: Settings: 1.) Enter the distance you intend to run (default: 10000 m) 2.) Choose how to configure the Virtual Partner: min/km, km/h or seconds needed to run the given distance (default: seconds). 3.) Enter Virtual Partner data accordingly (default: 3600 s) 4.) Enter the length of a lap for AutoLap (default: 1000 m). Start Run: Immediately starts to record both time and distance of your current run, calculates and displays useful information. Last Run: Shows some details about your last run. It basically works as follows: While the player is running the cartridge records his position every second and then calculates the distance to its last position. Based on my first test run it seems to be fairly accurate. A few comments on this version: - This is my very first cartridge and thus kind of a rapid proof-of-concept. It doesn't look very fancy but it works - I don't know how to turn of logging for cartridges built by Wherigo.com (the setting on the webpage is ignored by the online compiler...). This might result in large log-files in the saves folder... Just delete them manually if they get too big - At the moment the entire cartridge is based on the metric system which (hopefully) should be fine for runners... - The Virtual Partner works as follows: - first set him to min/km, km/h or seconds needed to run the given distance - thereby five and a half minutes would e.g. be entered as 5.5 - when running the distance to the Virtual Partner is shown in seconds - thereby +5 s signifies that the Virtual Partner is 5 seconds ahead of you while -5 s means that the Virtual Partner is 5 seconds behind you - AutoLap works as follows: Every time you complete a lap the new laptime, avg speed etc will be calculated. Note that the actual distance of a lap might slightly differ from the theoretic value as the distance is onyl updated every second... - The cartridge does not automatically stop recording after finishing the given distance but keeps on recording until the user presses the stop button. This is a feature not a bug This is mainly done to prevent that the cartridge wrongly stops a run (e.g. due to inaccurate measurements) while you have not finished the actual distance yet... Now have fun running. Any feedback is appreciated.
  2. Thanks for your help. Did some research in the forum and built a very first version of my Oregon ForeRunner Here's a list of some useful functions which might save some other newbies some time: Get the location of the player: Player.ObjectLocation Player.ObjectLocation.latitude Player.ObjectLocation.longitude Display variables in Message boxes: [[Location: ]] .. tostring(Player.ObjectLocation) [[speed: ]] .. string.format("%.2f",mydist/mytime) .. [[ km/h]] Get distance between two points: local d = Wherigo.VectorToPoint(Player.ObjectLocation, tmppt) print(d("m")) print(d("ft")) print(d("mi")) print(d("km")) where tmppt is an ObjectLocation stored earlier as e.g. in: tmppt = Player.ObjectLocation Once I figure out how to actually prevent logging in cartridges which are compiled by the Wherigo webpage I will publish the cartridge...
  3. I just created my first cartridge including a 1 second timer. To prevent creating huge log files I turned off logging. Unfortunately I just found out that the Wherigo webpage simply ignores this setting. Every time I uncheck the "Turn on logging" option, save the Cartridge details and go back to the "Edit Details" page the box is checked again! When I built the cartridge locally (also unchecked logging in the Builder) it works perfectly well... Any ideas?
  4. I discovered your cartridge a couple of days ago and really love the idea of adding missing functionality to my Garmin Oregon using a Wherigo Cartridge. Therefore I started to play around with the Builder yesterday and really found the lack of documentation very disturbing. Now I have the following questions: 1.) Do you plan on making your cartridge open source or would you be willing to send the lua code to interested people via email? 2.)Do you know of anything like a list of all (or at least some) Wherigo built in functions? What functions are there, which features of the GPS device can be accessed via lua? If there is no such list, would you mind listing all the built in functions you used in your cartridge? 3.) If I intend to add my own functions using a Wherigo cartridge, should I write a new cartridge or could I just contribute to your cartridge? In particular, I was thinking about adding some features of the Garmin Forerunner to my Garmin Oregon. I thought about starting with easy functions like recording and displaying the time I needed for the last kilometer while running (i.e. after each kilometer I ran the Oregon would display the time needed for the last kilometer and maybe additional information like how much faster or slower I'm running as compared to a predefined time). This could then e.g. be used for things like keeping track of my time while trying to run a half-marathon in a given time... Any help would be appreciated. Again thanks for having that great idea
  5. After repairing my unit (by downgrading to 2.4) I immediately upgraded to 2.5 again (using the webupdater). I didn't have any problems ever since. So I would also recommend to upgrade to 2.5 again.
  6. Based on my own experience I can add the following information: 1.) The Garmin Player Version on the Oregon seems to have no meaning at all. With every software update it is simply set to the number of the software version (which is currently 2.5). Doesn't seem to affect the Wherigo Player on the Oregon at all. 2.) While the Wherigo Engine version (currently 2.11) is the same on the Oregon and the Colorado both devices actually seem to have different engines running. There is at least one cache I know of (GC1EMF3) which can be played using the Colorado but cannot be played using the Oregon. I already wrote a not-so-friendly email to Garmin support as I really hate to travel a long distance to play a Wherigo cartridge only to find that my Oregon Wherigo Player does not support it. Didn't receive an answer until now though... The latest PDA Player is from 5/29/2008. Garmin should have updated the Oregon Player by now! Especially since they advertise Wherigo as one of _the_ features of the Oregon...
  7. Hey, I had the exact same problem on my oregon and already wrote a post including the solution on this board. (see: http://forums.Groundspeak.com/GC/index.php...204072&hl=) Solution: Just go to: http://garminoregon.wikispaces.com/Miscellaneous#toc3 and follow the instructions (at your own risk). Basically you will need to downgrade to 2.4 using the updater.exe and the 2.40 Firmware. It took five to six tries till it worked on my unit. Once you are back to 2.4 you can update to 2.5 again using the webupdater. This worked for me and my Oregon is running smoothly ever since... I don't know what caused the problem but I think it had something to do with transfering some gpx files from and to the Oregon....
  8. As far as I know there is no option to hide caches on the map yet. The only way would be to remove them from the gpx file on the Oregon. However, when navigating to a cache there is always the option to chose "log attempt" and set it to found. After that found caches will be shown as a little treasure chest instead of the regular geocaching item. This will at least help you keep track of which geocaches you already found.
  9. Today my Oregon 300 with software version 2.5 would start to freeze while loading waypoints, tracks and routes. This probably happened after I transfered some new caches to the gpx folder on the Oregon. It then showed the following symptoms: - when powered on it would always freeze and switch itself off while loading waypoints, tracks and routes - when connected to a PC via USB it would freeze and switch itself of while saving current waypoints to gpx - when trying to do a master reset (press and hold upper left corner of screen while switching the unit on), it would show the "would you like to erase all date" screen and freeze and turn itself off before one could touch either yes or no - this all happened independent of whether it had an SD card installed or not I eventually found the following webpage: http://garminoregon.wikispaces.com/Miscellaneous#toc3 It describes a way to downgrade to software version 2.4. However, the first couple of times the unit would also freeze and switch itself off. Eventually it actually worked and my unit was back to life! I re-updated to version 2.5 and again transfered the same caches to the gpx folder on the Oregon. So far everything seems to work just fine. Thought I'd share my experience in order to spare others the two hours in shock that I had to experience. Thanks Garmin... P.S.: Is it just me or is Garmin merely increasing the Wherigo Player version together with every software update while the Wherigo Player itself isn't updated at all?
  10. The Wherigo Player Versions are currently not identical on the Colorado and the Oregon. There is at least one Wherigo Cartridge (see GC1EMF3) which can be played on the Colorado (current Software version) but doesn't work properly on the Oregon (Software 2.4).
  11. So far I used two devices for paperless caching: One device (my Sony PSP) to read the cache description, hints and so on, and one device (Garmin Gecko) to navigate to the stages of the cache. I bought an Oregon 300 to combine these functionalities into one single device. However, while only having to carry one device now, I think it is quite complicated to switch between cache management and routing on the Oregon. Here's what I usually do: - I navigate to the starting point of the cache, solve the first puzzle and create a waypoint for the newly calculated coordinates of the second stage - I then navigate towards that manually entered stage - If I now want to do things like read the hint for that stage - it forces me to stop navigating to the stage - search for the cache itself again - start a navigation to the starting point of the cache (otherwise I won't be able to see the hint or access any other cache related functions!) - read the hint I was looking for - stop navigating to the cache - search for the manually entered waypoint again - navigate there again Is it actually that complicated or am I missing something here? What are your best practices to paperlessly solve a multi-cache using the Oregon? How do you switch between cache management and routing?
  12. On the Oregon you are able to scroll both ways while editing the coordinates of a waypoint. That is not the problem. The problem is that while editing you never see the entire coordinate at a glance (From what you are writing I guess it probably is the same on the Colorado). So here is what usually happens when I edit a waypoint: - First I scroll to the right until I hit the first digit I like to edit - Then I change from scrolling mode to editing mode - After editing the digit I change back to scrolling mode and scroll to the next digit I would like to enter, ... - Since I am not able to see the entire coordinates while doing this, I usually end up scrolling through the entire coordinates after editing them to double check whether I entered them correctly While editing waypoints on my Gecko, however, I was able to see the entire coordinates all the time. The screen of the Gecko is at most one third of the size of the Oregons screen!
  13. Is it just me or does editing the coordinates really suck on the Oregon? Even on my good old Gecko I was able to see the entire coordinates at one glance when editing the location of a waypoint. On the Oregon, which has a significantly larger screen, I only see some digits of the coordinates when editing them. Especially annoying when I want to double check that I correctly entered the coordinates of the next stage... Plus I think it is unnecessarily complicated to change between editing digits and scrolling within the coordinates...
  14. I absolutely second that! The new feature is really annoying and a hindrance when trying to get an overview of new caches in the area. This kind of makes the google map search unusable for me. Especially since the new areas cover both found and not found caches. Could you please turn this feature of by default and then include some kind of checkbox to turn that feature on? P.S.: Speaking of google maps, it would also be great if the map would be centered on my home coordinates instead of somewhere in Seattle. This should also reduce a great number of redundant database queries on geocaching.com...
  15. Hey, Why is it that when searching with google maps the map is always centered to some place in the US? (Like Seattle at the moment). Wouldn't it make more sense to automatically center the map on my home coordinates? I mean 90 percent of the time I'm using the search with google map feature the first thing I do is to set the map to somewhere close to my home coordinates. Should be easy to implement and would probably serve a lot of server resources (which arise when hundreds of people look at caches in Seattle all day Where would I post a feature request for something like that?
  • Create New...