Well I recieved the IT-100 & WIZnet module today. 
Now I was reading the VERY informitive 1 page instructions that came with the IT-100 (iām being sarcastic). It states to use a straight thru cable. Is this being the case connecting to a PC or is this the case connecting it to the WIZnet module?
OK kudos for these manufactures for making these things crossed to start with, and to eliminate the need for a null modem cable; however it doesnāt help when the other device may have done the same!
Anyway luckily it appears the WIZnet has not done this, and I just confirmed by cracking opening my custom cable that it is wired straight 2>2 and 3>3
No null modem adapter required for the IT100 and the WIZnet combo at least.
Greatā¦ Iāll try working on it today when I get out of work. The mfg date on my IT-100 is 1/2011 so it just came off the assy line.
[quote=āstrangely, post:62, topic:167215ā]OK kudos for these manufactures for making these things crossed to start with, and to eliminate the need for a null modem cable; however it doesnāt help when the other device may have done the same!
Anyway luckily it appears the WIZnet has not done this, and I just confirmed by cracking opening my custom cable that it is wired straight 2>2 and 3>3
No null modem adapter required for the IT100 and the WIZnet combo at least.[/quote]
Well had a bunch of stuff to do today, but just finished installing my IT-100 & WIZnet modules. I configured the WIZnet & now working on the plugin in VERAā¦ While I had my panel downed I had to move a motion sensor that I wanted to move for awhile. Keep you postedā¦
SOS! Canāt seem to get this plugin to work.
Are you sure you have the WIZnet configured correctly?
I assume you are using the new plug-in?
Iām assuming its configured correctly, but Iām not sure if the plugin settings are right though. The plugin instructions were a little vague. As what are all the files I need to load, then when I create the device in vera what are all the fields that need to be filled, and when it display the device on vera what are all the settings I need to configure under advance. I was told to use the weather plugin as an example. I have the weather app working fine, this is far from close to the settings of the weather plugin.
The DSC plugin hasnāt worked for me eitherā¦
I have a brand new IT-100 plugged into a DSC PowerSeries PC1616. The cable I got from Monoprice and it is showing pl2303 in the serial port config, so looks like itās got the Prolific chipset.
I have tried putting the service id (urn:micasaverde-com:serviceId:AlarmPanel1) into all 3 variables like the help page explains and tried putting a ā1ā for the variablesā¦all with the same result. After saving, the UI refreshes and acts like itās configuring the zwave device, opening the I/O port, running Luaa start. It just keeps doing this infinitely. If I try to send the access code I get āDelivery Failedā.
Iāve tried re-installing the plugin too. I emailed tech support and got a reply on Feb. 8ā¦
āWe identified that problem in the firmware version youāre running now and solved it. Our engineers are working on developing a new firmware version which will be out soon. You will be notified on the Dashboard when that happens and I can assure you that a lot of improvements happened, including this fix.ā
I hope the firmware fix comes soon. Does anyone else have any suggestions to make it work?
Ok so a couple of things:
Donāt follow the Wiki as the information will just confuse you.
The Wiki is also only applicable to MCVās plugin anyway.
If using the MCV plugin, then once youāve uploaded all the files, created the plugin, and then associated the serial port, you then just need to follow my post here:
http://forum.micasaverde.com/index.php?topic=5154.msg33638#msg33638
If anyone is wanting to run the DSC version for the time being then I recommend downloading it from the MiOS marketplace as the only part that needs to be done then is associating it with a serial port.
I will write a guide, but the problem is that Iām running the V1 plugin by @ guessed which is already obsoleted by a V2 plug-in that heās nearly finished working on as part of a standardization effort for all the alarm vendor version.
I havenāt started to run the V2 of the plugin yet so it seems silly to write something until Iāve played with it.
strangely howās it going my friend. First off, on the WIZNet. what should be the proper config? As should it state āconnected vs not connectedā on the config tool. Also, Under network, should the server IP be the same as the WIZnet IP or is that to be VERAās IP address. Operation Mode, leave it as Mixed or should it be set to client or server. Lastly baud rate leave it at 9600 or something different. I need to iron out each one at a time. It will make things A LOT easier to debug.
As for the plugin I downloaded the lastest one from guessed, so I think itās V2.
Iāll take a screen grab of mine and post it in about 10 mins. Youāll just need to copy everything other than my specific IP setup.
Strangley, thanks for taking me back to your previous post on ignoring the wiki. It finally worked! I was testing all the settings and set off the alarm and woke up my whole neighborhood at 11pm!
Not sure if it had something to do with me updating the firmware from 1047 to 1186 or not.
Thanks again.
Thanks youā¦ Much appreciatedā¦ ;D Iāll PM you my personal email address, not sure if you want to post your IP config on an unsecure site.
Its OK to post here as its just a common NAT address 
Mine is setup as DHCP, but I have my router set to assign this based on the MAC address. If this is not possible with your router then obviously the last thing you want is the address to changeā¦ so make it static.
Glad to see that it worked for you. Good heads up, last thing I need is to wake up the wifeā¦
[quote=ākwik5, post:72, topic:167215ā]Strangley, thanks for taking me back to your previous post on ignoring the wiki. It finally worked! I was testing all the settings and set off the alarm and woke up my whole neighborhood at 11pm!
Not sure if it had something to do with me updating the firmware from 1047 to 1186 or not.
Thanks again.[/quote]
No, itās the same āv1ā version that @strangely has. I wanted to ensure that you could get the basics working for yourself before launching the [just converted] āv2ā version upon you 8)
A very early, very preliminary, āv2ā version is what I checked into the trunk area of the DSCās Trac space in the /trunk directory.
Itās still evolving though, so it should not be picked up by users yet. Iām using it as a vehicle to validate the āv2ā Partition API under the "standardization track. I also took the opportunity to gut the prior āv1ā implementation code from it, to ensure that no CP owner would write against the old specā¦ no wine before itās time 
I configured the WIZnet to your examples (I wasnāt that far off), but still states Not Connected. Iāll have to down the panel tomorrow after work & power it up with the WIZnet connected to the IT-100. See if that corrects it.
It will only show connected if something on the ethernet side is connected to something on the RS232 side. (Vera to the IT100 for example) If you donāt have it linked with Vera and the IT100, then disconnected is correct. The connection state isnāt to show that the configuration program is connected Its just a tell tale trouble shooting indication to show you if the respective devices have handshaken etc.
Donāt forget that when you enter the IP for this in the plug-in in vera, then using mine as an example, you also need to enter the port number tooā¦ e.g 10.0.0.190:5000
Ah, that makes sense I guess. Would be nice if the WIZnet had a test function, so that we knew that it was communicating to a serial device. Thanks for the heads up.
[quote=āstrangely, post:78, topic:167215ā]It will only show connected if something on the ethernet side is connected to something on the RS232 side. (Vera to the IT100 for example) If you donāt have it linked with Vera and the IT100, then disconnected is correct. The connection state isnāt to show that the configuration program is connected Its just a tell tale trouble shooting indication to show you if the respective devices have handshaken etc.
Donāt forget that when you enter the IP for this in the plug-in in vera, then using mine as an example, you also need to enter the port number tooā¦ e.g 10.0.0.190:5000[/quote]
Still pulling my hair out. Though I did get to test my WIZnet with a serial loopback adapter tonight. I found a really nice program that I can test serial ports via TCP. That at least confirms that my WIZnet is working. Now I have to hammer down the settings in Vera