Premise Premise compatible audio amplifier

[sic0048]

According to the manual...

The serial port requires 38400-baud, 8 data bits, no parity, 1 stop bit, with Xon/Xoff flow control
enabled. 38400 is recommended, but 1200 to 115200 is available via a configuration command.

So I would try 38400 speed and see what they reply is.

If that doesn't work....

You can also force the system to 9600-baud by holding the rear-panel Memory-Erase button depressed as you apply power.
This provides a quick field change to 9600 for systems that cannot reach 38400-baud (notably some Vantage controllers).

I would try that and then connect at 9600.

Also, here is the link to the firmware if you think it needs to be reloaded for some reason. Download the zip file and open the Readme document for directions.

 

[ajeysp]

Hurrah !!
I finally got it to work .
The problem was probably with the firmware. I used the link that sic0048 gave me to reload the firmware, and Premise is now able to connect to the Vaux switcher.
Thanks very much sic0048, pm2000, 123, chucklyons, etc6849 for all the help, because of you guys I could get this to work.

ajey

 

[123]

I'd like to know if a Vaux switcher's firmware can be upgraded to a new version or if one is limited to reloading the same version.

What is your switcher's current firmware version? Do you know if you installed the same version as what you had or did you upgrade it to a newer version? Does Premise's Vaux driver handle the switcher as a "Lattis" or "LattisV6"?

 

[ajeysp]

I'd like to know if a Vaux switcher's firmware can be upgraded to a new version or if one is limited to reloading the same version.

What is your switcher's current firmware version? Do you know if you installed the same version as what you had or did you upgrade it to a newer version? Does Premise's Vaux driver handle the switcher as a "Lattis" or "LattisV6"?

I am not sure if it can be upgraded or not. My switcher's current version is 5.22. I don't really know which version it had earlier, but pm2000 (the guy from whom i recently bought it) had told me to select "Lattis" to handle it from Premise. That prompted me to try version 5.22 (and not 6.0).

 

[ajeysp]

I am now facing a new problem. The firmware that I load into the VAUX switcher doesn't hold for more than 1-2 days. What I mean is that after every couple of days I need to reload the firmware. any clues as to why this could be happening and whether there is any fix?

 

[samgreco]

I am now facing a new problem. The firmware that I load into the VAUX switcher doesn't hold for more than 1-2 days. What I mean is that after every couple of days I need to reload the firmware. any clues as to why this could be happening and whether there is any fix?

Seems odd. I wouldn't expect it to be a battery backed up type of chip, like CMOS. I would have expected a non-volatile memory (EEPROM) which theoretically never lose their data. But you should probably check with Vaux to see. You could open up the unit and see if there is a battery on the board somewhere. Usually they are the batteries that look like a coin, watch battery style.

 

[ajeysp]

Hi Everyone,

Reopening this thread. To avoid the hassle of going through this entire thread (to understand the background),,,I had purchased a "third hand" audio Vaux switcher, and connected it to my PC via a serial port. Every time I lose power, if my switcher gets powered down for more than a couple of hours, I need to reload the firmware. However if I just toggle its power switch, it retains the firmware.

I now have changed my PC to a newer one, which doesn't have a serial port. So I am using a USB to serial interface to control this switcher from Premise. Whenever my PC comes on automatically in the morning (thanks to the nice feature in the CMOS that the newer PCs have), the switcher does not respond to the commands from Premise. On checking the status of the com port under "Devices", it shows that the com port is open. Under "Devices"->"Vaux"->"Lattis", "PortStatus" it shows "Port(Opened)". However the "CommunicationFailure" check box is checked, but the "LastFailuretime" shows a time which is much before the current time. I am able to get it to work, sometimes by changing the port to some other port, and setting it back to the correct port, and sometimes by toggling the power switch of the Vaux switcher.

Any tips/hints to resolve this issue will be greatly appreciated.

Ajey

 

[etc6849]

Ajey,

Is the switcher being used with Premise use an add-in (e.g. native driver)? If it's not an add-in and instead is a module (e.g. you can see it's code in Builder), there are some easy fixes for you to try such as an onchangescript that triggers when CommunicationFailure is set. This script could automatically attempt to reset the port x times. You might also try toggling the line terminators if the serial device uses ascii code. Chuck found that Onkyo receivers need to have the line terminators toggled on a reboot in order for serial two way communications to work. Both me and Chuck reproduced the error.

If it is a native driver, you obviously can't add an onchangescript. However, you could explore modifying the CommunicationsFailure property so that it is bindable and building a home object that would reset the port.