I use a dymo Rhino pro label machine with a special heat shrink tube print
cartridge. And for the cables that are bigger than the tube, the normal print
tape wrapped round the cable. The Rhino will also do patch panels automatically.
Just tell it the module width and the starting number and press print. It then
prints out the numbers with the correct spacing etc.




--- In homevision-users@yahoogroups.com, "jacqu0" <ian@...> wrote:
>
> As I add more connectivity to my HV controller my node-0 is getting ever more
like a birds nest.
>
> Q: How do other people label their wires and keep everything tidy?
>

Jim,

I don't think you have to mess around with networking settings.
I never did. At what point did you plug in the USB to serial
device? You should do that after installing the drivers.

Schedule files saved by HomeVisionXL have no dependency on the
platforms they were originally created on. So you can use one
you made on Windows also with the Mac version of HomeVisionXL.


Thanks,
Schelte


On Wednesday 09 December 2009 18:27:13 Jim Robertson wrote:
> Schelte
>
> Thanks for the advice.
>
> Loaded FTD drivers
> used TERMINAL
> No /dev in USB
>
> FOR other New Mac users here is what I did find.  I went into
>   FINDER/APPLICATIONS/UTILITIES and opened SYSTEM PROFILER
>  and found nothing listed under USB but then I saw serialUSB
>  loaded in network section. opended the devise in
>  SETUP/networking and found it configured as a modem and not
>  set up I set it up for PPP blanked the dial fileds  and
>  apply then in TERMINAL I did a cd /dev  ls and there was a
>  /serialUSB listed cut and pasted that into HVXL and now i
>  can talk to HV.
>
> Just one more question. Can I use any of the Windows
>  configuration files on the Mac version of HVXL ? or will I
>  have to climb in the attic and isolate each digital (one
>  wire temp devices) so i can get them into the Mac version of
>  XL.
>
> I can select each temp sensor in macHV and read it's temp but
> when I go to set up new periodic events the digital temp
>  sensor choice is grayed out. I did not load a new schedule
>  from the MacHV as I am still using it as a data logger until
>  I get the Mac version ready
>
> Thanks for your help on getting me started, without that
>  guidance I think this project would not have worked.
>
> Jim R
>
>
>
>
> ----- Original Message ----
> From: Schelte Bron <sbron@...>
> To: homevision-users@yahoogroups.com
> Sent: Mon, December 7, 2009 5:02:21 PM
> Subject: Re: [HOMEVIS] Need help with Mac PPC HomeVisionXL
>  software: can't see controller
>
> Jim,
>
> So you have FTDIUSBSerialDriver_v2_2_14.dmg in your downloads
> directory. Open up the finder and double-click on that file.
> That opens up another finder window containing two files:
> FTDIUSBSerialDriver_10_3 and
>  FTDIUSBSerialDriver_10_4_10_5_10_6. For snowleopard you need
>  the second one. Double-click on it and a wizard called
>  "Install FTDIUSBSerialDriverInstaller" will start. Go
>  through the steps of the wizard, making sure you pick your
>  hard disk as the destination for installing the package.
>  When done with the wizard, plug in your USB to serial
>  device.
>
> Unfortunately, the finder will not show the /dev directory.
>  So you have to use a terminal to examine it. Using the
>  finder, go to Applications. In the subdirectory Utilities,
>  double-click on Terminal. In the terminal window enter: "ls
>  /dev/cu.usb*". That should return a result like:
>  /dev/cu.usbserial-FTR1J33L. This is what you have to enter
>  as the device on the controller interface screen after
>  selecting Local Serial Port as the interface type. (There
>  are no spaces anywhere in the file name.)
>
> Finally make sure your Homevision controller is powered up
>  and you should be in business.
>
>
> Thanks,
> Schelte.
>
> On Monday 07 December 2009 22:09:23 Jim Robertson wrote:
> > Schelte
> >
> > I have been running on a very old pc win98 and thought I
> >  would get the Intel Mini Mac hooked up,  I have run into a
> >  configuration problem and hope you can expand on the
> >  following. (from your info)
> > If you
> > get yourself a USB serial converter based on the FTDI
> > chipset
> > you can download FTDIUSBSerialDriver_v2_2_14.dmg or
> > whatever the latest version is from
> > http://www.ftdichip.com/
> >
> > Then
> > when you plug the device into a USB port of the
> > Mac you
> > should automatically get a new device called something
> > like
> > /dev/tty.usbserial-ftXYSPQR. That's what you specify as the
> > serial
> > device in HomeVisionXL.
> >
> > I am on my second usb-serial converter and have downloaded
> >  and installed the snowleapard driver as per your
> >  instructions above.  When I open homevision and select
> >  configure/controller interface I changed interface type to
> >  .... local serial port ...... then when I select device it
> >  points to the download file and of course when I select it
> >  homevision tells me it is a read only file. (Where will
> > the drive file be located?)
> >
> >  (I do have FTDIUSBSERIAL.... LISTED UNDER DEVICES and when
> > I select it it points to the download package). when I do a
> > info on it is defined Disk image:
> >  /users/jamesxxxx/downloads/FTDIUSBSerialDriver_v2_2_14.dmg
> >  Which is where the download file is located........?
> >
> > below are you saying when I select device I should be
> >  entering not a file location  but  " /dev
> >  2.1.10.FTDIUSBSerialDriver_v2_14.dmg"     this produces a
> > no such file or directory.
> >
> >  Bet you like Mac folks!
> >
> > Thanks
> > JR

