Hey,

I am trying to set up 2 Artiq systems master + satellite connected via fiber link. I connected SFP 1 of the master to SFP 0 of the satellite Kasli. LAN connection to the computer is at SFP 0 at the master.

I generated the device_db.py file from the two config files via
python -m artiq.frontend.artiq_ddb_template bonn2master.json -s DESTINATION bonn2satellite.json -o device_db.py
where I set DESTINATION to be 1, but there is no more documentation about what to put there as a destination that I could find. The device_db lists now all devices.

I can ping the master system and am able to run experiments using the master hardware, so this is working. I am however not able to access any hardware in the satellite, even that it is listed in the device_db.py with incremented adresses (e.g. ttl0 to ttl39 on master, tt40 to ttl55 on satellite).

I then created a routing table as explained here (https://m-labs.hk/artiq/manual/drtio.html?highlight=tree#using-drtio) and here (https://forum.m-labs.hk/d/191-drtio-master-satellite-ping-failure), but this did not helped.

The gateware is the one freshly provided by (QU)ARTIQ.

Is DESTINATION = 1 correct? Are the fiber connections correct? What else could I check? Can I communicate with the satellite via USB to check whether it is connected to the master?

Any help is appreciated.

Thanks
Thorsten

We generate the joint master+satellite device db for you at https://nixbld.m-labs.hk/job/artiq/full/device-db-bonn2/latest/download/1
Do flash the one crate with the new bonn2master bitstream. It was transitioned from standalone previous to master now (https://git.m-labs.hk/M-Labs/sinara-systems-legacy/commit/a95a3d939e780a2e12438da89bd9b22efdb88318). The new crate is already bonn2satellite.
Connect the devices bonn2master:SFP1 to bonn2satellite:SFP0. There is no need to set up a routing table. The default will work.
In the console log of the devices there will be messages indicated the link status and progress of synchronization between them. Use a terminal emulator to connect to them as described in the manual.

    Thanks for the quick help. Generating the device_db.py ourselves created indeed the exact same file as provided. So DESTINATION = 1 was a good guess. SFP connections were also all fine.

    Reflashing both systems worked. I can now access all harware modules. Thanks.

      16 days later

      As we are currently facing the same issue on our stuttgart2 system, I would also be interested in your solution.
      If I understood correctly, changing your bitstream solved the communication issue directly. This might also be the solution in our case, as I suspect that our Kaslis are currently configured as standalone devices from your side.

      rjo It would help a lot, if you could check into this and update our bitstreams if necessary. Just to make sure that I did not generate a wrong device_db, I would also ask you to generate one for our setup. Additional info: We want to make stuttgart2a the master, and stuttgart2b the satellite device. Thanks for your help!

      ThorstenGroh Just to have an option to double check: Did you see DRTIO entries in your master logs when rebooting the devices? If yes, can you post the logs for me to revise if needed? Thanks a lot!

            4 months later