Re: Slider Crosspoint Issue
Hi Jason,
My solution to this (it's buried deep inside our framework, but it's used in lots of places) is to pass each analog value (from the user interaction side) into an AOS, with say a 1 second pulse width. The output of each AOS then goes into a digital on the x-point.
On the x-point destination ("equipment"), the digital enables an analog buffer for each "managed" signal.
Since AOS's are retriggerable, any *changing* analog value will propagate, but switching x-points doesn't propagate a new value (unless you happen to switch the x-point while the AOS is still high.)
The AOS/buffer stuff is all encapsulated within the x-point framework wrappers, so you don't even notice it's there. We use the technique for anything that has a slider/analog control - lights, treble/bass/balance, heating dials, etc.
Hope that helps,
Ol
toggle quoted message
Show quoted text
--- In Crestron@..., "Jason Andersen" <jandersen@...> wrote:
When I switch crosspoints the slider input value which ends up sitting on the output side of the abuf gets sent to the set volume input of my room module.
Thanks Heath. That is actually an idea I came up with last night and when I compiled I forgot to save the changes to the room module. I'm going to finish it now.
|
They are removing Studio from the class? Many they found out there are too many issue with it. On May 2, 2013 12:09 PM, "kriskasprzyk@..." <krisk@...> wrote: **
Gave it a few minutes of my time to see what it was all about. Haven't
used it since.
--- In Crestron@..., Seth Olle <seth@...> wrote:
Just wondering since the big news of it being removed from training etc.
Is anyone still using at all for anything? Or everyone has shelved it
for now?
|
Gave it a few minutes of my time to see what it was all about. Haven't used it since.
toggle quoted message
Show quoted text
--- In Crestron@..., Seth Olle <seth@...> wrote:
Just wondering since the big news of it being removed from training etc.
Is anyone still using at all for anything? Or everyone has shelved it for now?
|
Re: OT: Introducing HDMI to component distribution (PVID/BIPAD) creates ground loop
Use a ground cheater ac "adapter" on the power cord of the PVID. 9 times out of 10 that will work. (using it for the exact opposite of it's intended purpose!)
toggle quoted message
Show quoted text
--- In Crestron@..., "weddellkw" <weddellkw@...> wrote:
Thanks for the responses:
The loop is actually present all the time. With no HDMI connection, it is impossible to detect except on a very dark image, as a very thin and dim rolling band. Plugging in the HDMI to any source in the rack causes it to become much larger.
This suggests to me that there has always been a loop issue but it simply wasn't noticed until we put in a big 80" tv. Even then it wasn't noticed until the problem was exacerbated by the addition of HDMI.
The band does not appear on any of the other TV's (older Fujitsu plasmas, component only, and a small Samsung, component only)
I've been on the phone with our tech on-site off and on all morning, and he's tried every permutation we can think of.
Disconnected the cable feed from service.
Powered TV and equipment from one surge protector (Furman) via extension cord.
--- In Crestron@..., "Kol Johnson" <kol.mstc@> wrote:
So, whatever you plug the HDMI cable (and Vanco balun setup) into at the
equipment rack causes the loop to appear on any of the component sources
that run through the pvid?
_____
From: Crestron@... [mailto:Crestron@...] On Behalf
Of weddellkw
Sent: Wednesday, May 01, 2013 1:47 PM
To: Crestron@...
Subject: [Crestron] OT: Introducing HDMI to component distribution
(PVID/BIPAD) creates ground loop
Basically, the above. We've taken over an old analog distribution system,
and recently replaced an old Fujitsu plasma w/ a large Samsung LED unit. No
problem while on component distribution.
We were then asked to connect 'His Cable' to the new TV via HDMI as the
lead-in to a DM system. Pulled 2x Cat6 about 60' and used a Vanco balun to
accomplish this.
We now have a ground loop on component signals (additional cable boxes, BD,
AppleTV gen1) to the Samsung. No issue on the other TVs.
Disconnecting the HDMI from the cable box fixes the issue. Other cable
boxes/BD also reintroduce the loop. Have tried an isolator on the component
connections between the TV and the PVID, and the PVID and the cable box, no
change.
Any suggestions/fixes?
|
Just wondering since the big news of it being removed from training etc.
Is anyone still using at all for anything? Or everyone has shelved it for now?
|
Fixed length what
OLD SCHOOL
From: matt_rasmussen_2000 <mjrtoo@...<mailto:mjrtoo@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 2:34 PM
To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Re: Crappy protocols
You're complaining about fixed length delimited strings? How lazy are we getting! :)
toggle quoted message
Show quoted text
--- In Crestron@...<mailto:Crestron%40yahoogroups.com>, Seth Olle <seth@...> wrote:
I heard once in 1976 they hired Tim(name made up) to do all the protocols for pretty much everyone.
Then never changed them again, when checksums and all that other stupid stuff was necessary.
I like simple POWERON for example. Makes sense.
It seems to be less and less, I can remember back in the day, all the time doing complex string parsing, for huge hex strings.
Not so much anymore.
From: rickmcneely <rickmcneely@...<mailto:rickmcneely@...>>
Reply-To: "Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>" <Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>>
Date: Thursday, May 2, 2013 2:22 PM
To: "Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>" <Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>>
Subject: [Crestron] Crappy protocols
Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?
1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.
They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.
|
You're complaining about fixed length delimited strings? How lazy are we getting! :)
toggle quoted message
Show quoted text
--- In Crestron@..., Seth Olle <seth@...> wrote:
I heard once in 1976 they hired Tim(name made up) to do all the protocols for pretty much everyone.
Then never changed them again, when checksums and all that other stupid stuff was necessary.
I like simple POWERON for example. Makes sense.
It seems to be less and less, I can remember back in the day, all the time doing complex string parsing, for huge hex strings.
Not so much anymore.
From: rickmcneely <rickmcneely@...<mailto:rickmcneely@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 2:22 PM
To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Crappy protocols
Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?
1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.
They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.
|
I heard once in 1976 they hired Tim(name made up) to do all the protocols for pretty much everyone.
Then never changed them again, when checksums and all that other stupid stuff was necessary.
I like simple POWERON for example. Makes sense.
It seems to be less and less, I can remember back in the day, all the time doing complex string parsing, for huge hex strings.
Not so much anymore.
From: rickmcneely <rickmcneely@...<mailto:rickmcneely@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 2:22 PM
To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Crappy protocols
Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?
1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.
They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.
|
Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?
1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.
They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.
|
Re: Slider Crosspoint Issue
When I switch crosspoints the slider input value which ends up sitting on the output side of the abuf gets sent to the set volume input of my room module.
Thanks Heath. That is actually an idea I came up with last night and when I compiled I forgot to save the changes to the room module. I'm going to finish it now.
toggle quoted message
Show quoted text
--- In Crestron@..., Heath Volmer <hvolmer@...> wrote:
Are you saying that when you switch crosspoints, that the "previous" room's volume feedback sets the volume in the "new" room?
Maybe if you pass the press associated with the slider through the crosspoint to an ABUF in the zone's logic, then the interface's logic won't force through that value unless it's being pressed. Let the zone or audio device decide when its volume should be changing, (when it's being pressed) and the interface provide presses and feedback only.
I like to send the user interactions as far down the chain as makes sense, as to keep things as abstract as possible. Do the operations as close as possible to the things being operated on, and let the interface merely reflect what the device is doing.
Heath
On May 2, 2013, at 11:25 AM, Jason Andersen <jandersen@...> wrote:
So my problem with the abuf solution is related to the output side of the abuf, it holds it value. So when that interface connects to another audio zone, the output of that abuf sets the volume for the next room it connected to through the crosspoints.
--- In Crestron@..., "jac777888" <jchelton@> wrote:
Or you can use an abuf driven by the digital press join of the slider.
--- In Crestron@..., Nick Mitchell <nick@> wrote:
I just fixed this issue today. Here is what I did.
Analog equate driven off econnect room id that triggers an abuf for each
room that sets tp's analog fb to vol out of that room.
I have 3 sets of xpoints
TP -> Room -> Device
Hope that helps
Nick
Sent from my eMail.
On May 1, 2013, at 7:17 PM, Jason Andersen <jandersen@> wrote:
I attempted this several times and I still can't come up with a viable
solution. I am going to do my best to explain this and if anyone wants to
help it would be appreciated.
I want to use a slider for volume and I use crosspoints for the interfaces
and room modules, like I'm suppose too.
When I use the slider on interface A it sends the volume to the room A
module correctly but that slider value is held in memory.
When I change to room B, interface A still holds the slider value and
changes the volume of Room B to whatever the slider was left at.
My brain hurts.
[Non-text portions of this message have been removed]
|
Re: Samsung UE55ES7000 - EX-Link
this is power toggle, make sure the TV is on, send it right out Samsung_TX$ in debugger "\x08\x22\x00\x00\x00\x00\xD6" _____ From: Crestron@... [mailto:Crestron@...] On Behalf Of grumpy_cake Sent: Thursday, May 02, 2013 9:11 AM To: Crestron@... Subject: [Crestron] Re: Samsung UE55ES7000 - EX-Link At the moment I am using the program that is in the folder with the module from: ed_partner_modules/default.asp?manufacturer_id=134 samsung_un55es8000_v1_0_demo I've changed nothing so would expect it to be set up correctly. I can send commands using Toolbox but nothing happens and I get no feedback from the com port. The module offers lots of sends and feedback. Maybe I should try the UN55ES7500 instead. --- In Crestron@... <mailto:Crestron%40yahoogroups.com> , "cyberbri24" <cyberbri24@...> wrote:
Are you just using the generic CEC mod? I just programmed a UN65Dxxxx and
the Exlink didn;t offer any menu options to turn on so I am only using the Power on and off commands which works only.
--- In Crestron@... <mailto:Crestron%40yahoogroups.com> ,
"grumpy_cake" <crestron@> wrote:
I've gone back to square 1 here to try and get this working.
I've got rid of my program and am just using the one supplied with the
module.
I've uploaded it to my QM-RMC. (Was using an AV2)
I made the cable myself, pins 2,3,5 -> T,R,S tested it with a mm several
times to be sure.
I've also tried changing the baud rate to 115200 as previously
suggested. It's now back on 9600.
I think the key thing here is that I am getting absolutely nothing
coming into SIMPL Debugger on the Rx$ of the com port that the Ex-Link is connected to.
The TV should be spurting something out regardless of what I am sending
it no?
--- In Crestron@... <mailto:Crestron%40yahoogroups.com> ,
"LENREX" <lenrex@> wrote:
If you downloaded the UN55ES8000 module from the website. It's a
straight through cable.
Did you load BOTH the Hardware & Logic modules into your program?
Did you make your own cable, or use a Samsung cable?
I used the UN55ES8000 module on a 46" with a Samsung cable plugged
straight into a MC3 and it worked perfectly. ...wasn't a long run.
--- In Crestron@... <mailto:Crestron%40yahoogroups.com> ,
"grumpy_cake" <crestron@> wrote:
Thanks,
But does this actually apply to me? The pdf regarding the module I
am using has no mention of injecting power...
I am connecting directly from an AV2 to the EX-Link port.
Have I missed something here? When others connect Ex-Link do you not
connect directly?
--- In Crestron@... <mailto:Crestron%40yahoogroups.com>
, "javimanga" <javimanga@> wrote:
Hi!
Check this info about ex-link
rs
Specially this!!!:
"As the TV uses 3.3V TTL levels, the serial input/output has to be
converted to/from TTL levels to RS232 levels (~10-15V). Thus a level shifter is needed. But most computers today, doesn't have an RS232 port, so you also need a USB-to-RS232 serial adapter (cable). Thus its a definite advantage to buy a pre-fabricated USB-to-serial converter using 3.3 Volt TTL levels on the serial side. Common one to look for are based on the PL2303 and FTDI chips. WARNING! RS232 levels are up to 15V, which can cause seriously
damage at your TV!"
Regards,
Javier VM
--- In Crestron@...
<mailto:Crestron%40yahoogroups.com> , "grumpy_cake" <crestron@> wrote:
Hi,
I hope someone can have some patience and spoon feed me through
this as I have sat here for hours and have got nowhere. I am guessing a bit so please let me know if I am doing something stupid.
Firstly this may all be down to me using a module that may not
work as I can't find my TV.
I have a: UE55ES7000
Closest I can find is the UN55ES8000
I've made up a cable for EX-LINK control using the diagram in
the module pdf
(integrated_partner_modules/help_files/959/samsung_un55es8000_v1_0_help.pdf)
Tested cable with multi-meter, seems fine.
I have set the value of the RS232 mode to Debug.
Tried a basic test with the module set up like this:
I'm getting nothing in debugger on Samsung_Rx$ and the TV
responds to nothing.
Any help appreciated.
Thanks.
|
Re: Slider Crosspoint Issue
Are you saying that when you switch crosspoints, that the "previous" room's volume feedback sets the volume in the "new" room? Maybe if you pass the press associated with the slider through the crosspoint to an ABUF in the zone's logic, then the interface's logic won't force through that value unless it's being pressed. Let the zone or audio device decide when its volume should be changing, (when it's being pressed) and the interface provide presses and feedback only. I like to send the user interactions as far down the chain as makes sense, as to keep things as abstract as possible. Do the operations as close as possible to the things being operated on, and let the interface merely reflect what the device is doing. Heath On May 2, 2013, at 11:25 AM, Jason Andersen <jandersen@...> wrote: So my problem with the abuf solution is related to the output side of the abuf, it holds it value. So when that interface connects to another audio zone, the output of that abuf sets the volume for the next room it connected to through the crosspoints.
--- In Crestron@..., "jac777888" <jchelton@...> wrote:
Or you can use an abuf driven by the digital press join of the slider.
--- In Crestron@..., Nick Mitchell <nick@> wrote:
I just fixed this issue today. Here is what I did.
Analog equate driven off econnect room id that triggers an abuf for each
room that sets tp's analog fb to vol out of that room.
I have 3 sets of xpoints
TP -> Room -> Device
Hope that helps
Nick
Sent from my eMail.
On May 1, 2013, at 7:17 PM, Jason Andersen <jandersen@> wrote:
I attempted this several times and I still can't come up with a viable
solution. I am going to do my best to explain this and if anyone wants to
help it would be appreciated.
I want to use a slider for volume and I use crosspoints for the interfaces
and room modules, like I'm suppose too.
When I use the slider on interface A it sends the volume to the room A
module correctly but that slider value is held in memory.
When I change to room B, interface A still holds the slider value and
changes the volume of Room B to whatever the slider was left at.
My brain hurts.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
|
Check Answer ID: 4971 for more details
toggle quoted message
Show quoted text
-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Seth Olle
Sent: Thursday, May 02, 2013 1:39 PM
To: Crestron@...
Subject: Re: [Crestron] Xpanel for Mac
Sadly it is not quite that easy.
You basically have to design an Xpanel that follows the same principles as a IPAD, all graphics etc.
Then you have to install a small piece of software on the mac to actually make the panel work.
Other than that you should be good.
From: Timothy Loiselle <timothyloiselle@...<mailto:timothyloiselle@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 1:36 PM
To: crestron group <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Xpanel for Mac
I am hoping someone can shed some light on this subject for me, please. In some of my classrooms, my teachers have Mac's running parallels with WIN XP just to run xpanel for av control. I have the teachers trained on how to run parallels and the xpanel but I would love to have xpanel for mac installed on their new machines when they come back from summer break. How do I go about doing this? I don't even know where to start.
Thanks,
Tim
[Non-text portions of this message have been removed]
------------------------------------
Check out the Files area for useful modules, documents, and drivers.
A contact list of Crestron dealers and programmers can be found in the Database area.
Yahoo! Groups Links
|
Sadly it is not quite that easy.
You basically have to design an Xpanel that follows the same principles as a IPAD, all graphics etc.
Then you have to install a small piece of software on the mac to actually make the panel work.
Other than that you should be good.
From: Timothy Loiselle <timothyloiselle@...<mailto:timothyloiselle@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 1:36 PM
To: crestron group <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Xpanel for Mac
I am hoping someone can shed some light on this subject for me, please. In some of my classrooms, my teachers have Mac's running parallels with WIN XP just to run xpanel for av control. I have the teachers trained on how to run parallels and the xpanel but I would love to have xpanel for mac installed on their new machines when they come back from summer break. How do I go about doing this? I don't even know where to start.
Thanks,
Tim
[Non-text portions of this message have been removed]
|
I am?hoping?someone can shed some light on this?subject?for me, please. In some of my classrooms, my teachers have Mac's running parallels with WIN XP just to run xpanel for av control. I have the teachers trained on how to run parallels and the xpanel but I would love to have xpanel for mac installed on their new machines when they come back from summer break. How do I go about doing this? I don't even know where to start.
Thanks,
Tim
|
Re: Slider Crosspoint Issue
So my problem with the abuf solution is related to the output side of the abuf, it holds it value. So when that interface connects to another audio zone, the output of that abuf sets the volume for the next room it connected to through the crosspoints.
toggle quoted message
Show quoted text
--- In Crestron@..., "jac777888" <jchelton@...> wrote:
Or you can use an abuf driven by the digital press join of the slider.
--- In Crestron@..., Nick Mitchell <nick@> wrote:
I just fixed this issue today. Here is what I did.
Analog equate driven off econnect room id that triggers an abuf for each
room that sets tp's analog fb to vol out of that room.
I have 3 sets of xpoints
TP -> Room -> Device
Hope that helps
Nick
Sent from my eMail.
On May 1, 2013, at 7:17 PM, Jason Andersen <jandersen@> wrote:
I attempted this several times and I still can't come up with a viable
solution. I am going to do my best to explain this and if anyone wants to
help it would be appreciated.
I want to use a slider for volume and I use crosspoints for the interfaces
and room modules, like I'm suppose too.
When I use the slider on interface A it sends the volume to the room A
module correctly but that slider value is held in memory.
When I change to room B, interface A still holds the slider value and
changes the volume of Room B to whatever the slider was left at.
My brain hurts.
[Non-text portions of this message have been removed]
|
Re: OT: Introducing HDMI to component distribution (PVID/BIPAD) creates ground loop
TV is a two prong unit. We're going to run a temporary RG6 between the TV and cable demarc to see if grounding it that way solves the problem.
toggle quoted message
Show quoted text
--- In Crestron@..., jason santlofer <jason@...> wrote:
Did you try lifting the ground? If that tv even has one.?
Sent from my Verizon Wireless 4G LTE DROID
weddellkw <weddellkw@...> wrote:
??
Thanks for the responses:
The loop is actually present all the time. With no HDMI connection, it is impossible to detect except on a very dark image, as a very thin and dim rolling band. Plugging in the HDMI to any source in the rack causes it to become much larger.
This suggests to me that there has always been a loop issue but it simply wasn't noticed until we put in a big 80" tv. Even then it wasn't noticed until the problem was exacerbated by the addition of HDMI.
The band does not appear on any of the other TV's (older Fujitsu plasmas, component only, and a small Samsung, component only)
I've been on the phone with our tech on-site off and on all morning, and he's tried every permutation we can think of.
Disconnected the cable feed from service.
Powered TV and equipment from one surge protector (Furman) via extension cord.
--- In Crestron@..., "Kol Johnson" <kol.mstc@> wrote:
So, whatever you plug the HDMI cable (and Vanco balun setup) into at the
equipment rack causes the loop to appear on any of the component sources
that run through the pvid?
_____
From: Crestron@... [mailto:Crestron@...] On Behalf
Of weddellkw
Sent: Wednesday, May 01, 2013 1:47 PM
To: Crestron@...
Subject: [Crestron] OT: Introducing HDMI to component distribution
(PVID/BIPAD) creates ground loop
Basically, the above. We've taken over an old analog distribution system,
and recently replaced an old Fujitsu plasma w/ a large Samsung LED unit. No
problem while on component distribution.
We were then asked to connect 'His Cable' to the new TV via HDMI as the
lead-in to a DM system. Pulled 2x Cat6 about 60' and used a Vanco balun to
accomplish this.
We now have a ground loop on component signals (additional cable boxes, BD,
AppleTV gen1) to the Samsung. No issue on the other TVs.
Disconnecting the HDMI from the cable box fixes the issue. Other cable
boxes/BD also reintroduce the loop. Have tried an isolator on the component
connections between the TV and the PVID, and the PVID and the cable box, no
change.
Any suggestions/fixes?
[Non-text portions of this message have been removed]
<!-- #ygrp-mkp { border: 1px solid #d8d8d8; font-family: Arial; margin: 10px 0; padding: 0 10px; } #ygrp-mkp hr { border: 1px solid #d8d8d8; } #ygrp-mkp #hd { color: #628c2a; font-size: 85%; font-weight: 700; line-height: 122%; margin: 10px 0; } #ygrp-mkp #ads { margin-bottom: 10px; } #ygrp-mkp .ad { padding: 0 0; } #ygrp-mkp .ad p { margin: 0; } #ygrp-mkp .ad a { color: #0000ff; text-decoration: none; } #ygrp-sponsor #ygrp-lc { font-family: Arial; } #ygrp-sponsor #ygrp-lc #hd { margin: 10px 0px; font-weight: 700; font-size: 78%; line-height: 122%; } #ygrp-sponsor #ygrp-lc .ad { margin-bottom: 10px; padding: 0 0; } #actions { font-family: Verdana; font-size: 11px; padding: 10px 0; } #activity { background-color: #e0ecee; float: left; font-family: Verdana; font-size: 10px; padding: 10px; } #activity span { font-weight: 700; } #activity span:first-child { text-transform: uppercase; } #activity span a { color: #5085b6; text-decoration: none; } #activity span span { color: #ff7900; } #activity span .underline { text-decoration: underline; } .attach { clear: both; display: table; font-family: Arial; font-size: 12px; padding: 10px 0; width: 400px; } .attach div a { text-decoration: none; } .attach img { border: none; padding-right: 5px; } .attach label { display: block; margin-bottom: 5px; } .attach label a { text-decoration: none; } blockquote { margin: 0 0 0 4px; } .bold { font-family: Arial; font-size: 13px; font-weight: 700; } .bold a { text-decoration: none; } dd.last p a { font-family: Verdana; font-weight: 700; } dd.last p span { margin-right: 10px; font-family: Verdana; font-weight: 700; } dd.last p span.yshortcuts { margin-right: 0; } div.attach-table div div a { text-decoration: none; } div.attach-table { width: 400px; } div.file-title a, div.file-title a:active, div.file-title a:hover, div.file-title a:visited { text-decoration: none; } div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div.photo-title a:visited { text-decoration: none; } div#ygrp-mlmsg #ygrp-msg p a span.yshortcuts { font-family: Verdana; font-size: 10px; font-weight: normal; } .green { color: #628c2a; } .MsoNormal { margin: 0 0 0 0; } o { font-size: 0; } #photos div { float: left; width: 72px; } #photos div div { border: 1px solid #666666; height: 62px; overflow: hidden; width: 62px; } #photos div label { color: #666666; font-size: 10px; overflow: hidden; text-align: center; white-space: nowrap; width: 64px; } #reco-category { font-size: 77%; } #reco-desc { font-size: 77%; } .replbq { margin: 4px; } #ygrp-actbar div a:first-child { /* border-right: 0px solid #000;*/ margin-right: 2px; padding-right: 5px; } #ygrp-mlmsg { font-size: 13px; font-family: Arial, helvetica,clean, sans-serif; *font-size: small; *font: x-small; } #ygrp-mlmsg table { font-size: inherit; font: 100%; } #ygrp-mlmsg select, input, textarea { font: 99% Arial, Helvetica, clean, sans-serif; } #ygrp-mlmsg pre, code { font:115% monospace; *font-size:100%; } #ygrp-mlmsg * { line-height: 1.22em; } #ygrp-mlmsg #logo { padding-bottom: 10px; } #ygrp-msg p a { font-family: Verdana; } #ygrp-msg p#attach-count span { color: #1E66AE; font-weight: 700; } #ygrp-reco #reco-head { color: #ff7900; font-weight: 700; } #ygrp-reco { margin-bottom: 20px; padding: 0px; } #ygrp-sponsor #ov li a { font-size: 130%; text-decoration: none; } #ygrp-sponsor #ov li { font-size: 77%; list-style-type: square; padding: 6px 0; } #ygrp-sponsor #ov ul { margin: 0; padding: 0 0 0 8px; } #ygrp-text { font-family: Georgia; } #ygrp-text p { margin: 0 0 1em 0; } #ygrp-text tt { font-size: 120%; } #ygrp-vital ul li:last-child { border-right: none !important; } --> [Non-text portions of this message have been removed]
|
Remote Acess by Apple Time Capsule
Dear friends how are you?
I'm needing a little help from you guys, my client is going to travel to the USA on Saturday, he wants to remotely access your home via the ipad, but I'm not getting properly set up remote access, create the account correctly dindnsfuncionando pis Tenos 08 IP cameras he envisions the ipad anywhere), set up the doors of the Time Capsule (at least imagine that they were done correctly), but try connectar ipad web I have only the status bar to load the system and nothing else .
Someone would have a little tutorial or any tips to get to make this work, I was informed by another developer in Brazil that the Time Capsule is what might be causing this problem myself, I think this should not be the reason.
Please help me because I have only today and tomorrow to make it work.
Thanks in advance everyone's attention.
Marino Penteado
Integration Expert
|
Re: OT: Introducing HDMI to component distribution (PVID/BIPAD) creates ground loop
Did you try lifting the ground? If that tv even has one.? Sent from my Verizon Wireless 4G LTE DROID weddellkw <weddellkw@...> wrote: ?
Thanks for the responses:
The loop is actually present all the time. With no HDMI connection, it is impossible to detect except on a very dark image, as a very thin and dim rolling band. Plugging in the HDMI to any source in the rack causes it to become much larger.
This suggests to me that there has always been a loop issue but it simply wasn't noticed until we put in a big 80" tv. Even then it wasn't noticed until the problem was exacerbated by the addition of HDMI.
The band does not appear on any of the other TV's (older Fujitsu plasmas, component only, and a small Samsung, component only)
I've been on the phone with our tech on-site off and on all morning, and he's tried every permutation we can think of.
Disconnected the cable feed from service.
Powered TV and equipment from one surge protector (Furman) via extension cord.
--- In Crestron@..., "Kol Johnson" <kol.mstc@...> wrote:
So, whatever you plug the HDMI cable (and Vanco balun setup) into at the
equipment rack causes the loop to appear on any of the component sources
that run through the pvid?
_____
From: Crestron@... [mailto:Crestron@...] On Behalf
Of weddellkw
Sent: Wednesday, May 01, 2013 1:47 PM
To: Crestron@...
Subject: [Crestron] OT: Introducing HDMI to component distribution
(PVID/BIPAD) creates ground loop
Basically, the above. We've taken over an old analog distribution system,
and recently replaced an old Fujitsu plasma w/ a large Samsung LED unit. No
problem while on component distribution.
We were then asked to connect 'His Cable' to the new TV via HDMI as the
lead-in to a DM system. Pulled 2x Cat6 about 60' and used a Vanco balun to
accomplish this.
We now have a ground loop on component signals (additional cable boxes, BD,
AppleTV gen1) to the Samsung. No issue on the other TVs.
Disconnecting the HDMI from the cable box fixes the issue. Other cable
boxes/BD also reintroduce the loop. Have tried an isolator on the component
connections between the TV and the PVID, and the PVID and the cable box, no
change.
Any suggestions/fixes?
[Non-text portions of this message have been removed]
<!-- #ygrp-mkp { border: 1px solid #d8d8d8; font-family: Arial; margin: 10px 0; padding: 0 10px; } #ygrp-mkp hr { border: 1px solid #d8d8d8; } #ygrp-mkp #hd { color: #628c2a; font-size: 85%; font-weight: 700; line-height: 122%; margin: 10px 0; } #ygrp-mkp #ads { margin-bottom: 10px; } #ygrp-mkp .ad { padding: 0 0; } #ygrp-mkp .ad p { margin: 0; } #ygrp-mkp .ad a { color: #0000ff; text-decoration: none; } #ygrp-sponsor #ygrp-lc { font-family: Arial; } #ygrp-sponsor #ygrp-lc #hd { margin: 10px 0px; font-weight: 700; font-size: 78%; line-height: 122%; } #ygrp-sponsor #ygrp-lc .ad { margin-bottom: 10px; padding: 0 0; } #actions { font-family: Verdana; font-size: 11px; padding: 10px 0; } #activity { background-color: #e0ecee; float: left; font-family: Verdana; font-size: 10px; padding: 10px; } #activity span { font-weight: 700; } #activity span:first-child { text-transform: uppercase; } #activity span a { color: #5085b6; text-decoration: none; } #activity span span { color: #ff7900; } #activity span .underline { text-decoration: underline; } .attach { clear: both; display: table; font-family: Arial; font-size: 12px; padding: 10px 0; width: 400px; } .attach div a { text-decoration: none; } .attach img { border: none; padding-right: 5px; } .attach label { display: block; margin-bottom: 5px; } .attach label a { text-decoration: none; } blockquote { margin: 0 0 0 4px; } .bold { font-family: Arial; font-size: 13px; font-weight: 700; } .bold a { text-decoration: none; } dd.last p a { font-family: Verdana; font-weight: 700; } dd.last p span { margin-right: 10px; font-family: Verdana; font-weight: 700; } dd.last p span.yshortcuts { margin-right: 0; } div.attach-table div div a { text-decoration: none; } div.attach-table { width: 400px; } div.file-title a, div.file-title a:active, div.file-title a:hover, div.file-title a:visited { text-decoration: none; } div.photo-title a, div.photo-title a:active, div.photo-title a:hover, div.photo-title a:visited { text-decoration: none; } div#ygrp-mlmsg #ygrp-msg p a span.yshortcuts { font-family: Verdana; font-size: 10px; font-weight: normal; } .green { color: #628c2a; } .MsoNormal { margin: 0 0 0 0; } o { font-size: 0; } #photos div { float: left; width: 72px; } #photos div div { border: 1px solid #666666; height: 62px; overflow: hidden; width: 62px; } #photos div label { color: #666666; font-size: 10px; overflow: hidden; text-align: center; white-space: nowrap; width: 64px; } #reco-category { font-size: 77%; } #reco-desc { font-size: 77%; } .replbq { margin: 4px; } #ygrp-actbar div a:first-child { /* border-right: 0px solid #000;*/ margin-right: 2px; padding-right: 5px; } #ygrp-mlmsg { font-size: 13px; font-family: Arial, helvetica,clean, sans-serif; *font-size: small; *font: x-small; } #ygrp-mlmsg table { font-size: inherit; font: 100%; } #ygrp-mlmsg select, input, textarea { font: 99% Arial, Helvetica, clean, sans-serif; } #ygrp-mlmsg pre, code { font:115% monospace; *font-size:100%; } #ygrp-mlmsg * { line-height: 1.22em; } #ygrp-mlmsg #logo { padding-bottom: 10px; } #ygrp-msg p a { font-family: Verdana; } #ygrp-msg p#attach-count span { color: #1E66AE; font-weight: 700; } #ygrp-reco #reco-head { color: #ff7900; font-weight: 700; } #ygrp-reco { margin-bottom: 20px; padding: 0px; } #ygrp-sponsor #ov li a { font-size: 130%; text-decoration: none; } #ygrp-sponsor #ov li { font-size: 77%; list-style-type: square; padding: 6px 0; } #ygrp-sponsor #ov ul { margin: 0; padding: 0 0 0 8px; } #ygrp-text { font-family: Georgia; } #ygrp-text p { margin: 0 0 1em 0; } #ygrp-text tt { font-size: 120%; } #ygrp-vital ul li:last-child { border-right: none !important; } --> [Non-text portions of this message have been removed]
|
Re: OT: Introducing HDMI to component distribution (PVID/BIPAD) creates ground loop
Thanks for the responses:
The loop is actually present all the time. With no HDMI connection, it is impossible to detect except on a very dark image, as a very thin and dim rolling band. Plugging in the HDMI to any source in the rack causes it to become much larger.
This suggests to me that there has always been a loop issue but it simply wasn't noticed until we put in a big 80" tv. Even then it wasn't noticed until the problem was exacerbated by the addition of HDMI.
The band does not appear on any of the other TV's (older Fujitsu plasmas, component only, and a small Samsung, component only)
I've been on the phone with our tech on-site off and on all morning, and he's tried every permutation we can think of.
Disconnected the cable feed from service.
Powered TV and equipment from one surge protector (Furman) via extension cord.
toggle quoted message
Show quoted text
--- In Crestron@..., "Kol Johnson" <kol.mstc@...> wrote:
So, whatever you plug the HDMI cable (and Vanco balun setup) into at the
equipment rack causes the loop to appear on any of the component sources
that run through the pvid?
_____
From: Crestron@... [mailto:Crestron@...] On Behalf
Of weddellkw
Sent: Wednesday, May 01, 2013 1:47 PM
To: Crestron@...
Subject: [Crestron] OT: Introducing HDMI to component distribution
(PVID/BIPAD) creates ground loop
Basically, the above. We've taken over an old analog distribution system,
and recently replaced an old Fujitsu plasma w/ a large Samsung LED unit. No
problem while on component distribution.
We were then asked to connect 'His Cable' to the new TV via HDMI as the
lead-in to a DM system. Pulled 2x Cat6 about 60' and used a Vanco balun to
accomplish this.
We now have a ground loop on component signals (additional cable boxes, BD,
AppleTV gen1) to the Samsung. No issue on the other TVs.
Disconnecting the HDMI from the cable box fixes the issue. Other cable
boxes/BD also reintroduce the loop. Have tried an isolator on the component
connections between the TV and the PVID, and the PVID and the cable box, no
change.
Any suggestions/fixes?
[Non-text portions of this message have been removed]
|
Kris K