OK, so here are my insights in to setting up the net module and getting it working with iReef and over the net. I'll start with the basic stuff and I'll point out where I had issues or did not quite understand the instructions that I had found, what I did to get around it the issue, and any lesson learned through the process.
Step 1. Setting up the NET module on the RKE system.
This was pretty straight forward. I used a direct connection (Ethernet cable) from the net module to my router. I did not try to set up a gaming controller or anything to make it wireless but obviously you can if that is needed for your setup.
A couple of tips for this step... make sure that under the SYSTEM COM options you have NET Control set to "ON" ... I missed this step and wasted about an hour! D'oh! Don't forget you also need to set myReef to "ON". This is not for the NET setup but for updating or "flashing" the module.
I'll divert for a minute here... I had to update the firmware on my NET module from 2.07 to 2.09 (the most current) before I started. I had a problem when I tried to do the update with my SID 2.08. First start MyReef 2.0 on your PC, then plug in the SID, then When I plugged in the NET to the SID, it showed up correctly and it was the only module plugged in. I choose the update function in MyReef and it started the update process. For some unknown reason the first update step failed, but the second update step completed. It looked like it worked, but when it went back to the main menu the myReef no longer recognized the NET module and it came up with FFFFFFFF as the module. I thought I was screwed. I was able to click on the "FFFFFFFF' in the left hand menu and a drop down screen came up which allowed me to identify the module as the NET module and attempt the update again. I could not get it to work. After searching the DA forum I saw a suggestion from Oscar to 1) change the USB port I was using on my PC, 2) plug the net module in to the SID using BUS 1, and 3) put a cable in the empty BUS 2 port not connected to anything else. I did all that, and thankfully the update worked this time and I was able to flash the 2.09 code. Remember that you also have to follow the directions to upload the 2.09 Bin file on your computer as well or the web page will not work. The directions for that are with the RKE firmware update page on the DA forum.
OK, back to the NET setup. Three was one more thing to check on your RKE headunit. Go to "IN" and select the "NET" module. Now select "STATUS" and you should see the iP address of your net module IP=192.168.1.xx which you will need when you setup the router.
STEP 2 - setting up the router
I followed the directions that Oscar has posted in the DA forum for Port forwarding and DDNS for Dummies http://www.forum.digitalaquatics.com/viewtopic.php?f=22&t=7098">http://www.forum.digitalaquatics.com/viewtopic.php?f=22&t=7098</a>
Oscar directions and my experience below: for Static IP Service:
1. Go to [IMG]http://www.no-ip.com/">http://www.no-ip.com</a> and sign up for a free account - I used this service but it was not free
2. Once you register and activate your account via the email they send you can create you new host name
3. From the home page, while logged in, click on the "Your No-IP" link at the top right of the screen
4. Click on the tab that says Hosts/Redirects
5. Click the button that says "Add Host"
6. Type the first part of the host name and then choose the rest from the drop down under the "No-IP Free Domains list - you can call it anything you want, for example "johns-reef" and pick an option form the list for the remaining part of the name ,so you end up with a name like johns-reef.no-ip.info as an example
7. You can set the port 80 redirect if you want. It will just send you to your IP/port and show those in the address bar and not show your URL but I don't think it matters.
8. Do not worry about the IP since the updater will take care of that
9. On the left hand side click the link that says "Download Client"
10. Choose your OS, download it then install it
11. Open the client from the start menu and enter your email and password then choose the host name you want forwarded
12. To make sure the client runs each time your system reboots you should copy the shortcut from the "No-IP DUC" folder and paste it in your "startup" folder in the start menu - IF you are running WINDOWS 8 this is a bit trickier! I had to google how to update the start menu in windows 8 to figure it out. THey made it a lot harder to do but you need to do it so that each time you restart your PC the service starts up....
13. Now go through the steps for your specific router brand.
That part worked great for me and I had no issues. I also downloaded the DynDns updater service for the PC:
[IMG]http://www.dyndns.com/support/clients/">http://www.dyndns.com/support/clients/</a>
Not sure that I actually needed to do that but I did.
Step 3. Router Setup
Again, follow Oscar's directions in the DA post for your router. I included the ATT U-Verse directions here because I had a couple of hiccups along the way I wanted to point out.
2-Wire:
Port Forwarding:
1. Open up a web browser (Internet Explorer or Firefix) on a computer that is connected to your 2-Wire router.
2. Open your 2-Wire router's control panel in the web browser by going to this location [IMG]http://gateway.2wire.net/">http://gateway.2wire.net</a>. If that doesnt work try [IMG]http://192.168.0.254">http://192.168.0.254</a> (In my case the ip address was different but it is printed on the 2wire model as well as the device access code which you will need to make changes to the firewall)
3. After you are logged into your 2Wire modem, click the Firewall tab.
4. Click the Firewall Settings link under the tab to open the Edit Firewall Settings page.
5. Click on the Add a new user-defined application link to open the Edit Application page.
6. In the Application Name field, enter a name for the application profile. You can enter any name you like,
although it’s recommended that you use the name of the application (for example, NET Module).
7. In the Definition panel, create a definition for your application. A definition consists of a series of protocol-specific ports that are to be allowed through the firewall.
8. In the Protocol field, select the TCP or UDP radio button. Choose TCP since all http sites are TCP.
9. In the Port (or Range) field, enter the port that your NET uses. Put the same value in the From and To fields. (This is the ip address that you got in step 1 from the RKE 192.168...)
10. In the Protocol Timeout (seconds) field, you may optionally enter a value for the amount of time that can pass before the application “times out.” I recommend that you leave the field blank, in which case the system uses the default values (86,400 seconds for the TCP protocol; 600 seconds for the UDP protocol).
11. In the Map to Host Port field, leave that field blank so that it will default to the port you defined above.
12. In the Application Type drop-down menu, select None (Default).
13. Click ADD DEFINTION to add the values to the profile definition list.
14. Click DONE.
15. Click on the Firewall tab again, then click on Firewal Settings.
16. Select your NET from the dropdown where it says "Select a Computer". (in my case I had to find the port on the router that was associated with where I plugged in the net module because the name showed up as Unknown. I selected that port and followed the rest of the directions)
17. Click the Allow individual application(s) radio button.
18. In the Applications panel, select the application that you created for your NET (E.G. "NET Module").
19. Click the ADD > button. The application you selected now appears in the Hosted Applications pane.
20. Click DONE.
I do not believe the newer 2-Wire supports DDNS so you will need to install the DDNS updater service to keep your IP updated at dyndns.com. (oh yeah, this is why I added the DDNS code!)
Now once I had this all setup, I was ready to access the rkm-net page from both within and outside of my network.
To test your lan connection just open up a browser and got to the rkm-net page. You should see the login screen where you can enter your ID and password.
To test the internet connection, enter the ip address that your no-ip provider gave you as the external address. for example; 99.98.155.xx:7001/ this should also take you to the login screen. you should also be able to enter the url you set up in no-ip, i.e, johns-reef.no-ip.net and get the same result.
Assuming this all worked for you, then you are ready to setup iReef
Step 5 iReef setup
I had downloaded the app to my iPhone awhile back, but it looks like it may not be in the app store anymore.
In the settings screen you should put the external IP address from no-ip 99.98.155.xx (for example) and in the Port field I use 7001
This should connect to the Net module. When I first set up the iReef it would connect but I had no data. I figured out that the only data that gets sent is the RSS feed so I had to go back to rkm-net module and turn on logging for any channel I wanted to see on the iReef screen. Once I turned on logging, those channels appeared on iReef.
Although this is next part is not related to the RKE NET setup, I also have a remote Cam setup on my tank to keep track of things while I am gone. My setup was VERY simple and quick.
STEP 6 - Remote camera setup
First, I just used an old webcam that I had laying around and set it up pointing at my 210.
Second, I went to EyespyFX.com and downloaded the free webcam broadcaster software
Third, I registered for the service and setup the id and password.
Fourth, I went through the simple setup steps to assign the webcam to my account
as soon as that was complete, I could view the webcam over an internet connection that was private and required my login
the last step I took was to download the eyespyFX app to my iPhone. This cost a couple of bucks but I was able to view the webcam of my tank on my iphone. Now I can easily check the tank parameters and see the tank to make sure everything looks ok while I am traveling.
Since I am on the road a lot, this was worth it for me!
I hope this helps anyone going through the effort to set up the NET module and route.
Let me know if I can help, I am not expert but just went through the battle.
Bob Z