Schelte

Thanks for the advice.

Loaded FTD drivers
used TERMINAL
No /dev in USB

FOR other New Mac users here is what I did find.  I went into 
FINDER/APPLICATIONS/UTILITIES and opened SYSTEM PROFILER and found nothing
listed under USB but then I saw serialUSB  loaded in network section. opended
the devise in SETUP/networking and found it configured as a modem and not set up
I set it up for PPP blanked the dial fileds  and apply then in TERMINAL I did a
cd /dev  ls
  and there was a /serialUSB listed cut and pasted that into HVXL and now i can
talk to HV.

Just one more question. Can I use any of the Windows configuration files on the
Mac version of HVXL ?
or will I have to climb in the attic and isolate each digital (one wire temp
devices) so i can get them into the
Mac version of XL.

I can select each temp sensor in macHV and read it's temp but
when I go to set up new periodic events the digital temp sensor choice is grayed
out.
I did not load a new schedule from the MacHV as I am still using it as a data
logger until
I get the Mac version ready

Thanks for your help on getting me started, without that guidance I think this
project would not have worked.

Jim R




----- Original Message ----
From: Schelte Bron <sbron@...>
To: homevision-users@yahoogroups.com
Sent: Mon, December 7, 2009 5:02:21 PM
Subject: Re: [HOMEVIS] Need help with Mac PPC HomeVisionXL software: can't see
controller

Jim,

So you have FTDIUSBSerialDriver_v2_2_14.dmg in your downloads
directory. Open up the finder and double-click on that file.
That opens up another finder window containing two files:
FTDIUSBSerialDriver_10_3 and FTDIUSBSerialDriver_10_4_10_5_10_6.
For snowleopard you need the second one. Double-click on it and
a wizard called "Install FTDIUSBSerialDriverInstaller" will
start. Go through the steps of the wizard, making sure you pick
your hard disk as the destination for installing the package.
When done with the wizard, plug in your USB to serial device.

Unfortunately, the finder will not show the /dev directory. So
you have to use a terminal to examine it. Using the finder, go
to Applications. In the subdirectory Utilities, double-click on
Terminal. In the terminal window enter: "ls /dev/cu.usb*". That
should return a result like: /dev/cu.usbserial-FTR1J33L. This is
what you have to enter as the device on the controller interface
screen after selecting Local Serial Port as the interface type.
(There are no spaces anywhere in the file name.)

Finally make sure your Homevision controller is powered up and
you should be in business.


Thanks,
Schelte.


