| Author |
|
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 08 2011 at 23:35 | IP Logged
|
|
|
Happy New Year!!!
Well its been a long time coming but its finally here. PowerHome beta version 2.1.2 is now online. I'll get around to updating the download page shortly. For now, use this link PowerHome Beta 2.1.2.
Current Alpha users will need to zip there database file and email it to me so I can manually upgrade it.
Some potential gotchas...
1. PowerHome now default installs into c:\powerhome. This is due to the fact that more and more people are running Vista and above and PowerHome works much better here rather than under program files.
2. Because of this change, just be keenly aware of the locations when using the Database Upgrade Utility.
3. Another potential problem with the new location is that you'll need to update the locations of INI files for plugins that you've defined.
4. Not sure if there is a problem with the CPU-XA/Ocelot controller or not. Mine did not fully come up on the new version. Changes were only minor on this controller between 2.1b and 2.1.2 so not sure if its the install or Ive just got a problem with my Ocelot.
5. Documentation was not updated. Check the changes.txt or Readme.rtf for a list of changes. I'll start working on notes for the new functions and such. In the meantime, if you see something you want to know about listed in the changes, just post to this thread and I'll provide the details.
Thats all I can think of for now. Please use this thread to post any problems, etc. and I'll reply here as well.
I'll be catching up on the current problems/issues being posted on the forum shortly.
Happy testing!
Dave.
Edited by dhoward - January 08 2011 at 23:37
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 00:02 | IP Logged
|
|
|
Just a quick followup of other potential problems with the new location...
1. You'll need to update the location of the Web Server directory. You can do this in the PowerHome Explorer under Setup|Web. You'll need to reinit for the changes to take effect.
2. Any Control Center tabs you've created that uses graphics will likely need to be updated. You can do a general search of the PowerHome database to find anywhere you may have used the string "program files" by going to Reports|Database Where Used and entering "%program files%" without the quotes.
Dave.
|
| Back to Top |
|
| |
BeachBum
Super User
Joined: April 11 2007
Location: United States
Online Status: Offline
Posts: 1880
|
| Posted: January 09 2011 at 00:08 | IP Logged
|
|
|
And some come bearing gifts.. Happy New Year Dave. Thanks….
__________________
Pete - X10 Oldie
|
| Back to Top |
|
| |
mike0999
Groupie
Joined: June 14 2009
Location: United States
Online Status: Offline
Posts: 56
|
| Posted: January 09 2011 at 06:07 | IP Logged
|
|
|
Cool. Thanks Dave. Happy New Year!
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: January 09 2011 at 10:17 | IP Logged
|
|
|
Installed 2.1.2 with no problems. Upgraded from 2.1b. DB converted and PH2 comes up at what seems to be a faster initialization. Found the changes and readme files describe new Extended commands.
Cannot find reference material on syntax, parameters, etc for Extended commands.
__________________
Lee G
|
| Back to Top |
|
| |
smarty
Super User
Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728
|
| Posted: January 09 2011 at 11:05 | IP Logged
|
|
|
Additionally to what Lee mentioned...
The New Functions:
ph_settstat,ph_x10other,ph_trim,ph_storevars,ph_split,ph_sna p xml,ph_setothercounter,....
don't appear to be available in the Formula Builder window....you have to type them in rather than picking them from the drop down....
I guess this applies here:
5. Documentation was not updated. Check the changes.txt or Readme.rtf for a list of changes. I'll start working on notes for the new functions and such. In the meantime, if you see something you want to know about listed in the changes, just post to this thread and I'll provide the details.
+++++++++++++++++++++++++++++
Looking forward to at the new goodies! Thanks!
Edited by dhoward - March 19 2011 at 00:19
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: January 09 2011 at 11:34 | IP Logged
|
|
|
Cool! Can someone post a link to changes.txt or Readme.rtf?
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 13:29 | IP Logged
|
|
|
For Lee:
integer ph_insteonrawext(string as_ctlr,string as_address,integer ai_flags,integer ai_cmd1,ai_cmd2,string as_data)
as_ctlr, as_address, ai_cmd1, and ai_cmd2 match the other ph_insteonraw functions. ai_flags should contain the bit set for extended commands, otherwise it will make no sense. as_data is a string containing the extended bytes to pass. This string should be in uppercase hex characters with each byte separated with a space. An example would look like "01 0A DE 03". You do not need to supply all 14 bytes. Any unspecified bytes will automatically be padded out to zeros.
string ph_insteonwithretext(string as_id,ai_cmd1,ai_cmd2,as_extdata)
as_id, ai_cmd1, and ai_cmd2 match ph_insteonwithret. as_extdata matches as_data in ph_insteonrawext. This function will send the extended command and will wait for the return data. The function returns the returned cmd2 along with all 14 bytes of returned extended data. The data is returned as a continuous hex string of 30 characters. The first two chars are the returned cmd2 (in hex). The next two characters are the first byte of the extended data in hex.
To make use of the built in extended command background processing, you must enable it in the Devices tab of the Insteon Explorer. The two columns of import are the "IEngine" and the "Use Ext for ALDB" which is short for "Use Extended commands for All Link Database". When a new Insteon device is added, PowerHome will query it for its Engine type (Legacy or I2). The "Use Ext for ALDB" will automatically be set accordingly (checked if the Engine type is I2). Whether PH uses extended commands for the background ALDB commands is controlled by the "Use Ext for ALDB" column and can be set independantly of the IEgine column as the user desires. If the "Use Ext for ALDB" column is checked, PH will attempt to use extended commands for background ALDB. PH also now tracks COMM stats for extended commands including a failed count. If the extended failed count exceeds the "Max Failures" setting, then PowerHome will fall back to using standard commands even if "Use Ext for ALDB" is checked. This extended failed match can be reset by checking the "Clear Failed" column or by zeroing the "Ext Failed Matches" column.
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 13:34 | IP Logged
|
|
|
Something I completely missed to add to the Change log...
PowerHome now has a new Devices type...Thermostats. Currently only supporting the Insteon thermostat, it will soon support the X10 and Elk thermostats. If you've got an Insteon thermostat and are using the various macros for control, you can now do everything by defining your thermostat under the Thermostats section. PowerHome will automatically query for the data and display and allow control via the Device Status screen. Choose a type of "Insteon" and set the "C Address" to the Insteon address of your Thermostat. Set the "Controller" to the Insteon controller. The "Poll Interval" is in minutes and I use a value of 5.
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 13:35 | IP Logged
|
|
|
For Tony...the changes.txt:
Added support for the X10 CM15A controller (both PLC and RF). This support uses the ActiveHome SDK so any limitations are limitations of the SDK itself.
Added support for the Global Cache GC-IRL Infrared Learner.
Added support for the Global Cache GC-IRE Infrared Extender.
Added support for a generic Parallel port controller.
Added a new Virtual Serial Port plugin. Using this plugin, the serial ports on a Global Cache are now available for use for any standard COM plugins or controllers.
Added support for extended Insteon commands. New columns to track extended COMM stats as well. Background database reads and writes now use extended commands if the device supports it. New functions allowing users to generate their own extended Insteon commands within PowerHome.
Fixed bugs associated with Virtual Insteon devices (Insteon devices whose address starts with V?.??.??). For both PLC and PLM, poll status commands were being performed against virtuals. This is now fixed. For PLM, creating a virtual would result in a critical error as well as a critical error whenever the status was polled. This has been fixed as well.
Changes made to Insteon group status functionality. When receiving incoming Insteon group commands, if PLC/PLM is a member of the group, the appropriate PLC/PLM group status will be updated. Also fixed bug on updating PLC/PLM group status when broadcasting commands to group 255.
Added new "No Control" column to Insteon Types maintenance. Previous versions would not show "Control" buttons in the Device Status screen if the Responder Groups column was 0. The appearance of the "Control" buttons is now determined by the "No Control" column.
Added new "Dont Display" column to Insteon Groups maintenance. Placing a check in this column will cause the Insteon Group to not appear in the Device Status screen.
Rewrote ph_sendsmtpemail and ph_sendsmtpemailfile functions to use a new SMTP email control. Both functions now operate in a separate thread and performance is vastly improved.
New function ph_number (similar to existing number function). This function will convert a string to a number (long, integer, or double depending upon string). It will also properly convert negative numbers even if spaces exist around the negative sign. The number function will fail if one or more spaces exist between the sign and the number.
Modified IR triggers so that key description as well as incoming/outgoing code is passed in the TEMP variables. Also standardized all IR triggers so that the key number will be in the same TEMP var.
Modified PowerHome Shutdown routines so PowerHome will play nice with Windows Shutdowns and Logoffs. New ph_shutdown function to cleanly shut PowerHome down.
Updated Elk/Insteon M1XSP programming tab in Insteon Explorer to include support for newer M1XSP firmwares supporting Insteon PLM controllers.
(Almost...) Completely replaced all references to Microsoft Winsock control and Catalyst 3.6 Socket control with latest version of Catalyst Secure Socket tools.
PNG SUPPORT....FINALLY!
New RegEx object and functions for enhanced regex searching. RegEx support of these new functions now matches that in VBScript.
Webserver rewritten to use Catalyst Internet Server control. Webserver now supports SSL. Support for a new authentication routine using cookies also implemented.
Major facelift on PowerHome Explorer. New treeview control allows for better functionality and icons. New control will also enable the requested "grouping" functionality (in a future beta).
PowerHome code base upgraded to PowerBuilder version 11.5. Currently on its way to full PowerBuilder 12 support.
Added support for new encrypted SQL routines. Now certain database actions can be accomplished without having to send in your database using a special encrypted SQL.
Device status screen has been updated for better touchscreen support. No more buttons for On, Off, and ADim. These have been replaced with a single dropdown list for control. Older styles still available though.
Rewrote both the PLC and PLM Insteon controller modules. Code has been aligned to share the same code base. Efficiency has been improved and new error detection algorithms implemented eliminating "echoed" commands and further improving speed. New routines also prevent lockups associated with controllers losing power.
PLC and PLM Insteon controller routines now only attempt to restart up to 5 times before timing out. Restart routines are now more intelligent.
Insteon communication reports rewritten to be more accurate using new underlying Insteon routines. Terms have been clarifed between NAK and Timeout along with support for ACK, NAK, and Timeout.
Modified Insteon PLM controller wizard (serial and USB) so PH will now attempt to automatically locate your attached PLM controller.
New Insteon Problem Links report. Comprehensive report that shows all potential problems concerning the Insteon network.
USB to Serial drivers for Insteon PLM and UPB PIM are automatically installed with PowerHome.
Added new URL Scraper plugin. This plugin allows the user to define multiple URL's to retrieve at regular intervals and use RegEx to extract information and fire triggers. using this plugin, one can eliminate a variety of macros for retrieving various web based data to import into PowerHome.
Removed Device ID and Network Password from UPB controller setup. PIM device ID and network password will instead be read directly from PIM registers (previously set by UpStart).
Added new comments field to macro details. Each macro detail line can now have a comment.
New trigger that is fired when an Insteon device is flagged as COMM Failed.
New triggers for controller connect, disconnect, restart, and failure.
Fixed bug in ph_sendsocketdata1 function where including a value of 4 in the flags parameter resulted in all of the data being returned as a string of \000.
Fixed ph_getglobal_n, ph_getvar_n, ph_sql_n, ph_formulabtn_n so that they properly interpret negative numbers with spaces around the negative sign.
Fixed major bug where a number of ph.??? Windows Script Host functions would not properly handle negative numeric parameters. All functions should now properly handle negatives.
Fixed bug where a legitimate formula evaluation result of "!" does not fire the Syntax error trigger and log entry. Only an actual syntax error will do this now.
Fixed bug where certain macro commands (Insteon, Insteon Group, Insteon Raw Group, UPB, UBP Link) could trigger a Formula Syntax error when none actually exists.
Fixed bug where an Insteon "Stop Manual Change" command could possibly trigger a status request to the connected PLC/PLM controller ultimately resulting in the controller being flagged as COMM Failed.
Fixed major bug where multi-channel UPB devices could not be controlled properly (all channels would be controlled together). Also fixed other minor UPB bugs.
Fixed critical error when attempting to Print Preview the Device Status screen. Print and Print Preview of PowerHome Explorer was enabled in 2.1b and inadvertantly enabled the Print and Print Preview options for the Device Status screen. The menu options remain enabled for Device Status and print and preview now work properly.
Fixed critical error (line 26 of f_executeph of w_formula) that occurs when evaluating a formula with a runtime error from the Formula builder window and the window is closed before the evaluation or the runtime error is complete.
Fixed critical error (line 26 of f_executeph of w_wshedit) that occurs when evaluating a formula with a runtime error from a PowerHome Multi-editor window and the window is closed before the evaluation or the runtime error is complete.
Fixed critical error (Invalid DataWindow row/column specified at line 10 in function f_id of object w_devicecontrol).
Fixed critical error (Null object reference at line 1 in function f_setmenu of object w_tabdesign).
Fixed critical error (Invalid DataWindow row/column specified at line 8 in itemchanged event of object dw_1 of uo_insteontypes).
Fixed critical error (Invalid DataWindow row/column specified at line 509 in itemchanged event of object dw_detail of w_explorer).
Fixed checksum calculation routine on Elk controller where incoming Elk commands with a checksum of 0 would be ignored by PowerHome. Checksum routine now calculates properly and eliminates this problem.
Changed the last of all X-10 references to X10.
And more that didnt get documented :(
New Functions:
ph_settstat,ph_x10other,ph_trim,ph_storevars,ph_split,ph_sna p xml,ph_setothercounter,ph_setdeviceval,ph_saveurlviaproxy1,p h_saveurl1,ph_retrievevars,ph_regexsnap2,ph_regexdiff2,ph_re gex2,ph_not,ph_locatehandle1,ph_latlongdist,ph_insteonwithre text,ph_getothercounter,ph_getmtret,ph_getmd5hash,ph_fill,ph _encrypt,ph_deletetimedevent,ph_decrypt,h2d,d2h,ph_base64dec ode1,ph_getdeviceval,ph_runsync1,ph_runasuser1,ph_ctlrcontro l,ph_shutdown,ph_gettstat_s,ph_gettstat,ph_getsyspwrstat,ph_ co nvertir,ph_insteonrawext,ph_geturlviaproxy1,ph_geturl1,ph_pi ng1,ph_sendsmtpemailfileasync,ph_sendsmtpemailasync,ph_numbe r,ph_getlasterrorstring
Changed Functions:
ph_geturl,ph_geturlviaproxy,ph_runasuser,ph_saveurl,ph_saveu rlviaproxy,ph_webds
Removed Functions:
ph_rr2topronto,ph_rr3topronto,ph_prontotogc,ph_prontotorr2,p h_connect,ph_disconnect
PWRHOME.INI Changes:
[SYSTEM]
AllowPHShutdownFunc=NO
[WebServer]
AUTHMODE=1
COOKIEPERSISTDAYS=30
ENABLEWAP=YES
WEBSERVERUSESSL=NO
WEBSERVERCERTNAME=
Database Changes:
Drop view insteon_bk (no longer used)
Added comment column [char(256) nullable] to macrodetail table.
Added flags column [char(50) nullable] to insteongroups table.
Added timeoutcnt column [integer nullable] to insteondevices table.
Added xcommcnt,xackcnt,xnakcnt,xtimeoutcnt,xttacnt to insteondevices table. All fields are [integer nullable].
New tables: userdata2,userdata3,userdata4,userdata5 (they all use the same format as follows)
New views: devicestatusdd,devicestatus
CREATE TABLE "powerhome"."userdata2"
(
"uid" & nbsp;& nbsp;& nbsp; & nbsp; integer NOT NULL DEFAULT autoincrement,
"type" integer ; NULL,
"idstring" &n bsp;&n bsp; &n bsp; char(25) NULL,
"idnum" ; ; ; integer NULL,
"iddate" &nbs p;&nbs p; &nbs p; timestamp NULL,
"valstring1" &nbs p; &nbs p; char(25) NULL,
"valstring2" &nbs p; &nbs p; char(25) NULL,
"valstring3" &nbs p; &nbs p; char(25) NULL,
"valstring4" &nbs p; &nbs p; char(1024) NULL,
"valnum1" &nbs p; &nbs p; integer NULL,
"valnum2" &nbs p; &nbs p; integer NULL,
"valnum3" &nbs p; &nbs p; integer NULL,
"valnum4" &nb sp;&nb sp; &nb sp; double NULL,
"valdate1"&nbs p; &nbs p; timestamp NULL,
"valdate2"&nbs p; &nbs p; timestamp NULL,
"valdate3"&nbs p; &nbs p; timestamp NULL,
"valdate4"&nbs p; &nbs p; timestamp NULL,
"lastchange" timestamp NOT NULL DEFAULT timestamp,
PRIMARY KEY ("uid")
)
CREATE INDEX "ud2_1" ON "powerhome"."userdata2"
(
"type" ASC,
"idstring" ASC,
"idnum" ASC,
"iddate" ASC
)
New table webtokens using following format:
CREATE TABLE "powerhome"."webtokens"
(
"token"&nbs p; &nbs p; char(10) NOT NULL,
"created"&nbs p; &nbs p; timestamp NOT NULL,
"active" &nbs p;&nbs p; &nbs p; smallint NOT NULL,
PRIMARY KEY ("token")
)
New table thermostats
PH.CSS Changes:
Add sections below:
form
{
font-family: Verdana, Arial, sans-serif;
font-size: 8pt;
margin: 0;
padding: 0;
}
.xt1roc7e5,.xt1rec7e5
{
font-family: Verdana, Arial, sans-serif;
font-size: 7pt;
width: 100%;
}
.lt1r1c1e1,.lt1r1c1e2,.lt3r1c1e1,.lt3r2c1e1,.lt3r2c2e1,.lt3r 3c1e1,.lt3r3c2e1,.lt3r4c1e1
{
font-family: Verdana, Arial, sans-serif;
font-size: 7pt;
}
.gvt1roc1e1,.gvt1roc1e2,.gvt1rec1e1,.gvt1rec1e2
{
font-family: Verdana, Arial, sans-serif;
font-size: 7pt;
}
Remove sections below:
form
{
font-family: Verdana, Arial, sans-serif;
font-size: 8pt;
}
.gvt1roc3e1,.gvt1roc4e1,.gvt1rec3e1,.gvt1rec4e1
{
font-family: Verdana, Arial, sans-serif;
font-size: 7pt;
}
Dave.
Edited by dhoward - March 19 2011 at 00:20
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: January 09 2011 at 13:43 | IP Logged
|
|
|
Dave
Thank you! Exactly what I was looking for.
Lee
__________________
Lee G
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 14:05 | IP Logged
|
|
|
Some of what Smarty asked for:
integer ph_gettstat(string as_id,string as_type,integer ai_flags)
Retrieves data from the new Thermostat device type. as_id will be the thermostat ID. as_type is a string describing the data you'd like returned and can be one of the following values: coolsp,heatsp,temp,humidity,mode,fanstat,setpoint. ai_flags can be either 0 or 1. If 0, then the function does not actually cause the device to be queried and only returns the values currently stored in the thermostat table. If 0, then "setpoint" will return the appropriate coolsp or heatsp based upon the current mode and temperature. If the ai_flags is 1, then PH will actually query the thermostat device and return the current value. Since only Insteon is supported at this time, with ai_flags = 1, then the only valid values for as_type are temp,humidity,mode, and setpoint. Insteon does not provide a way to specifically query the cool setpoint or heat setpoint (and fanstat is not supported) so the coolsp and heatsp are set according to the current temperature and mode.
integer ph_gettstat_s((string as_id,string as_type,integer ai_flags)
Returns a string rather than an integer. The parameters are the same as ph_gettstat above. The only valid values for as_type are mode and fanstat. This function will return a string equivalent of the mode and fanstat.
long ph_storevars(long al_id)
This function will store a snapshot of all the current local and temp variables into the database (these variables are usually memory only). The al_id is a numeric ID identifying the stored variables. If a 0 is passed, a new ID will be created and that is the return value of the function. This ID is later used in the ph_retrievevars function to restore the variables. If an al_id is specified and variables are already saved under that ID, then they will be overwritten with the new snapshot.
integer ph_retrievevars(long al_id,integer ai_type)
This function will restore local and temp variables snapshot previously stored in the database (overwriting whatever values are currently in the local and temp vars). al_id should be a value > 0 representing the numeric ID (returned by ph_storevars) of the stored vars. ai_type can be either 0,1, or 2. A value of 0 will restore the vars and delete the stored ID from the database. A value of 1 will restore the vars but not delete them from the database. A value of 2 will NOT restore the vars and will only delete them from the database.
long ph_split(string as_data,string as_sep,integer ai_local)
This function populates the local variables from the supplied data in the as_data parm. as_data should be a list of data separated by character(s) defined in as_sep. ai_local is a number identifying the local var to start populating. ph_split("This is a test"," ",3) will place "This" in [LOCAL3], "is" in [LOCAL4], "a" in [LOCAL5], and "test" in [LOCAL6]. The function returns the count of individual pieces of data whether they were placed into a local var or not.
Dave.
Edited by dhoward - March 19 2011 at 00:17
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: January 09 2011 at 15:46 | IP Logged
|
|
|
Happiness is a new release for the New Year.
This is a very happy camper!
Thanks Dave! 
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: January 09 2011 at 15:54 | IP Logged
|
|
|
Dave -
In order to keep the ol Homestead running while bringing up the new release, is it possible to install the new version without removing the old?
I'm assuming I duplicate the db, graphics, etc into the new install folder so that both installs are completely separate.
My concern is with the Registry and any confusion over two installs of a program with the same name.
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 15:56 | IP Logged
|
|
|
Another one...
integer ph_settstat(as_id,as_type,ai_value)
Set thermostat values. as_id and as_type are as described under ph_gettstat. ai_value is the value you wish to set. With Insteon thermostats (the only kind currently supported), the valid values for as_type are coolsp,heatsp, and mode. coolsp and heatsp values should be self explanatory. Valid mode values are:
0 - Off
1 - Heat
2 - Cool
3 - Auto
4 - Fan
5 - Program
6 - Program Heat
7 - Program Cool
Dave.
Edited by dhoward - March 19 2011 at 00:20
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: January 09 2011 at 15:59 | IP Logged
|
|
|
Thanks Dave! 
|
| Back to Top |
|
| |
smarty
Super User
Joined: May 21 2006
Location: United States
Online Status: Offline
Posts: 728
|
| Posted: January 09 2011 at 16:36 | IP Logged
|
|
|
This one has my attention:
"Added a new Virtual Serial Port plugin. Using this plugin, the serial ports on a Global Cache are now available for use for any standard COM plugins or controllers."
Outside of PowerHome, I use a virtual serial port (HW_VSP) that allows an Xlobby plugin to connect to my Elk system. It would be great if PH's new feature could allow me to NOT USE HW_VSP....=>because, I have tracked down a bunch of problems related to using HW_VSP.
Details to the set-up and configuring of the PH virtual serial port would be greatly appreciated! 
__________________
Elk - Insteon - BlueIris - DMC1 - PowerHome - XLobby - HA_Bridge w/Dots - Brultech
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 16:38 | IP Logged
|
|
|
Some more info...
The Insteon PLM, UPB PIM, and Global Cache IRE/IRL controllers have all been updated to use a new serial port control. This control allows you to use ports from 1 to 256. The other serial controllers (CPU-XA/Ocelot already done) will be updated to use this control in future beta's.
Also, I have confirmed that there is nothing wrong with the CPU-XA/Ocelot controller. It appears my problem is a result of the new Insteon PLM controller. I was loading the Insteon PLM followed by the Ocelot but the Insteon PLM startup routine was causing the Ocelot routine to time out. Loading the Ocelot first followed by the Insteon PLM resolved the problem. If anyone experiences issues with controllers not loading, try adjusting the order. I'll look into trying to pinpoint what exactly is causing the issue and see if I can fix it.
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 16:50 | IP Logged
|
|
|
Smarty,
PH indeed should deliver. The virtual serial port plugin for PowerHome should replace your HW_VSP virtual serial port (both PH and HW_VSP use the same Eltima virtual serial port control) as I have licensed the VSP control from Eltima.
In plugin setup, the ActiveX classname is: PH_VSP.phvsp. The initialization data is the desired virtual COM port number, a space, the remote TCP/IP port number, a space, and the remote TCP/IP IP address.
5 4999 192.168.0.70
The above init data will create a virtual serial port on COM5 and connected to IP 192.168.0.70 at port 4999.
In my testing, the PH setup program did not properly install the drivers for the virtual serial port so you'll probably need to run them manually. They're located in c:\powerhome\drivers\VSP 6.2\vspdxp_install.exe. Just execute this file (its a silent install but will likely take a total of 30 seconds to complete) and you should be good to go.
Not sure what problems you're having with HW_VSP but hopefully you wont experience them even though PH shares the same base control.
Good luck,
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 09 2011 at 16:54 | IP Logged
|
|
|
Ken,
The new install will default to c:\powerhome so you should be able to have both setups available and just run one or the other.
Dave.
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: PowerHome Beta 2.1.2
