SX80 Output Issues
Cameron
Posts: 56
Hi Guys,
Has anyone had an issue where the outputs of a Cisco SX80 stops outputting to a DVX? I am currently running Hotfix 1.6.42 for the switcher.
The SX80 is connected to HDMI 7 and 8 on the DVX and DVI 2 on a TPI. Everything will work fine for days, and sometimes weeks, then suddenly an output from the SX80 drops offline - the DVX shows a red source. Rebooting either device does nothing (most of the time).
I am using custom layouts on the SX80 (created through TC Console).
Some resolutions I have found have been;
> Replaced HDMI, this was an isolated issue
> Reboot Cisco and then AMX DVX
> Reapply Cisco Layouts and then reboot AMX DVX
> Switch monitor roles on the SX80
The strangest one was today, switching the output (1) to monitor role second and then back to first fixed the issue..
Has anyone seen this or have any ideas?
Thanks,
Cameron
Has anyone had an issue where the outputs of a Cisco SX80 stops outputting to a DVX? I am currently running Hotfix 1.6.42 for the switcher.
The SX80 is connected to HDMI 7 and 8 on the DVX and DVI 2 on a TPI. Everything will work fine for days, and sometimes weeks, then suddenly an output from the SX80 drops offline - the DVX shows a red source. Rebooting either device does nothing (most of the time).
I am using custom layouts on the SX80 (created through TC Console).
Some resolutions I have found have been;
> Replaced HDMI, this was an isolated issue
> Reboot Cisco and then AMX DVX
> Reapply Cisco Layouts and then reboot AMX DVX
> Switch monitor roles on the SX80
The strangest one was today, switching the output (1) to monitor role second and then back to first fixed the issue..
Has anyone seen this or have any ideas?
Thanks,
Cameron
0
Comments
I don't know if the issues you are experiencing are related.
Some resolutions I have been able to incorporate (but they all are only temporary):
Switching the HDMI input format on the DVX from HDMI to DVI (this will clear up the "red source" issue)
Toggling the DVX "logo" option on and off on the affected DVX output often clears things up as well.
Also, I originally had code that reset the DVX input format to HDMI on a regular basis and that seemed to cause scaling issues.
As it stands right now, (until AMX fixes the intermittent HDMI input issues with the PrecisionHD cameras), I have to add extra routines to have all of the DVX outputs switch on a logo (or test pattern) and switch them offf a half second later to get the output to scale the camera signal correctly.
It looks a bit messy when it's happening, but it's better than having no picture or a severely mis-scaled one instead.
AMX tech support currently has one of our PrecisionHD cameras in an effort to resolve the issue, but swears they have been unable to reproduce the issue.
Quite frustrating for me, as I've been battling this issue for a couple of years now, with about 40 of these cameras setup in this configuration.
If you discover anything, please let me know.
-Chris
Yes, unfortunately i ran into this. When installing the SX80 and connecting two outputs to DVX-2150 inputs 5 & 6, it refused to show any image. The webpage on the DVX showed the inputs in red (no input signal).
Connecting the displays directly to the SX80 worked fine.
I also tried different things, for instance:
Replacing cables,
setting inputs to DVI mode,
rebooting in different ways,
switching monitor roles, etc.
even tried downgrading the firmware for the SX80...
Nothing really worked. The strange thing was that it was very persistent, no image at all for about an hour trying all those things. Then, for no apparent reason, it suddenly started working. The connection survived reboots for both the SX80 and the DVX and has worked for about 2 weeks. Today the customer called that he had problems with the image again. I still have to check on location, but based on the last experience, not sure what i can do.
The DVX was running master, device and switcher firmware versions, that are up-to-date with the AMX website.
As a side note: I REALLY wished that AMX would update the SX80 comm module. It is based on an old firmware version which apparently had problems. Because of that they just completely left out the CALL- feedback (present in other VC modules) and sort off replaced(?) it with something undocumented, IPNAME-. I appreciate the effort they put into making these modules, but they are closed source, so we depend on AMX to keep them updated.
Anyway, not wanting to hijack the thread...
Any solution would be appreciated!
Richard
AMX DUET driver: Cisco_SX80_v1_0_4_dr1_0_0 (including AMX touch panel file)
Tested control methode: RS232 baudrate 38400 & 115200, IP control.
Remarks regarding the Phonebook in the AMX driver;
If you use the Cisco_SX80_v1_0_4_dr1_0_0 DUET module the results for search phonebook or search folder are the same, in both cases you get an overview of all folders and all contacts.
It’s not possible to see all contacts within one specific folder.
This way we can use the folders where they are intended for, organizing accessible groups of contacts. The Cisco touch panel does work this way.
We expect that after a “search folder” you only see the list of found folders and afterwards you get a list of contacts within that specific folder, you can call.
It’s currently not possible to store private addresses in a separate folder.
It’s currently not possible to create a small internal group of contacts.
With the search function you can’t find the listed contacts, only the * works to get all records.
Because this way the list is very long, names starting with a “w” will show up after a lot pages which is very inconvenient.
Further the results of a “search phonebook” and “search folder” varies, often not all records or folders are found/shown.
Further remarks regarding the phonebook are;
- “Record count” counts besides the records also the folders, what results in wrong value of the existing records.
- The page number in the phonebook page is not working it remains on 1 so can’t see how many page’s there are.
- ID page, it’s not clear what the function is, but it’s certainly not showing the Phonebook server ID.
- It’s not possible to stop searching if a record is not found, the popup “please wait” remains active.
These points above, could only be tested in “local phonebook” mode.
These points are only about the phonebook, there are a lot issues that make this driver useless, even simple input switching is only possible on the first 3 inputs.
In the document (Cisco SX80 Interface v1_0_4.doc) there is nothing to find what will work and what does not work.
For me for now it is complete useless.
In the next week it will be installed using a DVX-2150, I keep my fingers crossed.
But for now, have a nice weekend.
This is just more reason to not bother with DUET modules.
When I first started the programming for the Cisco C90s, the only available Duet module was written for TC4 something. The C90s shipped with TC6. I knew right away the module would be pretty much useless.
I started writing my own, knowing full well I could fix and change it as the software versions incremented (and they always do!).
Duet modules are really only useful for simple devices, switchers and displays mainly... and sadly, the simple devices can be controlled with a simple function or two, so why bother with the module?
Anything with fairly complicated functions (especially a video conferencing Codec), the duet module will never be able to keep up, even if the original module works correctly to start with.
I'd like to see AMX ditch the duet modules and have all of their provided modules written in native Netlinx...that way I (we) can fix the broken functions and have a good portion of my (our) code already written for me (us), instead of essentially providing a waste of time and frustration.
I have never understood why the source code of the AMX modules is not freely available to everyone.
If you do not use it then you can learn how they do it and maybe why they do it that way.
I have always been told that it is a support issue, how troublesome supporting a module once it has been modified would be. Judging by how poorly most of the AMX modules work I don't know that you would want to use them as example of how to do things the right way! LOL
cheers
I'm not sure how one can support broken code to begin with.
Is there different support for Duet vs Netlinx?
I've never tried to get support for either.
The "trying to support a modified module" seems moot to me.
There could always be a master module that they could support, but not support any customization to it.
If I'm going to modify the module myself, I'm obviously not looking for support!
*You* might not, but someone, somewhere *will*, and not admit they modified it. Like the MVP-8400 I serviced some years ago ... complaint was the buttons were sticky. Understatement: they were all but welded in place. So I pop the cover, and there is liked dried syrup inside, and what looked like the end of a bag of chips. "You spill your drink on this?" "Oh no, nothing was spilled on it ... "
I was having similar issues to the video drop with a DVX-3155 and SX-80. The issue was pushed to a firmware engineer and I was sent directly version 1.6.49. This has thus far fixed all my issues in 4 identical installations. They may be waiting for additional testing before releasing, but it is definitely worth asking for if you are having problems. Release notes are below.
Fixes in this release:
- Fixed an issue that caused loss of video when setting the VIDIN_FORMAT for a Multi-Format input to the same format it was already configured to.
- Modified the EDID sent by the Multi-format input so that it no longer indicates that it supports digital audio.
- Fixed an issue that could result in a VGA input on the multi-format card indicating a valid signal when nothing is connected.
- Fixed an issue that caused compressed audio to be played on a connected DXLink Receiver's analog audio output.
- Fixed an issue that could caused pink-tinted video on DVI displays connected to DXLink receivers when using the DVX-215x DXLink output.
- Improved compatibility of HDMI inputs with certain HDMI sources, including some WolfVision Document Cameras, that send invalid audio
infoframes without sending proper audio status bits which prevented the DVX from displaying video from that source.
- Fixed an issue where Tandberg/Cisco codecs fail to display video when connected as a DVI source to a Multi-Format input.
- Improved audio surround sound (HBR) when video switching
- Fixed false temperature sensor readings being reported to RMS
- Fixed color space settings with some PC/laptops with hdmi outputs
- Fixed Multi-Format DVI video input detect issues
- Fixed output blanking issue when switching video using auto or manual settings, occurs with Misubishi monitors
- Fixed persistant red screen after switching to a non-HDCP source following HDCP failure
- Fixed temporary audio mute on HDMI outputs when inputs are switched for other outputs
- Fixed issue where the output would only send a black screen when a DXLink input receives data from an upstream device in freerun.
- Updated equalizer settings to allow for longer HDMI cables
- Fixed an issue that caused IGMP messages to not be forwarded correctly.
- Fixed multichannel PCM audio support problem
- Fixed persistant blue screen issue caused by selecting different analog input format types on the web interface
- Fixed noise on analog audio output while digital audio modes were selected
- Fixed video issue caused by some devices going in and out of standby or sleep modes
Thanks jwstuff, I tried this one the other day but it made my DELL PC's go mental and flick on and off
Thanks,
Cameron
Did you have the SX80 connected to the multiformat inputs, or to one of the HDMI's?
Both the OP and myself seem to have issue's with the SX80 connected to HDMI inputs.
I can't really see anything that seems related to that in the 'fixed in this release' list. A lot of the issues were already reported as fixed in the current firmware, by the way.
Thanks for reporting your experience.
Richard
The SX80 was two HDMI Inputs and a DVI. I also had issues sending DVX switched content back to the SX80 out an HDMI into the SX80 on DVI. I just included all the verbiage in the release as a quick and easy. Sorry to hear it's not working for you, I guess YMMV.
Well, I didn't say it wasn't working for me. I don't know, cause I haven't tried it. It's just because I've had things gone worse, not better, after installing new switcher firmware (see the last post from Cameron...) . So I thought I asked more information to see if it it worth the trouble to try.
Seeing you also used HDMI inputs, maybe I should try this. I'll see if I can hold out until it is officially released.
Richard