trying to install 3.1.2 on Companion Pi. Configuration page load crashes repeatedly.
any ideas?
24.01.27 22:04:42 Instance/ModuleHost: Instance “yamaha-CLQL” failed to init: Error: Call timed out Error: Call timed out
at t.IpcWrapper.sendWithCb (/opt/companion/main.js:2:2165956)
at Object.init (/opt/companion/main.js:2:7902222)
at l. (/opt/companion/main.js:2:7911209)
at l.emit (node:events:514:28)
at l.emit (node:domain:489:12)
at ChildProcess. (/opt/companion/main.js:2:2153461)
at ChildProcess.emit (node:events:514:28)
at ChildProcess.emit (node:domain:489:12)
at emit (node:internal/child_process:937:14)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Copy that. Have you tried the companion beta 3.2.2?
Basically, companion is timing out trying to load the module, which can happen on low power RPIs, which is why I was asking. An RPI4 with 4g shouldn’t have a problem.
Might be a bug fixed in the beta, so give it a try if you can.
Well, 3.2.2 now.
Still the same. There is no desk in the network now though.
24.04.15 12:33:49 Instance/ModuleHost: Instance “yamaha-CLQL” failed to init: Error: Call timed out Error: Call timed out
at t.IpcWrapper.sendWithCb (/opt/companion/main.js:2:2450560)
at se.init (/opt/companion/main.js:2:2792889)
at l.s (/opt/companion/main.js:2:2803654)
at l.emit (node:events:517:28)
at l.emit (node:domain:489:12)
at ChildProcess. (/opt/companion/main.js:2:2437855)
at ChildProcess.emit (node:events:517:28)
at ChildProcess.emit (node:domain:489:12)
at emit (node:internal/child_process:944:14)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
24.04.15 12:33:49 Instance/ModuleHost: Unhandled error restarting connection: Error: Restart forced
Weird!
Desktop version of Companion seems to still be fine, so not sure what the issue is.
Can you send me the “support bundle” so I can see if there’s a hint in the logs as to what’s going wrong?
Trying to get the MIDI running in 3.5.4 . Module is in Dev folder and loaded, but configuration can’t start with this error:
25.04.25 17:58:53 Instance/ModuleHost: Instance “yamaha-MIDI” failed to init: Error: Call timed out Error: Call timed out
at t.IpcWrapper.sendWithCb (/opt/companion/main.js:2:2761785)
at k.init (/opt/companion/main.js:2:3649235)
at V.o (/opt/companion/main.js:2:3664316)
at V.emit (node:events:524:28)
at ChildProcess. (/opt/companion/main.js:2:3661428)
at ChildProcess.emit (node:events:524:28)
at emit (node:internal/child_process:949:14)
at process.processTicksAndRejections (node:internal/process/task_queues:91:21)
25.04.25 17:58:53 Instance/ModuleHost: Unhandled error restarting connection: Error: Restart forced
Is this giving any clue? Same happens with the sysex Module.
The RCP module is trying to connect to a console at 192.168.1.128 and it’s not seeing it.
The CLQL module is crashing, but you’re running an old version. You should try the latest from here, 3.1.3.
When I copied the support bundle the console was linked to my computer. IP was correct.
I will try the newer module next time I get a hand on a CL/QL (or would DM3 be enough to test it?).
Thanks for your efforts.
The RCP module will work with the CL/QL, TF, DM3, DM7 and Rivage. The CLQL module (only available from this website) will ONLY work with the CL and QL consoles.