Any interest in wireless RGB LED strip lights with HomeSeer?

[kenrad]

Kevin,

How many controllers will your plugin support with wifi, I am looking at adding a lot more led lighting to my home and might end up with a lot of controllers eventually.

I have been looking into this for a while but I figured that it would be alot of remotes to control the lighting but now with your controllers it add a awesome way to integrate them into homeseer.

Cheers Ken

[Kevin Lo]

Kevin,

How many controllers will your plugin support with wifi, I am looking at adding a lot more led lighting to my home and might end up with a lot of controllers eventually.

I have been looking into this for a while but I figured that it would be alot of remotes to control the lighting but now with your controllers it add a awesome way to integrate them into homeseer.

Cheers Ken

It support multi-controller , there is no limit.

[Pete]

Hello Kevin,

I am testing tonight on two HS2 servers. I initially validated the setup program to work without running Homeseer to make sure it connected. It did and I can control the RGB controller with the set up program.

Copied over the new DLL. Validated the USB-TTL port and I made sure the INI file matched the com port number for the RGB controller.

I left debug on and not seeing any debug in the HS logs.

The HS Plugin to RGB controller control is not working at this time.

This is what I see in the HS logs.

1/13/2014 10:57:47 PM Device Control Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) ON
1/13/2014 10:57:54 PM Device Control Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) OFF
1/13/2014 10:59:59 PM Device Control Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) ON

I shutdown Homeseer and shut down computer and rebooted.

It is working now but showing an error in the Homeseer logs. I am though able to control the RGB controller with the 4 variables created by the plugin.

1/13/2014 11:08:22 PM Device Control Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) ON
1/13/2014 11:08:24 PM WifiRGB (3P) Error ComSend Error: System.TimeoutException: The operation has timed out. at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) at HSPI_WIFIRGB.HSPI.ComSend(Int32 ClientNo, Byte[] ByteArr, String Command)
1/13/2014 11:08:27 PM Device Control Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) OFF
1/13/2014 11:08:28 PM WifiRGB (3P) Error ComSend Error: System.TimeoutException: The operation has timed out. at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) at HSPI_WIFIRGB.HSPI.ComSend(Int32 ClientNo, Byte[] ByteArr, String Command)
1/13/2014 11:08:32 PM Device Control Device: WifiRGB (3P) WifiRGB (3P) Device Red Channel (#1) ON
1/13/2014 11:08:33 PM WifiRGB (3P) Error ComSend Error: System.TimeoutException: The operation has timed out. at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) at HSPI_WIFIRGB.HSPI.ComSend(Int32 ClientNo, Byte[] ByteArr, String Command)
1/13/2014 11:09:02 PM Device Control Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) ON
1/13/2014 11:09:04 PM WifiRGB (3P) Error ComSend Error: System.TimeoutException: The operation has timed out. at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) at HSPI_WIFIRGB.HSPI.ComSend(Int32 ClientNo, Byte[] ByteArr, String Command)

Enabled Debug and see it now.

1/13/2014 11:16:08 PM - WifiRGB (3P) Info - WifiRGB (3P) - shutting down I/O ...
1/13/2014 11:16:50 PM - WifiRGB (3P) Info - WifiRGB (3P) version 1.0.3.1 Starting ...
1/13/2014 11:16:50 PM - Plug-In - Initializing Plug-in: WifiRGB (3P)
1/13/2014 11:16:50 PM - WifiRGB (3P) Debug - Entered InitIO() function.
1/13/2014 11:16:50 PM - Plug-In - Finished initializing plug-in WifiRGB (3P)
1/13/2014 11:16:58 PM - Device Control - Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) ON
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - SetIOEX Receive : #4 Command : 2 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - SetIOEX Receive : #4 Command : 19 , Brightness Value : 100 , Data1 Value : 0 , Data2 Value : 0
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - ComSend Called - Client: 1
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - ComSend ByteArr(0) - 32
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - ComSend ByteArr(1) - 221
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM2Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM19Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM3Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM12Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM13Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM14Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM15Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM16Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM17Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM18Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM4Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM5Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM6Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM7Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM8Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM9Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM10Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - COM11Found
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - Opening ComPort
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - Sending Data...
1/13/2014 11:16:58 PM - WifiRGB (3P) Debug - Command Sent : AA 20 DD FF
1/13/2014 11:16:59 PM - WifiRGB (3P) Error - ComSend Error: System.TimeoutException: The operation has timed out. at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) at HSPI_WIFIRGB.HSPI.ComSend(Int32 ClientNo, Byte[] ByteArr, String Command)
1/13/2014 11:16:59 PM - WifiRGB (3P) Debug - Last RGB Dim Value Return :
1/13/2014 11:16:59 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/13/2014 11:16:59 PM - WifiRGB (3P) Debug - SetIOEX Receive : #1 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/13/2014 11:16:59 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/13/2014 11:16:59 PM - WifiRGB (3P) Debug - SetIOEX Receive : #2 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/13/2014 11:16:59 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/13/2014 11:16:59 PM - WifiRGB (3P) Debug - SetIOEX Receive : #3 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0

