Anyone found a way to get a Multimedia Agent to ‘play’ on the remote PC. We’re starting a sound from an Alarm agent, but can only get it to play on the Server PC, not on any of the connected remote instances of Operator…
If You’re using smartui, try this Playing a custom sound when alarms occur
Will do - I’ll have to code it myself though - these guys aren’t really up to speed on spiders yet… Is there no other simple way?
If you’re feeling more comfortable with scripting instead you can try this Global Client Side Events with a pinch of .net sound control. Remember that file used for playing should be either available through network path or reside on each client machine in the same location. A good idea would be to use built in windows alarm sounds.
This KB article has also been updated to provide a “ready-made” wizard which can be used. This wizard already contains the necessary logic to work with the associated MediaPlayer control:
Here is an alternative control as well.
Playing an alarm sound
Playing an alarm sound on any smart ui operator being it local or remote
In many cases a sound is required from the SCADA to alert a process controller that there is an alarm or problem that needs to be attended too. Let’s look at some options here.
Using the Agent Server to generate the sound
Making use of the agent server’s alarming sub-system an alarm can be routed to the beeper agent. In most cases this will suffice but there are cases where the server machine on which the agent server is running is in another room altogether and the process controller will not even hear it. If multimedia speakers are attached to the server machine it could also be used in conjunction with the multimedia agent that can play WAV files. See steps below to follow:
In your alarm agent select the route you are interested in sending a sound to it ad add the beeper agent to it.
If you want to make use of the multimedia to play WAV files just create a Multimedia agent and then add it into the alarm agents route accordingly.
Configure the agent accordingly and start the agent, then add it to the alarm agent.
Now any agent alarmed to the defaultAlarmAgent on route 2 in this case will trigger the sound to be played while it is unacknowledged.
The only downside to this method is that the sound is not being transferred to the remote clients and as such will only work on the local server machine where the agent server is running. That brings us to the next option.
Using the Operator Alarm Sound Control to generate the sound
Operator Alarm Sound.dll (7.5 KB)
The attached “Operator Alarm Sound.DLL” file can be used to generate the sound of any WAV file which is playable on any smart operator both locally and remotely. See steps below to use the file and setup the sound to be played.
- Copy the DLL file into “c:\program files (x86)\adroit technologies\maps\plugins” folder for MAPS and “c:\program files (x86)\adroit technologies\adroit\smart ui\plugins” folder for ADROIT.
- Open the designer and in the toolbox perform a right mouse click for the context menu and select “Add Controls”. Browse and select this DLL file and press finish. The control will now be accessible from the “Custom” section in the toolbox.
- Add this control onto a graphic form that is basically always open. Most commonly this will be a graphic form with a TGO on it as well. Normally your default landing page that loads when the operator opens up.
- The following control properties will need to be adjusted accordingly to the requirments.
a. AlarmEnabled – Enables or disables the playing of sound.
b. AlarmSoundAgent – This is a data element pointing to a Boolean slot. This could be any Boolean slot that will trigger the playing of the sound while it is high and will stop playing the sound when the value is low.
c. AlarmSoundDelay – The delay in milliseconds that will be used to repeat the sound as well as check if it is required to be played at all.
d. AlarmSoundFile – type the file and path to the WAV file in here.
- Save the form and test it in the operator.
PS. ENSURE THAT THE WAV FILE AND CONTROL DLL FILE IS PLACED ONTO ALL OPERATOR MACHINES IN ALSO THE EXACT SAME PLACE AS THE CONTROL WILL RUN LOCALLY ON THE OPERATOR STATIONS.
This solution tested by Carl, m’self & Mark Hill from NGF Europe on an installation with remote clients in the North West of England and in Poland (agenda server running in different countries, never mind different rooms!) Worked a treat - good solution Carl Just requires replicating the dll and the sound-file over all the client machines. (I guess they might end up using translated sound files on the Polish remote client - I’ll have to suggest it!)