On Monday 07 December 2009 22:09:23 Jim Robertson wrote:
> Schelte
>
> I have been running on a very old pc win98 and thought I
>  would get the Intel Mini Mac hooked up,  I have run into a
>  configuration problem and hope you can expand on the
>  following. (from your info)
> If you
> get yourself a USB serial converter based on the FTDI
> chipset
> you can download FTDIUSBSerialDriver_v2_2_14.dmg or whatever
>  the latest version is from http://www.ftdichip.com/
>
> Then
> when you plug the device into a USB port of the
> Mac you
> should automatically get a new device called something
> like
> /dev/tty.usbserial-ftXYSPQR. That's what you specify as the
> serial
> device in HomeVisionXL.
>
> I am on my second usb-serial converter and have downloaded
>  and installed the snowleapard driver as per your
>  instructions above.  When I open homevision and select
>  configure/controller interface I changed interface type to
>  .... local serial port ...... then when I select device it
>  points to the download file and of course when I select it
>  homevision tells me it is a read only file. (Where will the
>  drive file be located?)
>
>  (I do have FTDIUSBSERIAL.... LISTED UNDER DEVICES and when I
>  select it it points to the download package). when I do a
>  info on it is defined Disk image:
>  /users/jamesxxxx/downloads/FTDIUSBSerialDriver_v2_2_14.dmg
>  Which is where the download file is located........?
>
> below are you saying when I select device I should be
>  entering not a file location  but  " /dev
>  2.1.10.FTDIUSBSerialDriver_v2_14.dmg"     this produces a no
>  such file or directory.
>
>  Bet you like Mac folks!
>
> Thanks
> JR


------------------------------------

   Post message: homevision-users@yahoogroups.com
   Unsubscribe:  homevision-users-unsubscribe@yahoogroups.com
   Homepage:     http://groups.yahoo.com/group/homevision-usersYahoo! Groups
Links

I use white electrical tape, wrap the cable and write with a fine point marker.
Its removable, legible and cheap.
Jack


--- In homevision-users@yahoogroups.com, "jacqu0" <ian@...> wrote:
>
> As I add more connectivity to my HV controller my node-0 is getting ever more
like a birds nest.
>
> Q: How do other people label their wires and keep everything tidy?
>

Schelte - Opening the file will work fine for me for the present. I will use
that method.

As far as the  white flash goes, it does not happen on my previous computer
which has a much faster processor and more memory. So it may be related to how
fast the screen refreshes and/or updates. Matching the background color may be a
good workaround for slower (laptop) computers.

Jack


--- In homevision-users@yahoogroups.com, Schelte Bron <sbron@...> wrote:
>
> Jack,
>
> You are right, importing the control file you provided does not
> work correctly. I will look into that. However, simply opening
> it is no problem at all. Did you actually need to import it into
> another control file, or are you just using a complicated method
> to open it?
>
> Using your control screens I also see what you meant with the
> white flash when changing pages. I think it is more noticeable
> as a result of your choice of background color. I suspect I can
> greatly reduce the effect by matching the background color of
> the underlying window to the background color of the current
> page.
>
>
> Thanks,
> Schelte.
>
>
> On Tuesday 08 December 2009 03:34:31 jolivier98 wrote:
> > Schelte - I am using HV 2.0b17 and Control Plug In 6.1a. From
> >  the Control Screen Toolbox, I try to import a control file
> >  (Jack1.ctl) and I get the error.
> >
> > The error message and the file is in the folder:
> >
> > Control Screen_Error Message in the files section.
> >
> >
> > thanks,
> > Jack
> >
> > --- In homevision-users@yahoogroups.com, Schelte Bron
> <sbron@> wrote:
> > > On Wednesday 02 December 2009 13:32:29 jolivier98 wrote:
> > > > I have been moving my Homevision XL application from one
> > > >  computer to another. I re-installed everything and
> > > > updated the control plug-in from 5.0 to the latest
> > > > version(6.0). When I try to import the ctl file that I
> > > > created under 5.0, I get an error message. Am I doing
> > > > something wrong or are they not compatible?
> > >
> > > Control plug-in 6.0 is supposed to be able to handle
> > > control files created with 5.0. But "I get an error
> > > message" is not enough information for me to be able to
> > > tell what is wrong.
> > >
> > > http://hv.tclcode.com/help.html
> > >
> > >
> > > Thanks,
> > > Schelte.
>

Jack,

You are right, importing the control file you provided does not
work correctly. I will look into that. However, simply opening
it is no problem at all. Did you actually need to import it into
another control file, or are you just using a complicated method
to open it?

Using your control screens I also see what you meant with the
white flash when changing pages. I think it is more noticeable
as a result of your choice of background color. I suspect I can
greatly reduce the effect by matching the background color of
the underlying window to the background color of the current
page.


Thanks,
Schelte.