[Kevin Lo]

Hello Kevin,

I am testing tonight on two HS2 servers. I initially validated the setup program to work without running Homeseer to make sure it connected. It did and I can control the RGB controller with the set up program.

Copied over the new DLL. Validated the USB-TTL port and I made sure the INI file matched the com port number for the RGB controller.

I left debug on and not seeing any debug in the HS logs.

The HS Plugin to RGB controller control is not working at this time.

This is what I see in the HS logs.



I shutdown Homeseer and shut down computer and rebooted.

It is working now but showing an error in the Homeseer logs. I am though able to control the RGB controller with the 4 variables created by the plugin.



Enabled Debug and see it now.

Pete , is that mean now you can control the device via Homeseer device ?
According to the log , it seem can be send out the data to COM , but cannot read the data from the COM.

[Pete]

Pete , is that mean now you can control the device via Homeseer device ?

Yes

According to the log , it seem can be send out the data to COM , but cannot read the data from the COM.

Yes; why is that?

I have left the serial port baud rate at 9600. Should I set it to something else?

BTW and I think this was mentioned before relating to the integration of an RS-232 port to TTL right on the RGB device versus the use of the external USB to TTL device.

Noticed that the external device does get a bit warm; but not hot.

It is not plug n play with Homeseer for whatever reasons. If I pull the plug on the USB-TTL device while running Homeseer I do get a microsoft error showing up in the middle of my screen and that also shuts down Homeseer but doesn't cause a BSOD in the wintel OS.

[Kevin Lo]

Yes



Yes; why is that?

I have left the serial port baud rate at 9600. Should I set it to something else?

BTW and I think this was mentioned before relating to the integration of an RS-232 port to TTL right on the RGB device versus the use of the external USB to TTL device.

Noticed that the external device does get a bit warm; but not hot.

It is not plug n play with Homeseer for whatever reasons. If I pull the plug on the USB-TTL device while running Homeseer I do get a microsoft error showing up in the middle of my screen and that also shuts down Homeseer but doesn't cause a BSOD in the wintel OS.

Pete , can you check your RS232 settings , it should be 9600,n,8,1 , no Flow Control.
And please also check you've update the lastest driver.

[Pete]

Hello Kevin,

I am using Windows 2003 standard 32bit OS for my base two Homeseer 2 installations.

I did notice that the Prolific driver was from 2009 that auto installed when I plugged in the USB to TTL device.

I had left the baud rate at the default of 9600 baud.

I upgraded the prolific USB driver to most current.

The "issue" though does still remain with the VB script error showing up in the log when I turn on and off the RGB device.

The RGB controller still does work though with the error in the log relating to comm.

1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - SetIOEX Receive : #4 Command : 2 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - SetIOEX Receive : #4 Command : 19 , Brightness Value : 100 , Data1 Value : 0 , Data2 Value : 0
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - ComSend Called - Client: 1
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - ComSend ByteArr(0) - 32
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - ComSend ByteArr(1) - 221
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM3Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM12Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM13Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM14Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM15Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM16Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM17Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM18Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM4Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM5Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM6Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM7Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM8Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM9Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM10Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM11Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM19Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - COM2Found
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - Opening ComPort
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - Sending Data...
1/15/2014 6:45:14 AM - WifiRGB (3P) Debug - Command Sent : AA 20 DD FF
1/15/2014 6:45:15 AM - WifiRGB (3P) Error - ComSend Error: System.TimeoutException: The operation has timed out. at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) at HSPI_WIFIRGB.HSPI.ComSend(Int32 ClientNo, Byte[] ByteArr, String Command)
1/15/2014 6:45:15 AM - WifiRGB (3P) Debug - Last RGB Dim Value Return :
1/15/2014 6:45:15 AM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/15/2014 6:45:15 AM - WifiRGB (3P) Debug - SetIOEX Receive : #1 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/15/2014 6:45:15 AM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/15/2014 6:45:15 AM - WifiRGB (3P) Debug - SetIOEX Receive : #2 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/15/2014 6:45:15 AM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/15/2014 6:45:15 AM - WifiRGB (3P) Debug - SetIOEX Receive : #3 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0

