[ARTIQ] starter ARTIQ hardware for neutral atoms

2017-03-07 Thread Neal Pisenti via ARTIQ
Hi all,

The strontium lab at the JQI is finalizing the computer control system for
our new experiment, and I am finally revisiting ARTIQ to figure out what
hardware we need.

Our current experiment uses the following:

* 48 digital outputs (8 are designated as triggers for other devices)
* 24 analog outputs (from NI's PCI-6733 DAC cards)
* several (~8?) homebuilt DDSs, which aren't phase synchronized but have
profile-select control for hopping frequencies/initiating simple frequency
ramps with ~ < 1ms latencies.
* Point Grey / PIXIS cameras for image acquisition, currently analyzed
"offline" between experimental shots
* For analog ramps, the fastest update rate we currently use is 10us/sample
(although that also has to do with our shitty labview control interface,
which can crash if your DAC sample buffer gets too long...)
* Eurocard 19" rack enclosures are already used for most of our custom
electronics; we like this form factor.

That all said, in the new system we would like

* A few phase synchronized DDS (likely operated at 30-50MHz), eg, for
fancier lattice AOM control, feed forward/feedback on narrowline clock
laser, ... other
* analog input
* upgraded analog output to move away from NI; some channels with PDQ-esque
AWG capability, although most of our analog control needs are relatively
slow.
* more analog/digital I/O for future expansion.

Given those requirements, here's what I'm thinking to buy in the short &
longer term. Since we're still building the vacuum chamber, many of the
"fancy" control requirements are many months away. I was hoping to get
input/feedback/suggestions as to whether this plan sounds good:

* For ARTIQ core device, we would ideally jump straight to using a Kasli,
but as that isn't likely to be done in the next few months, I was planning
to use a KC705 as the core.
* KC705 has 2x FMC headers, which would drive 1x VHDCI carrier card,
providing 8x IDC for EEMs. We would buy FMC -> VHDCI adapters for this
interconnect.

>From 8 EEM headers, we could get:

* 6x BNC EEMs -> 48 DIO
* 2x EEMs for... analog IO? Initially, we could continue to use the 6733
DACs, but longer term switch to Zotino/PDQ/...

It seems we will eventually want at least one Kasli expansion DRTIO module.
This would be connected on the KC705 SFP.

**Specific questions**:

* what limitations are there (latency/bandwidth/etc) on daisy-chaining
additional Kasili DRTIO modules off of the single KC705 SFP?
* What IO mapping needs to be done to support KC705 as a core driving EEMs
over the two FMC connectors? Is there any plan to allow the HPC connector
to drive an entire VHDCI adapter on it's own (thus expanding the KC705 to
drive 12 EEM modules, 1x from the HPC + 0.5x from the LPC), and is this
even desirable over, say, adding a Kasli over DRTIO?
* Is there an estimate on the timescale for finished Kasli?
* Should I reconsider any of this approach, or does it seem reasonable? Any
other suggestions/advice?

Thanks in advance for the input!
Neal
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq


Re: [ARTIQ] starter ARTIQ hardware for neutral atoms

2017-03-09 Thread Neal Pisenti via ARTIQ
>
>
> On Wednesday, March 08, 2017 06:11 AM, Neal Pisenti via ARTIQ wrote:
> > * For ARTIQ core device, we would ideally jump straight to using a
> > Kasli, but as that isn't likely to be done in the next few months, I was
> > planning to use a KC705 as the core.
>
> The "EEM" DDS/synth Kasli extensions may not necessarily be ready before
> Kasli. So I don't see how the KC705 helps - is it because you want more
> extensions that one Kasli would support? Supporting this KC705 scheme is
> more gateware development and one more configuration that needs to be
> documented, packaged and maintained. Maintainance means that we need to
> check regularly (preferably automatically) that it keeps working when we
> modify ARTIQ and fix any bugs that pop up. It takes work.
>