On Tuesday 08 December 2009 03:34:31 jolivier98 wrote:
> Schelte - I am using HV 2.0b17 and Control Plug In 6.1a. From
>  the Control Screen Toolbox, I try to import a control file
>  (Jack1.ctl) and I get the error.
>
> The error message and the file is in the folder:
>
> Control Screen_Error Message in the files section.
>
>
> thanks,
> Jack
>
> --- In homevision-users@yahoogroups.com, Schelte Bron
<sbron@...> wrote:
> > On Wednesday 02 December 2009 13:32:29 jolivier98 wrote:
> > > I have been moving my Homevision XL application from one
> > >  computer to another. I re-installed everything and
> > > updated the control plug-in from 5.0 to the latest
> > > version(6.0). When I try to import the ctl file that I
> > > created under 5.0, I get an error message. Am I doing
> > > something wrong or are they not compatible?
> >
> > Control plug-in 6.0 is supposed to be able to handle
> > control files created with 5.0. But "I get an error
> > message" is not enough information for me to be able to
> > tell what is wrong.
> >
> > http://hv.tclcode.com/help.html
> >
> >
> > Thanks,
> > Schelte.

As I add more connectivity to my HV controller my node-0 is getting ever more
like a birds nest.

Q: How do other people label their wires and keep everything tidy?

Schelte - I am using HV 2.0b17 and Control Plug In 6.1a. From the Control Screen
Toolbox, I try to import a control file (Jack1.ctl) and I get the error.

The error message and the file is in the folder:

Control Screen_Error Message in the files section.


thanks,
Jack





--- In homevision-users@yahoogroups.com, Schelte Bron <sbron@...> wrote:
>
> On Wednesday 02 December 2009 13:32:29 jolivier98 wrote:
> > I have been moving my Homevision XL application from one
> >  computer to another. I re-installed everything and updated
> >  the control plug-in from 5.0 to the latest version(6.0).
> >  When I try to import the ctl file that I created under 5.0,
> >  I get an error message. Am I doing something wrong or are
> >  they not compatible?
> >
> Control plug-in 6.0 is supposed to be able to handle control
> files created with 5.0. But "I get an error message" is not
> enough information for me to be able to tell what is wrong.
>
> http://hv.tclcode.com/help.html
>
>
> Thanks,
> Schelte.
>

Would it be possible to use the first B12 to trigger a macro to then look for
the other 2 B12 commands. This would avoid a periodic event.


--- In homevision-users@yahoogroups.com, Schelte Bron <sbron@...> wrote:
>
> Bobby,
>
> I don't know how to explain this any different than I already
> did on the wiki page and my previous mail. To detect a sequence
> of [B-12, B-12, B-12] you have to use a periodic event that runs
> every loop. A loop takes something like 20ms, so that means the
> controller checks the condition several million times per day.
> When instead you use [B-12, B-12, B-On] you can put the check in
> the B-12 On actions. That action is only executed when B-12, B-
> On is received, which happens maybe a dozen times a day. Now,
> most likely you will not notice any slowdown of the controller
> at all with the periodic event. But it just feels like a waste
> to me. Probably I'm just weird.
>
> I understand what your periodic event looks like. But in future,
> if you want to copy text from the action editor into a mail, you
> can do that with HomeVisionXL.
>
>
> Thanks,
> Schelte.
>
>
> On Monday 07 December 2009 20:41:10 robert_green1963 wrote:
> > <stuff snipped>
> >
> > > The big advantage of using [B-12, B-12, B-On] over [B-12,
> > > B-12, B-12] is that you can detect the first one inside the
> > > B-12 On action. For the second one you would need to
> > > constantly check using a periodic event that runs every
> > > loop. So the overhead can be much lower for sequences that
> > > end in an On or Off signal, especially if you have a fair
> > > number of sequences to check for.
> > >
> > >
> > > Schelte.
> >
> > I don't think I follow the reasoning since I've already got
> >  the [B12, B-12, B12] inside a periodic event that runs
> >  during every loop. (Is there any way to cut and paste the
> >  code from the periodic event editing screen in HV 3.45A to
> >  show you?)
> >
> > I won't have an awful lot of such constructs - perhaps 20,
> >  and some I can easily convert to having the last sequence
> >  being either ON or OFF.  Is there a better way to do what I
> >  want besides inside a period loop?
> >
> > Thanks!
> >
> > --
> > Bobby G.
>

Jim,

