开云体育

I don't think so... they will always be a pain to work with until they eliminate the uber-module and let us have direct hardware access like we do in a DM-MDXxX.

I'v been pretty annoyed by the database changes, especially the one that made the COM ports stop working - lost hours trying to figure out what was going on, it wasn't until I posted here that the answer was found.

The biggest problem with the DMPS is that the box has awesome features for an awesome price, so salespeople will continue to specify it. If you look at the total cost of re-creating a DMPS-300-C using a control processor and a DM8x8 it will be a lot more $$, and you would still need a 3rd party DSP for the mics.

Another big problem with the DMPS is that it seems to be very stable once it is programmed and tested, and my customers are very happy with it, ordering more all the time.

Maybe tell the salespeople to double their programming estimates with DMPS to account for all the dead time that the unit causes.

Personally, I feel major resentment towards Crestron about this box. I have a strong suspicion that the pain that these boxes cause is not necessary, but some manager said "it has to have a front panel" and "it has to have an uber-module to make it 'easy' to program."

The most success I've had with these is in cookie-cutter rooms, it's not so bad to configure and upload to one of these, I can usually get it done in about an hour or so.



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

Long compile times, firmware update failures, hardware failures, long boot times, long initialize times, inaccurate feedback, new device databases that make your older programs stop working..............etc., etc., etc.,

Our sales guys love this box and our installers and programmers can't make them stop selling it. I guess my real question is, how do you convince a salesman to stop selling DMPS's?

Long compile times, firmware update failures, hardware failures, long boot times, long initialize times, inaccurate feedback, new device databases that make your older programs stop working..............etc., etc., etc.,

Our sales guys love this box and our installers and programmers can't make them stop selling it. I guess my real question is, how do you convince a salesman to stop selling DMPS's?

Has anyone controlled a HRDP series recorder? If you have a module it would be great but even if you can answer a couple of questions.



Chris



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

**


Thanks but I just ended up running it through a variable

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

Is it possible to modify D3 schedule times without rebuilding and
loading the program? I see a bunch of things in the "real-time view"
but I'm not really sure where to go.

Thanks, Heath

FYI, the latest TPMC-3X firmware Release Notes states the panel will perform a
"maintenance mode" (i.e., reboot) at 2 AM every day, if it's not in use at the
time. Although it's not mentioned in the MTX-3's Release Notes, I'd be
surprised if the same didn't apply.

--- on Tuesday, December 25, 2012 at 6:03 PM, LENREX wrote:

I'm wondering if this is Prodigy processor specific only? Or if MC3's do it
too? Or if it's purely a PTX-3 & MTX-3 hardware issue where the remote gets
it's time from the processor somehow and reboots itself. I've tried
changing the time on the processor and or adding clock drivers in SIMPL yet
no difference. Still reboots at @ 11pm PST EVERY night.

I personally have a PMC3 & PTX3. I have a client with 2) PMC3-XP's &
MTX3's. And I know another dealer that has PMC3 & PTX3 rebooting issues as
well.

My Pro2>Cenrfgwex>MTX3 clients either haven't noticed this issue and
haven't told me, or they don't have this problem...?

--- In Crestron@..., "Block-O-Matic" <michael@> wrote:

A PMC-2+ and ptx-3

--- In Crestron@..., "LENREX" <lenrex@> wrote:

What processor/remote do you have?

--- In Crestron@..., "Block-O-Matic" <michael@> wrote:

Yes, that happened. It will again tonight.

mb

--- In Crestron@..., "LENREX" <lenrex@> wrote:

Has anybody seen their MTX-3 or PTX-3 reboot late at night? Around

11pm PST or 2am EST?

Is it possible to modify D3 schedule times without rebuilding and
loading the program? I see a bunch of things in the "real-time view"
but I'm not really sure where to go.

Thanks, Heath

**


Is it possible to Set up a scheduler event and only have it run based on a
button's feedback in d3?

Now that's a head start! :D


On Tue, Dec 25, 2012 at 12:34 PM, eagrubbs <eagrubbs@...> wrote:

**


