开云体育

Not done on the panel itself. The TOGGLE symbol in SIMPL Windows is what

- Chip


--- In Crestron@..., "cheinemann605" <cheinemann@> wrote:

I am having some issues with toggle buttons. Where is a button

Not done on the panel itself. The TOGGLE symbol in SIMPL Windows is what you're looking for...

- Chip


--- In Crestron@..., "cheinemann605" <cheinemann@> wrote:

I am having some issues with toggle buttons. Where is a button configured to be a toggle? is this done with VT-PRO, or is it done with a toggle command in SIMPL?

Not sure about the example you listed below, but "Arrakis Multi-Zone Single-Port with Setup Pro2 Demo v2.smw" has multiple touchpanels controlling multiple Arrakis zones.

Also, I believe it was Neil Dorin who recently posted some links to really awesome pictures illustrating how this all works.

-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of davidwestgate@...
Sent: Wednesday, March 20, 2013 5:03 PM
To: Crestron@...
Subject: [Crestron] Crosspoint routing - please help

Hey guys, I know this topic has come up before, but I am really trying to get my head around crosspoint routing. Can anyone please assist me as the Crestron IPM example from Arrakis Systems DC6-1000 does not seem to contain any ecross or ccross symbols. Could someone please post an example program or point me to one that contains working ecross, ccross symbols connected to touch panels and devices. Many thanks in advance! Dave



------------------------------------



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

pass me an e-mail address and I will send what I have.

--- In Crestron@..., "Adam" <adam@> wrote:

Hi All

Has anyone written a module for Interact Pro Presets. I cannot see macros strings And is there only 4 presets, that you can setup?. We have used converge products with no problems.

A week or so ago, we were hung up in a nightmare EX install where none of the EX dimmers or MLX3 would acquire. Wi-spy scans showed lots of not-too-high level interference across the spectrum.

I'm back in town today. I fought here and there, bringing the MC3 up to the dimmers, and managed to get some of them going. Finally, today, starting from the gateway and working outward, I was able to get the rest of them going.

I have a couple of theories:

1: There is a Chinese microwave spy station broadcasting out of the 30M house next door that just happened to be offline for the duration of my acquisition procedure.

2: All of these silly dimmers are spitting out "wide" band interference of some sort until they are acquired and locked into a channel. After more and more are locked in, the spectrum gets cleared out until the last one finishes up. They also build up their mesh and adjust accordingly of course.

Does anyone have any good knowledge of how these things behave before and during acquisition? I'll do some research. Might be smart to start acquiring as they get powered up.


Heath Volmer
Digital Domain Systems
Littleton, CO

Can you use a non-dimmable load like a florescent light with a CLW-DIMEX-P set in switch mode or do you have to use CLW-SWEX-P?



--- In Crestron@..., "focusontheworldd" <eaposition@> wrote:

We've installed about a thousand of these and the CLW-SWEX-Ps with great success. They are reliable and fairly durable with most of the features we've needed. The acquisition process is a little tedious, especially for a large installation. The gateway can support a lot of devices with good response time. The infiNet Diagnostic Tool is great for determining where there are "holes" in the coverage. We've only used these with D3Pro and that interface is feature-rich. We seldom see them falling off the network. We would always prefer the C2N-CBDs with CLX-xDIMx modules in a CAEN cabinet but retrofits often preclude that approach.

Here's the things on our wish list for these dimmers:
1. Backlighting
2. Consistent button layouts with the other Cameos like INET-CBD and C2N-CBD. These are 6 button units and the CLW are 4 button so sometimes it's hard to get a uniform look at one site.
3. Even pressure side to side. The mechanical guts of the dimmer is on one side so pressing that side takes less pressure than the other. Missed presses are significantly higher on the "other side". It would have been good if the mechanism was on both sides of the button for consistent user results.
4. Can sometimes strip the terminals if torqued to typical electrician torque levels.
HTH. Tom


--- In Crestron@..., "avselec" <peter@> wrote:

Hi Group,
I am considering specifying the clw-dimex-p wallbox dimmers for a project. I'm interested to know the group's experience with this product. More specifically:
1. reliability
2. durability
3. feature set
4. performance
5. pros
6. cons

Thanks in advance for any opinions you have to share about this product.

Peter

Alright, I'm still having issues with this.

