Ourlaps
05-14-2015, 02:38 AM
#61
ourlaps-1.1.1 is released
Source code for cano plugin attached.
- Added (completely untested) support for Cano decoder
- Fixed bug that caused "show graph" to throw an exception if the temperature graph was enabled in the analyze dialog.
- If a windows shutdown message is detected try to perform quicker exit
Source code for cano plugin attached.
05-14-2015, 03:42 PM
#63
And you for yours! 
The latest version installs a small sample file to ("Documents\OurLaps\DecoderData\cano.dat"). You can load it up in analyze, but the lap times are sub 5 second so the ourlaps default values for graph min/max in settings need to be adjusted.
The latest version installs a small sample file to ("Documents\OurLaps\DecoderData\cano.dat"). You can load it up in analyze, but the lap times are sub 5 second so the ourlaps default values for graph min/max in settings need to be adjusted.
05-18-2015, 05:42 PM
#64
I tried the latest build on the weekend however I came across an issue and had to revert back to the previous build.
At the end of the day I do not think it was the fault of the new build and I will try it again soon.
After uninstalling the original version and installing the latest build I configured OurLaps and it was working as normal. It ran for about an hour or so before we noticed that we where not getting any laps called out.
I could see cars crossing the loop and OurLaps not picking up the transponder. I closed and reopened OurLaps and it still would not work. I had a look at the decoder and noticed that when a car crossed the loop the / bar would not go solid indicating the decoder was not functioning. Coincidently the decoder could not contact the server. Telnet test to decoders.amb-it.com 5500 from multiple sources confirmed the decoder server was offline. Power Cycling the RC4 got the / bar going solid as cars closed the loop however OurLaps would still not pick up the transponders.
Rebooted the timing PC and then OurLaps began to function again. About 45min later same problem as above. Rebooted the RC4, rebooted PC however I could not get the newer OurLaps build to work. Uninstalled it and installed the original version and we seemed to get normal behaviour however the RC4 locked up one more time before normal operation continued.
I'm not sure if the AMB decoder server being down upset the RC4 causing the OurLaps issues however I don't see how OurLaps could cause the RC4 to stop picking up the transponders either. The AMB decoder servers went back online the next day.
Feature Request for OurLaps Server
- rename "C:\Users\User\Documents\OurLaps\Racers.xml" to Racers.xml.bak during uninstall or upgrade to prevent drivers database loss. (I know I should have backed it up first)
- Option to alter the classes. I would like to add a class. I also cannot find how to edit/remove them.
At the end of the day I do not think it was the fault of the new build and I will try it again soon.
After uninstalling the original version and installing the latest build I configured OurLaps and it was working as normal. It ran for about an hour or so before we noticed that we where not getting any laps called out.
I could see cars crossing the loop and OurLaps not picking up the transponder. I closed and reopened OurLaps and it still would not work. I had a look at the decoder and noticed that when a car crossed the loop the / bar would not go solid indicating the decoder was not functioning. Coincidently the decoder could not contact the server. Telnet test to decoders.amb-it.com 5500 from multiple sources confirmed the decoder server was offline. Power Cycling the RC4 got the / bar going solid as cars closed the loop however OurLaps would still not pick up the transponders.
Rebooted the timing PC and then OurLaps began to function again. About 45min later same problem as above. Rebooted the RC4, rebooted PC however I could not get the newer OurLaps build to work. Uninstalled it and installed the original version and we seemed to get normal behaviour however the RC4 locked up one more time before normal operation continued.
I'm not sure if the AMB decoder server being down upset the RC4 causing the OurLaps issues however I don't see how OurLaps could cause the RC4 to stop picking up the transponders either. The AMB decoder servers went back online the next day.
Feature Request for OurLaps Server
- rename "C:\Users\User\Documents\OurLaps\Racers.xml" to Racers.xml.bak during uninstall or upgrade to prevent drivers database loss. (I know I should have backed it up first)
- Option to alter the classes. I would like to add a class. I also cannot find how to edit/remove them.
05-18-2015, 08:24 PM
#65
I tried the latest build on the weekend however I came across an issue and had to revert back to the previous build.
At the end of the day I do not think it was the fault of the new build and I will try it again soon.
After uninstalling the original version and installing the latest build I configured OurLaps and it was working as normal. It ran for about an hour or so before we noticed that we where not getting any laps called out.
I could see cars crossing the loop and OurLaps not picking up the transponder. I closed and reopened OurLaps and it still would not work. I had a look at the decoder and noticed that when a car crossed the loop the / bar would not go solid indicating the decoder was not functioning. Coincidently the decoder could not contact the server. Telnet test to decoders.amb-it.com 5500 from multiple sources confirmed the decoder server was offline. Power Cycling the RC4 got the / bar going solid as cars closed the loop however OurLaps would still not pick up the transponders.
Rebooted the timing PC and then OurLaps began to function again. About 45min later same problem as above. Rebooted the RC4, rebooted PC however I could not get the newer OurLaps build to work. Uninstalled it and installed the original version and we seemed to get normal behaviour however the RC4 locked up one more time before normal operation continued.
I'm not sure if the AMB decoder server being down upset the RC4 causing the OurLaps issues however I don't see how OurLaps could cause the RC4 to stop picking up the transponders either. The AMB decoder servers went back online the next day.
Feature Request for OurLaps Server
- rename "C:\Users\User\Documents\OurLaps\Racers.xml" to Racers.xml.bak during uninstall or upgrade to prevent drivers database loss. (I know I should have backed it up first)
- Option to alter the classes. I would like to add a class. I also cannot find how to edit/remove them.
At the end of the day I do not think it was the fault of the new build and I will try it again soon.
After uninstalling the original version and installing the latest build I configured OurLaps and it was working as normal. It ran for about an hour or so before we noticed that we where not getting any laps called out.
I could see cars crossing the loop and OurLaps not picking up the transponder. I closed and reopened OurLaps and it still would not work. I had a look at the decoder and noticed that when a car crossed the loop the / bar would not go solid indicating the decoder was not functioning. Coincidently the decoder could not contact the server. Telnet test to decoders.amb-it.com 5500 from multiple sources confirmed the decoder server was offline. Power Cycling the RC4 got the / bar going solid as cars closed the loop however OurLaps would still not pick up the transponders.
Rebooted the timing PC and then OurLaps began to function again. About 45min later same problem as above. Rebooted the RC4, rebooted PC however I could not get the newer OurLaps build to work. Uninstalled it and installed the original version and we seemed to get normal behaviour however the RC4 locked up one more time before normal operation continued.
I'm not sure if the AMB decoder server being down upset the RC4 causing the OurLaps issues however I don't see how OurLaps could cause the RC4 to stop picking up the transponders either. The AMB decoder servers went back online the next day.
Feature Request for OurLaps Server
- rename "C:\Users\User\Documents\OurLaps\Racers.xml" to Racers.xml.bak during uninstall or upgrade to prevent drivers database loss. (I know I should have backed it up first)
- Option to alter the classes. I would like to add a class. I also cannot find how to edit/remove them.
I'll add in some status messages during connection process.
What I have seen happen before is that if you start the rc4 decoder before the router is ready it does not always get a valid ip and then ourlaps and decoder can't communicate. Restarting the decoder fixes it at our track. We're also not connected to any AMB servers so I have no idea how those interactions affect things.
I'll probably remove the sample Racers.xml from the installer. That should at least not overwrite it.
I'll make a class editor. It's easy.
05-18-2015, 08:36 PM
#66
Thanks Torg
Sync decoder time was cleared the first time it crashed
I enabled it after the first recovery and it crashed again
The RC4 is configure with a Static IP
Turns out my log file is still there and has been logging from day 1 through the upgrade and down grade. I could not see anything in there that helps me determine the issue. Would you like a copy ?
Sync decoder time was cleared the first time it crashed
I enabled it after the first recovery and it crashed again
The RC4 is configure with a Static IP
Turns out my log file is still there and has been logging from day 1 through the upgrade and down grade. I could not see anything in there that helps me determine the issue. Would you like a copy ?
05-18-2015, 10:54 PM
#67
Thanks Torg
Sync decoder time was cleared the first time it crashed
I enabled it after the first recovery and it crashed again
The RC4 is configure with a Static IP
Turns out my log file is still there and has been logging from day 1 through the upgrade and down grade. I could not see anything in there that helps me determine the issue. Would you like a copy ?
Sync decoder time was cleared the first time it crashed
I enabled it after the first recovery and it crashed again
The RC4 is configure with a Static IP
Turns out my log file is still there and has been logging from day 1 through the upgrade and down grade. I could not see anything in there that helps me determine the issue. Would you like a copy ?
The second time, if you enabled sync decoder time. It may have set the RC4 decoder to be the same as the clock on your PC. Not sure if that triggered something on ourlaps end? Some rtc/utc/timezone snafu? Unfortunately those messages were sent to trace and not output/log.
I re-enabled output messages from the plugins. Also added a quick status bar. You should see the status messages tick in from the rc4 decoder even when no laps are turned. I think there is a status interval setting on the rc4 decoder itself if you want to increase/decrease status frequency.
1.1.2 released
Last edited by torg; 05-21-2015 at 12:09 AM.
05-20-2015, 08:32 PM
#68
I do recall closing OurLaps and reopening to make it work after editing the RC4 IP to get it to work.
Upgraded to 1.1.2, seems to be working OK..
I noticed the uninstall of the initial release deleted the racers.xml file and not the newer version overwriting it as I first thought.
Upgraded to 1.1.2, seems to be working OK..
I noticed the uninstall of the initial release deleted the racers.xml file and not the newer version overwriting it as I first thought.
06-15-2015, 01:47 AM
#69
Hi, thanks for the great program and app, we installed the latest ourlaps program on our race control system and it worked really well, the only problem we had was that android devices could not connect through the wifi, we double checked the ips settings and re installed the app on multiple android devices with no luck however the apple products could connect and get the info, any idea why ?
we even connected multiple pc's via the system wifi and all worked 100%
we even connected multiple pc's via the system wifi and all worked 100%
06-15-2015, 01:22 PM
#70
Hi, thanks for the great program and app, we installed the latest ourlaps program on our race control system and it worked really well, the only problem we had was that android devices could not connect through the wifi, we double checked the ips settings and re installed the app on multiple android devices with no luck however the apple products could connect and get the info, any idea why ?
we even connected multiple pc's via the system wifi and all worked 100%
we even connected multiple pc's via the system wifi and all worked 100%
Manufacturer, OS version, Carrier helps troubleshoot.
Does the app just say "connection lost" as soon as you try to connect or does it close? Do you ever hear "welcome"?
Is the wifi assistant enabled or disabled? (In settings.)
If enabled. Does the wifi SSID contain "Ourlaps"? If it finds multiple "Ourlaps" SSIDs it will prioritize the one that contains "5G". Try disabling the assistant. Verify that it's connected to the right wifi and that it stays connected to it.
Does your wifi have internet or not? Android and some carriers have "connection optimizers" that go "this wifi has no internet, let me disconnect from that for you". (google: android wont stay connected to wifi)
Maybe there is a bug in the ip entry field? Do you press enter at the end of the ip address or not? Try clearing the field, type in the ip. Try it both ways. With enter and without.
06-15-2015, 02:39 PM
#71
Not sure, there are no known issues with Android.
Manufacturer, OS version, Carrier helps troubleshoot.
Does the app just say "connection lost" as soon as you try to connect or does it close? Do you ever hear "welcome"?
Is the wifi assistant enabled or disabled? (In settings.)
If enabled. Does the wifi SSID contain "Ourlaps"? If it finds multiple "Ourlaps" SSIDs it will prioritize the one that contains "5G". Try disabling the assistant. Verify that it's connected to the right wifi and that it stays connected to it.
Does your wifi have internet or not? Android and some carriers have "connection optimizers" that go "this wifi has no internet, let me disconnect from that for you". (google: android wont stay connected to wifi)
Maybe there is a bug in the ip entry field? Do you press enter at the end of the ip address or not? Try clearing the field, type in the ip. Try it both ways. With enter and without.
Manufacturer, OS version, Carrier helps troubleshoot.
Does the app just say "connection lost" as soon as you try to connect or does it close? Do you ever hear "welcome"?
Is the wifi assistant enabled or disabled? (In settings.)
If enabled. Does the wifi SSID contain "Ourlaps"? If it finds multiple "Ourlaps" SSIDs it will prioritize the one that contains "5G". Try disabling the assistant. Verify that it's connected to the right wifi and that it stays connected to it.
Does your wifi have internet or not? Android and some carriers have "connection optimizers" that go "this wifi has no internet, let me disconnect from that for you". (google: android wont stay connected to wifi)
Maybe there is a bug in the ip entry field? Do you press enter at the end of the ip address or not? Try clearing the field, type in the ip. Try it both ways. With enter and without.
We had the same issue at Tamiya during the practice for the last FredTech race. The issue didn't exist before then, I was previously able to use the app at TQ without any issue. The issues that all with Android phones was experiencing didn't occur until after you us all change the IP of the server. Before changing the IP on that same day it was working without issue but after the change that's when the issue started. Granted changing the IP as long as it's correct should affect the device not connecting but that's what happens. When you try to start the timer it errors out (it just says it can't connect). This has been occurring with all Android devices no matter the hardware type.
I should add I went back to TQ after that day and the app still won't connect to the server, even after deinstalling/reinstalling the package.
06-15-2015, 02:56 PM
#72
If so then that's a client issue for sure, I haven't updated the server there in at least 6 months. And that time the computer running ourlaps wasn't even plugged in.
When uninstalling did you clear all app cache data for Ourlaps?
I might have to go visit TQ soon with my Android and laptop it sounds like.
06-15-2015, 03:21 PM
#73
So nobody can connect at TQ with Android now but they can with iOS?
If so then that's a client issue for sure, I haven't updated the server there in at least 6 months. And that time the computer running ourlaps wasn't even plugged in.
When uninstalling did you clear all app cache data for Ourlaps?
I might have to go visit TQ soon with my Android and laptop it sounds like.
If so then that's a client issue for sure, I haven't updated the server there in at least 6 months. And that time the computer running ourlaps wasn't even plugged in.
When uninstalling did you clear all app cache data for Ourlaps?
I might have to go visit TQ soon with my Android and laptop it sounds like.
06-16-2015, 03:10 PM
#74
I had a simular issue at our track with an Android device as well, IOS and WP works fine
06-16-2015, 10:24 PM
#75
Not sure, there are no known issues with Android.
Manufacturer, OS version, Carrier helps troubleshoot.
Does the app just say "connection lost" as soon as you try to connect or does it close? Do you ever hear "welcome"?
Is the wifi assistant enabled or disabled? (In settings.)
If enabled. Does the wifi SSID contain "Ourlaps"? If it finds multiple "Ourlaps" SSIDs it will prioritize the one that contains "5G". Try disabling the assistant. Verify that it's connected to the right wifi and that it stays connected to it.
Does your wifi have internet or not? Android and some carriers have "connection optimizers" that go "this wifi has no internet, let me disconnect from that for you". (google: android wont stay connected to wifi)
Maybe there is a bug in the ip entry field? Do you press enter at the end of the ip address or not? Try clearing the field, type in the ip. Try it both ways. With enter and without.
Manufacturer, OS version, Carrier helps troubleshoot.
Does the app just say "connection lost" as soon as you try to connect or does it close? Do you ever hear "welcome"?
Is the wifi assistant enabled or disabled? (In settings.)
If enabled. Does the wifi SSID contain "Ourlaps"? If it finds multiple "Ourlaps" SSIDs it will prioritize the one that contains "5G". Try disabling the assistant. Verify that it's connected to the right wifi and that it stays connected to it.
Does your wifi have internet or not? Android and some carriers have "connection optimizers" that go "this wifi has no internet, let me disconnect from that for you". (google: android wont stay connected to wifi)
Maybe there is a bug in the ip entry field? Do you press enter at the end of the ip address or not? Try clearing the field, type in the ip. Try it both ways. With enter and without.
Our wifi has no internet, we even tried switching off our mobile data on the phones and only have wifi enabled but had the same result,
Unfortunately our next event will only be in some time so i will make a list of things to try to get it sorted and its an awesome practice tool