Aprilaire 8825 Errors
davegrov
Posts: 114
I'm in the process of completing a conversion of my Aprilaire Viewstats from ICSNet to the IP based 8825. The physical install was pretty easy, but had to remember to reprogram from one to three 8870's in the system. My problem is in the AMX Duet Module. I am getting this errors in diagnostics. Is this the correct way to define the device? Or does it need to be 0:5:2 for system 2?
dvViewStat = 0:5:0 //ViewStat on IP
Can anyone help?
Line 774 :: SocketConnection.createSocket : IO exception - 16:26:46
Line 775 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: Connection failed! - 16:26:46
Line 776 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: IPConnect() connecting... - 16:26:46
Line 777 :: createSocket() 192.168.1.202,10001 - 16:26:51
Line 778 :: SocketConnection.createSocket : IO exception - 16:26:51
Line 779 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: Connection failed! - 16:26:51
Line 780 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: IPConnect() connecting... - 16:26:51
Line 781 :: createSocket() 192.168.1.202,10001 - 16:26:56
Line 782 :: SocketConnection.createSocket : IO exception - 16:26:56
Line 783 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: Connection failed! - 16:26:56
Line 784 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: IPConnect() connecting... - 16:26:56
dvViewStat = 0:5:0 //ViewStat on IP
Can anyone help?
Line 774 :: SocketConnection.createSocket : IO exception - 16:26:46
Line 775 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: Connection failed! - 16:26:46
Line 776 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: IPConnect() connecting... - 16:26:46
Line 777 :: createSocket() 192.168.1.202,10001 - 16:26:51
Line 778 :: SocketConnection.createSocket : IO exception - 16:26:51
Line 779 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: Connection failed! - 16:26:51
Line 780 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: IPConnect() connecting... - 16:26:51
Line 781 :: createSocket() 192.168.1.202,10001 - 16:26:56
Line 782 :: SocketConnection.createSocket : IO exception - 16:26:56
Line 783 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: Connection failed! - 16:26:56
Line 784 :: com.amx.duet.impl.aprilaire._8825.dr1_0_0.AprilAire8825: IPConnect() connecting... - 16:26:56
0
Comments
There's been previous post on ICSNET vs RS422 in regard to viewstats and I guess the consensius was ICSNET for large systems 20 + stats because its faster or something but its not like these stats have much to says so collisons would be rare and inconsequential.
I like the 422 but never did anything that large with it. By using the IP comms to connect your still essentially running all coms on a 422 bus so unless you are out of ports or have wiring issues you won't be gaining anything, actually you're just adding another piece of equipment that can create problems.
I may be completely wrong in all regards (I often am) but it seems to me if you have the port and the wires available don't use the brick.
Thanks for your reply. There are no DIP switches or configuration parameters in the the Aprilaire block or on the embedded Web Server. One of the things that cuaght my interest in the conversion was the ability to program (within the web server) the ability to changes the temperature set points on a schedule. This method saves considerable time and $$ from a programming standpoint. This was something that AMX had in Landmark that is a big customer request.
(I beleive HomeLogic is the OEM)
This quote was taken from the AMXViewstat .doc in the Duet module. Now what exactly this means is anyones guess but it would imply that there is either a dip switch or a setting that is change able through the web server. Maybe it's buried somewhere you haven't found yet. I don't think it would be possible to do both tasks, used via web server and com link to netlinxs at the same time unless "passthru" is appended to the string or something.
I would agree that the modules should include a scheduling feature but maybe they expect you to use !Schedule or just create your own with a simple GUI and a little code. IMHO having clients use a PC to make changes to programs or device controlled by AMX defeats the pupose of AMX in the first place. A users point of command, control and interaction with connected devices. If they want to access the system via PC have them VNC a TP for control thereby re-empahsizing the role of AMX not dimishing it.
I am curious so if you finds the answer please post it!
Dave, if you still need a scheduler module (non Duet) you're more than welcome to try mine.
Thanks, I'll show it to my boss and see if he likes it. The attachment still active? I know I downloaded it once to take a look at, but I lost my hard drive, and my downloads folder wasn't on the backup.