Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Walken100

Pages: [1] 2 3 4
General Discussion / Nothing is logging
« on: January 13, 2013, 09:39:26 am »
Ok, I suspect that this is simple but I'm hours into searching with no luck. I was trying to copy some information from my log and there is nothing in the log.  Logging is on for the global cache but commands are not being logged.  So I checked a couple of other devices that have logging on and they are not logging either.  Everything is working otherwise. 

In the past logging has worked fine. I've made no changes (that I remember or am aware of  :-\)

Thoughts on what I should look for?



Touch Screen Interfaces / Continuous volume up/down
« on: January 01, 2013, 01:29:21 pm »
Ok, I'm not sure if this is a touch screen topic or a global cache topic but I'll start here.

I'm trying to create a continuous volume up/down IR signal. In other words when I press and hold the volume up button the volume continues to increase until its released same as the factory control.

Seems simple and I've found documentation relative to the global cache but none I can seem to implement this functionality in Elve. Has someone done this? If so can you share.



User Showcase / Theater control with Elve and global cache
« on: December 22, 2012, 06:31:04 pm »
Ok, I'm on holiday, bored and playing with my touchscreens....

Here is the touchscreen I created for my theater.  I've been using it for the last 4 months. It's currently based on a Nexus 7 and controls an Epson projector, Yamaha Receiver, LG Blu-ray player, and lights. I have a global cache for IR and a variety of stuff to control lights.  It has replaced a URC RF remote and has worked nearly flawlessly since I started.  In fact it has been more reliable/robust than the URC remote (which was dang good).  It does not currently control my DirecTv but only because it is new I'm not yet bored enough to build/download the IR codes for the remote.

My hindsight is that if I had known how well this would have worked I would have bought the global cache a lot sooner. If you are thinking about using Elve with a global cache.... do it. 

And if you have the DirectTV HD receiver IR codes and a  better blue "disc menu" icon you can send me I'd appreciate it.....

Ok, I've shared.

Touch Screen Interfaces / A way to dim an android touchscreen after no use
« on: December 22, 2012, 01:31:42 pm »
Ok, this may seem mundane (and it probably is) but I'm looking for a way for my Touchscreen to dim or go black a minute or two after the last use and then be able to wake it up on touch. Ideally it would dim substantially but still be somewhat visible but black would work.

I use a Nexus 7 as my home theater touchscreen remote and the two choices I have for set up are to keep the screen on or let the tablet go to sleep.  The problem is that when it is on and not being used it is too bright in a dark theater (even when manually dimmed to the minimum).  When it goes to sleep it requires a hard button push and then a swipe to bring the touchscreen back.  Ok not the end of the world but neither is walking over and turning on a light using the switch at the wall (God forbid).

It would be nice if there was an option to go into a mode that was VERY dim or black and only required a touch to bring back the touchscreen to the correct/usable brightness.



Touch Screen Interfaces / Android touch screen guidelines
« on: August 18, 2012, 10:32:04 am »
Looking for some guidelines on structuring a touch screen for use on an android tablet (probably applies to Apple devices as well).  I have a specific question but I'm also looking for any lessons learned (good or bad).

My specific questions are:

- Related to popups and inner touchscreens. I'm using a pop up on the main screen and it works very slow.  Should this be avoided or is there a way to make it respond faster? Has anyone simulated a pop up using hidden controls and did this avoid the latency issue? Other work-arounds?

- Sound, has anyone made added sound to a touchscreen used on an android? If so where did you keep the native sound files?

The performance from the main touch screen is plenty fast and so far working with Elve and a global cache is producing more consistent results than either of my URC RF remotes  :)

Any guidelines would be appreciated.


Touch Screen Interfaces / Touch Screen Viewer Lite Ghosting
« on: July 14, 2012, 07:09:23 pm »
Ok this feels like a bug but every time I go down that path its something I've done so I thought I'd do some homework first.

Every time I run TS viewer Lite and change inner touch screens I have a ghosted image of the previous touch screen. This is bad enough that it can make it hard to see controls on the active touch screen.

Anything I'm doing wrong?

Also, I did search but I'm not sure of the correct terminology to search on so if this has been covered I apologize.


Device Configuration / Maximum number of driver services.
« on: July 03, 2012, 08:08:05 pm »
Ok, trying to install my USB-UIRT and I get the following error:

"Driver service 'DON' attempted to register with master server, but the maximum number of driver services are already registered (for the current software license)."

I uninstalled some unused drivers so I'm now down to 9 drivers and I still get the error.

What did I do wrong...

I'm trying to create a drop down box by having a pop up slide in from the bottom of a loader button. The behavior is different when using "slide in from a specific location" than when I use "slide in from top".  When I specify a "from" location (the bottom of the loader button) the pop up just appears with very little "slide in" motion instead of a clean drop down appearance like it does when I specify "slide in from top".

Is the position specified always relative to the top of the touchscreen. If so I don't see how you can have a "from" position that is the same as the "to" position but I may misunderstand the intent of the behavior. Different verbiage may make this clearer.

Am I doing something wrong?

By the way I really like the function, at least the "from the top" version.