So you have FTDIUSBSerialDriver_v2_2_14.dmg in your downloads
directory. Open up the finder and double-click on that file.
That opens up another finder window containing two files:
FTDIUSBSerialDriver_10_3 and FTDIUSBSerialDriver_10_4_10_5_10_6.
For snowleopard you need the second one. Double-click on it and
a wizard called "Install FTDIUSBSerialDriverInstaller" will
start. Go through the steps of the wizard, making sure you pick
your hard disk as the destination for installing the package.
When done with the wizard, plug in your USB to serial device.

Unfortunately, the finder will not show the /dev directory. So
you have to use a terminal to examine it. Using the finder, go
to Applications. In the subdirectory Utilities, double-click on
Terminal. In the terminal window enter: "ls /dev/cu.usb*". That
should return a result like: /dev/cu.usbserial-FTR1J33L. This is
what you have to enter as the device on the controller interface
screen after selecting Local Serial Port as the interface type.
(There are no spaces anywhere in the file name.)

Finally make sure your Homevision controller is powered up and
you should be in business.


Thanks,
Schelte.


On Monday 07 December 2009 22:09:23 Jim Robertson wrote:
> Schelte
>
> I have been running on a very old pc win98 and thought I
>  would get the Intel Mini Mac hooked up,  I have run into a
>  configuration problem and hope you can expand on the
>  following. (from your info)
> If you
> get yourself a USB serial converter based on the FTDI
> chipset
> you can download FTDIUSBSerialDriver_v2_2_14.dmg or whatever
>  the latest version is from http://www.ftdichip.com/
>
> Then
> when you plug the device into a USB port of the
> Mac you
> should automatically get a new device called something
> like
> /dev/tty.usbserial-ftXYSPQR. That's what you specify as the
> serial
> device in HomeVisionXL.
>
> I am on my second usb-serial converter and have downloaded
>  and installed the snowleapard driver as per your
>  instructions above.  When I open homevision and select
>  configure/controller interface I changed interface type to
>  .... local serial port ...... then when I select device it
>  points to the download file and of course when I select it
>  homevision tells me it is a read only file. (Where will the
>  drive file be located?)
>
>  (I do have FTDIUSBSERIAL.... LISTED UNDER DEVICES and when I
>  select it it points to the download package). when I do a
>  info on it is defined Disk image:
>  /users/jamesxxxx/downloads/FTDIUSBSerialDriver_v2_2_14.dmg
>  Which is where the download file is located........?
>
> below are you saying when I select device I should be
>  entering not a file location  but  " /dev
>  2.1.10.FTDIUSBSerialDriver_v2_14.dmg"     this produces a no
>  such file or directory.
>
>  Bet you like Mac folks!
>
> Thanks
> JR

Bobby,

I don't know how to explain this any different than I already
did on the wiki page and my previous mail. To detect a sequence
of [B-12, B-12, B-12] you have to use a periodic event that runs
every loop. A loop takes something like 20ms, so that means the
controller checks the condition several million times per day.
When instead you use [B-12, B-12, B-On] you can put the check in
the B-12 On actions. That action is only executed when B-12, B-
On is received, which happens maybe a dozen times a day. Now,
most likely you will not notice any slowdown of the controller
at all with the periodic event. But it just feels like a waste
to me. Probably I'm just weird.

I understand what your periodic event looks like. But in future,
if you want to copy text from the action editor into a mail, you
can do that with HomeVisionXL.


Thanks,
Schelte.


On Monday 07 December 2009 20:41:10 robert_green1963 wrote:
> <stuff snipped>
>
> > The big advantage of using [B-12, B-12, B-On] over [B-12,
> > B-12, B-12] is that you can detect the first one inside the
> > B-12 On action. For the second one you would need to
> > constantly check using a periodic event that runs every
> > loop. So the overhead can be much lower for sequences that
> > end in an On or Off signal, especially if you have a fair
> > number of sequences to check for.
> >
> >
> > Schelte.
>
> I don't think I follow the reasoning since I've already got
>  the [B12, B-12, B12] inside a periodic event that runs
>  during every loop. (Is there any way to cut and paste the
>  code from the periodic event editing screen in HV 3.45A to
>  show you?)
>
> I won't have an awful lot of such constructs - perhaps 20,
>  and some I can easily convert to having the last sequence
>  being either ON or OFF.  Is there a better way to do what I
>  want besides inside a period loop?
>
> Thanks!
>
> --
> Bobby G.

<stuff snipped>

