Version 4.37 Beta (Server, Client, Mini, PanelDesigner) 3/04/2010

1. WARNING: See Notes about version 4.36. If you are upgrading from a version prior to 4.36, you must upgrade all applications as the communications protocol changed between the client applications and server with version 4.36. As always we recommend making a backup of your PathfinderServer folder before upgrading.

2. This version requires .net framework 2.0 or later to run for some of the components in the PanelDesigner, Client, and Mini.

3. The installer package has been completely reworked in order to support the hybrid technologies. If you have created shortcuts to the applications on your desktop or quick start bar, they may need to be recreated after upgrading to this version.

4. Added support to create an IPort Mpeg router which routes the mpeg stream side of IPort. This currently only works if the MPEG streams are set to multicast.

5. Added EV for AVC.

6. Fixed a bug with standard events that caused the None option for source to not work correctly in standard routing events and caused unending wait icons in the client user interface. Also added the None option to the server interface for standard routing events.

7. Added a command line switch to the server to log metering/silence alarm mismatches. This is for internal debugging only unless support asks the client to enable it as it adds load to the cpu. The switch is –lm.

8. Added the ability to enable and disable stack event groups and stack events.

9. Optimized code in the client and mini for metering displays. Also optimized the meter control itself. This resulted in large reductions in cpu utilization for large metering user panels. A side effect is that the meter control on the panel will no longer have a transparent line between the left and right meters.

10. Added the clock control to user panels. This control can display time with an analog or digital clock with and without a face and with and without a background image. There are quite a few properties which can be manipulated with this clock.

11. Added the ability in user panels to change the font in buttons and labels.

12. Fixed a bug in the console control stack event qualifiers that was causing them not to get evaluated properly in some cases. This bug had been introduced since we added the ability to change source profiles loaded to a fader.

13. Updated the syntax and GetList router type strings so that they match for all routers in SAProtocol. Some routers which previously had spaces in the type names of the router for these commands have now been changed.

Version 4.36 Beta (Server, Client, Mini, PanelDesigner) 2/11/2010

1. WARNING: This version changes the communication protocol. All applications must be upgraded to move to this version. Older versions of the client will not work with this version of the server and vice versa. As always we recommend making a backup copy of the Pathfinder Server folder before upgrading.

2. Modified the communications protocol between server and client as well as between the server and mini to remove Ascii protocol markers above Ascii 128. This protocol change should allow the software to function on systems with international character sets.

3. International Customers who wish to migrate an existing server that is set to international language settings should upgrade and launch the new version of the server first. Then Open the new client and open any scenes and resave them. Then they can migrate to the new language settings. International customers who are installing new do not need to worry about this step.

4. Exposed Silence alarms in scripting by adding AddSilenceWatch, RemoveSilenceWatch, and GetSilenceWatchState functions in scripting.

5. Modified the textual copy and paste code in Panel Designer to allow copying and pasting in the property list

6. Modified the Save functions in Panel Designer to more closely represent normal save dialogs and remove the extra message boxes.

7. Added a * to the PanelDesigner title bar when the panel has changed and needs a save.

8. Fixed an issue in the GPIO stack event handling code that was causing it to take longer than it should due to duplicate analysis.

9. Includes the option to change the GPIO livewire channel number association in the GPIO stack event qualifier and action.

Version 4.35 Beta (Server, Client, Mini, PanelDesigner) 1/30/2010

1. Added Mixing capability to the BTools emulation. BTools emulation can now be configured to be switching or mixing. Mixing requires VMIX. Please see the white paper for setting up and configuring BTools emulation with mixing. http://pathfinderpc.com/BToolsEmulatedMixing.pdf.

2. Updated automatic generation of VMIX busses in the BTools mixing emulation to utilize fewer VMIX channels and achieve the same goal.

3. On computers with certain versions of the Microsoft XML interpreter there was a misinterpretation which would cause Source meters to display as the same numbered destination meter instead. This has been fixed in Client, Mini, and PanelDesigner. Remember Panel Designer does not need to be installed on a server machine as it is automatically installed as part of the Server installation package. 4.35 server package also carries 4.35 panel designer.

4. Added an option to change the GPIO livewire channel number association in the GPIO stack event qualifier and action.

Version 4.34 Beta (Server) 1/30/2010

1. Added Mixing capability to the BTools emulation. BTools emulation can now be configured to be switching or mixing. Mixing requires VMIX. Please see the white paper for setting up and configuring BTools emulation with mixing. http://pathfinderpc.com/BToolsEmulatedMixing.pdf.

Version 4.33 Beta (Server) 12/15/2009

1. Fixed a bug which was introduced in 4.32. The bug made creating Virtual Routers impossible because they would appear as Gateway Routers. This has been fixed.

Version 4.32 Beta (Server) 12/09/2009

1. Fixed a bug in time based events/stackevents. If there were a lot of events scheduled to run in the last second or two before midnight, it was possible that some would not complete before midnight and those that did not would get skipped. Now they all will get run even if it takes a second or so after midnight to complete.

Version 4.31 Beta (Server) 11/23/2009

1. Added an Any option to the memory slot qualifier which will allow the actions to be run whenever the memory slot is changed. When analyzing the qualifier, the qualifier will always be true unless the named slot does not exist (has been deleted/cleared or not created).

2. Protocol Translators can now be TCP Clients as well as TCP Servers. PFServer protocol translator will maintain and reconnect to another computer IP/port.

3. Added a field on the Protocol Translator tab which shows the connection state of the translator.

Version 4.30 Beta (Server) 11/20/2009

1. Fixed a bug in the memory slot qualifier with uppercase letters in the values which would not allow a match. Matching of memory slot values is now case insensitive.

2. In the User Command Stack Event UI the Enabled and Disabled items in the combo box for protocol translators were reversed. This has been fixed.

Version 4.29 Beta (Server, Client, PanelDesigner, Mini) 11/17/2009

1. Added support for Source Profile changing and sensing in the Console Control Stack events. Qualifiers can now sense when a source profile is loaded, and source profile changes on a physical fader can be triggered from stack events. This requires Element version 2.2.0.9 or later and PowerStation 1.0.2g or later.

2. Fixed a bug reported by Broadcast Bionics where console control actions would send the fader gain even if no fader change was selected to be sent.

3. Fixed a bug which sometimes caused destination meters not to display properly in panels. This is a fix in Client and Server and Mini.

4. Protocol translators can now have three states – Enabled, Disabled, and Sleeping. Startup states can be programmed. The states can be manually changed with the protocol translator tab, and they can also be changed through stack events. Changes in these states can also act as qualifiers in protocol translators. The sleep state includes a wake a sleep command which can be set. When a translator is in sleep, it is open and will accept connections but will not process or send any data unless it sees the wake command, which will kick it to enabled. If the sleep command is received it will go into sleep mode. The sleep mode is useful in situations where you have multiple backup automation systems trying to address the same set of resources (like GPIOs). For example if you have 2 Google boxes (Primary and Backup) communicating via BTools emulation, you can program both emulators to target the same GPIOs. The one that is not active will remain asleep and be ignored unless a wake command showing it has taken over is received. The current state is also synced across the cluster.

5. Added the REGEX keyword. This can be used in protocol translator sleep and wake commands and in memory slot analysis and in protocol translator command analysis. In these data fields use REGEX(myregex). This allows a stack event memory slot or inbound protocol translator command to be analyzed using a regex for a match. This is useful for example in data where you may get the results of multiple closures in a row and you only care about the third one. See Wikipedia for information on Regex.

6. Added the syntax command to SAProtocol. This allows the syntax for getlist functions to be retrieved. Will be used in the new stack event editor to retrieve PFS data.

7. Fixed a bug where if the main form load fails, it could leave the main client connect port at 0 which then picks an arbitrary port. This is fixed.

8. Added the Previous entry to the Route Change Source Stack Event Action. This will allow you to route back to whatever was previously selected without needing to know what that selection was. This is useful if you want to quickly change the source routed to a destination and then return back to whatever was previously selected. PFS must have been running long enough to have seen a change to know the previous entry.

9. Added the Previous entry to the Element Profile Change Stack Event Action. This will allow you to load the previously selected Element Profile. This is useful if you want to quickly change an Element profile and then change back. PFS must have been running long enough to have seen a change to know the previous entry.

10. Added the Previous entry to the Source Profile Combo (see item 1). This will allow you to load the previously selected source profile. This is useful if you want to quickly change a source profile loaded to a fader and then change back to whatever was selected. PFS must have been running long enough to have seen a change to know the previous entry.

11. Added the Any entry into the Router Change Source Stack Event Qualifier. This allows the actions to be run whenever a new source is assigned to a destination no matter what the source is.

12. Added the Any entry into the Element Profile Change Stack Event Qualifier. This allows the actions to be run whenever a new Element Profile is loaded.

13. Added the Any entry into the Source Profile Change Stack event Qualifier. This allows the actions to be run whenever a new Element Source Profile is loaded.

14. Introduced Functions into stack events. Functions may be used in fields in place of values. This allows you to do things like make a route change to whatever source number resides in a memory slot, or make a label on a panel display the name of whatever source is loaded to a destination. Use a Function by using the keyword funct:functname(). So for example – funct:add(1,2). Functions can also be nested. funct:StartsWith(funct:MemorySlotValue(“CurrentState”),”ONAIR”)

1. funct:RouterName(<RouterNum>) Returns the name of a specific Router when given the number

2. funct:SourceName(<RouterNum>,<SourceNumber>) Returns the name of a specific Source

3. funct:DestName(<RouterNum>,<SourceNumber>) Returns the name of a specific Destination

4. funct:SourceDescript(<RouterNum>,<SourceNumber>) Returns the description of a Source

5. funct:DestDescript(<RouterNum>,<DestNumber>) Returns the description of a Destination

6. funct:SourceRoutedTo(<RouterNum>,<DestNumber>) Returns the number of the source that is routed to a destination

7. funct:SourceNameRoutedTo(<RouterNum>,<DestNumber>) Returns the name of the source that is routed to a destination

8. funct:SourceDescriptRoutedTo(<RouterNum>,<DestNumber>) Returns the description of the source that is routed to a destination

9. funct:CurrentElementProfileID(<IPAddress>) Returns the ID Number of the currently loaded Element Profile

10. funct:CurrentElementProfileName(<IPAddress>) Returns the currently loaded Element Profile Name

11. funct:CurrentElementProfileState(<IPAddress>) Returns the state of the currently loaded Element Profile

12. funct:StartsWith(<DataString>,<StartsWithString>) Returns a String "True" or "False" as to whether the DataString starts with the StartsWithString (Case Insensitive)

13. funct:MemorySlotValue(<SlotNameOrNumber>) Returns the value in a specific memory slot

14. funct:Add(<NumberA>,<NumberB>) Adds two numbers and returns the result

