Wiznet’s WIZ110SR – Lessons learned so far

So I’ve played now with the WIZ110SR module on and off for a while. What have I learned so far. I unsuccessfully tried to upgrade firmware, and although I followed (or I like to believe I did) the instructions faithfully, I ended up with a brick at the very end. Nothing, the module would do nothing. It would happily draw power, but would not do a thing. Manufacturer recommended shorting the pads for SW1 (this is a switch for which the pads are already on the PCB, but is not populated), this would force a factory reset. Although an interesting approach, and probably useful in countless other times, it had no effect for this issue. Thankfully, Sparkfun gladly exchange the module for me and provided me a working one (they’re awesome that way). Out of this I learned three things: (1) why mess with updating the firmware if the previous one was working, (2) there is a nifty reset switch which may return me back to factory configuration if I mess up too bad (just don’t expect recovery from a failed firmware update), (3) Sparkfun goes out of their way to help their customers.

After receiving the new module, I had to re-do the configuration. A few things I re-learned in the process.
WIZ110SR – Initial/Default Setup
• WIZ100SR/WIZ110SR Ver. 04.01
• LOCAL IP ADDRESS : 192.168.11.2
• SUBNET MASK : 255.255.255.0
• G/W IP ADDRESS : 192.168.11.1
• Default Telnet Port -> 5000
• Default Serial Baud -> 57600, 8-N-1

To get these “default” values one must connect the module to the PC serial port, configure the port for 57600 baud (8-N-1) and listen to the port as power is applied to the module. During power-up the module will display its configuration. By default the module is configured to only accept requests through its Ethernet connection, so the Configuration Utility (explained here) must be used to modify the module’s configuration. To do this the PC Ethernet port must be configured to the same gateway as the module. An example configuration (for the PC Ethernet port) is shown below.
PC Ethernet Setup (example)
• LOCAL IP ADDRESS : 192.168.11.1 -> make it match the module’s gateway address
• SUBNET MASK : 255.255.255.0 -> make it match the module’s subnet mask

Once the PC is setup properly, the Configuration Utility can be used to setup the module as needed. I would suggest selecting Enable Serial Debug Mode checkbox. As for the IP configuration, make it match the router (or home network) as needed. A typical example, for most routers, is as follows:
• LOCAL IP ADDRESS : 192.168.001.101
• SUBNET MASK : 255.255.255.000
• G/W IP ADDRESS : 192.168.001.001

Additionally, the telnet port can be made match a standard Telnet configuration, and the BAUD can be lowered (to better accommodate uC) if the higher speed is not required.
• Telnet Port -> 23
• Serial Baud -> 19200, 8-N-1

Another thing I’ve learned is that the WIZ110SR can be directly connected to a uC by directly accessing the J2-J5 pads on the PCB. These pads are spaced at 0.1” and perfectly fit a standard header. The pads can be defined as follows:
WIZ110SR J2 – J5 Definitions

• J2 -> +5V (output from power supply)
• J3 -> GND (from power supply)
• J4 -> TX (TX from WIZNET)
• J5 -> RX (RX to WIZNET)

Do note that the WIZ110SR operates at +3.3V, so external interfacing with the serial (RS232) connections (J4, J5) should take this into account.

I now have a uC directly communicating with the WIZ110SR and a PC directly communicating to the WIZ110SR. I also have the WIZ110SR connected through the home network and have managed to access it within the network.

Example Telnet Response:
72271

It is still not complete, but it’s a start; I do have the uC reporting temperature to the PC through the WIZ110SR over the home network. The very basic training wheels right now :)

Next up is getting this information from outside the home network through some simple interface (not sure if Telnet is the answer yet). Maybe some sort of query language.