628495
6
Zoom out
Zoom in
Previous page
1/105
Next page
values and then send commands to the Vortexes to set them to the same state. This approach has significant
disadvantages since initializing the host program could undo settings made by other host programs or by the
front panel controls of one of the linked Vortex devices. A better approach is to query the linked Vortex devices
for their status and set the host program controls based on the return values.
3.2. Wildcard Characters
The use of the wildcard character, '*', can make programming the host controller much easier. Be careful when
using wildcards, however, since they can generate a lot of traffic on the digital bus.
3.3. Using Acknowledgements
It is a good idea for the host program or control system to make sure that all connected Vortex devices have
acknowledgment mode enabled (see the
ACKMOD command). When acknowledgment mode is on, a Vortex
device will send an acknowledgment for each command it receives. Proper use of acknowledgments makes the
host program more robust and makes supporting multiple hosts effortless. The rest of this section describes how
to use acknowledgments to achieve these goals.
As a convenient example, let us imagine a host program with a graphical user interface (GUI). The user presses
buttons on the GUI to enable or disable features of various linked Vortex devices. The buttons on the GUI reflect
the current status of the corresponding feature.
When the user presses a button on the GUI to enable or disable a feature, the host program should send the
corresponding command to the selected Vortex device. It may be tempting to update the status of the GUI
button at this point, but this can cause problems if there are transmission errors or if there are multiple host
controllers. The proper way to handle this is to only update the GUI controls based on acknowledgments
received from the Vortex device.
To implement this, organize your code so that the functions that send commands are totally separate from the
functions that receive responses from the Vortex devices. This also enables your host program to support the
presence of multiple host controllers. For example, consider the following sequence of events.
1. Another host sends a command to a Vortex device.
2. The Vortex device responds with an acknowledgment that is broadcast to all of the other hosts.
3. Your host program receives the acknowledgment and updates the status of the corresponding control.
The result of this programming model is that all hosts and linked Vortex devices will always be synchronized.
For simple on/off features, your host program can make use of the toggle arguments to some commands (e.g.,
'SSEN2'). By sending a toggle command when a button is pressed, and updating the button based on
acknowledgments, your host program will not have to keep track of the status of the button.
In a similar fashion, many of the integer commands (such as gains) can be controlled by incrementing or
decrementing them by a specific amount. For example, the command 'GAINIA>1 ' increments the input gain on
channel A by 1 dB. The acknowledgment for this command will return the actual value that the gain was
incremented to. Thus, to implement a volume control, your control program can send a command to increment
the gain by 1 dB when the "up" button is pressed and decrement the gain by 1 dB when the "down" button is
pressed. The control can update its level indicator based on the acknowledgment that is received.
3.4. Macros and Presets
Although macros and presets are similar, there are times when using one is better than the other. Presets store
6


Need help? Post your question in this forum.

Forumrules


Report abuse

Libble takes abuse of its services very seriously. We're committed to dealing with such abuse according to the laws in your country of residence. When you submit a report, we'll investigate it and take the appropriate action. We'll get back to you only if we require additional details or have more information to share.

Product:

For example, Anti-Semitic content, racist content, or material that could result in a violent physical act.

For example, a credit card number, a personal identification number, or an unlisted home address. Note that email addresses and full names are not considered private information.

Forumrules

To achieve meaningful questions, we apply the following rules:

Register

Register getting emails for Polycom Vortex EF2280 at:


You will receive an email to register for one or both of the options.


Get your user manual by e-mail

Enter your email address to receive the manual of Polycom Vortex EF2280 in the language / languages: English as an attachment in your email.

The manual is 0,82 mb in size.

 

You will receive the manual in your email within minutes. If you have not received an email, then probably have entered the wrong email address or your mailbox is too full. In addition, it may be that your ISP may have a maximum size for emails to receive.

Others manual(s) of Polycom Vortex EF2280

Polycom Vortex EF2280 User Manual - English - 62 pages


The manual is sent by email. Check your email

If you have not received an email with the manual within fifteen minutes, it may be that you have a entered a wrong email address or that your ISP has set a maximum size to receive email that is smaller than the size of the manual.

The email address you have provided is not correct.

Please check the email address and correct it.

Your question is posted on this page

Would you like to receive an email when new answers and questions are posted? Please enter your email address.



Info