Last night I installed the XBMCubuntu distro on a USB stick and booted my main home machine off of that. Got it up and running, then tried to connect to it with my CP3. No go. Same socket -1 error, though I was still getting feedback, like before.

So this is a different machine running xbmc, on a different OS, on a different LAN from my office, and still having trouble.

I wiped the program out on the CP3 and uploaded a new program with just a TCP/IP symbol configured for port 9090. I was able to connect to the xbmc machine just fine with that, and I could see json strings coming back into the CP3 when I would get a video playing with my mouse. I didn't have any strings ready to send to the machine, so I couldn't test the other direction.

This would lead me to believe it isn't a network, or port, or firewall issue. Has anyone seen this working on a CP3? If so, what version of firmware?

Thanks!



--- In Crestron@..., Marc Nield <nieldm@> wrote:

Strange. The issues are usually port related, what is the http port set to? Default is 8080 I think but it's quite common for other stuff to be talking on that number. Doesn't sound likely but worth a look.

Happy to kick this around offline if you prefer to email me.


On Wednesday, 13 February 2013 at 17:27, floyd1212 wrote:

No, when I press XBMC_BUTTON_STOP, for example, I get the socket error in Debugger telling me I am not connected. But if I stop the current video using a mouse with the on-screen controls on the xbmc machine, the feedback for XBMC_STOP_FB is updated.

I can't figure out how I don't have a connection to send, but I seem to have a connection to receive.

--- In Crestron@... (mailto:Crestron%40yahoogroups.com), Marc Nield wrote:

I have a Squeezebox Server on 9090 which I preferred not to mess with. You can change it an advancedsettings.xml, as described here . It shouldn't, of course, make any difference.

Do you have at least the remote controls via the "XBMC_BUTTON_xxx" signals?

Marc

On 13 Feb 2013, at 16:49, floyd1212 wrote:

Marc,

You changed from port 9090 to 8090? Was this because you were having a problem with the default 9090 port, or for some other reason?

How is changing the port accomplished, by adding the appropriate tags in advancedsettings.xml? I tried this, but I may not have done it properly.

Thanks.

--- In Crestron@... (mailto:Crestron%40yahoogroups.com), Marc Nield wrote:

The latest version of the module is working fine for me on Frodo. I changed the default port to 8090 but that's about it.

All feedback present and correct.

Marc

[Non-text portions of this message have been removed]

We've installed about a thousand of these and the CLW-SWEX-Ps with great success. They are reliable and fairly durable with most of the features we've needed. The acquisition process is a little tedious, especially for a large installation. The gateway can support a lot of devices with good response time. The infiNet Diagnostic Tool is great for determining where there are "holes" in the coverage. We've only used these with D3Pro and that interface is feature-rich. We seldom see them falling off the network. We would always prefer the C2N-CBDs with CLX-xDIMx modules in a CAEN cabinet but retrofits often preclude that approach.

Here's the things on our wish list for these dimmers:
1. Backlighting
2. Consistent button layouts with the other Cameos like INET-CBD and C2N-CBD. These are 6 button units and the CLW are 4 button so sometimes it's hard to get a uniform look at one site.
3. Even pressure side to side. The mechanical guts of the dimmer is on one side so pressing that side takes less pressure than the other. Missed presses are significantly higher on the "other side". It would have been good if the mechanism was on both sides of the button for consistent user results.
4. Can sometimes strip the terminals if torqued to typical electrician torque levels.
HTH. Tom


--- In Crestron@..., "avselec" <peter@> wrote:

Hi Group,
I am considering specifying the clw-dimex-p wallbox dimmers for a project. I'm interested to know the group's experience with this product. More specifically:
1. reliability
2. durability
3. feature set
4. performance
5. pros
6. cons

Thanks in advance for any opinions you have to share about this product.

Peter

--- On Wednesday, March 20, 2013 at 6:55 PM, Sean wrote:

Any HAI modules available out there besides the Infusebox set? I've looked
at Tony's module available from the HAI website, but I need feedback
support for more than 96 zones, as well as individual zone status. Control
system will be a CP3, or I may run it standalone on an AV2. Thanks in
advance!

~Sean

Here is another piece of the pie, after thinking about your Rx error thing, I had an idea. I went into the Simpl program and commented out everything associated with the ADMS and then disconnected it from the network. WOW... all poop broke loose... now it is vertually impossible to pull up the error log and when I try I get the following error...

