After receiving our Limelight today, I flashed it, and had it working for about 15 minutes before it decided that it no longer wished to stream data. I’ve reset it, where after digging it went to 10.36.23.129, but it no longer shows up on Limelight Finder and the config webpage isn’t responding. It’s direct powered, not POE, and the network status lights are good. The firmware definitely works, because the top LED’s are responding per the documentation (orange flashing because it’s not static, green flashing when it sees something). Anyone have any ideas for help here?
Is .129 the static IP you set, or had you just been using that as the dynamic address?
You can always reset it, and hopefully see it show up again in the finder.
I’ve reset it a few times, and it keeps falling back to .129.
So, DHCP falls back to .129. Then you re-configure it with a static IP (normally 10.te.am.11) and it works for a while, and it falls back to DHCP and gets .129?
Based on your post, I’m guessing you’ve read and followed the Recommended Settings section at their documentation site.
I had it initially running, based on documentation. Then it stopped broadcasting. Reset, power cycle, became .129, and not responding to attempting to use the port, or limelight.local. This issue has persisted through two re-flashes. It still pings, and there are activity lights from the ethernet port, so it’s definitely on the network and receiving an address from the radio. AngryIP sees the active host, but does not have a hostname, or any active ports.
Do you have a PoE injector to see if that provides any different stability?
I’ll have to try it, but I originally tried the PoE injector and it was not getting power at all.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.