> The big advantage of using [B-12, B-12, B-On] over [B-12, B-12,
> B-12] is that you can detect the first one inside the B-12 On
> action. For the second one you would need to constantly check
> using a periodic event that runs every loop. So the overhead can
> be much lower for sequences that end in an On or Off signal,
> especially if you have a fair number of sequences to check for.
>
>
> Schelte.

I don't think I follow the reasoning since I've already got the [B12, B-12, B12]
inside a periodic event that runs during every loop. (Is there any way to cut
and paste the code from the periodic event editing screen in HV 3.45A to show
you?)

I won't have an awful lot of such constructs - perhaps 20, and some I can easily
convert to having the last sequence being either ON or OFF.  Is there a better
way to do what I want besides inside a period loop?

Thanks!

--
Bobby G.

Schelte - thanks. I thought that if there were a known compatibility issue, the
error message details would be a moot issue. Since this should work, I will
identify my steps and copy the error screen tonight.
thanks,
Jack


--- In homevision-users@yahoogroups.com, Schelte Bron <sbron@...> wrote:
>
> On Wednesday 02 December 2009 13:32:29 jolivier98 wrote:
> > I have been moving my Homevision XL application from one
> >  computer to another. I re-installed everything and updated
> >  the control plug-in from 5.0 to the latest version(6.0).
> >  When I try to import the ctl file that I created under 5.0,
> >  I get an error message. Am I doing something wrong or are
> >  they not compatible?
> >
> Control plug-in 6.0 is supposed to be able to handle control
> files created with 5.0. But "I get an error message" is not
> enough information for me to be able to tell what is wrong.
>
> http://hv.tclcode.com/help.html
>
>
> Thanks,
> Schelte.
>

On Sunday 06 December 2009 00:27:24 robert_green1963 wrote:
> Yes, thanks.  That's exactly what I want to do and gives me
>  an idea how to do the variable timer part of my problem.
>
> Instead of
>
>       X-10 sequence [B-12, B-12, B-On] received within 5
>  seconds
>
> I had managed to create an IF THEN with
>
>       X-10 sequence [B-12] received within 5 seconds AND
>       X-10 sequence [B-12] received within 5 seconds AND
>       X-10 sequence [B-12] received within 5 seconds
>
> which never executed although I couldn't explain my answer on
>  paper, professor!
>
The big advantage of using [B-12, B-12, B-On] over [B-12, B-12,
B-12] is that you can detect the first one inside the B-12 On
action. For the second one you would need to constantly check
using a periodic event that runs every loop. So the overhead can
be much lower for sequences that end in an On or Off signal,
especially if you have a fair number of sequences to check for.


Schelte.

Yes, thanks.  That's exactly what I want to do and gives me an idea how to do
the variable timer part of my problem.

Instead of

       X-10 sequence [B-12, B-12, B-On] received within 5 seconds

I had managed to create an IF THEN with

       X-10 sequence [B-12] received within 5 seconds AND
       X-10 sequence [B-12] received within 5 seconds AND
       X-10 sequence [B-12] received within 5 seconds

which never executed although I couldn't explain my answer on paper, professor!

--
Bobby G.


--- In homevision-users@yahoogroups.com, Schelte Bron <sbron@...> wrote:
>
> On Saturday 05 December 2009 22:30:39 Bobby Green wrote:
> >  I'm trying to get a macro to fire by pressing unit button 4
> >  on a maxicontroller 3 times in a row.  I'm doing this to
> >  "multiplex" the keys on the maxicontroller to give me more
> >  than just 16 control options.
>
> http://hv.tclcode.com/wiki/19
>
>
> Schelte.
>

Actually, I was afraid I would have to use variables to get this to work.  I
probably will have to bulletproof what I am using now but the incredible simple
line of code I posted in the previous message does exactly what I want and has
enormous potential.

Since my wife is not as convinced that every possible chair, couch or bed in the
house should control the entire automation environment, I have been looking for
a way to extend the usefulness of some BSR era maxi controllers I've concealed
inside things like Chinese puzzle boxes for higher SAF.

This sequence [X,X,X]technique lets me access far more than 16 codes per unit. 
I can keep a numerical list printed up for the lids of the boxes and put it on
the house intraCCTV net.

I suspect the challenge will be when I implement more than the one sequence
command I have now and to make sure that I don't call the wrong one because my
code might let a 144 code also activate a 14 macro.  I guess I need to decide
now whether all macros will be three keyed or whether I can write a parse in HV
code that can handle different length X-10 sequences.

