I have connected the cable to the router. I powered up the 3-component shake. Blue LED lights, Red light is on steady. green lite next to red light blinks, yellow light on cable to router is steady with occasional blinks.
rs.local does not connect
Fing does not find seismometer.
What is next step?
Hello TimLong, welcome to our community!
Thank you for the detailed explanation. Is the green light next to the orange light on the LAN Cable port not blinking at all? The orange light should be steady, while the green should be blinking.
At this point, you should access the admin panel of your modem/router and see if the Shake has been assigned a valid IP address from the modem/router itself.
If it did assign an address, you can access rs.local/ by entering the IP address in the address bar of any browser of a PC connected to the same local network.
You can also try, if you haven’t already, to shut down everything, turn on the modem/router first, wait for it to fully connect to the internet, and then connect the Shake and turn it on.
I’ll wait for the results of these new tests.
The orange light (yellow?) next to the LAN cable is no steady except for about every 15 seconds it blinks off about 7 times. I do not see a green light next to the LAD cable.
There is next to the power cable a steady red light and a green light that blinks about once a second, time interval varies.
I disconnected the LAN cable at the seismometer and reconnected it with no change.
I replaced the LAN cable and put it into a different position on the Router
Powered off the router and turned it back on.
I waited about 2 hours (went to lunch)
Fing recognizes the seismometer and finds everything else turned on…
Lights on seismometer same as described before powering down and powering up the router.
Rs.local does not connect.
Was able to connect with ip address.
Do not know if it was cable or wrong plug on router.
Thanks for advice.
http://rs.local/ does not connect.
Replaced the LAN cable.
Plugged into different port on Router.
Waited about 10 minutes.
Blinking sequence of LAN port (yellow light) changed.
1 Like
Happy to hear that now the Shake is connected and you can access it via its IP address.
I am not sure why before it was not working, probably the modem restart helped? Sometimes this is the case, but even changing ports could have been a factor.
Anyway, enjoy your Shake!
Has the IOGear GWU637 been checked out for connecting raspberryshake to WiFi internet connection plugged into ethernet port.
Sounds like it could be much simpler than the USB WiFi dongles.
Tim Long
1 Like
I looked at those, and a few similar devices - they should work, and as you say, probably better idea than USB dongles. The problem is that if you look at a the reviews, they are a bit spotty. Mostly with the devices failing after a relatively short time.
I ended up using one of these, for a similar price:
I have used Ubiquity devices like this before, for links over a mile, so it’s a bit overkill, and not really making use of the full capabilities. I think there were two config changes from the default settings to get it going.
I deliberately chose the 2.5GHz version because it’s cheaper, and (for me) it has to connect to the house WiFi from within a metal pole barn - better chance of that working at 2.5GHz than 5GHz.
It is considerably bigger than the device you are looking at though.
2 Likes
Hello TimLong,
Not to my knowledge, but if you test it, feel free to discuss your findings with us, so that if other Shakers are able to use that module they can follow some guidelines.
We are always open to suggestions and tests made by our extensive community!
Test of IOGear Ethernet-2-WiFi connection. (GWU637). One week before this post I received a IOGEAR Ethernet-2-WiFi Universal wireless adapter. I first set up the 3-component raspberryshake using the ethernet plug on my wireless router. (slight delay because I put the ethernet cable in the WAN plug first) After that correction everything went smoothly. Next I set up the GWU637 link and made the WiFi connection. Only a couple steps using the WPS button. Took about a minute. Then I unplugged the ethernet cable connected to the raspberryshake from the router and put it into the GWU637. It again took about a minute but the recorded signal continued. No problem. Next I disconnected and turned off the raspberryshake and GWU637 and moved it to the basement, about 50 ft from the router. Plugged everything back in and after a short period, a minute or two. The system started back up and running. It have been running in that configuration for a few days now.
Concerns: I was using the power supply that came with the GWU637 so both systems were using a plug to AC. One option is to use the USB plug on the shake computer for power. Have not tried that yet. My concern is that the GWU637 is running a bit warm, but not as worm as other WiFi connectors I have used. Someone else expressed concern that some reviews indicate a high failure rate. However, the type of use here is probably not as heavy as the use they are designed to handle.
Conclusion. It is a simple and inexpensive way to connect to WiFi.
3 Likes
Thank you for your extensive testing and feedback TimLong, I’m sure that it will be useful to others that come here on our community!