PS. The Online Manual still has instructions for the old version of the loader button.

General Discussion / RS232 or IR
« on: June 25, 2012, 06:22:36 pm »
My next effort is to add my theater IR control to Elve. I've picked up a GC100 so now its just a matter of setting of the touch screen, learning a bunch of IR commands etc....

But then I noticed there is a driver for an Epson Powerlite.  Well running wire is running wire so IR or RS232 is equivalent to me. So what experience do you have with IR vs RS232 with Elve.

I know that IR would be straight forward but RS232 is mildly interesting.

Just looking for some personal experience and any input that would drive me one way or the other.

Thanks in advance.


General Discussion / Global Cache functionality other than IR
« on: June 15, 2012, 07:38:46 pm »
Anyone using global cache functionality other than IR? Contact closure, IO etc. It looks like Elve supports the contact closure functionality? I'm just confirming.  If so can it poll the state of the contact? What about sensor functionality?
Just looking for some input.  There are some zwave alternatives but this seems clean if it works.



I’m opening a popup to provide light controls for the light selected. I want to be able to use the popup to turn the lights on and off as well as set the levels.  I’m passing a variable to the touch screen to identify the light by number. I’m then using the following “press” events to operate the light

Dim (using radio buttons for 4 distinct values)
    -   Set X10CM15A light # value of variable named LightSelected to 25 %

    -   Turn on X10CM15A light # value of variable named LightSelected

Tain’t working.

At first I suspected I was doing something wrong with syntax. I’m passing the variable “LightSelected” from the control on the original touch screen with the number of the light that has been selected. Now I’m thinking I’m using the radio button wrong. If I do the same thing but replace the variable with an actual light it still doesn’t work. I tried it with both an X10 light and a Zwave light. Neither worked.

What am I doing wrong?


Edit: after a reboot of both computers involved the Zwave functionality is Ok. X10 isn't working. 

Ok, I'm using the Text field of a button to display the value from a global variable (in this case a temperature I can use as a thermostat set point). I control the value from one touch screen but use the value in a different touch screen as the text on a control. I want the Text to behave similar to an image in a boolean control. After an update I want the Text to be updated to the new value of the global variable that I'm using in the Text field. I can't use the set point in the thermostat because these two events are actually separate.

My options so far are:

1. every time I increment the global variable (with a button press) I can refresh the top touch screen
2. set a rule that refreshes the top touch screen every time the global variable is changed
3. set a rule to refresh the top touch screen at a fixed interval

The problem with the first two is that I may increment the global variable multiple times before a refresh is required but the top screen would refresh with every push of the button. In other words changing the value from 70 to 75 would take 5 button presses but I only need the text that displays the variable to be updated once.  Just seems clunky to refresh the button 5 times.

The problem with the third option is that I'm executing an action thousands of times when it is only needed now and then. Yes electrons are free but, again, this feels clunky.

I suspect that there is a more graceful way to do this but I haven't found it.


Touch Screen Interfaces / Wrong inner touch screen opens
« on: May 22, 2012, 08:54:31 pm »
Ok, I'm experiencing a strange behavior with my inner touch screens. This all started after copying all of the objects from one touch screen onto a new one. I then edited the new touch screen by removing some of the objects.  Each layout is similar, a touch screen with an inner touch screen and a standard set of buttons.

If I load the original touch screen after I've loaded the new touch screen the smaller inner that loads into the original screen is the wrong one. It is from the new touch screen.  This doesn't happen until I've loaded the new touch screen.

In other words, before the new touch screen is opened, everything is fine. After the new touch screen is opened the touch screen I copied objects from is broken (wrong inner opens).

Both touch screens are used as inner touch screens in the main touch screen.  (nested inner touch screens)

I know this is a little confusing but if anyone has ideas on how copying objects from one touch screen to another can corrupt the original touch screen I'd appreciate some input.

Thanks in advance.


Touch Screen Interfaces / Cant get a label's text box to update
« on: May 17, 2012, 08:01:53 pm »
I'm struggling to get a label's text to update.  I'm trying get the label to display the current thermometer set point (Trane z-wave).  The only time I can get it to update the value is if I close and reopen the touchscreen. It doesn't update over time and it doesn't update with a reload.

Any tricks for getting the label to update when the value is changed? I've tried refreshing the label when I update the set point. I've even tried to update a global variable with the actual set point value and then update the label with the variable (was worth a try).

This is the current text value - { lighting2.ThermostatHeatSetPoints[9] } { vars.HeatSetPoint }. Yes I'm trying two different ways to get the value. I've confirmed that the thermostat is updating and that the update registers with the device in the Management studio.

I'm blowing something. Any advice?


Like an image list a text list would display a different text value (or value from a variable) based on a state or mode.

For instance I establish a high and a low set point for the heating mode and a different high and low set point for the cooling mode. I then can select a set point from a button.  I currently only use two buttons to do this to keep the screen uncluttered instead of having 2 sets of buttons. If it was a text list the buttons would display the correct set points for the mode the thermostat was in.

This would just simplify setting up this functionality as it can be done with a little programming.

Pages: [1] 2 3 4