Valid point -- my main thought with this setup is exactly what Tom
articulated; the KC705 -> VHDCI is a stopgap until Metlino/Kasli
development is completed. And it would allow us to start using digital IO
immediately via the PCB_3U_BNC EEM, and we might spin up some in-house
boards for multichannel DAC over SPI. We shouldn't need the DDS/synth
modules for some time still, since all of our DDS currently exist as "slow
peripherals" in the artiq sense.

The other short-term alternative I see is adapting either the nist_clock or
nist_qc2 builds, and making our own FMC -> ___ breakout. But piggybacking
on the EEM architecture seems cleaner and more future-proof. When the Kasli
is done, we would either abandon the KC705 for a Kasli as core, or
(depending on the cost) plan for 1x Kasli as DRTIO connected to the KC705
SFP. That would certainly put a limit on how many things we can control,
but will probably satisfy our needs in the foreseeable future.

Even though the uTCA/Metlino setup will be exceedingly nice, for neutral
atom experiments it is currently overkill. But whether the upfront cost of
a uTCA chassis & associated hardware is worth additional development
headache to exclusively use Kasli baords...? Remains to be seen.


> * KC705 has 2x FMC headers, which would drive 1x VHDCI carrier card,
> > providing 8x IDC for EEMs. We would buy FMC -> VHDCI adapters for this
> > interconnect.
>
> What adapters in particular? http://www.ohwr.org/projects/fmc-vhdci? We
> didn't check compatibility of any of those.
>

When I chatted with Joe, we looked at this one:
http://www.ohwr.org/projects/fmc-dio-32chlvdsa/wiki/Wiki

@Greg -- are the board files available for this? I looked on the Creotech
website but couldn't find it for sale anywhere (which is odd, because I
swear I saw it there before, for ~ $500). Even so, I wonder about pricing
it out at MacroFab or one of these other small-turn PCB companies before
spending $1k on a pair of them.

Cheers,
Neal
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq


Re: [ARTIQ] ARTIQ Digest, Vol 34, Issue 3

2017-03-15 Thread Neal Pisenti via ARTIQ
I was about to email out for quotes from Creotech and Technosystem for the
FMC -> VHCDI boards. It sounds like Joe wants ~2x, we want 2x, and @Tom,
I'm guessing you guys want at least 2x as well... that puts us in the qty
6-10 range.

If we can bulk the order, that should bring the price down a little.
Talking to the accounts people here, it sounds like it is "nearly
impossible" to bill groups outside UMD (ie, to put 10x boards on a single
PO through UMD, then re-arrange monies afterwards), but hopefully either of
those companies will quote us with the assumption/promise that each group
will pay for their quantity separately...?

If you guys have any other ideas, let me know.

Neal

On Fri, Mar 10, 2017 at 8:58 AM Grzegorz Kasprowicz via ARTIQ <
artiq@lists.m-labs.hk> wrote:

I already received assembled 3U boards including VHDCI carrier and BNC IO.
So we can test whole setup in the lab quickly.
You can help us with simple HDL design for KC705 that i.e. toggles IOs or
makes loopback: ttl->lvds->VHDCI-> FPGA-> VHDCI->lvds->TTL.
At the moment we are so occupied with other tasks that every help is very
valuable.
Greg

On 10 March 2017 at 14:33, Thomas Harty 
wrote:

> It is compatible with VHDCI carrier - I used the same pinout.

Thanks for confirming that. In that case, we'll have a few of these made
up, and plan to use them with the KC705 + VHDCI carrier as a short-term
solution.


-Original Message-
From: ARTIQ [mailto:artiq-boun...@lists.m-labs.hk] On Behalf Of Thomas
Harty via ARTIQ
Sent: Friday, March 10, 2017 12:56 PM
To: artiq@lists.m-labs.hk
Subject: Re: [ARTIQ] ARTIQ Digest, Vol 34, Issue 3

> ..., and we might spin up some in-house boards for multichannel DAC over
SPI.

