?
Use the DSC driver linked above with "Crestron Certified Drivers Security System Ethernet v2.0 (cm)" module in SIMPL.

The above link is no longer available.?

Anyone knows where to get hold of the DSC driver? I seem to have an old RS232 (based on COM port) driver from DSC v1.0, but I do not have the latest Ethernet 2.0 or 2.1 driver.?

?

Furthermore, the package in the??does not contain any drivers nor module. It only has these few illogical files:

SecuritySystem_DSC_PowerSeries-Neo_IP.dat

SecuritySystem_DSC_PowerSeries-Neo_IP.dll

libSecuritySystem_DSC_Shim.so

?

Wonder what's the purpose of these files? I'm really lost now. Please help!!!

Hello, I am writing a TCP client class in VS2019 using System.Net.Sockets TCPClient.?
I created a test server on the MC4 at TCP port 9001.
The MC4 IP is 10.0.0.57 and the MC4 hostname is?MC4-00107FE73CAB
My Client class first checks if the IP address is pingable and then connects via IP Address
Everything is working great except now I am trying to ping test and connect with the HostName of the MC4 and nothing works.

string hostName = "MC4-00107FE73CAB"
_client = new TcpClient();
_client.Connect(hostName, port);

Any help would be appreciated

Thanks

I'm assuming you mean you're programming a 4-Series control system in SIMPL.

?
?

?
Use the DSC driver linked above with "Crestron Certified Drivers Security System Ethernet v2.0 (cm)" module in SIMPL.

Anyone has any updates on the release of the drivers to work with Crestron?

if we don’t have a driver, would it still be possible to programme our system??

Anyone has some samples to share? I really don’t know where to start.?

Thanks everyone. I swapped in CNPWS-75 power supply and the AP4 works fine, thus the DIN-PWS60 is fried. Sign, unreliable equipment.

This issue was identified back in late August and being tracked under BR 7307.
If you have a support case it can be added to BR 7307 for tracking and follow-up.
I've also added this groups.io thread to BR 7307 for follow-up when fix is released.

In the meantime, rolling back Toolbox or using the SETCRESNETIDBYPPN cmd in Text Console are both viable workarounds.

Toolbox - Network Device Tree View - Changing CNET ID on 1 Device Affects All Devices With Same ID

I have a few of PTX-3 and MTX-3 that apparently hang during boot up. ?They light up, then go dark, then light back up with splash screen and there is no further progress. ?The MTX-3 shows the progress bar on the bottom but it is frozen.

They do not respond to the OLH Recovery power button/side button procedure (unless the power button must be held for more than a minute . . )

TIA

Kol

Also the AP4 can be powered via POE, allowing you to test if it boots up by itself...

Do you have anything connected to the cresnet ports on the ap4? could it be a short circuit on the 24v wiring?

While I haven't had any DIN-PWS60 failures yet, I have seen a lot of other Crestron power supply fail.? In many cases the power LED on either the power supply or the end devices lights up yet the end device does not work.

The easiest thing to do is sub the power supply and if the end device then works, you know you have a bad power supply.?

Alternatively you can monitor the power supply output with an oscilloscope.? That will very quickly reveal if the power supply it outputting the right voltage and is ripple free.

I'm not sure if I have a spoiled DIN-PWS60.

When it's not hooked up to other DIN equipment, it has a GREEN light.

When it's hooked up to DIN-AP4, the Power button on DIN-AP4 is blinking in amber color.

I have replaced the fuse, still same blinking.

Anyone has any clue what problem am I facing? Is it a bad DIN-PWS60 or bad DIN-AP4?

Previous versions of Toolbox had the "Clear ID" option not greyed out, I don't know why Crestron greyed it out a few versions ago, I rolled back my Toolbox to version 3.03.252.00 on a 2nd laptop I had onsite with me and cleared each device before changing it. This speeds up the process quite a bit. I have seen this type of thing happen off and on for years, mostly with lighting devices, and made it a habit of clearing before changing a Cresent ID. I sent a request to True Blue to un-grayout the clear button about 3 weeks ago.

yes i think also this is a bug of the latest version of the toolbox, maybe it's better to use the previous version first if it works fine

Hi Stujrob

?

i have the same problem,

after I ask crestron support, do change the ID one by one device?

the result was successful?but it takes a lot of time

Hi John

I have the same problem trying to change some duplicate ID's on a new job

Anyone seen or had a fix for this?

Just to be clear, you have a functioning AM-200 that you could take the image from but rather than “risk harvesting” your unit you want someone to potentially brick one of theirs instead and give it to you…am I reading that right?

开云体育

Thanks Richard!

While the code example didn't include uppercasing the result, the documentation did.? I've actually tried it both ways and I can't get either one to work.?

I have posted the issue with the manufacturer's development group but I've been waiting 6 days and still haven't received any response from them.? Earlier today I pinged another contact I have with the company to see if they can help me get the issue resolved.?

Thanks again for your help

Jay

I'm sure a few on here have had the issue with older AM-200s where the OS fails to boot completely. Repairs always replace the SD card that runs the OS.

Considering that this?always happens with the 200s for us, rather than putting a system partially offline for two weeks to repair, we want to change the cards and flash the image ourselves, saving time + money for the customer.

I don't want to risk harvesting one of our last few remaining new AM-200s for an image, and obviously the 3200 software isn't compatible.

Would anyone have or be willing to try creating an image of the AM-200 firmware? Most likely a doable thing, and if it works flashing to a new device it's a great fix for a relatively common problem? ?

The following files and folders have been uploaded to the Files area of the [email protected] group.

• /CP4 Samsung QB43B v1 (TA).zip

By: Antoine Dervin <antoine.dervin@...>

Description:
Samsung MDC Protocol v1.1 (based on Ryan Oberndorf Samsung MDC Protocol v1.0) - modified the S-1.12 Volume and S-2.13 Volume FB logic to avoid bouncing command and response. - tested with a CP4 and a Samsung QB43B through either RS-232 port and TCP/IP client (port 1515). - test programm and basic XPanel included. - both Samsung MDC Protocol v1.0 (the original one from Ryan Oberndorf) and Samsung MDC Protocol v1.1 (modified version) included in programming to test the difference.

I quickly spun up your code (with the adjustments to use long for the timestamp - https://dotnetfiddle.net/BIOq4U) and tested against a hmac calculator and the results come out the same.

One thing I found curious though, you are uppercasing the result in the c# code, but that isn't present in the javascript code.