[Hai-users] Program compiler

Wed Nov 28 10:45:33 CST 2007

I don't know the internal format of the pca file. 

When redoing my programs using the compiler I use the GUI pgm to auto
generate the DEFINE cards using the panels current names.  The GUI does
not convert any existing programs, just names.  Then I rewrite the
programs using structured techniques and macros so I did not see any
advantage in converting the old programs.

Tom

________________________________

From: Brett Griffin [mailto:brett at architechtronics.com] 
Sent: Wednesday, November 28, 2007 11:28 AM
To: Tom Williamson; 'Tony Golden'; hai-users at tssi.com
Subject: RE: [Hai-users] Program compiler

Tony, 

I have not had time to look into your program much, but from what it
sounds like and what it could do are really cool.  

If you could create a way for me to upgrade a .pca file from say a Omni
(original) to an Omni Pro II, that I would pay you money for.  I have
upgraded 7 HAI controllers this year, and it takes 1-3 hours to
reprogram a controller based on the one I replaced and then test and
re-verify it.  I have yet to get a 100% upgrade without errors.  I know
the problem is between the keyboard and the chair, but your program
should be able to fix that!  Seems like this would be a simple task, and
just use defaults when the new panel has new settings the old one
didn't.

Let me know your thoughts!

-- 
Brett Griffin
Home Technology Designer

P  (206) 774.3622
F  (206) 260.7475

Architechtronics, Inc
http://www.architechtronics.com <http://www.architechtronics.com/> 
Designing technology to fit your lifestyle.

Visit our blog! http://www.architechtronics.com/blog/

From: Tom Williamson [mailto:Tom at DTSsoftware.com] 
Sent: Wednesday, November 28, 2007 8:02 AM
To: Tony Golden; hai-users at tssi.com
Subject: RE: [Hai-users] Program compiler

They know it exists but I don't know if they want to take it over.

I did find a "bug" in there firmware when writing the compiler.  It had
to do with setting temps up/down.  They are going to fix it in the next
firmware release.

If they just had a way to import/export the programs in text form then
this would have been easier.  I would just generate the right text file
and import it into pcaccess.  Then pcaccess could download the programs
into the panel.  But I had to actually generate the hex program data,
names, and voices.  Then download the data to the panel.

Tom 

________________________________

From: hai-users-bounces at tssi.com [mailto:hai-users-bounces at tssi.com] On
Behalf Of Tony Golden
Sent: Wednesday, November 28, 2007 10:45 AM
To: hai-users at tssi.com
Subject: RE: [Hai-users] Program compiler

That does sound extra cool.

However, I'm concerned about it "breaking" with future firmware updates,
or not being compatible with specific versions.  Have you discussed
sharing your work with HAI, so they could officially support it?  I've
heard they've had plans to update PC Access for a long time, so
hopefully they would be interested...

Thanks for sharing!

________________________________

From: hai-users-bounces at tssi.com [mailto:hai-users-bounces at tssi.com] On
Behalf Of Tom Williamson
Sent: Wednesday, November 28, 2007 9:43 AM
To: hai-users at tssi.com
Subject: [Hai-users] Program compiler

I have finished my first pass at a compiler for the HAI Programs. 

It can be downloaded at http://www.dtssoftware.com/haipc (windows
version). 

The file 1701-1.haipc is a sample.  

It has the following advantages over the PCAccess program: 

1) You can add comments to your programs 
2) UNITS/ZONES... etc can be renumbered without changing your programs.
The HAI PCAccess program shows names of UNITS/ZONES but they are keep as
UNIT/ZONE numbers. If you move a name the program does not match the new
name. 
3) You can use long names in your programs. The DEFINE statement allows
any length for a UNIT/ZONE name that can they be referenced in the
program. The name that gets downloaded into the panel is separate from
this name 
4) The name/voice downloaded into the panel is also defined within the
compiler. If you change any UNIT/ZONE the panel name/voice will also
change. 
5) You can use structured programming. The WHILE statement can have more
than one IF/ANDIF or DO statement under it. This means that you do not
need to keep repeating the same WHEN or IF statement over and over
again. 
6) The normal BAT file used to invoke the compiler runs a macro
preprocessor first. This allows the source to have embedded macros or
equates or INCLUDE other files. 
7) The compiler accepts literals for device names. This allows the use
of device names within the program lines without actually defining the
names. 
8) The compiler produces a list of the programs generated with a symbol
cross-reference. This makes it easy to see where a symbol is used. 
9) More than two IF statement allowed. You can use more than two if
statements (IF / ANDIF) and the compiler will automatically pick an
unused button to chain the Ifs together. See XANDIF 

Tom 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://romaine.tssi.com/pipermail/hai-users/attachments/20071128/5fad3a44/attachment-0001.htm