Jump to content

Local program testing flags


larryllix

Recommended Posts

It would be nice for the purpose of testing program operation to have some local video flags or audible sounds generated on the local PC where the Admin Console is running. Possibly a spot that can be linked to a Program (true/False), a variable (maybe analogue value display), or a device status (I know there is a dedicated page for each device but a simple spot on the programmes page would help to watch more items at one time.).

 

Two different definable sounds and linkable to the same logic, as above, would also make trouble shooting much nicer where not being present at the Admin Console is a perquisite for initiating some input device. Recorded .wav files could be used to indicate "Yes/no", "True/false", or hiFreq/LoFreq tones etc..

 

Thanks!!

Link to comment
Hi larryllix,

 

Thanks so very much for the feedback.

 

This is a little difficult especially if you have more than 2 programs. How would you distinguish between them? And, that's precisely the purpose of the Summary tab.

 

With kind regards,

Michel

The screen indicator test flags and sounds could possibly be defined as psuedodevices so that they could be used for debugging INSIDE PROGRAM FLOW instead of real devices like X10 chimes or lamps. Of course this would mostly be temporary usage. Sound may be useful for some permanent uses.

 

If

complex logic condition

 

Then

. set 'some stuff' On

. set 'screen message 1' "Then is running"

. set 'Sound 1' On

. wait 20 minutes

. set 'screen message 1' "Then wait completed"

. set 'some other stuff' On

. set 'screen message 1' ""

 

Else

. set 'screen message 2' "Else has been entered"

. set 'Sound 2' On

. wait 20 minutes

. set 'screen flag 2' ""

. do more stuff

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

Or for hands-free, eyes-free program monitoring of program logic while watching and test running OTHER programs while onscreen.

 

If

. variable '$sState_Variable' = $cTrue

 

Then

. set 'Sound 1' On '* (speak 'the variable is true')

 

Else

. set 'Sound 2' On '* (speak 'the variable is false')

Link to comment

Hi larryllix,

 

I understand. This is going to be a little difficult since, using this method, we would need to send commands to the computer/screen instead of a device. At least in 4.2.x, this will be rather non-trivial. In 5.0, we might be able to do something similar but it all depends on everything else that we have to implement.

 

Thanks again and with kind regards,

Michel

Link to comment
Hi larryllix,

 

I understand. This is going to be a little difficult since, using this method, we would need to send commands to the computer/screen instead of a device. At least in 4.2.x, this will be rather non-trivial. In 5.0, we might be able to do something similar but it all depends on everything else that we have to implement.

 

Thanks again and with kind regards,

Michel

I get what you're saying but already I have used X10 pseudodevices as indicators for Mobilinc Pro, in view of it's lack of variable indicators in the Android version. Similar pseudodevices should be fairly easy to implement in the ISY device tree. Some logic bits/flags would be needed for ISY to not send out Insteon commands when manipulated by programs.

 

At the other end of the spectrum, the device updating process in Admin Console already has all the processes in place as these pseudopoints would just be another monitored device and no difference in process should be apparent.

 

On the GUI part, we would require a spot on the Admin Console or a pop-up message box, a sound driver with settable file name, or even a user settable command line executable to run any other software based on a change of a device/pseudodevice. This could have a any media file play using the already system defined players. Obviously this would have to be in Admin Console end of things. The Admin Console could then make phone calls and advise people of things. Before people get too excited about that the Admin Console would have to be running permanently and it seems to have some time-out problems yet.

 

On that same vein I would be sure somebody could create a settable commandline dispatch app based on ISY events that could perform these duties. That would only leave creating pseudopoints in ISY.

 

I hope this stuff isn't already part of the network module. :)

 

Thanks for listening to my rants.

Link to comment

Larry-

 

Have a look at EventGhost. I believe there are some on here using it to do some of the things you are asking for. I believe there is an ISY plugin for it as well.

 

I have not used it and don't know much about it beyond what I have read here but sounds to me like just what you are looking for.

 

-Xathros

Link to comment

Thinking again about the flags/text message boxes for testing, all that would be needed is to associate variables with command line strings or message boxes in the Admin Console. The rest is already there using ISY variables as the communication medium. Different integer values could invoke from a table of shell command lines or, for testing, just be displayed on the Admin Console page.

Link to comment
Hi larryllix,

 

Thanks so very much for the details. Although quite useful, it's a little out of our scope especially since have a huge project going forward with 5.0. Perhaps we can revisit after we are done with 5.0.

 

Thanks again and with kind regards,

Michel

You go girl(s)!! :) I know things are moving fast in this industry.

 

Thanks Michel.

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...