Your technique will be useful for another project:  I want to be able to leave
the house, and depending on the number of teen-age hooligans there are in the
street, want to be able to set a variable delay from a single button.  In other
words, if I press 16 - 16 - 16 to run a turn out the lights macro, I would like
to be able to press another button, say 4, X times, with X representing an
incremental 5 minute delay.


16-16-16-4 means turn off the lights in 5 minutes
16-16-16-4-4 means turn off the lights in 10 minutes
16-16-16-4-4-4 means turn off the lights in 15 minutes

As awkward as it seems, it's better than trying to remember the timer sequence
on the UR24-remote. I'm sure it lends itself to much smarter coding using
timers, variable and iteration but it's been ten years or more since I have
written a line of code . . .

Thanks for your input,

--
Bobby G.



--- In homevision-users@yahoogroups.com, "toscal" <toscal@...> wrote:
>
> Why not try using a variable that gets incremented by one every time you press
the same button. You will also need to add some sort of time limitation.
>
> Something along the lines of:
>
> If
>    X-10: A 2 (HiFi Lights) is on
>    And Var #0 (Var 0) = 3
> Then
>    Do Macro #4 (Macro 4) once
>    Var #0 (Var 0) = 0
> Else
>    Var #0 (Var 0) = Var #0 (Var 0) + 1
> End If
>
>  Needs the timing thing sorting out, but hope this helps.
>
> --- In homevision-users@yahoogroups.com, Bobby Green <robert_green1963@>
wrote:
> >
> >  I'm trying to get a macro to fire by pressing unit button 4 on a
maxicontroller 3 times in a row.  I'm doing this to "multiplex" the keys on the
maxicontroller to give me more than just 16 control options.  I've tried
everything I could think of but nothing happens.  Can someone point me in the
right direction?  I am using HomeVision 3.45A.  I've already fallen for the trap
where I didn't press the "Change This Signal" button that you need to press to
actually change the signal!! I've also tried putting the code in a periodic
event without luck.  My tech experience with HV programming is obviously very
low so speak s-l-o-w-l-y.  (-:
> >
> > Thanks in advance!
> >
> > --
> > Bobby G.
> >
>

On Saturday 05 December 2009 22:30:39 Bobby Green wrote:
>  I'm trying to get a macro to fire by pressing unit button 4
>  on a maxicontroller 3 times in a row.  I'm doing this to
>  "multiplex" the keys on the maxicontroller to give me more
>  than just 16 control options.

http://hv.tclcode.com/wiki/19


Schelte.

Why not try using a variable that gets incremented by one every time you press
the same button. You will also need to add some sort of time limitation.

Something along the lines of:

If
    X-10: A 2 (HiFi Lights) is on
    And Var #0 (Var 0) = 3
Then
    Do Macro #4 (Macro 4) once
    Var #0 (Var 0) = 0
Else
    Var #0 (Var 0) = Var #0 (Var 0) + 1
End If

  Needs the timing thing sorting out, but hope this helps.

--- In homevision-users@yahoogroups.com, Bobby Green <robert_green1963@...>
wrote:
>
>  I'm trying to get a macro to fire by pressing unit button 4 on a
maxicontroller 3 times in a row.  I'm doing this to "multiplex" the keys on the
maxicontroller to give me more than just 16 control options.  I've tried
everything I could think of but nothing happens.  Can someone point me in the
right direction?  I am using HomeVision 3.45A.  I've already fallen for the trap
where I didn't press the "Change This Signal" button that you need to press to
actually change the signal!! I've also tried putting the code in a periodic
event without luck.  My tech experience with HV programming is obviously very
low so speak s-l-o-w-l-y.  (-:
>
> Thanks in advance!
>
> --
> Bobby G.
>

Found out how to properly chain 3 sequences in a row so that the code says:

IF
    X-10 Sequence [B4, B4, B4] received within 5 seconds.

I had been added them as ADD clauses within the IF statement.  I'll probably
need more help, but this seems to have been the logjam.

--
Bobby G.

I'm trying to get a macro to fire by pressing unit button 4 on a maxicontroller
3 times in a row.  I'm doing this to "multiplex" the keys on the maxicontroller
to give me more than just 16 control options.  I've tried everything I could
think of but nothing happens.  Can someone point me in the right direction?  I
am using HomeVision 3.45A.  I've already fallen for the trap where I didn't
press the "Change This Signal" button that you need to press to actually change
the signal!! I've also tried putting the code in a periodic event without luck. 
My tech experience with HV programming is obviously very low so speak
s-l-o-w-l-y.  (-:

Thanks in advance!

--
Bobby G.

On Wednesday 02 December 2009 13:32:29 jolivier98 wrote:
> I have been moving my Homevision XL application from one
>  computer to another. I re-installed everything and updated
>  the control plug-in from 5.0 to the latest version(6.0).
>  When I try to import the ctl file that I created under 5.0,
>  I get an error message. Am I doing something wrong or are
>  they not compatible?
>
Control plug-in 6.0 is supposed to be able to handle control
files created with 5.0. But "I get an error message" is not
enough information for me to be able to tell what is wrong.

http://hv.tclcode.com/help.html


Thanks,
Schelte.

So I got my control file (ctl) working on the new computer by cutting and
pasting of the code from the old ctl file to the new one.

Now it works, but there is a split second flash to white when switching screens
within the control screens which did not happen on the previous computer.

The previous computer is a 3.0 GHZ desktop with 768 MB of RAM and the "new"
computer is a 1 GHZ laptop with 256MB of memory. Does anyone know if I upgrade
the memory, the problem will go away or it the laptop just too slow?

thanks,
Jack

I have been moving my Homevision XL application from one computer to another. I
re-installed everything and updated the control plug-in from 5.0 to the latest
version(6.0). When I try to import the ctl file that I created under 5.0, I get
an error message. Am I doing something wrong or are they not compatible?

thanks,
Jack

On Sunday 29 November 2009 18:50:10 Bob Baldwin wrote:
> While I currently do not have a `need', or even a hint of a
> `need', for said  `services'  it's actually really nice to
> know that there is the capability available.

On Monday 30 November 2009 13:42:09 Bruce Fisher wrote:
> That is really awesome!  You never cease to amaze me.
>
Thanks for the encouragement, guys :-)


Schelte

As I learn more about Windows 7...which version are you running?
I see that two of them have an XP compatibility mode. Do you
need to invoke that to run the HV software? Thanks.

Mark


---- On Mon, 30 Nov 2009, Glen Ferguson
(glen.ferguson@...) wrote:

Works fine on my Win7



From: homevision-users@yahoogroups.com
[mailto:homevision-users@yahoogroups.com] On Behalf Of Mark A.
Dalla Valle
Sent: Monday, 30 November 2009 12:48 PM
To:
Subject: [HOMEVIS] Windows 7





Will the HV software (non-Pro) run on the new Windows 7 OS?
Thanks.

Mark

Will  HV pro run on the new Windows 7 OS?

Thanks

----- Original Message -----

From: Schelte Bron

To: homevision-users@yahoogroups.com

Sent: Sunday, November 29, 2009 8:43 AM

Subject: Re: [HOMEVIS] Counting pulses

 

Undeterred by the total absence of any reaction to my previous
messages about the subject I have vastly improved the picprog
plug-in. It can now handle several different types of PICs and
keep track of multiple self-programmable expansion boards.
http://hv.tclcode.com/picprog.html

I have also modified the MiniMFEB code. By defining the COUNTER
symbol while building the project, one of the analog ports gets
turned into a pulse counter. With an optional 8-bit prescaler it
can count over 65000 pulses during each "loop" of the controller
without any loss of accuracy.
http://hv.tclcode.com/minimfeb.html

Thanks,
Schelte.

On Monday 26 October 2009 23:44:29 Schelte Bron wrote:
> On Tuesday 20 October 2009 20:27:55 Chuck wrote:
> > Thanks guys. Well I don't have a serial port so the 1 wire
> > won't work... dropping a few pulses won't be the end of the
> > world.
> >
> > Maybe Craig can put on the wish list 'pulse counting input
> > channels'. With all the power/gas/water monitoring stuff
> > people are starting to do I'm sure it would be a feature
> > that would sell more units! Probably more work to change
> > the documentation than the code. I can dream.
>
> The "Mini MFEB" (http://hv.tclcode.com/picprog.html#minimfeb)
> I just mentioned to Jim would only need different firmware
> to be able to count pulses into the MHz range itself, or to
> support the 1-wire counter board from Hobby Boards.
>
>
> Thanks,
> Schelte.