Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Crestron
- Messages
Search
|
Re: NVX programming jump start
I would have agreed that Director saves time setting up and updating NVX's originally, but since the release of the NVXTool, most of the needed setup functionality that made the Director worthwhile went away.? For programming, if your under 50 sources (?), then just setup subscriptions and then routing the NVX's streams is the SAME as it is on the director (a single analog value for source stream #).? This is how I've done nearly ALL NVX deployments (using subscriptions).? I've never had a deployment yet that forced me to use serial$ addresses to make the routes, but that wouldn't be much more difficult than analog when/if needed.
?
The downside to the director that I've seen, is when companies engineer systems that have multiple rooms containing NVX and control, and they spec in 1 director for all the NVX's in all the rooms.? That's fine for the setup of them, but for programming and control, it makes no sense to have multiple rooms trying to share a single director so they can do local routing in their local room.? Then you have to architect your programs so that everything for routing funnels down to a single program (single point of failure) that controls the director and EISC's to the other programs.? That is not the best architecture method when you can avoid it (especially for critical functions like routing).? It's much better to have each room directly connect to the NVX endpoints in the local room, and control routing directly, and your programs don't have to be designed to all connect to each other over EISC to handle routing on a single Director.? If the director is used to abstract the NVX's into a DM-type device, it's great...? but most of the time I've seen Director's spec'd into systems, is on larger multi-room deployments where a Director is spec'd in and is expected to handle all the NVX's that span multiple systems, which is not great.
?
But to clarify what the original posted asked, if you use the director or not, you don't HAVE to setup the streaming serial strings if you opt to do the routing using subscriptions.? It takes mere minutes to setup a common list of subscriptions using the NVXTool.
--
Jason Mussetter
Control Systems Designer Mussetter Programming Services |
|
Re: Sonos Network Issues
Not only does the CP4 loses connection to the Sonos intermittently, but I had a case recently where the Crestron Sonos module was? causing the TSR-310 remote to intermittently stop responding.? The TSR-310 (or CP4) would cue up commands,? then several minutes later eventually reconnect, and then spit out out the stored commands at once.? At no time was the TSR-310 displaying "Connecting to control system".? If was only after looking at the CP4 error log that I discovered it was the Crestron Sonos module that caused the issue.? While there was a Sono module in the CP4 program, at this point the Sonos device wasn't installed yet.? Here are the errors I got..
?
? ? ? ? ? ? CP4 Control Console
? ? ? ? ? ? CP4>
? ? ? ? ? ? CP4>err
? ? ? ? ? ?? ..... ? ? ? ? ? ? ? 289. Notice: SimplPlus[App01] # 2025-03-13 12:56:59 # Sonos Broadcast discovery result: no devices found. ? ? ? ? ? ? ? 290. Notice: SimplPlus[App01] # 2025-03-13 12:57:04 # Sonos - The system state changed to "Not Connected". ? ? ? ? ? ? ? 291. Notice: SimplPlus[App01] # 2025-03-13 12:57:04 # Sonos - The system connection failure reason changed to "Sonos Household Not Found". ? ? ? ? ? ? ? 292. Error: LogicEngine_1 # 2025-03-13 12:57:53 # Could not obtain console symbol protection mutex for S-15.1.2.2:S-3.3 (status: 1460). Did not transmit [who\x0D] ? ? ? ? ? ? ? 293. Notice: SimplPlus[App01] # 2025-03-13 13:02:05 # Sonos - Auto discovery in progress. ? ? ? ? ? ? ? 294. Notice: SimplPlus[App01] # 2025-03-13 13:02:05 # Sonos - The system state changed to "Auto Discovery Mode". ? ? ? ? ? ? ? 295. Notice: SimplPlus[App01] # 2025-03-13 13:02:05 # Sonos - Discovery mode changed to "multicast". ? ? ? ? ? ? ? 296. Notice: SimplPlus[App01] # 2025-03-13 13:02:05 # Sonos - Multicast discovery started. ? ? ? ? ? ? ? 297. Notice: SimplPlus[App01] # 2025-03-13 13:02:05 # Sonos - The system state changed to "Connecting to Primary Device". ? ? ? ? ? ? ? 298. Error: LogicEngine_1 # 2025-03-13 13:02:07 # Could not obtain console symbol protection mutex for S-15.1.2.2:S-3.3 (status: 1460). Did not transmit [who\x0D] ? ? ? ? ? ? ? 299. Error: TLDM # 2025-03-13 13:02:07 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 300. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 301. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 302. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 303. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 304. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 305. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 306. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 307. Error: TLDM # 2025-03-13 13:02:08 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 308. Error: TLDM # 2025-03-13 13:02:09 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 309. Error: TLDM # 2025-03-13 13:02:09 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 310. Error: TLDM # 2025-03-13 13:02:09 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 311. Error: TLDM # 2025-03-13 13:02:09 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 312. Error: TLDM # 2025-03-13 13:02:09 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 313. Error: TLDM # 2025-03-13 13:02:09 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 314. Error: TLDM # 2025-03-13 13:02:09 # S3 IOP error: Queueing IR packet failed ? ? ? ? ? ? ? 315. Notice: SimplPlus[App01] # 2025-03-13 13:02:35 # Sonos - Discovery state changed to idle. ?
It was between error 294 and error 299 that the TSR-310 stop responding (note there is only 2 seconds between these two errors).
Remove the Sonos module from the program and the TSR-310 hasn't failed since.
?
|
|
Re: Pentair Screenlogic
Tony,
If you are going to try to control the Pentair EasyTouch directly, you don't need an adapter. The Pentair bus is just RS485. The other day I connected a din-ap3 to a EasyTouch to test control. My hopes were that the old Compool 3800 module that I have would work. It didn't! I did a quick search and found this git site: . They explain the protocol but leave vital information out. |
|
Re: Pentair Screenlogic
toggle quoted message
Show quoted text
|
|
Re: Pentair Screenlogic
I know this is an old thread, but I have a client that wants to integrate their Pentair EasyTouch pool controller.? Although I suggested they upgrade to an IntelliCenter, of course they don't want to do that.? My job now is simply to tell them what is required to integrate the EasyTouch, assuming it's even possible, so they can make a decision.
Does anyone know exactly what is the "Compool adapter" mentioned in the post below?? A picture, part number, anything?
Thanks in advance! ?
?
On Fri, Oct 23, 2020 at 04:42 PM, Caleb Radecky wrote:
|
|
Re: NVX programming jump start
Nope, there's absolutely no reason to spend the frankly exorbitant expense of a DIR when you can literally handle every necessary function (besides firmware updates, which are simple enough just with the free DM NVX Tool) from within SIMPL itself.? The only real reason to get a Director is if you need a really expensive machine to bloat a quote's bottom line and insert one more point of failure into the system.? You don't even need to use subscriptions... ADDM (number) (processor address) on the NVX's terminal and if you've written your SIMPL code right, everything just snaps right to where it needs to be.
?
Director's a crutch for people who can't code.
?
? |
|
Re: NVX programming jump start
On Mon, Mar 31, 2025 at 09:03 AM, <jacksonkfortune@...> wrote:
It seems to me that with or without the director, I still need to pull the individual streams into a serial strings for the logic. You found the secret.? The XIO Director is a completely useless waste of money.
?
?
Seems like you've been getting some really bad advice.? The DIR pays for itself with the time saved on a job, both in ease of setup and in programming.? I won't design a job with over 20 endpoints with out DIR. If you've only looked at firmware v2 and older, maybe you're right.? And for a tiny system with less than 15 endpoints the cost is hard to justify.? But starting with v4 it's a complete overhaul and the dashboard feature is far better and more powerful than NVX Tool.?
|
|
Re: NVX programming jump start
What are you talking about?? The DIR is like magic.? Who told you they were useless?? You should update firmware on endpoints to current - period.? Don't try to use old firmware on NVX.? DIR DOES handle credentials very well.? Why do you need a module?? DIR is a native Crestron device, not a 3rd party device that would need a module.? There is a programming object, so what's the point of a module?? I think you've been getting some really bad advice from someone who doesn't know how to use a DIR correctly. |
|
Re: NVX programming jump start
Use DIR for this - the firmware updates are much easier with DIR compared to using NVX tool.? The new dashboard that was introduced in v4 essentially replaces all of the functions in NVX tool and gives you some that aren't available in NVX Tool.? NVX Tool is not really needed now with the dashboard on DIR. |
|
Re: Home compatible security system recommendations?
Okay what am I missing....
I think I'm with Andrew M on this. For the Past 10 years, We have used DSC with all our Crestron Integrations (SMPL & Home) up until 1 year ago when they stopped making the old Panels. Our Security Company, and 3 more I talked to, all said the same thing...
The new Panels will only integrate with ONE system.? Crestron or Alarm.com, but not both.
And No Security Company will Monitor an Alarm Panel if it can't be connected to Alarm.com.
GE, and Ademco, are all gone.? So we had no choice but to stop integrating with Alarm Panels.
?
Please someone, show me where I'm wrong.
|
|
Re: Crestron Home RAVA issues
Jumping back in here.
?
Chad is this a workaround to shorten the Rava ring time when 2N initiates a call and also to have flexible video switching capabilities.
?
The 2 requests my client has is:
?
1. Shorten ring time on inbound 2N<>Panel call
2. Change ringtone on panels
?
? |
|
Sonos Network Issues
Wondering if anyone has had issues with Sonos devices all dropping offline after a reboot? We have a rather large network and Sonos devices are on two switches in two separated racks connected over fiber. What's interesting is I get "Multicast Success" on the diagnostics page but all of my devices show up not registered. Wondering if I may still be having some kind of multicast/ network issues. Only major thing of note in my opinion is that our router/ primary managed switch are not in the same rack as our Cp4-R. Thanks!? |
CO Cowboy
to navigate to use esc to dismiss