开云体育

--- In Crestron@..., Robert Parker <robertparkernc@...> wrote:

To add to this, I had one unit that even using command line I gave up and
plugged in with a USB cable before I got everything to work right. It was a
unit I had been doing development work on and something got screwy. After I
USBed into it and did both initialize and restore everything got better.
Mind you it had been running deployed code so I don't know what was up.
Over all it can be a 'quirky' box but once you get it working it seems to
be stable.

On Tue, May 21, 2013 at 3:07 PM, jbudz1977 <jbudz1977@...> wrote:

**


Toolbox has been broken for a long time when using the System Info tool to
adjust network settings on a DMPS. Try using the terminal commands and
things will work way better for you.

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

I have a DMPS-300 and I keep getting this error after a reboot when I'm

trying to disable both the DHCP and the Private Network mode:

"Timeout waiting for the device to respond to the command

privatenetconfig<LF>. Waiting for one of the following tokens
[C2I-DMPS-300-VIDEO>]."

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

--- In Crestron@..., Heath Volmer <hvolmer@...> wrote:

Based on someone's hint here and for ease in renaming: Where there are logic groups that require multiple ID changes after a copy/paste, I make the 5-digit IDs from a 2-digit "type", 2-digit "zone", 1-digit "function". For example, audio zones (rooms) have four different crosspoints in their logic. Room 10's crosspoints might be numbered 40102, 40105, 40106, 40109. When it comes time to copy/paste, I can then F9 "4010" to "4016" to represent room 16.

In other places - source devices, single-crosspoint things, other things at the "end" of the chain - I just number them sequentially but in a separate number range (450nn).

I chose odd ranges of numbers because it seems rather unlikely that I will have coded a 40106 or a 40xx2 in the logic, thus eliminating the possibility of unintentional renames.

Using the 40xxn numbers requires a little more math. Switching rooms essentially requires me to take 46002 + (room * 10) to get the right ID.

Heath

On May 22, 2013, at 7:01 AM, Jay Basen <jay.m.basen@...> wrote:

I'm curious what numbering schemes other people are using for their crosspoint equipment and control symbols to keep things straight and make code easy to cut and paste in a large residential system with a lot of touch panels, rooms, and equipment. Previously, I've started numbering my equipment symbols at 1 and my rooms are numbered in increments of 1000. So, for example, DirecTV box 1 would have an ID of 1. Then the control symbol for DirecTV in room 1 would have an ID of 1001 (adding the equipment ID to the Room ID). In room 2 the control crosspoint symbol for DirecTV box 1 would be numbered 2001.

I've found this easy to keep straight but I've run into issues as the number of touch panels, rooms, and equipment has grown in a large system given the limitation of the crosspoint ID being an integer. I'm curious if others have a better numbering scheme

Thanks in advance

Jay

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

-----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Jay Basen
Sent: Wednesday, May 22, 2013 10:17 AM
To: Crestron@...
Subject: Re: [Crestron] crosspoint numbering schemes

Thanks Heath.

----- Original Message -----
From: "Heath Volmer" <hvolmer@...>
To: Crestron@...
Sent: Wednesday, May 22, 2013 8:03:01 AM
Subject: Re: [Crestron] crosspoint numbering schemes

Based on someone's hint here and for ease in renaming: Where there are logic groups that require multiple ID changes after a copy/paste, I make the 5-digit IDs from a 2-digit "type", 2-digit "zone", 1-digit "function". For example, audio zones (rooms) have four different crosspoints in their logic. Room 10's crosspoints might be numbered 40102, 40105, 40106, 40109. When it comes time to copy/paste, I can then F9 "4010" to "4016" to represent room 16.

In other places - source devices, single-crosspoint things, other things at the "end" of the chain - I just number them sequentially but in a separate number range (450nn).

I chose odd ranges of numbers because it seems rather unlikely that I will have coded a 40106 or a 40xx2 in the logic, thus eliminating the possibility of unintentional renames.

Using the 40xxn numbers requires a little more math. Switching rooms essentially requires me to take 46002 + (room * 10) to get the right ID.

Heath

On May 22, 2013, at 7:01 AM, Jay Basen <jay.m.basen@...> wrote:

I'm curious what numbering schemes other people are using for their crosspoint equipment and control symbols to keep things straight and make code easy to cut and paste in a large residential system with a lot of touch panels, rooms, and equipment. Previously, I've started numbering my equipment symbols at 1 and my rooms are numbered in increments of 1000. So, for example, DirecTV box 1 would have an ID of 1. Then the control symbol for DirecTV in room 1 would have an ID of 1001 (adding the equipment ID to the Room ID). In room 2 the control crosspoint symbol for DirecTV box 1 would be numbered 2001.

