Keyboard Shortcuts
Likes
- Crestron
- Messages
Search
Re: NVX V-5.1 FIRMWARE
pearce.bruce
开云体育Hi rob?Fixed it with a restore command . All the other units upgraded perfectly . A bit strange but working now? Regards
Bruce
On 30 Jan 2021, at 13:37, Rob <rob@...> wrote:
|
Re: NVX V-5.1 FIRMWARE
Are you private browsing? Did you do an initialize or restore after the upgrade? You'll have to set up authentication on the NVX after you do. And you'll have to set the host processor up for the same.
Also, make sure your running program is running the correct databases v5.1 requires. |
Re: DM Transmitters and Receivers Randomly Losing DM Connection with POE
Mike Jewell
开云体育I've seen touch panels be very picky about it's PoE power sources, ?I had a touch panel that absolutely hated anything but a Crestron switch feeding it. ?I was running shielded cable through the floor conduit but standard cable above the floor to the TP, ?the DM box had a shielded network cable and a local power supply (different location that had power).-Mike On Jan 29, 2021, at 3:53 PM, bryanga@... wrote:
|
Re: DM Transmitters and Receivers Randomly Losing DM Connection with POE
开云体育Thanks Steve, do you recall if the system used shielded cable? The issue I am experiencing seems to be related to whether or not the cable is shielded. ? Steve wrote: ? It has been a while, but I believe the end point was a DM-RMC-4K-100-C and it was a Luxul PoE switch feeding the DM-MD8x8.? The room box stopped working when I rebooted the DM so it was kind of embarrassing because it was working before I rebooted the DM.? I connected the DM-RMC directly to the DM chassis with a short Ethernet cable and tried output cards and other port? on the PoE switch and even a Ubiquitid PoE switch but had the same issue. I think I even tried a different RMC.?? I landed up putting a power supply on the DM-RMC to get the client going.? It I hadn't seen it working, I would have thought it never worked.? No changes to the system -- I had rebooted the DM because I needed to reroute the power cord. ? |
Re: DM Transmitters and Receivers Randomly Losing DM Connection with POE
It has been a while, but I believe the end point was a DM-RMC-4K-100-C and it was a Luxul PoE switch feeding the DM-MD8x8.? The room box stopped working when I rebooted the DM so it was kind of embarrassing because it was working before I rebooted the DM.? I connected the DM-RMC directly to the DM chassis with a short Ethernet cable and tried output cards and other port? on the PoE switch and even a Ubiquitid PoE switch but had the same issue. I think I even tried a different RMC.?? I landed up putting a power supply on the DM-RMC to get the client going.? It I hadn't seen it working, I would have thought it never worked.? No changes to the system -- I had rebooted the DM because I needed to reroute the power cord.
But I believe it is true that if you want to do PoE, you really need to use a Crestron PoE switch to power it.? Of coursed that is a pretty expensive option.? I've powered DM-RMC via PoE switches during testing but always been leery to use them in the field because whenever I call TB with an DM-RMC problem, they always ask if I am powering it by PoE.? So it is apparently a common issue. |
NVX V-5.1 FIRMWARE
pearce.bruce
开云体育
Hi All
Ive just upgraded the firmware on a nvx 360 and I can no longer see the subscriptions or routing options. What is also strange that in the address bar it says?/#/stage/(child:settings). I guest this isnt in full admin mode . Any one else seen this ?
Bruce
|
Re: processors connecting/disconnecting from LAN
nothing in the MC3 log
but stuff like this in the pyng-hub 107. Warning: CIPCommandProcessor.exe # 2021-01-27 13:42:35? # Lost Ethernet link on LAN A
108. Notice: CIPCommandProcessor.exe # 2021-01-27 13:42:40? # Link established on LAN A
109. Notice: CIPCommandProcessor.exe # 2021-01-27 13:42:40? # New Address 192.168.13.96 obtained from 192.168.13.1
110. Notice: CIPCommandProcessor.exe # 2021-01-27 13:42:46? # Link established on LAN A
111. Notice: CIPCommandProcessor.exe # 2021-01-27 13:42:52? # New Address 192.168.13.96 obtained from 192.168.13.1
112. Warning: CIPCommandProcessor.exe # 2021-01-27 13:42:52? # Lost Ethernet link on LAN A
113. Notice: CIPCommandProcessor.exe # 2021-01-27 13:42:53? # Link established on LAN A
114. Notice: CIPCommandProcessor.exe # 2021-01-27 13:42:53? # New Address 192.168.13.96 obtained from 192.168.13.1
115. Notice: CIPCommandProcessor.exe # 2021-01-27 13:42:55? # Link established on LAN A
116. Notice: CIPCommandProcessor.exe # 2021-01-27 13:43:05? # New Address 192.168.13.96 obtained from 192.168.13.1
117. Warning: CIPCommandProcessor.exe # 2021-01-27 13:44:02? # Lost Ethernet link on LAN A
118. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:21? # Link established on LAN A
119. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:21? # New Address 192.168.13.96 obtained from 192.168.13.1
120. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:22? # Link established on LAN A
121. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:22? # New Address 192.168.13.96 obtained from 192.168.13.1
122. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:26? # Link established on LAN A
123. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:26? # New Address 192.168.13.96 obtained from 192.168.13.1
124. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:38? # Link established on LAN A
125. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:38? # New Address 192.168.13.96 obtained from 192.168.13.1
126. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:41? # Link established on LAN A
127. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:41? # New Address 192.168.13.96 obtained from 192.168.13.1
128. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:42? # Link established on LAN A
129. Notice: CIPCommandProcessor.exe # 2021-01-27 13:44:42? # New Address 192.168.13.96 obtained from 192.168.13.1
130. Warning: CIPCommandProcessor.exe # 2021-01-27 15:50:53? # Lost Ethernet link on LAN A
131. Notice: CIPCommandProcessor.exe # 2021-01-27 15:50:58? # Link established on LAN A
132. Notice: CIPCommandProcessor.exe # 2021-01-27 15:50:58? # New Address 192.168.13.96 obtained from 192.168.13.1
133. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:04? # Link established on LAN A
134. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:10? # New Address 192.168.13.96 obtained from 192.168.13.1
135. Warning: CIPCommandProcessor.exe # 2021-01-27 15:51:10? # Lost Ethernet link on LAN A
136. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:10? # Link established on LAN A
137. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:10? # New Address 192.168.13.96 obtained from 192.168.13.1
138. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:13? # Link established on LAN A
139. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:22? # New Address 192.168.13.96 obtained from 192.168.13.1
140. Warning: CIPCommandProcessor.exe # 2021-01-27 15:51:24? # Lost Ethernet link on LAN A
141. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:33? # Link established on LAN A
142. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:33? # New Address 192.168.13.96 obtained from 192.168.13.1
143. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:34? # Link established on LAN A
144. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:34? # New Address 192.168.13.96 obtained from 192.168.13.1
145. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:37? # Link established on LAN A
146. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:37? # New Address 192.168.13.96 obtained from 192.168.13.1
147. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:59? # Link established on LAN A
148. Notice: CIPCommandProcessor.exe # 2021-01-27 15:51:59? # New Address 192.168.13.96 obtained from 192.168.13.1
149. Notice: CIPCommandProcessor.exe # 2021-01-27 15:52:01? # Link established on LAN A
150. Notice: CIPCommandProcessor.exe # 2021-01-27 15:52:01? # New Address 192.168.13.96 obtained from 192.168.13.1
151. Notice: CIPCommandProcessor.exe # 2021-01-27 15:52:02? # Link established on LAN A
152. Notice: CIPCommandProcessor.exe # 2021-01-27 15:52:02? # New Address 192.168.13.96 obtained from 192.168.13.1
153. Warning: CIPCommandProcessor.exe # 2021-01-28 00:03:07? # Lost Ethernet link on LAN A
154. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:11? # Link established on LAN A
155. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:11? # New Address 192.168.13.96 obtained from 192.168.13.1
156. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:17? # Link established on LAN A
157. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:23? # New Address 192.168.13.96 obtained from 192.168.13.1
158. Warning: CIPCommandProcessor.exe # 2021-01-28 00:03:23? # Lost Ethernet link on LAN A
159. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:24? # Link established on LAN A
160. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:24? # New Address 192.168.13.96 obtained from 192.168.13.1
161. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:25? # Link established on LAN A
162. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:36? # New Address 192.168.13.96 obtained from 192.168.13.1
163. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:36? # Link established on LAN A
164. Notice: CIPCommandProcessor.exe # 2021-01-28 00:03:42? # New Address 192.168.13.96 obtained from?
165. Error: CIPCommandProcessor.exe # 2021-01-28 00:03:42? #? Error sending Autodiscovery message to 192.168.13.255:41794.?
?
166. Warning: CIPCommandProcessor.exe # 2021-01-28 00:03:42? # Lost Ethernet link on LAN A
167. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:02? # Link established on LAN A
168. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:02? # New Address 192.168.13.96 obtained from 192.168.13.1
169. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:02? # Link established on LAN A
170. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:02? # New Address 192.168.13.96 obtained from 192.168.13.1
171. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:14? # Link established on LAN A
172. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:14? # New Address 192.168.13.96 obtained from 192.168.13.1
173. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:16? # Link established on LAN A
174. Notice: CIPCommandProcessor.exe # 2021-01-28 00:04:16? # New Address 192.168.13.96 obtained from 192.168.13.1
175. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # Exception:SendJoinEventDataForSmartObject - System.ArgumentOutOfRangeException:?
Parameter name: index
? ?at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
? ?at System.ThrowHelper.ThrowArgum176. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # entOutOfRangeException()
? ?at System.Collections.Generic.List`1.get_Item(Int32 index)
? ?at Crestron.Seawolf.UserInterfaceConfig.d.al(Object A_0, SubpageReferenceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.al(Object A_0, SubpageRefe177. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # renceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.List_OnSmartObjectSignalChange(GenericBase currentDevice, SmartObjectEventArgs args)
? ?at Crestron.SimplSharpPro.SmartObject.a(InternalSmartObject A_0, SigEventArgs A_1)
? ?at Crestro178. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # n.SimplSharpProInternal.InternalSmartObject.SendJoinEventDataForSmartObject(SigEventArgs args)
? ?at Crestron.SimplSharpPro.SigCollectionBase`1.NotifyOfSigsNewValue(UShortOutputSig paramSig, eSigEvent paramSigEvent, Boolean paramSigWasAdded)
? ?at Crest179. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # ron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithOutIncrementWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro180. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # Internal.DeviceBasis.ReadAnalogPacket(UInt32 joinNumber, UInt16 joinValue)
? ?at Crestron.SimplSharpProInternal.DeviceWithTextCues.HandleIncomingBufferForSpecificDevice(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.Device181. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # Basis.ParseProcessedCresnetData(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.CrestronDevice.ParseDataFromStructure(Byte* pIncomingDataBuffer, UInt32 tldmToAppDeviceOrSlotId)
? ?at Crestron.SimplSharpProInternal.CrestronD182. Error: SimplSharpPro.exe # 2021-01-28 11:26:20? # evice.ProcessIncomingDeviceEvent(ITldmPacket pObjectReadFromQueue, Stopwatch stopwatch)
? ?at Crestron.SimplSharpProInternal.SimplSharpProManager.d()
?
183. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # Exception:SendJoinEventDataForSmartObject - System.ArgumentOutOfRangeException:?
Parameter name: index
? ?at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
? ?at System.ThrowHelper.ThrowArgum184. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # entOutOfRangeException()
? ?at System.Collections.Generic.List`1.get_Item(Int32 index)
? ?at Crestron.Seawolf.UserInterfaceConfig.d.al(Object A_0, SubpageReferenceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.al(Object A_0, SubpageRefe185. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # renceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.List_OnSmartObjectSignalChange(GenericBase currentDevice, SmartObjectEventArgs args)
? ?at Crestron.SimplSharpPro.SmartObject.a(InternalSmartObject A_0, SigEventArgs A_1)
? ?at Crestro186. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # n.SimplSharpProInternal.InternalSmartObject.SendJoinEventDataForSmartObject(SigEventArgs args)
? ?at Crestron.SimplSharpPro.SigCollectionBase`1.NotifyOfSigsNewValue(UShortOutputSig paramSig, eSigEvent paramSigEvent, Boolean paramSigWasAdded)
? ?at Crest187. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # ron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithOutIncrementWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro188. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # Internal.DeviceBasis.ReadAnalogPacket(UInt32 joinNumber, UInt16 joinValue)
? ?at Crestron.SimplSharpProInternal.DeviceWithTextCues.HandleIncomingBufferForSpecificDevice(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.Device189. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # Basis.ParseProcessedCresnetData(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.CrestronDevice.ParseDataFromStructure(Byte* pIncomingDataBuffer, UInt32 tldmToAppDeviceOrSlotId)
? ?at Crestron.SimplSharpProInternal.CrestronD190. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # evice.ProcessIncomingDeviceEvent(ITldmPacket pObjectReadFromQueue, Stopwatch stopwatch)
? ?at Crestron.SimplSharpProInternal.SimplSharpProManager.d()
?
191. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # Exception:SendJoinEventDataForSmartObject - System.ArgumentOutOfRangeException:?
Parameter name: index
? ?at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
? ?at System.ThrowHelper.ThrowArgum192. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # entOutOfRangeException()
? ?at System.Collections.Generic.List`1.get_Item(Int32 index)
? ?at Crestron.Seawolf.UserInterfaceConfig.d.al(Object A_0, SubpageReferenceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.al(Object A_0, SubpageRefe193. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # renceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.List_OnSmartObjectSignalChange(GenericBase currentDevice, SmartObjectEventArgs args)
? ?at Crestron.SimplSharpPro.SmartObject.a(InternalSmartObject A_0, SigEventArgs A_1)
? ?at Crestro194. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # n.SimplSharpProInternal.InternalSmartObject.SendJoinEventDataForSmartObject(SigEventArgs args)
? ?at Crestron.SimplSharpPro.SigCollectionBase`1.NotifyOfSigsNewValue(UShortOutputSig paramSig, eSigEvent paramSigEvent, Boolean paramSigWasAdded)
? ?at Crest195. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # ron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithOutIncrementWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro196. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # Internal.DeviceBasis.ReadAnalogPacket(UInt32 joinNumber, UInt16 joinValue)
? ?at Crestron.SimplSharpProInternal.DeviceWithTextCues.HandleIncomingBufferForSpecificDevice(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.Device197. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # Basis.ParseProcessedCresnetData(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.CrestronDevice.ParseDataFromStructure(Byte* pIncomingDataBuffer, UInt32 tldmToAppDeviceOrSlotId)
? ?at Crestron.SimplSharpProInternal.CrestronD198. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # evice.ProcessIncomingDeviceEvent(ITldmPacket pObjectReadFromQueue, Stopwatch stopwatch)
? ?at Crestron.SimplSharpProInternal.SimplSharpProManager.d()
?
199. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # Exception:SendJoinEventDataForSmartObject - System.ArgumentOutOfRangeException:?
Parameter name: index
? ?at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
? ?at System.ThrowHelper.ThrowArgum200. Error: SimplSharpPro.exe # 2021-01-28 11:27:02? # entOutOfRangeException()
? ?at System.Collections.Generic.List`1.get_Item(Int32 index)
? ?at Crestron.Seawolf.UserInterfaceConfig.d.al(Object A_0, SubpageReferenceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.al(Object A_0, SubpageRefe201. Error: SimplSharpPro.exe # 2021-01-28 11:27:03? # renceListEventArgs A_1)
? ?at Crestron.Seawolf.SubpageReferenceList.List_OnSmartObjectSignalChange(GenericBase currentDevice, SmartObjectEventArgs args)
? ?at Crestron.SimplSharpPro.SmartObject.a(InternalSmartObject A_0, SigEventArgs A_1)
? ?at Crestro202. Error: SimplSharpPro.exe # 2021-01-28 11:27:03? # n.SimplSharpProInternal.InternalSmartObject.SendJoinEventDataForSmartObject(SigEventArgs args)
? ?at Crestron.SimplSharpPro.SigCollectionBase`1.NotifyOfSigsNewValue(UShortOutputSig paramSig, eSigEvent paramSigEvent, Boolean paramSigWasAdded)
? ?at Crest203. Error: SimplSharpPro.exe # 2021-01-28 11:27:03? # ron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithOutIncrementWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro.DeviceUShortOutputCollection.UpdateValueWithEvent(UInt32 index, UInt16 newValue)
? ?at Crestron.SimplSharpPro204. Error: SimplSharpPro.exe # 2021-01-28 11:27:03? # Internal.DeviceBasis.ReadAnalogPacket(UInt32 joinNumber, UInt16 joinValue)
? ?at Crestron.SimplSharpProInternal.DeviceWithTextCues.HandleIncomingBufferForSpecificDevice(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.Device205. Error: SimplSharpPro.exe # 2021-01-28 11:27:03? # Basis.ParseProcessedCresnetData(CParsedPacketData IncomingDataStructure)
? ?at Crestron.SimplSharpProInternal.CrestronDevice.ParseDataFromStructure(Byte* pIncomingDataBuffer, UInt32 tldmToAppDeviceOrSlotId)
? ?at Crestron.SimplSharpProInternal.CrestronD206. Error: SimplSharpPro.exe # 2021-01-28 11:27:03? # evice.ProcessIncomingDeviceEvent(ITldmPacket pObjectReadFromQueue, Stopwatch stopwatch)
? ?at Crestron.SimplSharpProInternal.SimplSharpProManager.d |
Re: 2 panel setup, lock 1 out
You have to do this using custom code, there is not real built-in function for this.? When I have to do a lockout panel like this, I use the method Scott mentioned, make a full screen popup for lockout, with your message, and make it block the entire screen.? Place this popup on all TP pages, so that it can be active no matter what page is being shown.? When you want to activate the lockout, you can use a Toggle, latch, or INIT/EQU pair to drive the popup on, which blocks user input to the panel until the popup is closed from code.
I've used this on combine/divide type rooms, as well as rooms that contain panels that are in public accessible spaces and might want to be locked out to prevent 'accidental usage' during a big meeting. -- Jason Mussetter Control Systems Designer Mussetter Programming Services |
Re: DM Transmitters and Receivers Randomly Losing DM Connection with POE
开云体育Steve, were you ever able to attribute this to any particular cause? Do you recall what model TX and RX were involved? What model or brand POE switch? ? To the others who have responded, this behavior is also happening on the test bench with 10’ patch cables, so it is definitely hardware related, not cabling. ? ? “Yes I have seen issues with DM end point dropping offline if operated with PoE.? And this is on a system where it use to work.? Been enough of an issue where I don't use PoE on the DM anymore. _._,_._,_ Groups.io Links: You receive all messages sent to this group. ? |
Re: DM Transmitters and Receivers Randomly Losing DM Connection with POE
开云体育Long DM runs will cause problems with POE even if within published length limitations for the cable and resolution used. 4K is more prone to the problem. The voltage drop on some cables and/or poor cable wiring will cause these problems particularly with DM endpoints with higher power requirements like RMC scalers and also larger multi-input TX units. I use local PS for anything over 50ft and sometimes less if problematic.. ? Also, as of a few years ago DM firmware was changed to blank video if POE was marginal with no other on-screen message. It is in a tech note somewhere. ? ? ? David Radin Vidkey, Inc. email: radin@... ? ? |
Re: DM Transmitters and Receivers Randomly Losing DM Connection with POE
开云体育I was told directly from Crestron that you cannot use PoE injectors to power DM devices. ?You can only use PoDM power supplies cause it isn't the same as PoE standards. ? I'm just the messenger. ?
On Jan 29, 2021, at 8:01 AM, bryanga@... wrote:
|
Re: DM Transmitters and Receivers Randomly Losing DM Connection with POE
Theres likely a grounding potential difference between the TX end and the RX end. Like one end is not properly grounded and / or something is putting voltage onto the ground / shield. ?This isn't always a conclusive test but you could try disconnecting the cat6 on one end and meter voltage between the shield and a ground. ?then re-connect and do the same on the other end. ?you should get effectively 0v if you've got voltage there then theres definitely an electrical issue of some sort.
|