MERRY CHRISTMAS ALL!!!!!!!

I hope you all have a great Christmas. Enjoy the family time and thanks
for all the help you guys/gals have provided.

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

--- on Tuesday, December 25, 2012 at 6:03 PM, LENREX wrote:

I'm wondering if this is Prodigy processor specific only? Or if MC3's do it
too? Or if it's purely a PTX-3 & MTX-3 hardware issue where the remote gets
it's time from the processor somehow and reboots itself. I've tried
changing the time on the processor and or adding clock drivers in SIMPL yet
no difference. Still reboots at @ 11pm PST EVERY night.

I personally have a PMC3 & PTX3. I have a client with 2) PMC3-XP's &
MTX3's. And I know another dealer that has PMC3 & PTX3 rebooting issues as
well.

My Pro2>Cenrfgwex>MTX3 clients either haven't noticed this issue and
haven't told me, or they don't have this problem...?

--- In Crestron@..., "Block-O-Matic" <michael@...> wrote:

A PMC-2+ and ptx-3

--- In Crestron@..., "LENREX" <lenrex@> wrote:

What processor/remote do you have?

--- In Crestron@..., "Block-O-Matic" <michael@> wrote:

Yes, that happened. It will again tonight.

mb

--- In Crestron@..., "LENREX" <lenrex@> wrote:

Has anybody seen their MTX-3 or PTX-3 reboot late at night? Around

11pm PST or 2am EST?

For the most part we have had few problems with the hardware. We did have a PoE switch that lost its configuration (with VLANs) twice. But it hasn't happened again.

My only other gripe is that the web interfaces to configure the WAPs and the switches is painfully slow and does not render properly in all browsers. The interface for the routers (re-badged Fortinets) is much better.


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

I have to chime in here as well and report nothing but good things about pakedge. I've worked with them directly on a lot of things and they're all very helpful. What issues are you having?

--- In Crestron@..., "m.nguyen" <mpninc@> wrote:

We have been using pakedge as well and it been pretty solid aside from the
issue with ps3 with virtual cell.
On Dec 22, 2012 5:22 PM, "Kris" <kris.k@> wrote:

**


Never had hardware issues. Only issues with improper setup, wiring or
implementation. Got to love IT issues!

--- In Crestron@..., "Bill Karlis" <vkarlisc@> wrote:

Hello All :-)

For our crestron IT backbone, we've been using Pakedge routers,

switches, access points and their virtual kit lately.

Occasionally, we seem to be having network issues at clients homes and

apartments. Its not often but does seem to happen.

I am trying to narrow it down whether its a problem on our side with

running wires / terminating ends properly etc.

Has anyone else had hardware issues with Pakedge gear?

Thanks in advance,
Bill

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

I am not new to Crestron but
?I am new to doing myself?
Have been paying others to do this for 10 years?
My turn now?

Any way I bought prodigy PMC3 (hope that was not a mistake)
intent is:
?control for theater with I-pad?

replacing older cp2 (no ethernet)
no access to software
programmer died

have?
vutec on relay

direct tv ?(IR)

blue ray ?(IR)


sony str d2es (IR)

JVC DLAX 90 ?(iR ?)

graffic eye 4 button (serial)

Is this going to work?

will graffic eye integrate on serial or is that prodigy only

Thank You

Paul
AHT PHX AZ

I'd add another MC3 or CEN-CI3 with appropriate cards. I'd avoid using prodigy processors, with regular Crestron stuff. You'll just get pigeon-holed in the future. And yeah, I know PMC3's are probably cheaper.

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

In my personal system I have a MC3 that controls two rooms, each have some "local" sources, and there are some shared sources (BDP-7000ES, Roku, analog video switcher).

I'm thinking about adding a third room using a PMC3 and EIC, will that actually work? I can add the EIC symbol to the PMC3 system, and to the MC3. However, before I go about the ardous task of adding the handlers for those sources to the EIC, has anyone done anything similar?

If so, any pitfalls I should look out for? I'm not likely to run 1000s of symbols between the systems, just basic things like play/pause/stop, a few feedback and interlock states for the shared devices.