BTW (by the way) I was able to program the RGB controller via the RGB application to configure the controller such that it worked with the PLC TW-523 device just fine. Least it appeared to save my X10 numbers and dim / ramp values. I also did notice though that I had to reset the RGB controller a couple of times for the original programming of it; switching the program to using the TTS comm port. Could the issue be in the firmware of the RGB controller?

This morning moved the connection from the Digi 7 port USB hub to a direct USB connection and I get the same error as above.

1/15/2014 7:48:15 AM WifiRGB (3P) Error ComSend Error: System.TimeoutException: The operation has timed out. at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count, Int32 timeout) at System.IO.Ports.SerialStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.Ports.SerialPort.Read(Byte[] buffer, Int32 offset, Int32 count) at HSPI_WIFIRGB.HSPI.ComSend(Int32 ClientNo, Byte[] ByteArr, String Command)

Guessing here if I move the TTL-USB cable over to a Digi USB Anywhere device it will generate same error.

I am looking right now to hopefully move it to some sort of production testing using my DIN LED 12VDC power supplies and connecting the output to three LED zones to see how it works. I am currently though at some 12 up to 16 12VDC LED zones at this time. Testing on just three zones would be nice though.

[Kevin Lo]

Hello Kevin,

I am using Windows 2003 standard 32bit OS for my base two Homeseer 2 installations.

I did notice that the Prolific driver was from 2009 that auto installed when I plugged in the USB to TTL device.

I had left the baud rate at the default of 9600 baud.

I upgraded the prolific USB driver to most current.

The "issue" though does still remain with the VB script error showing up in the log when I turn on and off the RGB device.

The RGB controller still does work though with the error in the log relating to comm.



BTW (by the way) I was able to program the RGB controller via the RGB application to configure the controller such that it worked with the PLC TW-523 device just fine. Least it appeared to save my X10 numbers and dim / ramp values. I also did notice though that I had to reset the RGB controller a couple of times for the original programming of it; switching the program to using the TTS comm port. Could the issue be in the firmware of the RGB controller?

This morning moved the connection from the Digi 7 port USB hub to a direct USB connection and I get the same error as above.



Guessing here if I move the TTL-USB cable over to a Digi USB Anywhere device it will generate same error.

I am looking right now to hopefully move it to some sort of production testing using my DIN LED 12VDC power supplies and connecting the output to three LED zones to see how it works. I am currently though at some 12 up to 16 12VDC LED zones at this time. Testing on just three zones would be nice though.

Pete , can you do another test.
In the setup program , when connect with USB and select the COM port.
Can you read the firmware version and X10 address settings ?
I think you can control the RGB and setup the X10 address without problem. (That mean send the command to COM is OK) , but also cannot read the data from COM

I want to locate the problem is on my plug-in (access COM via VB.NET) . If the setup program also not work for read(My setup program access COM via VB6 OCX) , the problem should on your OS level for access COM.

Thanks
Kevin Lo

[Automated]

Any ETA on when the Ethernet & TTL port version will be available?

[Kevin Lo]

Any ETA on when the Ethernet & TTL port version will be available?

TTL version already available. For Ethernet version , actually is TTL + TTL to Ethernet adapter. I already test it , it work. I will post some photo tomorrow.

[gearyt]

got my LED kit.. very nice, superior to rope previously purchased..
will install around frame for tv backlighting this week-end..

Anyone know min radius on bends ? All I am waiting for now is a HS3 plug-in. Want to control thru HSTouch ( I-Pad)
Will post pics when completed.

[CharlieWayne]

got my LED kit.. very nice, superior to rope previously purchased..
will install around frame for tv backlighting this week-end..

Anyone know min radius on bends ? All I am waiting for now is a HS3 plug-in. Want to control thru HSTouch ( I-Pad)
Will post pics when completed.

This I would like to see. There is a spec I think from THX for a specific hue of blue that will enhance the overall theater experience.

Heres a video as example.

http://www.youtube.com/watch?v=nU1DKj4RfVA

[Pete]

Kevin,

I did another test connecting the RGB controller on another Computer.

