Peter Drmota

This particular revision has not been tested in isolation, only as part of continuative code changes. I was not able to build the docs yet due to "OSError: no library...

> Would you be able to test it, i.e. take unmodified ARTIQ, apply exactly these changes, and test carefully? I can test them on 11790c6d if that's alright, as our...

I just ran into the same issue and started looking at the core analyzer log. To see what's happening, I added `rtio_log` messages to `AD9910.write_ram()`: ```python @kernel def write_ram(self, data):...

I'd be surprised if #1584 would change the behaviour, but we could try masking the high bytes as follows to make sure that the bits `63:56` stay open: ``` @kernel...

Looking at Table 5. Data Source Priority in the AD9910 datasheet, I believe that in your case, the ASF is provided by the bits in the active single tone profile...

> @pmldrmota Looks familiar? Yes. For us, this issue appeared for the first time when we added a Kasli v2.0 to the system (we tried it in both roles as...

Maybe I should highlight a difference: we never had `error(s) found (0x04)`, it was always `0x03`. Also, I've also never seen unexpected `TSCAck`. It might well be several issues with...

We got the same `panic!` when we tried to configure the stabilizer IP on a different subnet than the MQTT broker. For us that's a killer because we have to...

> Is there any particular reason you're using STATIC_IP instead of letting DHCP assign an IP? This sounds more like an issue with the network topology instead of an issue...

Thank you for looking at this! > It seems to me like it would be more sound to accept a f: FnOnce(client, topic, payload, properties) function that gets passed to...