DVX Standby mode

George Krietsepis

Dear All,
as per the DVX documentation, Standby Mode can be activated via channel 100 and exits on any power cycle or reboot. This means that we can only hard switch off and on the rear panel power switch ? What about the reboot ? Can we send a "reboot" command on 5002:1:0 ? Is there any other way to take the DVX out of standby mode ?
Also, how can we ensure power on status of a DVX ? Is there any command requesting the power status of a DVX ?

Thanks,
George

d_gavin

To Deactivate Standby mode you need to turn Channel 100 Off. This is stated in the DVX documentation in the Standby Mode section. You also get your Standby Mode Feedback with this channel.
Standby Mode
You can activate Standby Mode using one of the following methods:

You can activate Standby Mode via channel 100 on the DVX. Set channel 100 to ON to activate Standby Mode. Deactivate Standby Mode by setting channel 100 to OFF.
You can activate Standby Mode by accessing the Status menu on the front panel LCD display. Use the navigational buttons fon the front panel to locate the Enter Standby Mode option in the Status menu, and use the left and right arrow buttons to set the value to YES to activate Standby Mode.

JasonS

Be aware that at one point, I don't know if this is still true, Standby mode powers down all of the DxLink endpoints powered via the DVX. Not a "Feature" in my book.

richardherman

And it will also turn of EDID communication. So, if someone connects their laptop to the system and then turn it on, they probably won't have any image. At least it was that way in the early DVX days. not sure if something like hot -plug detect will work better now.
While this probably is expected behaviour, it still can catch you off guard.

ericmedley

richardherman wrote: »

And it will also turn of EDID communication. So, if someone connects their laptop to the system and then turn it on, they probably won't have any image. At least it was that way in the early DVX days. not sure if something like hot -plug detect will work better now.
While this probably is expected behaviour, it still can catch you off guard.

In addition, if you have chosen to give the client an "Auto Sense" feature where they can plug in a laptop, and by doing so, automatically turn on a room. (deploy the screen/projector/select input/etc...)

I really wish these "power saving" functions were a bit more sensible. but, usually they're not.

TonyAngelo

This is part of the Programmer Re-certification practical, so I'm guessing the OP is just following directions and not intending to actually implement this in the field.

George Krietsepis

thank you all for your replies.. just one more question please.
How long does it take for DVX to be taken out of standby mode since we have turn channel 100 off ? Will we get the real mode state from this channel as well ( as per d_gaving reply above ) ?

button_event[dvTP,1] //activate standby mode
{
push : on[dvDVX,100]
}

button_event[dvTP,2] //de activate standby mode
{
push : off[dvDVX,100]
}

channel_event[dvDVX,100] //standby mode state
{
on : standby_mode = activate
off: : standby_mode = de_activate
}

But how can the above give a real state of the mode since the 2 button events cause anyway the DVX channel 100 to be tuned on/off ?
For example, by engaging the event for de activate the standby mode, the DVX channel 100 will be turned off. From that point, the DVX will start getting out of the standby mode. But how long does this procedure take ? In the meantime, the channel event should have set the standby_mode variable to de_activate value just because this channel has already been set to off because of the button event and NOT because of the DVX real standby mode feedback.
Am I missing something ?

richardherman

George Krietsepis wrote: »

But how can the above give a real state of the mode since the 2 button events cause anyway the DVX channel 100 to be tuned on/off ?

Am I missing something ?

A channel has 3 'states': input, output and feedback. If you push a channel, you use the inputside, if you turn on a channel, you use the outputside. In this case the DVX controls the feedbackside and that is what triggers the channel_event.

Below is a snippet from a 'port status' in the online tree for a (custom) module for some device. It only has the feedback channel 255 on (power feedback in this case). No output or input. That's how almost every Duet module works, just look at the documentation for a given one and see wat they do for ie the power channel (255)

Feedback Channels on for [33001:1:1]: 255
No Input Channels on for [33001:1:1]
No Output Channels on for [33001:1:1]

If you make you own modules and use "DYNAMIC_VIRTUAL_DEVICE" and 'TRANSLATE_DEVICE" you can do the same. Unfortunately those commands are unsuported and undocumented. But they work...

I admit it's sorta confusing and maybe someone else has a better/clearer explanation...

George Krietsepis

The below is from the notification window when activating the standby mode of the DVX :

button_event[dvTP,1]
{
push: on[dvDVX,100]
}


Output Channel : On-From [5002:1:0] - Channel 100
Output Channel : On [5002:1:0] - Channel 100
Feedback: On [5002:1:0] - Channel 100

Which of the above expresses the real feedback coming from DVX and which will trigger the below channel event ?


channel_event[dvDVX,100]
{
on : send_string 0, 'Standby activated'
}

Raphayo

In documentation, it take about 20 sec process. Other standby cmd (on/off) send during that process are ignored.