Crestron Modules with AV3 / Build 7 FAIL

[Oly (Oliver)]

@support

I’m working on a project integrating Roon with Crestron controlling multiple endpoints. The Nucleus is due for delivery in the next couple of days.
Yesterday I added the Roon modules to my Crestron program - pretty much a replica of the demo program using the Core3 Media Object but instead with 7 zones.

Loading the program to an AV3 immediately locked up the processor - commenting out the Roon modules and all is well again. Further diagnostics reveal that from a reboot the Roon modules break the TCP/IP stack or internal router - you can only gain access to the AV3 via USB.

I have access to two AV3’s and both behave exactly the same. I also tried loading the demo program exactly as downloaded and it causes the same issue.

I then tried loading my program and the demo program to a CP3 and all seems well.

The AV3s and CP3 are all running similar 1.503.0016 firmware from there respective PUF files.

More playing… after staggering the modules loading I can get the AV3 to boot and not break the TCP/IP stack or internal router … it does give a few errors in the error log… I shall report back as to whether this then actually works when the Nucleus is delivered.

So something definitely needs looking at with these modules and an AV3!

[eric (Eric Stewart)]

Hi @Oly ---- Thank you for the report and sharing this observation you have made with us. The insight and feedback are both greatly appreciated!

Moving forward, I have opened up a ticket in our system and shared the information from your post with our tech team to get some feedback on this error you encountered. Furthermore, please do keep us posted on how things perform once the Nucleus has arrived.

Many thanks!
-Eric

[Oly (Oliver)]

@support @eric @noris

Ok update as promised - looks like I’m going to need some help!

Roon Nucleus Version 1.5 (build 339) stable with lifetime license
Crestron AV3 firmware 1.503.0016
Crestron TSW760 touchpanel
Crestron Build 7 Modules

Same issue using the Build 7 Demo (modified so the AV3 responds - see above) or my own program.

Using the iOS app. under Settings, Extensions I have enabled and paired Crestron 1.0 (Build 7).

Under the crestron extensions I’ve paired Zone 1 to my Meridian Endpoint.

Now on the TSW760 I select the Core 3 Media router for Object 1 which is correct for Zone 1 which is paired to the Meridian.

All that happens is I get a spinning icon top right on the Core 3 media player object.

Please advise how best we debug this?

