Make your own Wireless Photo-finish

We have been playing with a set of ESTeem wireless b/g modems for our setup with initial good progress. They can get about 3 miles line of sight with the omni antenna's but can be stretched to about 33 miles with directional antennas. Pricey but may be just the right piece of gear at certain events.

http://www.esteem.com

195e/g is the product.

JK

I normally use the lynksys 54g .. I connect the the router directly to the camera .
My pc is over the athletics lane (about 30 mts) and all are Ok..

bye

I'm very interested in your solution sylvan! Where can I find a guide of your work?

Thx

davide

Hi David, there is no guide for that. We only connect the camera to the C-Box and the C-box to the Wireless router. The best way is to use Static IP with your router as 192.168.0.x and your computer as 192.168.0.y on the wireless Ip config of your computer.

Cannot use this for event who need acurate time if you are not able to reach the start button of the c-box.

I know this is an older thread, but I have been trying to get this to work and am not sure where I'm stuck. Trying to use a Netgear N900 to hook my camera up wirelessly to the finish lynx computer. Are there specific static IPs I should be using for the computer and router?

You should set in static ip adresses 192.198.0.x and turn off the DHCP

192.198.0.x or 192.168.0.x...I have it set to 192.168.0.x which is what finishlynx suggests but I have not disabled dhcp. I can try that...did you do anything to configure the router?

Got it working! Thanks RSS! Have you had any issues with losing a connection and missing images?

I only test it for one complete day for cycling and i had ni error

quote:

n

And what about delay time to see the image on screen? how much percent is late against wired connected?

There is a slight delay, but on a one camera set-up it works fine. When adding a reverse angle camera (wired into the router) finishlynx throws a bit of a fit and says that timer synchronization is off due to a poorly configured network or too much network traffic. Any networking guys have any ideas on how to solve that problem?

We are currently testing the same type of setup just to use on our reverse angles instead of running cat5 over or under (where available) to the other side of the track.

I have some time this weekend while at a meet to play around with it a bit & will let you guys know what we find out.

Any questions or hints - shoot me a email @ timing@njraces.com

Any luck with that reverse angle camera? I think part of the problem is with the setup we were using was that we were running everything through the wireless router and connecting to the wireless network on finishlynx...I don't know if having the timer enabled hardwired into the Lynx computer would solve the issue or not.

Played around with the wireless reverse angle last week and had success.

We had to boot each camera up one at a time but it didn't take too long and the images were instant.

We had our main camera hardwired - with Radiolynx plugged into the back of the camera (connect connection box). Our main camera is hardwired into our wireless router & then had our wireless unit separate.

Today we test with our wireles router and works great, well, some problems with power energy, and two reconections, but the Laptop using and "Alfa Wireless Card" received well the finishlyx images

So, I've been following this thread for a while, and finally have something to add.

A few years ago I played around with the same router as the original poster, a Linksys router with WRT-DD firmware and boosted signal. I had some success but the range was disappointing. Then about two years ago I used a DLink DIR-655 at a small HS meet with decent success. No missed images. But I wasn't always comfortable with it, and sometimes it straight up lost the signal.

A few weeks ago I got permanent access to a second camera and got to thinking about things. After attending the Division III indoor meet, I saw DeltaTiming using some EnGenius wifi receivers to control their Galaxy Displays, and started to think about what I really wanted to do.

The most important thing is to have the near camera hardwired, but the reverse camera is always a challenge to deal with. I hate running wires over the track, but I want a more secure setup (without forking out $$$$ to Lynx for their AirLynx).

I decided to pick up a DLink DAP-1522 Wireless Bridge/AP to connect to the DIR-655. Setup of the bridge took five minutes, and I was able to hide the wireless network to avoid any unnecessary traffic (network was secure). Yesterday we put it to a real test, using the bridge to connect an IdentiLynx Pro and a regular B&W EtherLynx camera across 30 yards to the router, which hardwired the primary color Etherlynx.

We had a few issues with alignment, the camera was slower to react than when hardwired, but the short bursts of packets during capture were handled very well, but did take a little longer to arrive.

No major issues over the course of the day, feel pretty good about the complexity, as I don't have a great amount of network/it knowledge.

hello, I read the comments above and thank you, I was able to create a wireless bridge for my reverse angle camera (2nd camera).

My current set up is that the main camera (timing camera) is directly plugged into my router which is plugged into my laptop. For the reverse camera, it is plugged into a wireless router then send a signal to a Edimax N300 universal wi-fi bridge, which is tehn plugged into my router. Everything works great (recording looks great), however I noticed a pop up window in my finishlynx software that says "Camera timer synchornization failed. This is a serious problem which could mean that the times on some cameras may be incorrect....."

does anyone know if this could cause a problem with my track results (remember that my main camera is hard wired into my laptop, only my reverse camera (non-timing black and white)). I just want to use the reverse camera in those situation that I need to break a tie.

I had the same issue and warning message. I didn't really investigate it but if anybody has more info about that, it could be great.

I've had the message as well when running the off side as part of one system, time tracking seemed off but did not bother to really check.
Did not get the message when running the infield camera and ID Lynx to a wi fi hub and the computer operating on the out field connecting to the wifi, boot time was slower than normal. Hub was a normal "N-150" Ran out field camera as separate "back up" system.

I'm not sure that's a huge problem for a backup/reverse angle camera. I've run an IdentiLynx via wireless bridge, and seen that error before... I think it's related to the synchronization technique. If it's not being used for the actual timing, it's not an issue.

I've also run a reverse/backup camera on a separate laptop and never had the error (when using a bridge).

I think a packet must be dropped from time to time. Not sure if it's really worth worrying about.