The computer has old XP SP3 on it.

The RGB device works perfectly and I could read the firmware et al with it. The dialog did show up in the little box under the buttons. It did not show up on the HS2Pro box when testing it yesterday.

I do not here today though use XP for any automation server stuff rather its Windows 2003 standard that is utilized for my Wintel automation stuff.

This "other" computer is a spare with a base XP SP3 install and there might be some VB SDK stuff on it; don't really use it much these days.

That said you are corect!

The issue may be related to the OS or simply installing VB6 OCX on the W2003 server. IE: it works fine on the older XP SP3 computer but not on the Windows 2003 Standard server for HS2 Pro (note that it is updated regularly).

I keep the HS2 Pro server lean somewhat and it's been functioning fine in this manner for years now.

Next test to to check if I have VB6 OCX on the HS3Pro W2003 server.

Will download MS VB 6.0 Common controls for the W2003 Standard server. I would have though with all of the MS patches and upgrades it would have been there already.

http://www.microsoft.com/en-us/downl....aspx?id=10019

the problem should on your OS level for access COM.

[thymer]

The RFXtrx433 supports now 2 dx.com RGB LED strip controllers.

This one has a learn option and any ID can be used.
http://dx.com/p/rf-remote-touch-rgb-controller-130913


This one has a fixed ID and the ID of the remote must be used
http://dx.com/p/wireless-touch-panel...ip-light-67412




A beta version of the RFXCOM plug-in with support for the RGB LED controller is available on request.

How many of the dx.com devices could the plugin support at the same time?

[Pete]

Installed Microsoft Visual Basic 6.0 Common Controls

http://www.microsoft.com/en-us/downl....aspx?id=10019

On the Homeseer Pro Windows 2003 Standard Server.

Testing via RGB configuration program. I can now see and read stuff in the text box. IE: firmware et al.

Booted up Homeseer Pro and enabled the plugin. Worked fine.

Tested with Debug = True

1/16/2014 3:25:13 PM - WifiRGB (3P) Info - WifiRGB (3P) version 1.0.3.1 Starting ...
1/16/2014 3:25:13 PM - Plug-In - Initializing Plug-in: WifiRGB (3P)
1/16/2014 3:25:13 PM - WifiRGB (3P) Debug - Entered InitIO() function.
1/16/2014 3:25:13 PM - WifiRGB (3P) Info - WifiRGB (3P) - initializing I/O ...
1/16/2014 3:25:13 PM - WifiRGB (3P) Debug - Entered InitHW() function.
1/16/2014 3:25:13 PM - WifiRGB (3P) Debug - Entered InitPluginDevices() function.
1/16/2014 3:25:13 PM - WifiRGB (3P) Debug - Entered VerifyBaseCode() subroutine.
1/16/2014 3:25:13 PM - WifiRGB (3P) Debug - Entered GetDefinedHouseCode() function.
1/16/2014 3:25:13 PM - WifiRGB (3P) Info - Verification of base IO code # complete.
1/16/2014 3:25:13 PM - WifiRGB (3P) Debug - Entered GetDefinedHouseCode() function.
1/16/2014 3:25:13 PM - Plug-In - Finished initializing plug-in WifiRGB (3P)
1/16/2014 3:25:34 PM - Device Control - Device: WifiRGB (3P) WifiRGB (3P) Device RGB Channel (#4) OFF
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - SetIOEX Receive : #4 Command : 3 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - SetIOEX Receive : #4 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - SetIOEX Receive : #1 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - SetIOEX Receive : #2 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Entered SetIOEx() subroutine.
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - SetIOEX Receive : #3 Command : 19 , Brightness Value : 0 , Data1 Value : 0 , Data2 Value : 0
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - ComSend Called - Client: 1
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - ComSend ByteArr(0) - 16
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - ComSend ByteArr(1) - 221
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM2Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM3Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM12Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM13Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM14Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM15Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM16Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM17Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM18Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM4Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM5Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM6Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM7Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM8Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM9Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM10Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM11Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - COM19Found
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Opening ComPort
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Sending Data...
1/16/2014 3:25:34 PM - WifiRGB (3P) Debug - Command Sent : AA 10 DD FF
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Closing ComPort
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (0) - 170
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (1) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (2) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (3) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (4) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (5) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (6) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (7) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (8) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (9) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Receive Buffer - (10) - 0
1/16/2014 3:25:35 PM - WifiRGB (3P) Debug - Data Returned: ?