Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

4pro RX keeps silent, no comm with CMX anymore.
#7

Hi Werk_AG,
tnx for your advice. I did as you suggested, here are different scenarios:

Firmware now: Cumulus MX 5.1.5 b5012

As a reminder: via USB / Logger on

2026-08-13 08:54:24 - WakeVP: *** VP2 Not woken
2026-08-13 08:54:08 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:51 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:47 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:43 - GetArchiveData: No Ack in response to DMPAFT, giving up
2026-08-13 08:53:43 - GetArchiveData: No Ack in response to DMPAFT
2026-08-13 08:53:41 - GetArchiveData: Unable to wake VP
2026-08-13 08:53:41 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:37 - GetArchiveData: No Ack in response to DMPAFT
2026-08-13 08:53:35 - GetArchiveData: Unable to wake VP
2026-08-13 08:53:35 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:31 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:27 - GetArchiveData: No Ack in response to DMPAFT, giving up
2026-08-13 08:53:27 - GetArchiveData: No Ack in response to DMPAFT
2026-08-13 08:53:25 - GetArchiveData: Unable to wake VP
2026-08-13 08:53:25 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:21 - GetArchiveData: No Ack in response to DMPAFT
2026-08-13 08:53:19 - GetArchiveData: Unable to wake VP
2026-08-13 08:53:19 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:14 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:09 - Console clock: Failed to read console time
2026-08-13 08:53:09 - getTime: Expected 8 bytes, got 0
2026-08-13 08:53:09 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:05 - WakeVP: *** VP2 Not woken
2026-08-13 08:53:01 - Unable to determine the firmware version, LOOP2 may not be supported
2026-08-13 08:53:01 - WakeVP: *** VP2 Not woken
2026-08-13 08:52:57 - WakeVP: *** VP2 Not woken


Now: Via USB / Logger Off in RX and in CumulusMX

2026-08-13 09:49:13 - WakeVP: *** VP2 Not woken
2026-08-13 09:48:56 - WakeVP: *** VP2 Not woken
2026-08-13 09:48:40 - WakeVP: *** VP2 Not woken
2026-08-13 09:48:34 - WakeVP: *** VP2 Not woken
2026-08-13 09:48:30 - Console clock: Failed to read console time
2026-08-13 09:48:30 - getTime: Expected 8 bytes, got 0
2026-08-13 09:48:30 - WakeVP: *** VP2 Not woken
2026-08-13 09:48:26 - WakeVP: *** VP2 Not woken
2026-08-13 09:48:22 - Unable to determine the firmware version, LOOP2 may not be supported
2026-08-13 09:48:22 - WakeVP: *** VP2 Not woken
2026-08-13 09:48:18 - WakeVP: *** VP2 Not woken

VIA TCP / Logger Off

2026-08-13 11:22:18 - OpenTcpPort: Error - Connection timed out 192.168.0.150:22222
2026-08-13 11:20:03 - OpenTcpPort: Error - Connection timed out 192.168.0.150:22222
2026-08-13 11:17:47 - OpenTcpPort: Error - Connection timed out 192.168.0.150:22222
2026-08-13 11:15:19 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.
2026-08-13 11:14:43 - OpenTcpPort: Error - Connection refused 192.168.0.150:22222
2026-08-13 11:14:32 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.

and after a RESET - TCP / Logger OFF 
2026-08-13 12:07:19 - OpenTcpPort: Error - No route to host 192.168.0.150:22222
2026-08-13 12:07:04 - OpenTcpPort: Error - No route to host 192.168.0.150:22222
2026-08-13 12:07:00 - OpenTcpPort: Error - No route to host 192.168.0.150:22222
2026-08-13 12:06:22 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.
2026-08-13 12:05:19 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.

Further Issue(s): From the very beginning the screensaver didn´t start after the specified time. i could start the big clock only manually.  And sometimes i powerOn the device, but the screen keeps black. then i take a short brake for 1-2min and powerOn again and in most cases the device will work. This behaviour is the same, whether with powerplug over the dedicated 5V plug or the micro-usb.

Remark: I did flash the sketches with different USB-cables to rule out a cable-issue.

Tnx and greets,
Reply


Messages In This Thread



Users browsing this thread: 1 Guest(s)