VeEX AT1700M RF Switch Multiplexer Firmware 1.30 Download

Posted at April 27, 2024 by PCI-DB Team

VeEX AT1700M RF Switch Multiplexer Firmware 1.30 Description

Release Notes:

New and Changes:
- Note: AT2500 Software version 4.40.008 or higher is highly recommended when switches used in Realworx Monitoring system.
- RS232 Termination feature on switches will not be avaiable from this release. Therefore, external RS232 Terminators must be used when required.

Changes and Improvements:

- General Code Cleanup - removal of unused code for readability.
- Rewrite the RS232 drivers to be more efficient in parsing incoming messages.
- The software processing after the commands are parsed was made more consistent in its timing.
- Implemented a UI Partial Update - to speed up updating the LCD display with Port Channel.
- Changed the Boot-up Display to show VeEX Inc. and the proper Switch Model Type
- Removed Port B from the display in the AT1601’s and AT1701’s. Removed the Main Menu display and any settings for Port B.
- Removed Debug messages – Debug data is now logged instead of printed out in real time to optimize timing.

Fixed Bug:

- Resolved Timers - Timers from different tasks were overwriting each other, perhaps cutting some timers short, and delaying others more.
- Resolved issue of locking up due to Port B lockups (same as #7 below, a problem was it was not addressing port B)
- Initialize to port 0, as in old switches, instead of Port 1
- Resolved data being sent back to the AT2500 that was corrupt - this was due to the Switch beginning the communication on the RS232 bus before it was ready. - This had a further symptom that Ingress was able to restart without needing the Switch to be reset.
- Resolved issue during Trigger Mode. The Status command response reported the wrong port information. This was simply a bug, not a timing/communications problem.
- The switches would "lock up". This was due to an error on our receive buffer - which no amount of retries from the AT2500 would help. Further testing will be done to figure out which exact error.
- Moved the Short Protocol processing out of interrupt Service Routine to prevent overflow on other port.
- Resolved RS232 Driver errors (overflow, parity errors, etc)- this would cause a lockup before - necessitating reboot.
- Resolved RS232 Driver Issue- Made the RS232 Driver knowledgeable about which Protocol it is processing.

About Device Firmware:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device’s functionality in the event of a software update either turning up faulty or causing the unit’s overall performance to drop. However, bear in mind that applying an older firmware isn’t recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it’s best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device’s firmware. Also make sure you constantly check with our website to ensure that you don’t miss a single new release.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related VeEX Drivers