I've found this easy to keep straight but I've run into issues as the number of touch panels, rooms, and equipment has grown in a large system given the limitation of the crosspoint ID being an integer. I'm curious if others have a better numbering scheme

Thanks in advance

Jay

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



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





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



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

----- Original Message -----
From: "Heath Volmer" <hvolmer@...>
To: Crestron@...
Sent: Wednesday, May 22, 2013 8:03:01 AM
Subject: Re: [Crestron] crosspoint numbering schemes

Based on someone's hint here and for ease in renaming: Where there are logic groups that require multiple ID changes after a copy/paste, I make the 5-digit IDs from a 2-digit "type", 2-digit "zone", 1-digit "function". For example, audio zones (rooms) have four different crosspoints in their logic. Room 10's crosspoints might be numbered 40102, 40105, 40106, 40109. When it comes time to copy/paste, I can then F9 "4010" to "4016" to represent room 16.

In other places - source devices, single-crosspoint things, other things at the "end" of the chain - I just number them sequentially but in a separate number range (450nn).

I chose odd ranges of numbers because it seems rather unlikely that I will have coded a 40106 or a 40xx2 in the logic, thus eliminating the possibility of unintentional renames.

Using the 40xxn numbers requires a little more math. Switching rooms essentially requires me to take 46002 + (room * 10) to get the right ID.

Heath

On May 22, 2013, at 7:01 AM, Jay Basen <jay.m.basen@...> wrote:

I'm curious what numbering schemes other people are using for their crosspoint equipment and control symbols to keep things straight and make code easy to cut and paste in a large residential system with a lot of touch panels, rooms, and equipment. Previously, I've started numbering my equipment symbols at 1 and my rooms are numbered in increments of 1000. So, for example, DirecTV box 1 would have an ID of 1. Then the control symbol for DirecTV in room 1 would have an ID of 1001 (adding the equipment ID to the Room ID). In room 2 the control crosspoint symbol for DirecTV box 1 would be numbered 2001.

I've found this easy to keep straight but I've run into issues as the number of touch panels, rooms, and equipment has grown in a large system given the limitation of the crosspoint ID being an integer. I'm curious if others have a better numbering scheme

Thanks in advance

Jay

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



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

----- Original Message -----

From: "Neil Dorin" <neildorin@...>
To: Crestron@...
Sent: Wednesday, May 22, 2013 7:22:09 AM
Subject: Re: [Crestron] crosspoint numbering schemes





I separate my crosspoint IDs into groups with at least 100d between each group. Then I use ASUMs to add the difference to a common set of integers.

This way if I want an "infinitely" scalable set of crosspoints for say audio zones, I start counting at 1d and increment by 1d for each additional zone. My ASUM for audio zones adds 1000d so the actual crosspoint IDs become 1001d-1099d. (I limit my scalability to 100 Zones)

For lighting I still count starting at 1d but add 2000d, and so forth.

Even if you were to limit your scalability to 1000 of each group of crosspoints you'd still have up to 64 groups of crosspoint subsets. (Based on the limitation in SIMPL that crosspoint IDs are a 16 bit number)

The other rule i have is to always use comments with the crosspoint ID visible at the to top folder level you will copy and paste to create a new "zone". This way when you F9 rename you can rename the signals and crosspoint ID and see visual confirmation in the folder comment without having to drill down to the crosspoint symbols, open them up and scroll to the bottom to change the ID.
On 2013-05-22, at 7:01 AM, Jay Basen < jay.m.basen@... > wrote:

I'm curious what numbering schemes other people are using for their crosspoint equipment and control symbols to keep things straight and make code easy to cut and paste in a large residential system with a lot of touch panels, rooms, and equipment. Previously, I've started numbering my equipment symbols at 1 and my rooms are numbered in increments of 1000. So, for example, DirecTV box 1 would have an ID of 1. Then the control symbol for DirecTV in room 1 would have an ID of 1001 (adding the equipment ID to the Room ID). In room 2 the control crosspoint symbol for DirecTV box 1 would be numbered 2001.

I've found this easy to keep straight but I've run into issues as the number of touch panels, rooms, and equipment has grown in a large system given the limitation of the crosspoint ID being an integer. I'm curious if others have a better numbering scheme

Thanks in advance

Jay

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

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

I have a raspberry pi with openelect(xbmc) installed.
i just soldered up an IR receiver to the GPIO ports and learned a remote to control it. (or use a pre defined remote like a MCE/apple tv)
it has cec control so you can also use the tv remote via HDMI connection (tried this but a bit slow for my liking)
also being xbmc you can use the crestron module using json commands.

