• jeffrGGC

    For any screen with sort capabilities...

    • would like to sort by last, first... and set this as default in the settings.

    posted in AXti.me RM read more
  • jeffrGGC

    Repost from the feature request forum:

    We had some issues with crashes at an event earlier this month and had to log results on paper to keep the event moving while we debugged the situation. As a result, those events were not entered into the system until after the event concluded. I did this by queuing up the drivers and manually entering their times. All the runs were credited to the correct drivers, but for us, order is important.

    Because our rules state that the first run is a practice run and it's not counted towards best time calculations for the event, the order of the runs for this event is not correct for some of the drivers. I can't see a way to manually adjust the order of the runs, so I'd like to request some enhancements to the Driver Details screen.

    For the time keeper, event admin, and/or admin, it would be very helpful if they could:

    • Edit a run by clicking on it from the driver details screen
    • Manually add a run for the driver from the driver details screen
    • Re-order the runs for a driver from the driver details screen

    This would make it very easy to fix any issues for a driver all from one place.

    posted in AXti.me RM read more
  • jeffrGGC

    We ran in the cold and wet at Crows Landing yesterday. 91 attendees, three run groups. ZERO system crashes!

    Thanks to Chris for fixing up those couple of bugs.

    posted in Announcements read more
  • jeffrGGC

    Figured it out... the update creates a new folder "website-2-3-7" and keeps "website" in tact. Rename website to website-2-3-6 and then renamte website-2-3-7 to website and we're good to go.

    Big testing event this weekend! Fingers crossed for a crash free experience.

    j

    @jeffrGGC said:

    Finally got around to applying the update, which is my first since joining the family. I did read on one of the initial screens "this upgrade does not change your existing version..." but I'm not sure how to verify I have the updated code now.

    When I restarted step2, then reloaded localhost in Chrome, I'm still seeing 2.3.6 version number. Is that as expected?

    posted in Announcements read more
  • jeffrGGC

    Finally got around to applying the update, which is my first since joining the family. I did read on one of the initial screens "this upgrade does not change your existing version..." but I'm not sure how to verify I have the updated code now.

    When I restarted step2, then reloaded localhost in Chrome, I'm still seeing 2.3.6 version number. Is that as expected?

    posted in Announcements read more
  • jeffrGGC

    @Chris Thank you!!!

    posted in Announcements read more
  • jeffrGGC

    I'd like to request a rush fix on this issue if possible. Run order is important to our program.

    Thanks, Chris!

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    More input... it's not every driver who had their results exported in the wrong order. Very baffling! Perhaps this is something to do with fixing up runs by editing/adding runs as needed post event. After doing so I did "recalculate" before exporting results. Print Results shows proper orders, though.

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    I wrote a function to reverse the columns in our spreadsheet so the run order is corrected during processing. However, a fix in a future release would eliminate that need.

    What's really strange is when I compared export csv data from our previous event, the run order is correct. Now I'm wondering why the 10/17 export file is reversed.

    Thanks!

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    I just discovered the export function reverses the run/penalty order. What's in RUN 1 columns is actually the last run. However, Print Report and Live Results publish them in the correct order.

    Any chance an emergency fix can be done on this? We have intricate Excel spreadsheets with macros that count on the run order to calculate results for us. Our first run is a practice run and does not count towards official runs. Order is important.

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    Yes

    @MarcGSR said:

    @jeffrGGC it will likely be 2.3.7 that has the fixes, to be released.

    Question to those experiencing a crash. Do you have your timing console on and plugged in /before/ running AXti.me Step 1 and Step 2?

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    Which release has these fixes? We're on 2.3.6 and are seeing both of these issues.

    @Chris said:

    I'm guessing that it is one of 2 things. a "ttl" issue or the socket connection issue (both should be solved in next release).

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    I did, but nothing from the backup was present.

    I just restarted the system (after a brief brain phart where I had Skype running, which interferes) and the 9/19 event was not present. I did the restore from backup again, got the error popup immediately after clicking the "yes I want to!" button, but noticed in the CMD window that it was proceeding.

    I logged out, then back in, and now the 9/19 event is present.

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    I'm attempting to restore a backup file from the cloud to a different computer than created it. Both machines are running on Windows 7 x64, same version of AXTime. The backup is out there, but when I attempt to restore it I get an error dialog "oops, something did not go right." Thoughts?

    Yes, I've tried other files too.

    Screen capture log:
    attempting cloud restore
    doing cloud restore
    downloading from http://live.axti.me/api/backup/axtime-backup_POSTevent_2015-09-19-16-16-06.zip?cloudkey=formyeyesonly
    get response
    statuscode:200
    downloaded to ../_backups/tmp-cloud-1444250565418-axtime-backup_POSTevent_2015-09-19-16-16-06.zip
    download from cloud duration: 1716ms
    Extracting zipped backup file
    unzip duration: 518ms
    versions duration: 0ms
    users 40 duration: 0ms
    clubs 1 duration: 0ms
    converting 6 lines to json
    events 5 duration: 2ms
    members 183 duration: 2ms
    participants 364 duration: 8ms
    converting 2314 lines to json
    runs 2313 duration: 73ms
    seasons 1 duration: 0ms
    times 2457 duration: 5ms
    ttods 6 duration: 0ms
    DONE extracting data in 609ms
    backup database version is 1.0.2
    system is expecting 1.0.2
    DELETED all users data: null
    DELETED all clubs data: null
    DELETED all seasons data: null
    DELETED all events data: null
    DELETED all ttods data: null
    restored seasons in 23ms
    DELETED all members data: null
    DELETED all participants data: null
    DELETED all runs data: null
    restored clubs in 105ms
    DELETED all times data: null
    restored events in 196ms
    restored ttods in 198ms
    restored users in 420ms
    restored members in 980ms
    restored participants in 2019ms
    restored runs in 6542ms
    restored times in 6576ms
    done restoring data in 6708ms
    restore returned: null
    download and restore duration: 9033ms

    posted in Issues Bugs & Feature Requestsread more
  • jeffrGGC

    That's in case you don't know the cone station number.

    posted in Comments & Feedback read more
  • jeffrGGC

    That's exactly the difference. The window won't close if you run the program in it manually as suggested. I know there's a post somewhere about running it manually, but it's really as simple as I describe.

    @Duke said:

    @jeffrGGC - If starting the CMD window first is somehow different from just right clicking on the batch file and choosing Run, maybe that won't happen.

    posted in Hardware read more
  • jeffrGGC

    @Duke What I'm saying is, open a cmd window via Start Menu, for instance. Then, go in, change directory to where your axtime is installed, then type the batch file name and bang the enter key. I renamed the batch files to step1.bat and step2.bat to make it easier.

    You'll need one window for each.

    http://www.7tutorials.com/7-ways-launch-command-prompt-windows-7-windows-8

    posted in Hardware read more
  • jeffrGGC

    @Duke Run the processes manually. I open two cmd windows, then run step 1 batch file in one, step 2 in the other. If anything crashes, the window remains open so you can copy it.

    You can also redirect the output to a file so you have everything logged. I have not tried this during an event, but may next time.

    Some more info...
    http://www.howtogeek.com/howto/windows-vista/copy-to-the-clipboard-from-the-windows-command-prompt/

    http://pcsupport.about.com/od/commandlinereference/a/redirect-command-output-to-file.htm

    posted in Hardware read more
  • jeffrGGC

    @Duke Did you capture the errors? I didn't bother this time because I was, or so I thought, certain it was the network monitoring software, Perhaps that was coincidental.

    I do remember "TTL..." in the window when it crashed. Now I regreat not capturing it. And you're right, it's step2 that crashes. We'll see how our next event goes without the network monitoring software in the mix.

    We have a very tech savvy group and they are loving this. One guy had an iPad mini in his glove box connected to his navi unit via HDMI with the On Course view displayed. That's my favorite too.

    posted in Hardware read more
  • jeffrGGC

    @jeffrGGC Some follow-up info for you now that we have 4 events of experience with AXTi.me and the Ubiquiti Outdoor + access points.

    1. We had a very sunny and warm day at our site this weekend, something we don't often have. Our field/grid AP went out on us several times. I believe this was the direct result of the POE injector overheating from sun exposure. The previous month we did not have this problem, so I will get it in the shade at our next event.

    2. We're having problems with the UniFi AP management software crashing AXTi.me. At our August event, @chris and I determined "something" was disturbing connections to AXTi.me causing it to crash. I suspected the management software because it also runs on localhost. At that time I had it insalled on the timing computer along with AXTi.me.

    After that event, I purchased a SSD and reinstalled our timing computer from scratch with Win 7 X64. I did not install the UniFi AP software on that computer. Instead, I installed it on another computer thinking it would avoid conflicts. It's important for me to check the health of the network at times during an event and this software does that.

    Unfortunately, if this software is running on ANY device on the same network as AXTi.me, it causes problems. During our first session of the day I was logged in and using it and suddenly we see the dreaded "Reconnecting" spinner... AXTi.me had crashed.

    I now know 100% that this software is the cause of our system crashes. I immediately disconnected my Mac from the network, restarted AXTi.me, and we were trouble free for the remainder of the event. I really would like to figure this out. Maybe @chris can give us some insight on ports and such. I don't even know where to start.

    posted in Hardware read more
Internal error.

Oops! Looks like something went wrong!