The socket connection was closed with socket error 10053.

hows that for fun....

Thanks,
DAVE

--- In Crestron@..., "innoventgroup" <innoventgroup@> wrote:

Ok.. it had 3 Rx overruns... one more piece of info... this seemed that it started when Crestron released their latest firmware for the ADMS.. And, now that you bring it up... that may correspond to the overruns... what do you think?

--- In Crestron@..., "Sean" <sound.scan@> wrote:

I've seen this happen with 2-series control systems when they're slammed with broadcast traffic. The HW watchdog will reset the NIC after too many RX buffer overflows. Have you added anything to your network recently? Or any software that performs automatic device discovery?

In text console type EST /V and look at the RX overrun counter.

--- In Crestron@..., "innoventgroup" <innoventgroup@> wrote:

Ok.. I am totally baffeled. I have tried everything and cant seem to figure out what is causing the following errors.

System log:

1. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 02:54:41 3-12-13 UpTime: 0 days 02:11:18.91 Task: EnetLISR
2. Notice: Link established on LAN A
TimeStamp: 02:54:45 3-12-13 UpTime: 0 days 02:11:22.33 Task: PhyInitA
3. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:38:16 3-12-13 UpTime: 0 days 02:54:53.78 Task: EnetLISR
4. Notice: Link established on LAN A
TimeStamp: 03:38:20 3-12-13 UpTime: 0 days 02:54:57.54 Task: PhyInitA
5. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:38:22 3-12-13 UpTime: 0 days 02:54:59.26 Task: EnetLISR
6. Notice: Link established on LAN A
TimeStamp: 03:38:27 3-12-13 UpTime: 0 days 02:55:04.69 Task: PhyInitA
7. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:48:24 3-12-13 UpTime: 0 days 03:05:01.19 Task: EnetLISR
8. Notice: Link established on LAN A
TimeStamp: 03:48:27 3-12-13 UpTime: 0 days 03:05:04.62 Task: PhyInitA
9. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:49:28 3-12-13 UpTime: 0 days 03:06:05.01 Task: EnetLISR
10. Notice: Link established on LAN A
TimeStamp: 03:49:31 3-12-13 UpTime: 0 days 03:06:08.77 Task: PhyInitA
11. Warning: Lost Ethernet link on LAN A. (flags = 1)
TimeStamp: 03:50:03 3-12-13 UpTime: 0 days 03:06:39.90 Task: EnetLISR
12. Notice: Link established on LAN A
TimeStamp: 03:50:07 3-12-13 UpTime: 0 days 03:06:43.66 Task: PhyInitA

This error continues to repeat (I think it is up to 120 times right now). Can anyone tell me what changed that is causig this? It seemed to start when I updated the system with a modification that had nothig to do with a lan connection. I have wireless broadband and they are updating it to a faster speed. The problem is that it goes on and off continually. These errors seem to correspond to this up and down access to the inet. Any suggestions?

Please Help,
DAVE

If you have a Batteries Plus around you they can make 1 for you.

Pat M


From: cheinemann605 <cheinemann@...>
Reply-To: <Crestron@...>
Date: Wednesday, March 20, 2013 5:03 PM
To: <Crestron@...>
Subject: [Crestron] TPMC-10 battery






does anybody know where I can get a replacement battery for a TPMC-10?









[Non-text portions of this message have been removed]

I use NVRAMDISK 64k, NVRAMDISK 128k, and if you want to send it from your program via the console symbol add a V to the command, ie: VNVRAMDISK 64K&#92;r

--- In Crestron@..., Rafael Costa <rafaelg.costa@> wrote:

Yes, you?re right!


NVRAMDiskSetSize

Sets the size of the NVRAM disk or disables it.

*Inputs:*

1. |int| - Desired size of NVRAM disk in Kb. See for available
sizes per disk.


Em 20/03/2013 15:47, cyberbri24 escreveu:

NVRAMDiskSetSize 64

--- In Crestron@... <mailto:Crestron%40yahoogroups.com>,
"cyberbri24" <cyberbri24@> wrote:

Is there a secret command to script for enabling NVRAM in multiple

processors

?

[Non-text portions of this message have been removed]