does this help?

On May 22, 2013, at 6:41 AM, "ChrisK" <chris@...> wrote:

I HATE that Error!!!!!!! Arrghhh -

Although I haven't seen it nearly as much lately, I did find a 'work-around' for it. One or more of the following seems to get you out of it for the moment:

-Try compiling with just F12, and or Alt-F12
-Compile an open VTPro file and then try your SMW
-Combo of Above, Add a few SMW saves in between
-Close and reopen your SMW project, or Open an different SMW project then reopen the One that you need to compile - Save and Compile...
-Shoot yourself in the head (I haven't actually tried this one yet!)

Chris K..........;)

--- In Crestron@..., Heath Volmer <hvolmer@...> wrote:

Include4.dat not found. Please check for presence of Device Database.

Has anyone seen this message when trying to compile? I have to hit F12 three or four times before it will finally fire up. I just reinstalled the DB.

On 2013-05-22, at 7:01 AM, Jay Basen <jay.m.basen@...> wrote:

I'm curious what numbering schemes other people are using for their crosspoint equipment and control symbols to keep things straight and make code easy to cut and paste in a large residential system with a lot of touch panels, rooms, and equipment. Previously, I've started numbering my equipment symbols at 1 and my rooms are numbered in increments of 1000. So, for example, DirecTV box 1 would have an ID of 1. Then the control symbol for DirecTV in room 1 would have an ID of 1001 (adding the equipment ID to the Room ID). In room 2 the control crosspoint symbol for DirecTV box 1 would be numbered 2001.

I've found this easy to keep straight but I've run into issues as the number of touch panels, rooms, and equipment has grown in a large system given the limitation of the crosspoint ID being an integer. I'm curious if others have a better numbering scheme

Thanks in advance

Jay

--- In Crestron@..., "zorixnv" <koen.kips@...> wrote:

Hi,

We are working on this too. DO you still need more information?

Koen

--- In Crestron@..., "ics_crestron" <sergio.caridi@> wrote:

Hi folks

I'm working on a crestron- modbus TCP integration, does anyone have a sample prj or usefull documentation?

thanks in advance

Sergio

--- In Crestron@..., Heath Volmer <hvolmer@...> wrote:

Include4.dat not found. Please check for presence of Device Database.

Has anyone seen this message when trying to compile? I have to hit F12 three or four times before it will finally fire up. I just reinstalled the DB.

--- In Crestron@..., Heath Volmer <hvolmer@...> wrote:

Include4.dat not found. Please check for presence of Device Database.

Has anyone seen this message when trying to compile? I have to hit F12 three or four times before it will finally fire up. I just reinstalled the DB.

--- In Crestron@..., "ronw" <ron@...> wrote:

Input would be appreciated. Is it normal for a TPMC-9l to have slow page flips and slow graphic updates as well. Every page flips takes 2-3 seconds while a blue bar gauge sits in middle of screen? Also when using the video switcher widget, when you leave this page and return the screens do not indicate the sources they are all blank. This is my first project with this touchpanel and first using Core3. TIA

--- In Crestron@..., "Javier Huerta" <jav-gen@...> wrote:

Oliver,



From my understanding from the Apple tech web pages, the iPads and iPhones
automatically work on the wi-fi network for data if connected to one, and
only use the cellular signal for phone usage.



If your client is having issues even with wi-fi, it could just be a bad
wireless router or broadband service. Some of the less expensive smaller
routers tend to have very poor performance even with higher broadband data
rates.







From: Crestron@... [mailto:Crestron@...] On Behalf
Of Oliver
Sent: Tuesday, May 21, 2013 2:22 PM
To: Crestron@...
Subject: [Crestron] Ipads with cellular service + Mobile Pro G






I have a client and 3 out of 4 of her Ipads are cellular capable on AT&T,
and she lives in an area of terrible cell reception. The result of this, and
not the best wi-fi, is that the 3 AT&T ipads do a lot of "connection
interrupted" while on the Crestron Mobile Pro G app and the basic wifi only
first gen ipad is quite a bit better, but not perfect. If you turn off the
cellular service on the cellular ones, they get better too.

Obviously the situation can be improved with better wifi, but I was also
wondering if anyone has been down the path of trying to automate turning off
the cellular service when on a particular wifi network to force wifi only. I
know I could do this with the Android Tasker App (it's an amazing app), not
sure the equivalent exists for IOs.

Thx

OP

--- In Crestron@..., Heath Volmer <hvolmer@...> wrote:

Include4.dat not found. Please check for presence of Device Database.

Has anyone seen this message when trying to compile? I have to hit F12 three or four times before it will finally fire up. I just reinstalled the DB.