• Duke

    @JasonPowell :

    So I would download / install node.js directly form them, and then (I assume) the 2.3.7 Complete file from live.axti.me?

    I hope I can find my install files for the $10 non-profit Office suite I had. If not, that's my fault.

    Thanks again for your help.

    posted in AXti.me RM read more
  • Duke

    Awesome, Jason, thank you!

    posted in AXti.me RM read more
  • Duke

    We had a microcell blow through our last autocross. Most of our equipment is OK or at least usable, but the main T+S laptop is suffering either disk or main board damage. It won't boot. It's an HP 15-F162dx notebook and I've never really liked it anyway.

    If I replace that computer, how hard is it to reinstall AXti.me and the supporting software? I have no real way to uninstall it from the old laptop.

    I do have a fairly recent drive backup of the main HP notebook, and I have a cloud backup of the AXti.me database from the night before our last event.

    Is it as easy as restoring the AXti.me folder from the backup and refreshing the database from the cloud? Thanks.

    posted in AXti.me RM read more
  • Duke

    I have a NetZero mobile internet USB dongle. It works most of the time, with occasional troubles, but is overall pretty reliable. It typically drops once or twice during an event, and needs to have the connection reestablished.

    But starting when I was bench testing on Friday night, and during the event on Saturday, clicking the Sync button instantly killed the internet connection and reset the dongle as if it wasn't even inserted. I would have to unplug / replug for the connection software even to recognize the device so I could restart the connection. When the connection was established, even without attempting to manually sync via the button, Axti.me was giving continual connection errors and never uploaded data. The internet connection worked fine for other sites.

    There were no known settings changes on my part, though there were the inevitable Win10 updates, since it was last used successfully in June. The timing gear input is using COM3 and the dongle is using COM4-6, so there is no conflict there.

    Any ideas or advice will be appreciated. Thanks!

    posted in RM Live read more
  • Duke

    @sjd - I understand your point and share some of your sentiment, particularly your disappointment. However, I see no reason to abandon the system as long as it still continues to function. We paid our initial purchase price 3 years ago and AXti.me has not cost us a dime since then. As long as live results work on event days and the software is usable between, we plan to keep using it.

    posted in AXti.me RM read more
  • Duke

    Jason - thanks! I'll pass the information on.

    posted in AXti.me RM read more
  • Duke

    So, is Chris still available for new sales? I have an acquaintance who ghosted one of our events last year and is considering buying AXti.me for his club, but the main AXti.me site seems to have disappeared and the FB page hasn't changed in years. This forum and the demo are still available, so the message is ambiguous. He's worried about committing to the purchase with zero support, if he can even do so.

    Anybody have information?

    posted in AXti.me RM read more
  • Duke

    Yeah, our day went off without a T+S hitch that was not operator- or environment-caused. Live results stayed up all day even through our crappy and sometimes uncooperative NetZero mobile dongle.

    Good stuff!

    posted in RM Live read more
  • Duke

    Well, our first event of 2018 is Saturday. Fingers crossed.

    posted in RM Live read more
  • Duke

    @JasonPowell - That is excellent news! We also had very few problems last year, except for the OLR issues that were noted and resolved. I still have a list of suggestion open in the v3 thread, but like you, I'm happy to hear that at least the status quo will continue for the foreseeable future.

    Thanks for getting a hold of Chris, and thanks for reporting back to us.

    posted in Announcements read more

Internal error.

Oops! Looks like something went wrong!