The Crestron log is full of this -

Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56931, serialized 53 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 113
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Sent packetized data with payload length: 200
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Sent packetized data with payload length: 128
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Sent packetized data with payload length: 200
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Sent packetized data with payload length: 66
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 221
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Sent data with payload length: 61
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 registered connection cip-direct/json-rpc - 192.168.1.241:56932
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 received 250 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 250 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56931, serialized 312 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 31
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 received 69 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 client handler thread started
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 OnClientConnected
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client accepted: cip-direct/json-rpc - 192.168.1.241:56932
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 processing cip connect
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:08 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 19, Length: 23
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 20, Length: 221
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 69 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56931, serialized 1300 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 70
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 received 113 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 113 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 received 250 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 250 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56932, serialized 312 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 20, Length: 31
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 received 69 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 69 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56931, serialized 53 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 114
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 received 107 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 107 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56931, serialized 369 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 108
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56932, serialized 1300 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 20, Length: 70
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 received 113 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 113 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56932, serialized 53 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 20, Length: 114
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 received 116 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 116 bytes
Exception ‘Data Abort’ (0x4): Thread-Id=0bf200d2(pth=c0a28a08), Proc-Id=0b320002(pprc=c0972738) ‘splusmanagerapp.exe’, VM-active=0b320002(pprc=c0972738) ‘splusmanagerapp.exe’
PC=00479d90(???+0x00479d90) RA=003040d8(???+0x003040d8) SP=03bff7e8, BVA=00000000
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 received 107 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 107 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56932, serialized 369 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 20, Length: 108
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 received 116 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 116 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56931, serialized 3092 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 117
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 received 109 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 client received 109 bytes
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56931, serialized 53 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 20, Length: 110
Exception ‘Data Abort’ (0x4): Thread-Id=0bbe00ce(pth=c0a28500), Proc-Id=0b320002(pprc=c0972738) ‘splusmanagerapp.exe’, VM-active=0b320002(pprc=c0972738) ‘splusmanagerapp.exe’
PC=00479d90(???+0x00479d90) RA=003040d8(???+0x003040d8) SP=03e1f7e8, BVA=00000000
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: CIP transport cip-direct/json-rpc - 192.168.1.241:56932, serialized 3092 bytes of data
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 20, Length: 117
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:20:09 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 received 109 bytes of data

Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:41 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 processing heartbeat
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:41 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 handled packet CIP Type: 13, Length: 2
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:42 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 processing heartbeat
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:42 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 handled packet CIP Type: 13, Length: 2
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # CRPCConnectionHelper - Received new IP Address: ip:192.168.1.221, adapter:0
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # CRPC Logger Primary Adapter Log: Message: Server Transport cip-direct/json-rpc - 192.168.1.221:41800 caught exception System.Net.Sockets.SocketException: A blocking operation was interrupted by a call to WSACancelBlockingCall
at System.Net.Sockets.SocNotice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # ket.AcceptNoCheck()
at System.Net.Sockets.Socket.Accept()
at System.Net.Sockets.TcpListener.AcceptTcpClient()
at Crestron.CRPC.CIPDirectTransport.CIPServerTransport.ListenerProc()

Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # CRPC Logger Primary Adapter Log: Message: Server Transport cip-direct/json-rpc - 192.168.1.221:41800 stop requested, exiting
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56931 processed stop command
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 closed connection cip-direct/json-rpc - 192.168.1.241:56931
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # CRPC Logger Primary Adapter Log: Message: Transport cip-direct/json-rpc - 192.168.1.241:56932 processed stop command
Notice: splusmanagerapp.exe [App 1] # 2018-08-22 13:23:48 # CRPC Logger Primary Adapter Log: Message: Server transport cip-direct/json-rpc - 192.168.1.221:41800 closed connection cip-direct/json-rpc - 192.168.1.241:56932

[Oly (Oliver)]

@support @eric @noris

How do we get support? Can I contact someone directly to help me resolve this?

[mike (Mike Fass)]

Hey @Oly – sorry for going dark on you here, we’ve had a few people out over the last 2 weeks, so things have been a bit slower than normal.

We’ve been looking into how we can debug this issue, since we don’t currently have an AV3 in-house. At the moment, that is still in progress, but it’s looking like we might need to get this hardware in order to understand what’s happening here.

I don’t have a firm timeline, but we are going to try to get an AV3 in front of our developers – we’ll keep you updated on our progress here, and we’ll do everything we can to get this resolved ASAP for you @Oly.

Thanks!

[Russ_Hohensee]

Oly did you get the Roon working with your AV3?

[Oly (Oliver)]

Hi Russ,

No, Roon spent many hours working remotely on my AV3 and were unable to make it work reliably. This is the case for any Crestron processor that has an internal router (PRO3/ AV3/ CP3N).

We then free issued a CP3 to the client as we’d promised Roon integration, however the experience is so poor we have since removed it from the Crestron panels. Even with a CP3 it continually locks up, the log fills with errors, high CPU usage and the Tidal search function is useless.

The client just uses the Roon iPad app. which is really good!!

Oliver

[noris]

Hi @Oly / @Russ_Hohensee,

We have just released Crestron Module Build 8 which addresses the communication issues when using a processor with a control subnet:

Roon Crestron Module Build 8 is Live!

Hello Everyone, we have just released Crestron Build 8 Have a processor with a Control Subnet? Wait no more and make the upgrade to Build 8! Full details for this release can be found on our KB page: http://kb.roonlabs.com/Crestron Release Notes: You are now required to place the Nucleus IP address in the RoonSystemModule symbol and it is recommended that this IP does not change Added support for processors with Control Subnets such as CP3N, PRO3 & AV3 Improved TIDAL Search function…

Please update to the latest build and let me know if everything is working as expected for you!

Thanks,
Noris