We'd recently had a firmware update from a series of binaries received from M-Labs to reflect adding in a Sinara 5108 sampler into an ARTIQ chassis for SUServo capability, and since then, whenever we've run the chassis from our lab's dedicated Windows machine, we've been prompted to run aqctl_moninj_proxy alongside any use of the ARTIQ dashboard, which we didn't prior.

Furthermore, whenever this is run with the correct device IP address, the connection drops after (usually) several minutes, mentioning that connection to moninj was lost and that the "Event loop is closed" (indicating that the Asyncio loop was deleted/shut down). Is there any workaround to this issue, as it was not occurring in our old firmware version? We've tried changing out our Ethernet cable, our external clock is functional, we can still ping the core device even when the dashboard loses moninj connection, and nothing unusual shows up in artiq_coremgmt log.

Please post the entire error message as well as any prior error or warning messages emitted from the dashboard or the moninj proxy.


Here are the errors from the dashboard and from aqctl_moninj_proxy- this error doesn't show immediately, only after a few minutes and in a manner uncorrelated to if any experiment is being run or of any RTIO events.

Weird and possibly a bug in asyncio or possibly in your network driver as some websites seem to suggest. What Python version is this? When using anaconda it's hit or miss which version you are going to get.
Try modifying the code to ignore the error, see https://github.com/alexbers/mtprotoproxy/issues/40