FYI, the Zotino and Novogorny DAC/ADC EEMs are now funded (Oxford/Freiburg)
and being designed by WUT. They should be ready in ~12weeks. We're planning
to contract M-Labs to provide full support for them.

The draft specifications are on the Wiki at
https://github.com/m-labs/sinara/wiki feel free to comment on them if you
have requests/questions.

> What adapters in particular? http://www.ohwr.org/projects/fmc-vhdci?

@Greg, can you confirm whether this is compatible with the VHDCI carrier?
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq


___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq


Re: [ARTIQ] Pipistrello Install Issue

2017-08-01 Thread Neal Pisenti via ARTIQ
It almost certainly is a path issue -- depending on how you have anaconda
installed, you might need to manually prepend the conda path to your PATH
variable. I'd check ~/.bashrc, or 'echo $PATH' to verify that's not the
issue. Another thing to try -- if you run python from the command line and
try to import artiq, does it import cleanly?
On Tue, Aug 1, 2017 at 10:49 AM Joe Britton via ARTIQ 
wrote:

> >​
> I've followed Chris' suggestion and artiq 2.4 is listed in my
> environment's packages.
> ​>​I can find artiq_flash.py files in my file manager but these are not
> able to be called.
> >Would this be something to do with paths? Will
> ​
> Just now I followed Ballance's instructions. And confirm I can run
> artiq_browser from the command line. I'm using Ubuntu 14.04 and Conda
> 4.3.22.
>
>
> On Fri, Jul 28, 2017 at 10:06 AM, Joe Britton 
> wrote:
>
>> Also be sure you're using ARITQ 2.x. See Release Notes.
>>
>>
>> https://github.com/m-labs/artiq/blob/471605ec1ed951f9033472a19c04287494978d49/RELEASE_NOTES.rst
>>
>> On Thu, Jul 27, 2017 at 6:43 PM, Chris Ballance via ARTIQ
>>  wrote:
>> > Hi,
>> >
>> > Do not try to install from source - installing the package is much
>> easier.
>> >
>> > Following the instructions at
>> > https://m-labs.hk/artiq/manual-release-2/installing.html
>> > After running
>> >
>> > $ conda create -n artiq-main artiq-pipistrello-nist_qc1
>> >
>> > (which should finish without error)
>> > Then
>> >
>> > $ source activate artiq-main
>> >
>> > followed by
>> >
>> > $ conda list
>> >
>> > should show you the list of installed packages in this environment. This
>> > should include artiq 2.4 - does it?
>> >
>> > C
>> >
>> >
>> > On 26/07/2017 16:29, William Evans via ARTIQ wrote:
>> >
>> > Hello there,
>> >
>> >
>> >
>> > I have been trying to install the ARTIQ system on a pipistrello to
>> trial it
>> > and demonstrate it to my group at the University of Sussex.
>> >
>> >
>> >
>> > I have tried both installing from the packages and from source.
>> Sébastien
>> > has advised me to contact the mailing list to find some help.
>> >
>> >
>> >
>> > In my most recent attempt, I have followed the instructions in the
>> manual to
>> > install on a Linux VM. When trying to use the artiq_flash command I
>> receive
>> > the following message:
>> >
>> > ‘artiq_flash: command not found’
>> >
>> >
>> >
>> > Is anyone willing to help me to understand the installation process in
>> more
>> > detail and figure out how to proceed?
>> >
>> >
>> >
>> > Kind regards,
>> >
>> > William Evans
>> >
>> >
>> >
>> >
>> >
>> > ___
>> > ARTIQ mailing list
>> > https://ssl.serverraum.org/lists/listinfo/artiq
>> >
>> >
>> >
>> > ___
>> > ARTIQ mailing list
>> > https://ssl.serverraum.org/lists/listinfo/artiq
>> >
>>
>
> ___
> ARTIQ mailing list
> https://ssl.serverraum.org/lists/listinfo/artiq
>
___
ARTIQ mailing list
https://ssl.serverraum.org/lists/listinfo/artiq