15. funct:ProfileNameLoadedToFader(<ElementIP><FaderNum>) Returns the name of the source profile loaded to a physical fader (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

16. funct:ProfileIDLoadedToFader(<ElementIP><FaderNum>) Returns the ID Number of the Profiel loaded to a physical fader (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

17. funct:LWCHLoadedToFader(<ElementIP><FaderNum>) Returns the Livewire Channel Number loaded to a physical fader (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

18. funct:FaderLWCHLoadedTo(<ElementIP><LWCHNumber>) Returns the physical fader number that a Livewire Channel Number is loaded to (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

19. funct:LWCHLoadedToFaderDest(<Router><Dest>) Returns the Livewire Channel Number loaded to a fader by the fader’s Pathfinder Destination Number (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

20. funct:ProfileNameLoadedToFaderDest(<Router><Dest>) Returns the Source Profile Name loaded to a fader by the fader’s Pathfinder Destination Number (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

21. funct:ProfileIDLoadedToFaderDest(<Router><Dest>) Returns the Source Profile ID loaded to a fader by the fader’s Pathfinder Destination Number (requires element version 2.2.0.9 or later or PowerStation version 1.0.2g or later).

15. More functions will get added later as the need arises. It should be noted that the UI does not guarantee that a function is returning a valid value for the field the function is being used in. An invalid response will be ignored.

16. Fixed a display bug in the response of getlist userpanels.

17. Added hovering tooltips over fields in the stack event editing ui so the user knows whether text or a number are being written to the stack event XML from the field. This helps proper function use.

18. Warning: Significant changes were made to stack events to accomplish all of the goals above. If you run into any problems with your stack events in this beta, feel free to roll back to 4.28 and report so that we can fix ASAP.

Version 4.28 Beta (Server, Client, PanelDesigner, Mini) 8/17/2009

1. Rewrote much of the underpinnings of stack events so that they consume less memory and the properties pass through a function that analyzes for function calls. Function calls will be introduced in 4.29.

2. Added scripting support for PlayAudio and user log messages so that they can be called from a script,

3. Added support for PowerStation. This is the first version of PFS that fully supports Powerstation and ICEIO. The powerstation must be running software version 1.0.0d or later.

4. Fixed the gain range for controlling normal audio nodes, mic nodes, and ICEIO gains.

5. Fixed issues with PFS where new panels often required a restart of PFS before they would be available and start working.

6. Fixed an issue where deleting a memory slot was not causing a check of related stack events. Now it does.

7. PFS now monitors the PFSPanels folder for changes to panels and to the hardwaremap file and reloads files accordingly within a minute of their being changed.

8. Added two additional tabs to PFS – One for logs and one for panels.

9. The Panels tab now displays the panels that are on the server. The add and edit buttons will launch the panel designer and load the correct panel or a new one. The delete will delete a panel.

10. The log files tab now displays the list log files. Files may be viewed or deleted. Clicking view will open the log file in whatever application the machine is set up to open .txt files with.

11. The log file tab also now has an option for auto deletion of log files older than a certain date. If this option is turned on, deletion will take place nightly at approximately 12:12:00 AM.

12. Found and fixed an issue where LWCP commands which spanned multiple packets might not be parsed properly. For example long user profile lists. This has been fixed.

13. Fixed an issue where closing a meter or meter fader in one place would cause the meter or meter fader that was locked to the same IO to freeze. The meter was not unsubscribing and subscribing properly. This has been fixed in the server, client, and mini.

14. Added code to clean up meter subscriptions if the client is forcibly removed such as in a non-graceful shutdown of the client.

15. Placed a timer to space out the initial check of modified stack events after their loading to allow subscriptions for silence detection, etc. to spin up properly and subscribe with the device. This issue was previously causing silence detect events to execute on application startup before the actual initial subscription to those events took place with the node.

16. Added an addition line that can be added into the PFSMini configuration file at the end. Placing the line “AlwaysOnTop=True” without the quotes will make the mini panel always stay on top of other applications.

17. In Panel Designer – added the command line options for opening a specific panel file or a new panel. This is used by the server to launch the designer with a new panel or a specific selected file.

18. In Panel Designer - Fixed an issue where after saving a panel to a location other than the default location, Panel Designer would resort back to the default location on each FileIO operation. It will now remember the last save/open location until you shut down the application.

Version 4.27 Beta (Server 4.27 – Not released to public) 5/16/2009

1. Added SetMemorySlots and DeleteMemorySlots to SAProtocol (Alias sms and dms)

2. Added wildcards for Get,Set,and Delete Memory slots. Using a * at the end of the slot name will find all slots that start with the text before the *.

3. Added code to auto-delete memory slots if they are only being used by a stack event and that stack event gets deleted.

4. When in verbose mode in SAProtocol, gms can return the owner, last read object, and last write object.

Version 1.07 Beta (SAPortRouter 1.06) 6/17/2009

1. Added an option in the GPIO config when sending user commands to a GPIO driver via the GPIO port option. With this option, quotes will not be sent around the custom message. Prophet did not implement this with quotes, so this allows it to work better for Prophet.

Version 1.06 Beta (SAPortRouter 1.06) 6/17/2009

1. Fixed a bug in the GPIO port messaging via SAPortRouter where the port was not issuing the login command to the driver before attempting to send commands.

Version 4.26 Beta (Server 4.26, Client 4.26, Mini 4.26, PanelDesigner 4.26, GoogleVMIXWidget 1.0) 4/17/2009

1Since 4.25 was never publicly released – see the notes under 4.25 in addition to these notes to understand the changes since 4.24

2. Added the MeterFader control as described under 4.25 to Panel designer and Mini as well. This allows metering and a fader to control audio node level, VMIX level, or Element fader level. This control is now resizable as required by mini panel designing. The close float-in only appears when it is a standard meter in PFClient, and not in mini or designer. Right-clicking the panel will bring up program bus assignment buttons as well if the control is directed at an Element console fader. It is important to note that PF cannot always figure out the initial state of the Element fader on/off and program bus assignments. The commands to fix this are supposed to be included in the next Element release. Until then, after PFS is started it is possible you might have to switch the fader off once before these buttons will work properly in mini and client.

3. Fixed the output of some getlist commands when the request yielded no information to return.

4. Introduced a VMIX Control widget for the Google Automation system. This is a first beta release for the NAB show. Drop the zip file into the plug-ins folder on the Google automation system and then add the widget in Google. There is a text file in the resources folder that gets created that must be modified with the IP address of the Engine to control. After modifying this, restart the Google software to get the widget to control the correct engine. This only presents the first 5 VMIX channels at this point in time.

Version 4.25 Beta (Server 4.25, Client 4.25) 3/12/2009

1. Added a Gain Control Stack Action. This action allows you to pick a source or destination that supports gain control and change the gain as an action. It is intelligent enough to know whether the gain command should be directed at the node input or output gain, VMIX fader gain, or actual Element fader gain. This action also allows for turning channels on or off if the destination is a VMIX fader or Element fader. Of course turning these on and off is also possible through the Console Control and VMIX sections. For the Element fader, this option is slightly different from the console control action as it is tied to the actual fader as opposed to the livewire channel loaded to the fader. Internally the code dynamically changes the command sent to reflect the actual Livewire channel loaded on the fader. In the Console control section, the command is directed at a Livewire Channel number and so if that moves to a different fader the command is directed at the different fader. So it depends whether you want to control the physical fader no matter what is loaded to it or the Livewire channel no matter which fader it is loaded on. Warning! – PFS cannot currently detect the state of Program assignment and on/off buttons on the element on startup. They will not appear correctly until the user makes a change to them on the console. This will be fixed in the next Element beta code revision.

2. Added internal architecture so that engine objects know what Element is associated with them.

3. Added a latching option to user button qualifiers. Checking this option on will make the button event work in a latching fashion without any additional logic events. When this option is on, button down is no longer a qualifying property. Instead the State on or off is the property and PFS handles switching that state with each push.

4. Created a new meter in PFClient. This meter has new graphics and includes a fader for any IO that supports gain changing including node IOs, VMIX IOs, and Element Channel Destinations. The VMIX and Element faders, and On/Off Button is also present. For Element faders, right-clicking on the meter box will present a PGM assignment section. Dragging the fader with the left mouse button is for precise positioning. If you drag it with the right mouse button it will go to the nearest full db when letting go. Double-clicking will send it to 0.

5. Added a checkbox in the stack event main section that will allow delayed actions to be aborted if the qualifier state changes before the delay time is reached. This is useful when the customer wants the user to have to hold the button for a brief period of time before it will work.

Version 4.24 Beta (Server 4.24) 3/12/2009

1. Added a Device Failed qualifier to stack events.  This will allow users to run actions if PFS can no longer communicatye with a device.  This will trip if either LWCP or LWRP port fails for those devices that carry both,

2. Added a User Defined Log Message Action to Stack Events to generate user defined log messages.  The log message typeID must be 9000 or above

3. Added a checkbox to the email stack event action to include a Date/time stamp in the email

4. Replaced spaces in the remotedevice section of the log if present to make the log entries more easily parsed

5. Routers which use the Generic Setup Wizard were not closing the communication port and reconfiguring it after the router was edited (For example XI-Audio UDP, ZSys, Sigma)

6. Added logging to SARemoteGPIO By Port and By Pin object so that remote device state changes (online/offline) will get reported in the log

7. Attached RouterDeviceReceievedCommand RouteStat (2001) log messages to incoming XIUDP RouteStat commands

8. Attached RouterDeviceReceievedCommand SilenceThreshold (2002) log messages to incoming XIUDP StreamStat commands

9. Setup XIUDP Router StreamStat to act like silence threshold enabling this trigger to work in silence detect stack events and standard events

10. Added a log item for XIUDP Router Source stream active/inactive monitoring

11. Modified the remote device field of log messages coming from XIUDP routers so that it reported port 91 rather than 93

Version 4.23 Beta (Server 4.23, SA_PortRouter 1.05) 2/24/2009

1. Fixed a bug in the server where sending an ActivateRoute command through SAProtocolTranslator to a virtual router where the source was 0 would not clear the route, but rather would return an error. This command will now clear the route when addressing a virtual router.

2. Fixed a bug in the server where silence detect stack events would not get tripped and cleared when the node the event was addressing failed or became unresponsive. This condition will now trip the audio based stack event. It should be mentioned that it may take PathfinderServer as long as 30 seconds to a minute to detect and confirm a node failure. Then the silence wait time in the stack event will be added to that before the event will be tripped. In the future we hope to have a device failure qualifier that can be used independent of silence detect. Finally, it is possible that PFS would trip the silence alarm if the unit becomes unresponsive to commands from Pathfinder but is still passing audio. If PFS cannot talk to the node, it assumes it has failed and sets the audio to nothing.

3. Fixed an issue in the server installer that would cause the installer to get re-launched if certain non-critical text files were deleted from the server folders.

4. Fixed an issue in SA_PortRouter where if a source was routed to two destinations and the first destination TCP connection was not established, incoming commands would only get sent to the second connection intermittently.

Version 1.02 (SA_AudioPlay 1.02) 1/24/2009

1. Added a User Interface to the SA_AudioPlay service. The installer now also installs a user interface that can be used to start and stop the service and set parameters such as Username, Password, Default Audio folder, and TextToSpeech Voice. The service needs to be restarted after making changes to the configuration.

2. If you pass the service the name of a file without the full path, the service will try to find the file in the folder configured as the default audio folder by the configuration application.

3. If you pass the texttospeech a field with the prefix File:\\ (i.e. FILE:\\C:\Junk\text.txt), the service will try to open the text file and read the contents instead oif reading literally what is sent.

4. Known bugs in both 1.00 and 1.02

1. The service will currently only play on the first sound card on the computer which may or may not be the default one. We are working on a fix for this.

2. There may be an issue with PathfinderServer reestablishing a connection with the service after the service has been restarted. Restarting PathfinderServer fixes this. This has not been confirmed yet.

Version 4.22 Beta (Server 4.22, Client 4.22, PanelDesigner 4.22, SA_AudioPlay 1.00) 1/15/2009

1. Added port 9500 to the server. This is a dedicated port running the SAProtocol translation. It will always exist for remote systems to control and work with Pathfinder Server.

2. Added a Verbose command to the SA Protocol Translator. This adds additional stream and channel information into the getlist routestats command and may be used in the future to indicate the need for slightly more verbose responses to some commands. Turn the mode on and off with verbose on and verbose off.

3. Created 2 new router types (PathfinderRemoteGPIOByPort and PathfinderRemoteGPIOByPin). These routers will route GPIO closures through Pathfinder between sites by pointing one Pathfinder server at another server. Because it is TCP only, it will work over the Internet or WANs. The ByPin version can also be used to create a Pin based GPIO router rather than a port based GPIO router. This can be created between servers, or on the local server using the loopback address. These routers will also allow GPO to GPO and GPI to GPI (where the device supports GPI changes from software) routing.

4. Added a PUID table to the databases used by the two new routers mentioned above to make sure between creation and deletions, points obtain the same ID in the database. Eventually livewire points will also be added to this database so that in the future an ID is assigned at initial discovery and it will never change unless this table is wiped. Thus routers will be able to be destroyed and recreated and still always gain the same ID. This is only implemented for the remote GPIO routers at this point in time. But in a future edition will probably implemented for others as well.

5. Added support for the XIAudioUDP Router developed by Streamcom. Streamcom has developed a router that routes the UDP data from IPorts allowing a multsite audio router to be created. Pathfinder can now control this router just like any other router it supports.

6. Fixed a bug where if a time based stack event was edited from the raw file rather than the PFS UI, it would get picked up but the times would not get entered into the current day’s todo table and so they would never run.

7. Added the IPort as a device that support VMIX into PFS.

8. Fixed a bug that was causing the VMIX state to not get initialized properly so stack events might require the VMIX to get turned off and on again before they would register properly.

9. Added more detailed messaging to the getlist sourceaddress and destinationaddress commands in the SA Protocol Translator.

10. Increased performance significantly on stack event file loading.

11. Added code that would only check for and load newly created stack events (created manually by editing the file or by the UI) if there was at least 7 seconds before the next time based event. Some of the file IO can be intensive when loading a bunch of newly created events so we wanted to make sure existing time based events were not blocked. If there is not enough time the load is delayed slightly until there is time.

12. Added a field in the events tab of the server that displays the current time and date.

13. Added a field in the stack event tab so you can see how many stack events are in the list.

14. Added a GetMemorySlot command to the Software Authority translator. This allows you to view all of the memory slots, all used memory slots, or specific memory slots by name or by value. Type ? GetMemorySlot for details. There is also an alias for this command gms so you do not have to type the full GetMemorySlot.

15. Added a text file which if it exists will allow you to enter names of stack event files with a wildcard (*) at the beginning or end. If these stack event file names exist, they will not get synchronized across a cluster. The filename is StackClusterSkip.txt.

16. Added a menu item which will allow you to select memory slots to get stored to a table so that they do not get cleared between restarts. If this option is on, memory slots will retain their values between restarts. If it is off they will get cleared on restart.

17. Reloading stack events will not update a changed stack event in memory if it’s delayed timer is currently running. It will wait for the dely timer to end before loading the modifications for that event into memory. In that case the update will get loaded at the next normal refresh within 60 seconds.

18. Worked on the GPIO panel in the client. It now shows both GPI and GPO of both the source and destination involved in the route. This is much more intuitive. It also shows the route direction using a line. This line becomes important in the PFSRemoteByGPIOPort and ByPin routers as these routers can route GPI to GPI and GPO to GPO and GPO to GPI as well as GPI to GPO as long as the when the GPI is a destination the device supports it (Axia driver).

19. The SourceList call in SA Protocol Translator was reporting erroneous information in the last column when addressing GPIO routers. This has been fixed.

20. Certain internal collections for fast stack event searching were not getting cleared when events were being modified. This has been fixed.

21. Fixed a bug with the Broadcast Tools 16x4 protocol translator which caused routes on the 4^th destination not to work

22. Fixed a bug with the Broadcast tools protocol translator which would cause it to address the wrong virtual router in certain extremely rare situations.

23. Added support for the LCD 17 button panel into PFS.

24. Added support for the LCD 17 button panel into the Panel Designer UI

25. Fixed a bug that would not allow a stack event to function properly if multiple audio (silence detect/present) qualifiers existed in the same event. This is fixed in this version.

26. Fixed a bug where in certain extremely rare situations the clearrecordset would not work when updating a virtual router database leaving the database with a blank table in the sources or destinations.

27. Added the support for the GET SUPV STATE command supported by more recent beta versions of the Engine to check LWCP state.

28. Added a new stack event group in both qualifiers and Actions called Console Control. This supports tripping and sensing changes to On/Off/Mute/PGM 1 through 4 assignments. It also supports setting a fader level. It will not sense the initial state on startup so the state has to change for PFS to pick it up. This is due to current command restrictions in the Element. Also some of these functions are only supported in Beta and Alpha versions of Element code and so will not be fully available to the public yet.

29. Created a new service called SA_AudioPlay. This service can be deployed to computers on the network including the server and presents a TCP port (11051) to which you can send the following tcp commands. Login Admin Admin, playaudio <filename>, texttospeech <text>. It will allow files accessable by that computer to be called and text to speech commands to be called, and they will play on the default sound card. This installs on the computer as a service. Once installed either reboot or go into the service manager and start the service. At this point in time the service will only play wave files. The service requires the .net 3.0 platform which can be obtained from the Microsoft updates page if it is not already installed.

30. Added a stack event group of actions to trigger the SA_AudioPlay services on local or remote computers. In this way PFS can trigger basic text to speech and/or audio playback.

31. Added and implemented the following log objects ServerEvent_RefreshStackList, ServerEvents_StackEventLoadEvent, ServerEvents_EventRemoveEvent. These are not turned on by default. They must be turned on. But then stack event removals due to file deletion, changes due to stack event modifications, and initializations after modfiying, creating through UI, or discovery may be logged.

32. Added log events to track the SA_AudioPlay functions and responses from the remote computer so that they can be logged. These are turned on by default if logging is enabled.

33. Fixed a bug where very old versions of engines when upgraded would sometimes not get the right database entry updated for backfeed sources. And if automatic SRC/DST additions were turned on could actually lead to a duplicate entry getting created for the backfeed.

34. Fixed a bug in Panel Designer that would cause the selection of destination on meter controls to get written as source and not stick as destination.

Version 4.21 Release CandidateV2 (Server 4.21, Client 4.21, PFMini 4.21, PanelDesigner 4.21, VMIXControl 1-05)

1. Added new Help File to Client and Server installation packages.

2. BG_111 - Fixed a bug since 4.20 in Server where new protocol translators would not work or appear until PFS was restarted

3. BG_112 – Fixed a bug in the Server where new Element profiles would not be available to the server until the server disconnected and reconnected to the Element or was restarted.

4. In SAProtocol in the Pathfinder Server, modified the TriggerGPO and TriggerGPI commands so that they sould return a state command if no change was made. In other words if the command asks for the same state that already exists, previously PFS would return nothing since nothing actually changed. Now in this case it will return the current state.

5. Removed erroneous character from getlistversion command in SAProtocol.

6. Removed erroneous character from Error message if a route change is requested that is locked is SAProtocol.

7. In VMIXControl, fixed a bug that in certain reconfiguring circumstances could cause all faders to disappear when they are not supposed to,

8. In VMIXControl, made the Engine line at the top of the tree display the host name of the engine when possible.

Version 1.04 Release Candidate V1 (SA PortRouter 1.04)

1. First Release Candidate of the SAPortRouter serial data routing service application. This application runs as a service on the computer. There is a configuration application that allows the user to drag Serial, TCPClient, and TCPServer ports to the service and configure their settings. Then after committing the changes and starting the service, you can route the data traffic from any port to any port and vice versa.

2. At the moment this only supports ASCII data (characters below 128) as opposed to binary. A future version will also support binary.

3. Routing can also be controlled dynamically by Pathfinder.

4. Each port can have a defined End of Message set of characters as well which means the commands will only get forwarded when complete. To use non-typable characters for EOM, use a % and a 2 digit hex code for the ascii number. For example, a carriage return and lines feed end of message would be represented as %0D%0A.

5. This application and routing support for it requires a PathfinderPro or Legacy license.

Version 4.20 Release CandidateV1 (Server 4.20, Client 4.20, PFMini 4.20, PanelDesigner 4.20, VMIXControl 1-04)

1. Introduced the new licensing model for Pathfinder Legacy, PathfinderPC, and PathfinderPro. See Feature Comparison list and license FAQ for details.

2. Added Licensing menu item to the File menu of PathfinderPC Server.

3. Created Licensing web site to create and upgrade licenses. Legacy customers (purchased before July 1, 2008) are entitled to a free upgrade to PathfinderPro. See Feature Comparison list and license FAQ for details.

4. Added support for VMIX Control to PathfinderPC Server

5. Added a GPIO status command to Software Authority protocol.

6. Added router address and name commands to the GetList Functions.

7. Introduced VMIXControl application. This application requires a legacy or PathfinderPro licensed copy of Pathfinder. It can be installed on as many machines in this environment as desired. It must have TCP access to both the PathfinderPC server and an Axia engine. It controls the virtual mixer in the Axia Engine. This application requires PathfinderPC Server 4.20 or later.

8. Introduced Metering and web browser support to Panels. This feature is only available to legacy and pro licenses.

Version 4.19 Beta (Server 4.19) 5/22/2008

1. BG – If the Mail Server settings were set with a blank user name and password for anonymous emailing, setting an email address in a standard silence detect event would generate a warning message. Should be fixed in this version.

2. Add the new version of the Panel Designer (Version 1.20) to this installer package. See the notes below for the new features in this version of the Panel Designer.

Version 1.20 Panel Designer Only Beta (Panel Designer 1.20) 5/22/2008

1. You can now select multiple controls on the panel to manipulate together by holding the shift or control key and selecting the additional controls.

2. Selected controls will have a handle around them. Resize by dragging on the handles. If multiple controls are selected, they will resize together. Holding the Right mouse button and dragging on the handles with will allow you to move (as opposed to resize) selected controls.

3. When controls are selected, the arrow keys can be used to resize one pixel at a time.

4. If you hold the shift key while tapping the arrow keys, you can move the selected controls one pixel at a time.

5. Added AlignRight, AlignLeft, AlignTop, and AlignBottom menu items. There are also shortcut keys for these menu items. These will automatically align the selected controls to the selected edge. For example, selecting Align Left will look through the selected controls for the control that is farthest to the left. It will then align the rest of the selected controls to that same left point.

6. Added Spread Horizontally and Spread Vertically menu items. There are also shortcut keys for these menu items. These will find the left most and right most (or top most and bottom most) selected controls and evenly spread the other selected controls between them. If the spread would cause the controls to overlao or the controls are overlapping, spread will place them right next to each other instead of overlapping them.

7. If multiple controls are selected, changing properties that apply to all controls will be applied to all controls. So you can select a bunch of buttons and then apply the same color/picture settings, etc. to them. This also works for left, top, height, and width settings.

8. If multiple controls are selected and the property being changed is one that should not be duplicate (for example name), the system will ask if the user wants to auto-increment the property. This applies to properties such as Name, Caption, and hardware map Button/Circuit number. For example a user could select 10 buttons and then set the Hardware map IP address and module number with one property change. And then set the first button number property, and the system will ask if the user wants to auto-increment the rest.

9. If you change the panel name and the panel caption was the same as the old panel name, it will change to the new name too.

10. Fixed issues with Copy, Paste, and Delete functions.

11. You can now copy, paste, and delete multiple controls if they are all selected.

12. Fixed several other minor issues with Panel Designer.

Version 4.18 Beta (Server 4.18) 5/16/2008

1. BG_108 – Some users needed to send emails through a mail server that did not require user authentication. We modified the code so that if the username and password fields in the mail configuration are blank, PFS would not send the authentication commands. This did not work as expected in 4.17. Should be fixed in this version.

Version 4.17 Beta (Server 4.17) 5/16/2008

1. BG_106/105/102 – You could not enter a recurring daily stack event time based qualifier where the start day was different than the end day crossing midnight. For example - starting Mon at 11:00PM and ending Tues at 1:00 AM. The system would not let you set this up and would reset the end time to a second past the start time. In addition direct XML editing would also not allow this kind of event to run as the logic was not in place for this. This version has logic written to handle this condition and the restrictions lifted to allow this qualifier.

2. BG_104 – Some users wanted to be able to send emails to non-standard SMTP port. This version adds a field to define the server SMTP port. This ability has not been tested with a mail server set to this state yet.

3. BG_108 – Some users needed to send emails through a mail server that did not require user authentication. We modified the code so that if the username and password fields in the mail configuration are blank, PFS would not send the authentication commands. This has not been officially tested with a mail server set to this state yet.

Version 4.16 Beta (Server 4.16) 4/2/2008

1. BG_93 – Entering a start time for the afternoon of one day, and an end time for the afternoon of the next day would not work in stack events. The event system was designed to make sure that the end time is later than the start time, and was not taking the day into account as part of this. This has been fixed.

2. BG_94 – CRITICAL – Beginning with version 4.05, backfeeds are handled differently in the database. Because of this change some customers found that if there were 2 backfeed sources that had been loaded to the same fader, and then the router was edited, in certain situations, not all of the later engine sources and destinations would get brought back into the database after the edit. This has been fixed.

3. BG_95 – If locks states somehow got out of sync between a base router and a virtual router, the state would not get discovered until a lock was changed. This version adds the lock state into the regular check functions.

4. BG_96 – Locks were not always traversing properly from the base router to a virtual router unless the PF number of the base point and virtual point were the same. This has been fixed.

5. BG_97 – If a firmware update on an Axia device removed a system level lock state from a resource, PFS would not pick this change up and unlock the resource without a restart. This has been fixed.

6. BG_98/99 – The Auto SRC/DST addition function was not checking previous tables for pre-existing ID numbers before assigning a new number. This has been fixed.

7. BG_100 – Backfeeds using RTPA address as opposed to LWSA addresses were not always being detected by Auto SRC/DST additions or by the updating functions. This has been fixed

8. FQ_32 – This version detects the version of Engine software on the Engine, and only opens LWCP (VMIX) control connections if the Engine software is late enough to support it. It also will only list Engines with late enough software in the VMIX drop down combos.

Version 4.15 Beta (Server 4.15, Client 4.15, PanelDesigner 1.19, Mini 1.19) 3/20/2008

1. BG_88 - If server is set to require login, and you need to manually point client to a new IP, login would crash client. Then on restart it would work. This has been fixed. May still need some tweaking.

2. BG_87 - Captions for the main panel object entered in Panel Designer do not get written to XML. This has been fixed.

3. BG_87 - Captions for panels entered in Panel Designer do display in panels in client or Mini. This has been fixed.

4. BG_87 - Friendly Captions for panels entered in Panel Designer do display in panels in client in Panel List. The File name is shown instead. This has been fixed.

5. FQ_29 - Engine based VMIX control is now supported by both stack events and ACU-1 translator. All UI combo boxes that relate to VMIX now also display Engines as possible VMIX control objects. This also means that PFS will try to maintain a 4010 LWCP connection to all engines. This may lead to extra connection attempts and log activity when in a facility with older engine code. We will work on a modification in the next version to prevent these connection attempts if the Engine software is older than the new release version - 2.4.8w3.

6. BG_89 - During Livewire Scan in initial router setup, IP addresses are found and added to the list multiple times. This means the actual connect attempts in the next phase of the scan also happen multiple times causing a significant delay in the time it takes to complete the scan. Fixed

7. BG_90 - Forced any text commands being sent to DISP object on hardware user panel to be sent in the ON context.

8. BG_92 - Occasionally a scene change would be left showing all or most routes routed to a single source in the client. Closing and reopening the router in the client fixed the display problem. This has been fixed.

9. FQ_31 – Full cluster replication support now exists for the additional data file required by BT Protocol Translators.

10. BG_83 – The Top field in Panel Designer is read only. This has been fixed where necessary.

Version 4.14 Beta (Server 4.14) 2/28/2008

1. FQ_27 – Server – Added support in Stack Events to turn Element Faders On/Off. In the User Button Section of Stack Action, Select the Use Button Address option and enter the Element IP Address. For Module Number scroll to LWChannel. Enter the LWChannel Numer, and then select whether the On Button or Off Button will be triggered, though in reality either can be used and the actual channel on/off is then tripped by the State property. Use the State property for either On or Off.

Version 4.13 Beta (Server 4.13) 2/9/2008

2. BG_85 – Server – Compiled with the original TCP Base but with a fix for BG_75 instead of the new TCP base introduced in 4.12. The New base introduced in 4.12 has a bug where if there are more than 5 clients (PFClient or Mini) trying to connect at the same time as would happen during a cluster roll or when the server is starting and there are already a bunch of clients running that are trying to connect, the new TCP stack was not letting the clients join. Thus we fixed the BG_75 issue in the original TCP base as well, and rolled back to that TCP base until we could spend some more time on the new TCP base.

3. FQ_18 – Server – Introduced a protocol translator to translate BTools protocol. Will translate audio switching, GPI/PIP, GPO/Relay. No mixing or cross-fading is supported at this point in time.

Version 4.12 Beta (Server 4.12, Client 4.12) 1/20/2008

1. BG_75 – Server - If a client application was shut down or disconnected unexpectedly and the server connection had a large amount of data in buffer to be sent to the client, it could cause the server to crash with a Dr. Watson error. This has been fixed.

2. ***Important*** - This version also uses a new TCP base for communications between clients and server which provides for more efficient communications.

3. BG_76 – Server - If two Virtual routers shared the same base point and a lock was issued from one virtual router, the lock would not engage on the virtual point on the other virtual router. This has been fixed.

4. BG_77 – Server - A stack event with an Element profile load qualifier that was set to run actions on startup, would sometimes not execute when the server was not part of a cluster. This is because the stack event engine would launch before PFS has a chance to connect to the element and get the current profile. The first run of this kind of action on startup now gets delayed until a connection is established with the Element and the profile check successfully responds.

5. BG_78 – Client - The viewable audio state bubbles might not display after loading a very large router (5000x5000). This occurs if the scroll timer executes prior to the completion of loading all sources and destination information into the grid. This has been fixed.

6. BG_79 – Server – When editing Time based standard events from the client, the edit window would not appear if there were no events in the existing server. This has been fixed.

7. BG_80 – Standard Silence Detection/Backup route events were not displaying their state on clients that were connected to the backup server in a cluster. This has been fixed.

8. BG_81 – The state of Time based standard events was not being sent from the Primary machine in a cluster which owns the event system to the backup. Therefore this state would not display properly on clients connected to the backup server.

9. FQ_22 – Added log settings for script (not stack event) timers so that all changes in script based timers could be logged if desired.

10. FQ_23 – Added a text file which if it exists holds lines of text. If the text file exists, each line in the file is brought into an array. Before any line is written to the log file, the array will be checked to see if any of the lines of text exists in the log entry. If it does, the log entry is skipped and not written to the log. The text file to enter this information is called LogSkip.txt. This allows you to prevent certain log entries from appearing.

Version 4.11 Beta (Server 4.11) 12/18/2007

1. BG_76 – The flash state on user buttons would not always work properly or traverse a cluster properly. This has been fixed.

Version 4.10 Beta (Server 4.10) 11/15/2007

1. BG_73 – Duplicate event names in a stack event group cause the stack event not to load or run. This is only since 4.06 due to the optimization. Duplicate names are supposed to be disallowed by the UI, but if an older event has them, this version will alter the duplicate name when it loads to allow the event to load and run.

2. BG_74 – Any time based stack events beyond the first one would not load or run. This is only since 4.06 due to the optimization changes. This has been fixed in this version.

Version 4.09 Beta (Server 4.09) 11/13/2007

1. BG_72 – Panels that used RouteMaps where the maps where the names of the router, source, and destination instead of the numbers would cause the server to repeatedly launch a database finder box. This is the only fix since 4.08 in this version.

Version 4.08 Beta (Client 4.08, Server 4.08) 11/11/2007

1. Since 4.05, 4.06 and 4.07 were not general releases, please review release notes for those versions as well to get full scope of changes in this beta release)

2. BG_31 – When large routers are opened in the client, the client appears to hang. This has been fixed and a count bar added in the lower left corner of the client to display the load count as IOs are loaded into the grid.

3. BG_32/65/66 – Lock States were not synchronizing properly between cluster nodes. This has been fixed in this version.

4. BG_50 – The Use Lock State checkbox in a route status qualifier gets stuck on. If you turn it off, it is back on when you try to edit the qualifier again. This has been fixed in this version.

5. BG_51 – The Use Lock State checkbox in a route status qualifier did not work. With this check on, the lock did not affect the qualifier. This has been fixed in this version.

6. BG_52 – Protocol Translator message qualifier does not work. This is only an issue with 4.06 and later due to the optimization. It has been fixed in this version.

7. BG_53 – VMIX qualifier does not work. This is only an issue with 4.06 and later due to optimization. It has been fixed in this version.

8. BG_54 – Button name field at the bottom of a button qualifier was hidden as it is not viable as an option. The button name is already at the top of the qualifier as the primary object. Also the Caption field was not working as a potential part of the qualifier. This has been fixed.

9. BG_55 – The Force Lock checkbox in the ActivateRoute Stack Event action does not work. This has been fixed in this version.

10. BG_56 – In the UserButton Stack Event Action, if an IP based button is selected, the default button number was a single digit rather than an option from the drop down menu. This has been fixed in this version.

11. BG_58 – In the client, after adding a new virtual router, the router drop down combo would turn blank. After that no routes in an open chart view can be made until the router is reselected in the drop down. This has been fixed in this version.

12. BG_59 – The Lock Override checkbox in a Scene Change Stack Event Action would not save or work when the action was executed. This has been fixed in this version.

13. BG_60 – In the UserButton Stack Event Action, KeyState has no meaning as this is a qualifier function not an Action function. This has been hidden in actions.

14. BG_61 – Forecolor option in Stack Event Unser Button action and qualifier has been disabled as it is for future use and is non-functional at this point in time.

15. BG_64 – In a VMIX Stack Event Action, Setting a gain of 3 resulted in .3 rather than 3.0. 3.0 worked properly. This has been fixed in this version.

16. BG_67 – In a cluster, if you create a new virtual router on one server a PFClient connected to the other server would not see the new router until that client is restarted. This has been fixed in this version.

17. BG_68 – If the Probel Router translator is pointed at a virtual router, and routes on that router are in the Other State for sources routed that are not a part of the virtual router, the translator would report back garbled data. This has been fixed in this version. It now reports back 0 which equates to a cleared route state.

18. BG_69 – Prophet ACU-1 Translator was setting the timeout for silence alarms in milliseconds when the UI says seconds. This has been fixed so that the seconds variable from the UI gets multiplied by 1000 to create the correct alarm time.

19. BG_70 - Mismatched states between router tables during cluster synchronization could sometimes lead to empty or deleted router tables. This could be exhibited by deleting a router from a single server. And then shutting that server down and launching the other server and making lock changes on the still present router on that server causing a timestamp update of the routes table on that server. Then when the first server is brought back up corruption in the synchronization could occur. This has been fixed in this version.

20. BG_71 – Protocol translator additions and removals were not synchronizing across the cluster without several restarts. This has been fixed in this version.

Version 4.07 Beta (Client 4.07, Server 4.07) 10/31/2007 (not released to general public)

1. BG_42/45/47 - Editing an existing standard event in PF Client sometimes returned an error. This has been fixed.

2. BG_48 – Could not edit Virtual routers and scenes in the PF Client. This only existed in version 4.06 due to the optimization. It has been fixed in this version.

3. BG_49 – Time based stack events would not run. This only existed in version 4.06 due to the optimization. It has been fixed in this version.

4.

Version 4.06 Beta (Client 4.06, Server 4.06) 10/28/2007 (not released to general public)

1. A great deal of code optimization work has been done primarily to the server application but also to a limited degree the client application in this version. This optimization is designed to increase performance and decrease processor load on large routers. Because of the amount of code changes involved in this work this version is undergoing rigorous bug testing.

2. BG_8 – Rare crashes of PFS server with specific clients due to hung winsock connections with the PFclient and/or probel protocol load issues have been addressed.

3. BG_44 – Prophet router computer caused sluggish routing responses when the Probel protocol was in use. This was because certain embedded messages were causing NAKS (invalid message responses) which led to cueing and repetition of messages in both directions. This has been fixed.

4.

Version 4.05 Beta (Client 4.05, Server 4.05) 9/24/2007 (not released to general public)

1. BG_6 – When a route is requested using the Probel General Switcher protocol (for example from a Prophet Router computer), and the route change that is being requested already exists, PFS does not return a confirmation because no change has been made. In the case of the Prophet Router computer, it waits for a response for a period of time, so this could cause a delay in subsequent commands. This has been fixed so that PathfinderPC Server does respond even if the route already exists.

2. BG_12 – Leaving the Axia Automatic SRC/DST additions feature turned on can lead to duplicate additions in the database. If this feature is left on, a new source or destination can get added multiple times until the server application is rebooted. This has been fixed.

3. BG_27 - In a cluster if a PathfinderPC Client connects to the second server in a cluster before synchronization is complete, and that client has certain kinds of user panels open, they will not refresh with the initial state after synchronization completes. In this version a status is pushed after synchronization, but more importantly clients are not allowed to connect during the cluster synchronization process. Existing clients will not get dropped during synchronization though.

4. BG_28 – In a cluster if there is an orphan router database file on the second server, and a new router gets added on the primary server that uses the same number as the orphan file on second server, the router will not get created on the second server and may get deleted from the primary server during subsequent synchronizations. This has been fixed.

5. BG_29 – If a virtual route source and destination includes multiple points from the same base router, only 1 route will actually complete. This has been fixed.

6. BG_32 – In a cluster, locks made from a client connected to one server do not transfer to the other server. This has been fixed.

7. BG_33 – The Lock, UseLock, and Lock Overrides checkboxes in the RouteStatus stack event qualifier and action were not sticking between edits. Actually these were being written to the stack event file and acted upon, but on the next edit, these settings were not being brought into the edit window and would therefore revert if the user did not catch it. This has been fixed.

8. BG_34 – Cluster synchronization when large routers (greater than 5000x50000) were involved and changes were made that required a rewrite of the database on one of the synchronized servers could cause the process to appear to hang for an extended period of time with CPU loads on at least 1 of the servers at or approaching 100%. This has been addressed and the synchronization speed greatly improved in this version.

9. BG_35 – Element backfeeds may not maintain a unique source ID number in previous versions of PathfinderPC Server. The backfeed source number in PathfinderPC Server was bound to the fader number sourcing the backfeed rather than to the stream address itself. This has been fixed so that the backfeed stream address will always relate to the same PathfinderPC source address, and the information about the console and fader hosting it will change instead as it moves between consoles.

10. BG_36&37 - Cluster synchronization when large routers (greater than 5000x50000) were involved and changes were made that required a rewrite of the database on one of the synchronized servers could cause route points from the routes table to get lost and not entered into the synchronized database. This has been fixed.

11. BG_39 – The Axia Automatic SRC/DST additions feature was not sending the additions across the cluster link to the second server or updating the timestamp for the table. This has been fixed.

12. BG_40 – In the PathfinderPC Client the Number column was too small to accommodate numbers greater than 999. Numbers larger than this expanded beyond the width of the field. This has been fixed in this version.

Version 4.03 Beta (Client 4.03, Server 4.03) 8/6/2007

1. This Version includes everything from 4.02 plus the changes listed below.

2. BG_25 – If a client or mini connects to the secondary server in a cluster while the secondary server is undergoing synchronization, and that client has a user panel open, the initial state may not display properly until the control state changes or the panel is closed and re-opened. This has been fixed.

3. Added a heartbeat in the software user panels that occasionally pings the server to which it is connected to make sure the server knows it needs to be included in updates.

Version 4.02 Beta (Client 4.02, Server 4.02) 8/5/2007

1. BG_1_22 – Even when the “Run Actions on Startup” option is selected in a silence detect based stack event, it’s actions would not run after the server initially starts until the threshold is crossed. This has been fixed. This can be seen easiest using a user panel with buttons that light different colors for silence detection and audio present. With the “Run Actions on Startup” option selected, such panels will now display the correct state as soon as the server event system comes online.

2. BG_2 – Sometimes silence detect events could possibly get stuck in a state. This could happen if the meter response came back different and later than the silence detection response. Silence detect events are now completely independent of meter responses except for the initial state check after an event has been launched. This bug is also thought to have been reported more in relation to BG_7 and 15 below.

3. BG_3 – In Chart view in the client, selecting the last destination in the list would not drop the destination into the Take panel. This can lead to the user activating a route based on the last selected destination instead. This has been fixed in this version.

4. BG_7_15 – Stack events in a cluster that had a space in the name of the event did not always synchronize properly and were subject to spontaneous deletion from 1 or both of the servers in a cluster during cluster synchronization. In some places in the application spaces were converted to underscores, and in others they were left alone causing confusion in the clustering synchronization process. This has been fixed.

5. BG_9_10 – In the client, the window location storage buttons at the button of the screen were subject to an endless loop in certain configurations when the configuration was loaded. This has been fixed. In addition, the buttons were not saving whether the router panel was in list view or chart view. This has also been fixed.

6. BG_11 – If you delete a scene from a router on a server in a cluster, it tends to reappear after synchronization routines take place. There was a bug in the code that caused the scene not to get deleted on the second server, and so at synchronization time, the scene would get recreated. This has been fixed.

7. BG_13 – In the client, the connect menu to manually make the client connect to a different server would always error out. This has been fixed.

8. BG_17 – List orders on the server page sometimes displayed in a bizarre order. This has been fixed so that routers and Protocol Translators are always displayed in numerical order by ID, and stack events are displayed alphabetically.

9. BG_19 – The state of some software user panels (such as silence detect based user panels) would not update properly without being closed and re-opened after the panel had been rolled to another server either through manually connecting to a different server or from cluster server failure causing a rollover of the client. This has been fixed.

10. BG_20_23 – In the client in chart view, scrolling would not cause the blue lines to scroll as well. This resulted in the take panel being out of sync with the representative blue lines. This has been fixed.

11. BG_21 – Sometimes switching between routers in the client did not cause the correct scene list to be listed in the main scenes menu. This has been fixed.

12. BG_24 – After the client switched to a different server either because of manual server connection or cluster failover, if a router panel was active it would not be active properly unless it were closed and re-opened or the user switched to a different router panel and switched back. This would mean the user could not make routing changes on the panel until it was closed and re-opened or a different panel was selected first. This has been fixed.

13. FQ_1 – Limited the maximum size the routing dots can become in small router windows. This prevents the dots from becoming huge.

14. FQ_11 – Added the GetList function to the Software Authority Protocol Translator. This function accepts arguments and returns a variety of lists of information in the Pathfinder Server system. It has been developed for use in the new stack event editor that is still under development, but it can also be used by third party applications to obtain information from the routing system. See the document FR_11_GetListFunction.doc for more details.

15. Also, please review the white paper on the importance of time synchronization between servers in a cluster – Bug_14_ClusteringTimeSynchronizationIssues.doc.

Full Release Version 4.00       (Client 4.00, Server 4.00a, Mini 1.15a, PanelDesigner 1.16)    6/15/2007

1. Moved this to Full Release

Release Candidate Version 4.00       (Server 4.00a, Mini 1.15a, PanelDesigner 1.16)    6/13/2007

1. Panel Designer Insert menus were not working properly. This has been fixed

2. Updated the Server installer to include the 1.16 version of Panel Designer. No changes were made to the server executable itself.

3. Updated the PaathfinderPC Mini installer so that the uninstaller will not remove the configuration file. Uninstall of existing version will remove this file, but after installing this version future uninstalls will not remove this file so that it retains these settings from install to install.

Release Candidate Version 4.00       (Client 4.0, Server 4.0, Mini 1.15, PanelDesigner 1.15)    5/28/2007

1. After saving changes to a software panel, closing and reopening the panel in the client or mini should now display the changes without restarting the server. This is subject to altered state. If the current state of the control is the same as what the old control state was, then it will be updated. If a stack event has changed the property, then it is assumed the property should not be updated. Essentially when the panel is opened, the initial state is saved as a defualt. When the panel is then edited and reopened, if the current state before opening is the same as the defualt, then the control gets the new state from the newly updated panel. If it is not, then it does not inherit the new state since the control state has been altered to show something and it should continue to show that condition.

2. Fixed a bug in the panel designer that caused the wrong color to show when certain hexadecimal color numbers were used. If the number could also be interpreted as a decimal number, it would do so rather than using the hex version. This has been fixed

3. Fixed GPIO circuit naming to make it more intuitive.

4. When Selecting a GPI or GPO qualifier in a new stack event, only the source or destination drop down appears depending on whether it is a GPI or GPO. This makes this screen more intuitive.

5. Added warning messages in the GPIO stack event configuration for non-standard configurations.

6. Pathfinder PC was not restoring panel window positions when saving window positions in the window state store locations. This has been fixed.

7. Stack Event route changes were not able to use None in virtual routers to force a clear route. This has been fixed.

8. Using the Event Engine Start as a qualifier to initialize IP based button actions was not working. This has been fixed. Part of this also was that if you restarted the Element or lost and reestablished the conection to it, PFS would not push out the current button states. The LWCPCommand SendData module now Caches buttons states, and will push them out on reconnect. This will make buttons display properly after Element restart or loss of connection. It also answers the problem above since even though the Stack Event Engine in a stand-alone server starts before LWCP connection is established, the button state commands that cannot be sent to the unestablished connection get put in the button state cache and then sent when the connection does come up.

9. Fixed Tab Order in all screens in all 4 applications.

10. If the server and client have their date status set to New Zealand rather than English, standard events that are on a weekday schedule may not work. This has been fixed. However at this point in time, both client and server must be set the same. This was because the New Zealand calendar week begins on Monday rather than Sunday.

11. In Panel Designer you cannot set the GPIO hardware maps. This has been fixed.

12. If you add a new standard time based event, events for the same day that have already executed would get their status cleared. This has been fixed.

PathFinderPC Release Notes – Version 3.0

Version 3.68a       (Server Only)    5/22/2007

1. This is the same as the previous 3.68 server software except an issue with the installer and windows 2000 machines relating to the iphlpapi.dll file has been addressed.

Version 3.69       (Client and Mini Version 1.12)    5/11/2007

1. Script based panels would not work correctly if they were connected to the second server in a cluster (the server that does not own the event system). This has been fixed.

2. Editing existing time based events in the client produced a record not found error. This has been fixed

Version 3.68       (Server and Client)    5/4/2007

1. Fixed a bug in the ellipsis button of the client that would not allow the last item in the list to be dropped into drop down menus

2. Fixed a bug in the server that was breaking the ability to use direct ip address configuration for the buttons

Version 3.67       (Server and Client)    4/13/2007

1. Added scripting support for raw LWCP commands

2. Fixed a bug in the Route Status stack event qualifier that only allowed the qualifier to work on the first router in the database

3. Fixed a bug in the client where the ellipsis list would occasionally select item one off from requested after switching between routers.

Version 3.66       (Client and Server and Panel Designer)

1. In Server - prohibited cluster host names with spaces in them

2. In Server - added new context sensitive help file

3. In Client - added new context sensitive help file

4. In Panel Designer install - added new context sensitive help file

Version 3.65       (Client and Server - Both should be upgraded to move to this version)

1. In the Stack Event User Panel configuration, added a warning message if the user has not filled out either the buttonname or the hostIP field. One of the two must be filled in to commit the qualifier or action.

2. LWChannel Element ON, Off button addressing in user panel stack event did not work for LWChannels above 999.  This has been fixed.

3. Fixed a bug in clustering when the stack event group name had spaces in it, the file names were not synchronizing and replicating properly to and from secondary server.

4. Fixed a bug in the Ellipsis Select list. If a source or destination was selected that had the same name as the original source or destination, but was in fact different, it would not change properly.

5. Added additional sensing and messaging to alert clustering users of the illegal duplicate license state which prevents clustering from working properly.

Version 3.64       (Client and Server - Both should be upgraded to move to this version)

1. Stack Event GPIO drop down was displaying numbers rather than description, and the ellipsis buttons were not appearing.  This has been fixed.

2. Stack Event Source lists and GPIO lists were offsetting the Host IP, Name, Axia Channel information by 1 because of the None field at the top of the list in the ellipsis selct list.  This has been fixed.

3. In the Client Event wizard - the destination drop down lists were not populating with an initial value causing the ellipsis button to bring up a blank list until something was selected.  This has been fixed.

Version 3.63       (Client, Server, Panel Designer - Both client and server should be upgraded to move to this version)

1. Added Stack Event Qualifier Support for Element Channel On/Off buttons.  To use this select a user panel button qualifier, enter the Element IP, select LWChannel for the module, enter the LWChannel number, and select either On_But or Off_But to trigger the qualifier.  This requires Element software version 1.1.13.9 or later.

2. Fixed a bug in the Time Based stack event qualifier.  With events that were to run on repeated days, the qualifier was not resetting after the first run, and therefore would not run on subsequent days.  This should be fixed in this version.

3. Fixed a bug with Software User Panels in a Cluster.  If the user panel (Mini or Client) connected to the secondary server, and the panel actions were only based on stack events, the button pushes and property changes were not forwarded to and from the server owning the event system.  This should be fixed in this version.

4. Improved Performance on Server for large routers

5. Added the ellipsis button next to all source and selection drop down menus.  This button presents a grid to select a source or destination from.  The grid includes columns all of which may be moved and sorted.  The columns include such data as name, description, PFS number, Host IP, Host Name, Axia Channel Number . . .

6. Addressed Form resizing on all forms in client and server

7. Added the ability in the User Panel Stack Event qualifiers and Actions to address Element user panels directly without first having to create a software panel and map to it.

8. Added support for the Accessory Panel in both Panel Designer and the User Panel Stack Event qualifiers and actions

9. Fixed an issue where backfeed names were just displaying as To rather than the whole backfeed name

10. Reduced traffic between client and server as routers to have names transmitted were not being cleared out of the server pending cue and thus were being sent additional times periodically

11. Worked on Backfeed movement between Elements and subsequent owner displays

12. Fixed an issue in the server automatic addition of found LW sources when that was selected that was causing backfeeds to be added multiple times rather than their ownership changed

Version 3.61       (Client and Server - Both should be upgraded to move to this version)

1. Created the "Other" state for virtual route points whose base routes are not cleared but are also not routed to anything that exists in the virtual router

2. Added Clear Route capability to scene changes (Scene changes to be analyzed for clear route conditions as those will be met and executed by this version)

3. Increased client and server performance for larger systems

4. Fixed a bug in the Chart View of the client that locked the client application when trying to display chart matrixes above 1500 x 1500

5. Reworked the Import function for Virtual Router creation and editing in both the server and the client.  The Import function now allows you to pick the rows using intuitive standard windows selection techniques to be imported from the base router.  Previously you were forced to import the entire router and then remove the entries you did not want or manually create each virtual entry one at a time.  This was extremely cumbersome when the base router being used was large.  This update addresses that issue with displayed lists that can be used to select the entries to import using the shift and Cntrl key to import multiple entries.

6. In the client - added buttons next to the source and destination drop down boxes which will pop-up a list of the sources or destination in a table form.  This table includes not only name and description columns, but host ip, host name, Axia Channel Number, PFS number, etc.  The list is sortable by clicking on the top of any column.  Columns may be reordered by selecting the column using the top description, and then clicking and dragging on that bar again (red arrows are displayed to show the move status).  Double-clicking an entry is the equivalent of clicking an entry and then clicking select.  This drops the entry into the source or destination combo box on the main routing panel so it is ready for a take operation.  Holding the Ctrl Key and clicking on a destination type entry will go to that line in the main grid as well.  Many clients were asking to be able to see Axia Channel numbers in addition to PFS numbers.  This allows this.  This screen will also be allowed in the future on other screens that require source and destination selections.

7. Added a Shell Command Action to stacking events.  This allows any windows command line command to be run.  To run a VBS script, you must invoke the script handler as part of the command - for example the shell command would be:  CScript C:\Junk\Test.vbs.

Version 3.60        (Server Only)  1/18/2007 11:39:00 AM

1. Fixed a bug in the clear route function that caused an error message to appear when clearing routes in a main router

2. Fixed a bug in Stack Events Silence Detect that caused erroneous behavior when two stack events tripped off of silence and audio present on the same source or destination respectively.

Version 3.59        (Server Only)  1/12/2007 2:45:00 PM

1. Added hold time parameter to GPIs being sent as part of Prophet ACU translation to allow for Prophet polling

2. Fixed a bug in Stack Events - If the "Run Actions if any qualifier are met" was checked, Actions would only be run if the first qualifier was true, and not is any subsequent ones were true.  This has been fixed.

Version 1-03        (SAACU Bridge)  1/8/2007    9:00:00 PM

1. Added logging to the ACU Bridge Application

Version 3.58        (Server and Client)  1/04/2007 9:07:00 AM

1. Fixed a bug where in certain cases a 0.0.0.0 source route could get interpreted as an actual route point rather than a None route

2. Fixed a bug in Silence Detect stack events.  Certain left/right disparities and/or clip events could stop and or erroneously trigger the timers.  Event is only seen as silent if both left and right are silent.

3. In the Client, double-clicking lines in the source and destination lines in the search results now align the main grid to that point.  In the case of a source only, it will bring that source up in the routing drop down box.  There is still a little bit of work to do on this in the chart view rather than list view.

4. In the Client, search results line number column is now expandable.

Version 3.57        (Server)  12/03/2006 11:26:00 PM

1. Fixed a bug where in certain cases after an Element reboot, PFS would not re-connect with the VMIX/Profile Change Port 4010.

2. Fixed a bug in Silence Detect stack events.  If multiple stack events are monitoring the same source or destination for silence, the Actions were getting tripped more often than they should.

3. Reworked the Name Change screen code to protect names in nodes better.  There was an occasional condition that could make the wrong name get pushed to the node.

4. Eliminated Pathfinder's ability to automatically push name and address changes to a node.  This was put in Pathfinder Server to make it push changes if a new node replaced a bad one.  This was deemed dangerous as it could cause unwanted changes.  Also this functionality will be replaced by the Axia management tools under development.

5. If you change the name of a GPIO source or destination in the node, Pathfinder Server was not picking up the changed name.  This has been fixed.

6. Stack Event Time based interface did not re-populate the End Date option properly when the event was edited.  This has been fixed.

7. Time based Stack Events required a restart of the application to work.  This has been fixed.

Version 3.56        (Server, SAACUBridge, SAGenericBridge)  10/22/2006 11:26:00 PM

1. Fixed a bug in the ACU Translator that caused the proper state not to be sent when first starting PFS up with Channels/relays/optos on, until the channels/relays/optos were kicked off and on again

2. Added an option for the ACUTranslator to support the SAACUBridge through event driven changes rather than strictly polling on the TCP side of the bridge

3. Added an option to Translators to allow them to be turned on automatically or to follow the event system for cluster solutions where the translator should only be on on the computer currently owning the event system.

4. Fixed a bug where occasionally ACU Translators after being edited would not restart

5. Created the SAACUBridge application to run on serial computers where it is desirable to convert the ACU serial data to event driven TCP data and allow that communication to roll between cluster nodes with the event system.

6. Created the SAGeneicBridge application to convert serial control data to TCP data and roll the TCP side between multiple cluster nodes with the event system.

7. Added support for the SAPortRouter (not released yet).

Version 3.55        (Server)  10/5/2006 9:50:00 PM

1. Scan function now binds to the correct NIC

2. Cluster update router record refreshes router rather than reinitializes

3. HardwareMaps were getting reinitialized every time a router was updated.  This caused some state issues as seen in MPR scripts when ID light got left on.

4. NonTerminal sources should get converted to real sources during a scan if the scan finds a LWRP capable engine responding on those sources

5. Added an "Are You Sure?"  message when PatfhinderServer is asked to shut down.  However at this point in time the message is modal stopping other application capabilities until it is responded to.

Version 3.53                (Server, Client)    9/4/2006 9:18:00 PM

1. Client was not resubscribing to audio thresholds when it switched from one cluster node to another

2. Increased delay times available in stacking events from 60000ms to months in ms

Version 3.52                (Server, Client, Mini 1.09, PanelDesigner 1.09)    9/3/2006 8:26:00 PM

1. Fixed a bug in the ACU translator configuration screen which made it impossible to remove GPIO closure points from the translator

2. Finished all logging capabilities including logging to Syslog UDP destination

3. Fixed a bug when editing routers that caused multiple copies of hardware connections to be opened

4. Event creation was showing silence detect gui options on final screen no matter which event type was fixed - that has been fixed

Version 3.49 Beta        (Server, Client, Mini 1.07, PanelDesigner 1.07)   8/20/2006 8:29:00 PM

1. Added ACU-1 translator with support for VMIX

2. Fixed serial port settings bug when editing a protocol translator with serial port parity other than none

3. Fixed resizing issues of Protocol Translator wizard screen

4. Pathfinder Mini now remembers it's screen position from last startup

5. IF Client Connection to Server Hung but did not disconnect, client was still posting the lost connection and ending rather than trying to reestablish or find new server to which to connect.  This is fixed.

6. When LogToFile was enabled, server would create a garbage log file in the root of the PFSServer folder.  This has been fixed.

7. Added clustering support for the ACU Table in the Protocol Translator Database.

8. Added additional loss of connection sensing into the inidvidual node modules

9. Fixed log where disconnects were getting logged during inital connect that were not actually disconnects

10. Added additional connection logging code

11. Fixed a bug in the new refresh router function that could cause wrong information and require a reboot of the application

12. Added subscription for silence detect so only those sources and destinations in the current view window of a client, or involved in a stack event, or normal event are subscribed to. Cuts down dramatically on traffic analysis

13. Added AxiaAutoUpdate option which allows the server to automatically add sources and destinations on existing LW devices as they appear. For example when busses are turned on in element they will get added into the matrix if this option is on.

14. All TCP outgoing connections now include heartbeats, TCP Error handlers, and TCP Close Handlers

15. Added NO Change option to User Panel Key State Stack event Qualifer

16. Added \HEX escape characters to user command qualifier and action in Stack Events

17. Serial Port Transators only open when event engine is running

18. ACU Protocol Translator silence detection added

19. VMIX support for fadeup and down times, On/Off, Gain added to scripting engine, SA Protocol Translator, and Stack Events

20. Panel Designer fixed bug when saving file with a different name, was not writing the correct panel name into the hordware map file

21. Added support for DISP object into panel designer hardware map to support the LCD display at the top of a User panel

Version 3.48 Beta        (Server)   7/27/2006 8:29:00 PM

1. Fixed a bug in the Database writing for the Pro-Bel General Router Protocol Translator which in some situations was not allowing the router to be used field to get filled in. - Server Only Update.

Version 3.47 Beta        (Server)   7/24/2006 11:06:00 PM

This is a beta version of the software.

1. Fixed a bug in the Serial Port implementation of the Pro-Bel General Router Protocol Translator

2. Added support for commands 101, 106, 103, and 107 to Pro-Bel General Router Protocol Translator

3. Foxed Clear Route command in Pro-Bel General Router Protocol Translator

Version 3.46 Beta        (Server)   7/24/2006 2:16:00 PM

This is a beta version of the software.

1. Added Pro-Bel General Router Protocol Translator - Only commands 1 through 4 supported at this point in time

Version 3.45 Beta        (Server, Client, PathfinderPC Mini 1.05)   7/18/2006 10:05:00 PM

This is a beta version of the software.

1. Fixed a bug in the virtual router creation when early points in the imported list were removed, that caused synchronization with based tables to work incorrectly

2. Fixed a bug where if an Axia Audio router configuration was changed in the server, sometimes some of the nodes would get their destinations all set to the first route point in the PFS list

3. PathfinderPC Client and Mini now both will continue to search through the list of available servers in the cluster continuously until they find one or are shut down.  If the client of mini loses connection with the server, it will now try to reacquire that server first then any others in the list rather than shutting down.

4. Completed more logging parameters.  Still have some logging parameters that are available in the logging list to complete.  Should be finished in next version.

Version 3.43 Beta        (Server, Client, Panel Designer 1.06, Pathfinder Mini 1.04)  6/28/2006   3:35:00 PM

This is a beta version of the software.

1. Fixed a bug where Virtual Router Points would start at 0 rather than 1 when first creating the Virtual Router

2. Fixed a bug Virtual Route Point editor in the server would have the cpations Source and Destination Reversed

Version 3.42 Beta        (Server, Client, Panel Designer 1.06, Pathfinder Mini 1.04)  6/28/2006   3:00:00 PM

This is a beta version of the software.

1. Fixed a bug where UDP send in protocol translator was not working correctly

2. Fixed a bug where UDP send out parameters would not fit in the field in the protocol translator database

3. Fixed a bug where Panels mapped to Virtual Routers would not update properly

4. Significantly increased speed from receive of route change status to display in client and protocol translator

5. Changed Router numbering so that ID numbers do not get renumbered as routes are added or removed from the list.  Furthermore when adding a route the software will check back to the past revision of the database and if the route existed there, try to reuse the same number.  This means that the route list may not be contiguous numbering but rather those numbers will act as unique identifiers.  This will prevent scene change and protocol translator mappings from getting mis-assigned after route points are added or removed from a router.

6. Modified the first status update request to units on software startup to achieve faster synchronization with the network - less than 10 seconds.

7. Additions and removals from a router of points and Livewire devices should automatically post to the client and become active rather than requiring a reboot of the server application.  Some additional testing and modification of this point may still be needed.

8. Fixed a bug where if there where multiple silence detect stack events, anything above the first would also get its timer started whenever the first passed below the threshold causing unpredictable alarms.

9. Added a Default Graphic Path item to the Panel Designer.  If pictures are used in a Panel Design the panel will first look for the graphics in that default path location, and if it does not find them there, it will look for them in a PanelGraphics folder within the folder where the application is launched.  If they are not found either place, they will not be displayed.

10. Added ButtonOnUpPicture, ButtonOnDownPicture, ButtonOffUpPicture, ButtonOffDownPicture fields in the Panel Designer.

11. Made all of the graphic options listed above for user panels work on both the Pathfinder Client and Pathfinder Mini applications.

12. Changed the PanelDesigner so that right-clicking on an object enters it into a state for dragging and resizing.  Left click will allow simulation of the graphic changes listed above from within the designer.

13. Added escape characters to send LineFeed and Carriage Return in user defined commands out the Protocol Translator from stack events.

14. Added a label in the main control panel of the client to show the IO number selected for both Source and Destination.

15. PathfinderPC Client now only updates level graphics in the viewable part of the scroll for increased efficiency

Version 3.39 Beta        (Server, Client, Panel Designer Update)

This is a beta version of the software.  We are getting close to a final release but still have some known bugs and issues we are working on.

1. MouseUp in the Stack Events User Panel Qualifier fixed

2. Added Logging Gui

3. Added Logging Engine - though not all options in the gui are actually active in the code in this version.  That will be fixed in the next version

4. Fixed a memory leak when editing stacking events

5. Memory Qualifier in Stack event did not trigger if the memory option was the only qualifier.  This has been fixed

6. Added Element Show Profiles to both the qualifiers and actions in the stack events

7. Panel Designer now writes the hardware map file

8. Fixed Panel Designer Cancel Save

9. Panel Designer warns on exit if panel has changed giving the user a chance to save

10. Save operation with multiple panels opened fixed

11. Fixed the label shift in Panel Designer when clicking on a label

12. Controls in Panel Designer can be copied and pasted

13. \n works for carriage return in label and button captions and stores properly now

14. Panel name now follows filename and vice versa

15. Added scrolling to the chart view in PFClient - still needs some work for the next release

Version 3.35 Beta        (Server Update)

This is a beta version of the software

1. Fixed the negation function on memory slots in Stack Events.

2. Added support for GPI commands in SATranslator and Stack Events.  GPIs may only be changed in the software driver, not in hardware nodes.  SATranslator now has a TriggerGPI command and a TriggerAllDestGPI Command.

Version 3.34 Beta        (Server and Client Update)

This is a beta version of the software

1. Fixed an issue in both the client and server to make the GPIO status panels in the client work properly again by right clicking on any GPIO router line in the client.

2. Finished a performance enhancement in the SetMeter functions in the server.

Version 3.33 Beta        (Server Update)

This is a beta version of the software

1. Fixed an issue with GPO based stack events where the GPO information would not come back when trying to edit the event and the GPO event would not fire.

2. Produced several performance enhancements for large routing systems by using indexing in certain arrays.

3. Added a Generic Protocol Translator type.  In the future this will tie to a text file so that the user can create their own protocol translation rules.  For now this allows this will allow unique commands to trigger stack events.

4. Added a Protocol Translator command as a qualifier allowing the user to make any specified command on a protocol translator trigger a stack event.

5. Added a SA Command Action to the protocol translator which will allow an action to be any command in the Software Authority protocol translator protocol.

6. Made the TriggerGPO command work on virtual router destinations that have GPO points mapped to them.

7. Added a command to the Software Authority Protocol Translator Protocol called TriggerAllDestGPO.

o This command will trigger all GPOs to which a specified source (either GPI source in a GPIO router or virtual source) is routed.

o Syntax:   TriggerAllDestGPO <RouterNumber> <SourceNumber> <State 'lllll|hhhhh|lhhxxx . . .'> <PulseDuration in Milliseconds>

o Example:   TriggerAllDestGPO 2 3 lxxxx 500

o See the SAProtocolTranslatorProtocol document installed with the server for details.

Version 3.32 Beta        (Server, Client Update)

This is a beta version of the software

1. In the Server fixed an issue where GPI changes were not getting entered into the memory array above the first 8 in a GPIO router.

2. Produced several performance enhancements for large routing systems.

3. Added the beginning stages of System Logging

o This currently has three levels and may be outputted to a TCP port or a file.

o Care should be used with the Medium and high levels as these are meant strictly for debugging and will probably be changed later.  Plus they output a great deal of data and could slow the server down.

o The Low level will output disconnects and reconnects with the nodes making it easier to see if the server is having a problem communicating with the nodes.

o It is advisable to use the port version and capture using Hyperterminal or some telnet capturing program rather than having PFS write to a file as this is slower.

o In the future there will be a log capturing and viewing application and much more useful data will be added to the logging function.  Also the format for these logs is still under development so this is just an introduction to this feature

4. Fixed some issues in the User Database Editor

5. Added a backup table when editing a Livewire router system that will automatically initiate a clean rollback in the event that the Livewire edit fails to complete.

6. Added GPIO support to the Software Authority protocol translator to both view GPIO changes and initiate GPO changes

7. Added the ability within the Software Authority Protocol Translator setup to select which routers and thereby limit the routers the translator will display information for.

8. Fixed a bug where the runscript command in the protocol translator would not work if the particular script did not require an additional argument beyond the calling object.

9. In the client Added registry keys which can be used to limit access on the client without requiring a login

o  HKLM\Software\Software Authority\PathfinderPC\ACL\

a. FullAccess (0 or 1)

i. This is set to 1 by default when the program starts and this registry key does not exist.

ii. 1 enables full access (according to user login rights if enabled on server)

                                                            iii.      0 limits access to the below entries

b. Router_<RouterName>  (0 or 1) for deny or allow

c. Panel_<Panel

d. Name>  (0 or 1) for deny or allow

e. VirtualRouterEdit  (0 or 1) for deny or allow

f. SceneChangeEdit  (0 or 1) for deny or allow

g. LevelControlChange  (0 or 1) for deny or allow

h. EventEdit   (0 or 1) for deny or allow

Version 3.26 Beta        (Server, Client update)

This is a beta version of the software

1. In the client fixed the restart so that it brings up last used User Panels

2. In the Server dramatically increased speed of the scripts by caching them so that they do not have to get pulled from the hard drive each time

3. In the Server added support for Includes to the scripting

Version 3.25 Beta        (Server, PanelDesigner update)

This is a beta version of the software

1. Added hidden grid for dropping controls in designer

2. Reduced unnecessary traffic between client and server application

Version 3.24 Beta        (Client, Server, Mini, PanelDesigner update)

This is a beta version of the software

1. Added storage of the previous route point for each destination into the internal routing memory

2. Added a script command to allow the system to return to the previous route point for any destination.  For Livewire routers this will return to the actual previous source stored in the node regardless of whether that source lives in the PFS route list.  For standard and virtual routers it will return to the last route in the route list.

3. Fixed a hexi-decimal conversion issue with certain colors picked for panel buttons in both the client application and in Mini

4. Introduced the Panel Designer.  The Panel Designer is the alpha version of a graphical designer to design custom button panels.  No help is available for this application yet.  The application is now automatically installed along with the server application using the server application installation package.  The separate installer for the panel designer is for those users who wish to design the panels on a different workstation and then just copy the xml files to the server.

Version 3.23 Beta        (Server update)

This is a beta version of the software

1. Found 2 un-trapped socket errors that could cause application crashes.

Version 3.22 Beta        (Server update)

This is a beta version of the software

1. Adds support for UDP connections to the Protocol Translator.

Version 3.21 Beta        (Client and Server update)

This is a beta version of the software

1. Fixes issues with Panels making duplicate scripting calls under a clustering condition.

2. Adds a Heartbeat to the Clustering to double check activity between the nodes.

Version 3.20 Beta        (Client and Server update)

This is a beta version of the software

1. Adds support to run scripts from the protocol translator - undocumented and not in the protocol translator help files yet.

2. Fixes a bug with clustering where an extra cluster node object was being created and interacting with the clustering view making it appear that the connection was connecting and disconnecting repeatedly.

3. Fixes a bug that caused the hardware user panels not to repopulate after an engine was rebooted.

Version 3.19 Beta        (Client and Server update)

This is a beta version of the software

1. Fixes a loop created by the fix in version 3.18.

Version 3.18 Beta        (Client and Server update)

This is a beta version of the software

1. Fixes a problem where the router creation wizard cannot complete properly if there are blank names for sources or destinations in the nodes.  Blank names are not supposed to be allowed in the nodes, so this version of the software pushes a new factory default name to any blank names in the nodes.

Version 3.17 Beta        (Client and Server update)

This is a beta version of the software

1. Adds full support for Clustering including data synchronization of database files, Stack Event files, and memory slot and matrix locations.  Panels and scripts must still be manually copied as these must be manually created.

Pathfinder Mini Version 1.0        (Alternate Client Application - Requires Server Version 3.16 or later)

This is a beta version of the software

1. Pathfinder Mini is a small application that displays custom user panels.  The user panels are XML documents that are dropped inside the PFSPanels folder of Pathfinder server.  They allow a designer to create custom button panel to manipulate routes and call scripts for custom logic.  The controls in these panels can have their color, text, and other properties dynamically controlled by scripts and stackable events.  They can also be mapped directly to a particular route to light when the route is active and cause the route to be activated when the button is pushed.  Scripts can be used to create advanced routing logic tied to these panels.  The button panels have been available to advanced designers as a window within Pathfinder for some time.  Pathfinder Mini provides a small application to run these panels without all of the other features of the Pathfinder Client.  This is useful for end user panels where you do not want the end user to see the full interface of Pathfinder Client.

2. A demo file of a Pathfinder User Panel is also available for download as a self extracting exe file. This panel xml file when extracted on the Pathfinder Server gets dropped into the PFPanels folder.

3. The Pathfinder Mini file includes a simple text configuration file where an administrator defines the IP address of the server and the name of the panel from the server to display and use.  These configurations are not GUI driven because the idea is that it is to be used for situations where the end user is only supposed to have simplified limited control, and such a GUI would place other panels and properties and the end user's touch.

4. Documentation on the Panel definitions and Scripting language for advance work is still sparse though that will be forthcoming.  Contact Dan Bays and dbays@softwareauthority.com for more details until such documents have been completed and posted.

Version 3.16 Beta        (Client and Server update)

This is a beta version of the software

1. Fixes a GPO Contact closure issue in Stackable Events. Adds several new functions to the scripting engine including GPO sensing and triggering. Adds option in the Stackable events gui to force a run of the actions. Modifies hardware user panel commands in server so that text updates are only sent if they change to increase performance on the Element CAN bus.

Version 3.15 Beta        (Client and Server update)

This is a beta version of the software

1. Fixes a memory Leak in version 3.14

Version 3.14 Beta        (Client and Server update)

This is a beta version of the software

1. This version finishes Stackable Event support of Audio Events. Stackable Events can now have their qualifers set to be true if all qualifiers are true or if any qualifiers are true. It also adds GPO Trigger to standard silence detect events. Finally it fixes several bugs including a failure of scenes to activate if a User Panel has the focus. Please Note: GPO Pulse settings should remain at 0 until further notice as GPIO units do not seem to be responding to pulse command from LWRP correctly at this point in time.

Version 3.13 Beta        (Client and Server update)

This is a beta version of the software

1. This version introduces Stackable Events as well as the ability to map a route point to a panel button in the Panel XML definition.
Please Note: Audio Level Detection in Stackable Events not working properly yet in this version.

Version 3.12 Beta        (Client and Server update)

This is a beta version of the software

1. This version is exactly the same as the 3.11 Release version, except with the Clustering tab enabled for Beta sites to be able to start experimenting with Clustering.  Clustering users should be aware that this feature is still under development.  At this point in time clustering is working, but database synchronization is not complete.  Thus the system must be set up and then the databases manually copied from one server to the other.  That will be fixed in future releases.

Version 3.11b Release   (Client Update Only)

This is a release version of the software

1. Fixed Drop Down Lists losing Sources and Destination Lists When Switching between multiple routers

Version 3.11 Release   (Client and Server update)

This is a release version of the software

1. Fixed locks getting stuck on red

2. Fixed slow load time of long lists into combo boxes

3. Clustering Tab Disabled in this version

4. Fixed Chart View bug that made cleared routes still hold the last uncleared state.

Version 3.10 RC     (Client and Server update)

This is a maintenance release to fix certain bugs, and not a major feature set release.

1. Release Candidate version 3.10

2. Fixed GPIO Config bugs

3. Fixed GPIO trigger bug with nodes above the first GPIO Node

4. Fixed Locking bug with Scene Changes

5. Cleaned up Event List Viewer and Event Wizards

6. Added Automatic Backup of all critical changes to databases

7. Added Email Alert Support to all Events

8. Fixed Bug with events on repeating daily schedule

Version 3.05 to 3.07n     (Client and Server update)

1. Added ChartView, Support for Scripting Engine, User Panel Button Support, GPIO buttons as user button support, multiple fixes and updates

Version 3.0 5(Server update)

1. Scene Events could only add scenes that were named with names less than 16 characters.  This has been fixed to allow names up to 251.

Version 3.04 (Client and Server update)

2. Fixed a bug in the edit wizard of the livewire points from the route names screen on the server that prevented destination changes from being stored properly. Also added the description field to this window.

3. Fixed several bugs in the event wizard of both client and server which were causing source lists not to display properly, GPIO events to get stored with no proper contact closure number if stored from the client, and several other user interface issues

4. Modified the TCP/IP receive routines on both server and client to be more elegant and guarantee processing of all commands if multiple commands are included in the same transmission packet

5. Fixed some bugs in the user interface of the virtual router creation and editing wizard. This caused source lists to not display properly in some situations. Also caused naming issues on the grid columns. Also fixed issue with GPIO contacts with no descriptions being added as virtual maps to a virtual point.

Version 3.03 (Server update only)

1. Maintenance Fixes

Version 3.02 (Client and Server update)

1. Fixed a bug that caused the scene creation page to not allow multiple rows to be selected in the grid.

Version 3.01 (Client and Server update)

1. Fixed a bug in the Livewire setup wizard which added incorrect information into the database for Axia Windows driver Sources. This incorrect information was causing routing problems when the user attempted to route an Axia Windows Driver Source.