mumptai has joined #m-labs
mumptai has quit [Ping timeout: 245 seconds]
sb0 has joined #m-labs
sj_mackenzie has joined #m-labs
rofl__ has joined #m-labs
sh[4]rm4 has quit [Ping timeout: 265 seconds]
FabM has quit [Ping timeout: 258 seconds]
FabM has joined #m-labs
rofl__ is now known as sh4rm4
nicksydney_ has joined #m-labs
nicksydney has quit [Ping timeout: 244 seconds]
nicksydney has joined #m-labs
nicksydney_ has quit [Ping timeout: 244 seconds]
mumptai has joined #m-labs
sj_mackenzie has quit [Remote host closed the connection]
_florent_ has joined #m-labs
FabM has quit [Remote host closed the connection]
FabM has joined #m-labs
_florent_ has quit [Ping timeout: 255 seconds]
<
GitHub103>
artiq/master f3b727b Sebastien Bourdeauducq: py2llvm: replace array with list
* ysionneau
is having trouble using pylibftdi to talk to papilio pro :(
<
ysionneau>
someone ever used this?
<
sb0>
to papilio pro? why?
<
ysionneau>
it's one of the few devices I have which have ftdi chip
<
ysionneau>
I could try with M1 as well
<
sb0>
what are you trying to do with it?
<
ysionneau>
I'm trying to find a solution to talk to ftdi products for the thorlabs controllers
<
ysionneau>
thorlabs use ftdi
<
sb0>
hmm how do they use it?
<
sb0>
and using the kernel driver isn't good?
<
ysionneau>
I could do that and do if os == win32 then open "COMxx" else /dev/ttyUSBxx
<
ysionneau>
but I wanted to have a nice solution with the crossplatform (and open source) pylibftdi
<
ysionneau>
which would be ... well ... cross platform
<
sb0>
yeah. or if you have to add a dependency anyway, maybe pyserial
<
sb0>
in general, the further away you stay from ftdi-stuff, the better
<
ysionneau>
even the open source libftdi is buggy?
<
sb0>
ftdi chips and drivers are like sausages, you'd better not know how they are made
<
ysionneau>
compared to libftd2xx
<
ysionneau>
good one :)
<
sb0>
yeah, it's less disgusting, but still a bunch of crap code
<
sb0>
and the ftdi chip design is also full of crap
<
ysionneau>
anyway, I think you're right, I should better just use pyserial and the kernel driver
<
ysionneau>
let's do that
<
sb0>
if you go pyserial, can you also modify coredevice/comm_serial.py?
<
sb0>
I guess setting baudrates etc is different on win32/linux, so pyserial might make sense
<
ysionneau>
yes let's hope it's well done and correctly works cross-platform
<
ysionneau>
but is should
<
GitHub3>
artiq/master 8af0301 Sebastien Bourdeauducq: transforms/tools/value_to_ast: list support
<
sb0>
ysionneau, can you add unit tests for the lda and thorlabs stuff?
<
sb0>
e.g. set/get attenuation, and check that the readback from the device is what you wrote
<
sb0>
ysionneau, also I've reorganized the drivers a bit, the client/controllers are now in frontend/ (and installed in /usr/bin)
<
sb0>
and the bulk of the code in artiq/devices
<
ysionneau>
I'm just looking at it right now
<
sb0>
if you want to use the driver without rpc (might simplify unit tests) you can simply import from artiq.devices.xxx
<
ysionneau>
yep sure
<
ysionneau>
indeed it's cleaner to just have the driver class separate to the controller instanciation logic + argparse stuff
<
ysionneau>
for the GUI do you think maybe Cedric Bail would be interested?
<
ysionneau>
I don't know much GUI developers unfortunately :/
<
sb0>
hmm I don't know him.. do you?
<
ysionneau>
not much, but [florian] knows him well
<
ysionneau>
he worked a few years at Freebox, on Elixir (javascript binding of EFL or something like that)
<
ysionneau>
basically Cedric is(was?) an EFL developer
sb0 has quit [Quit: Leaving]
<
[florian]>
ysionneau: he still is
jaeckel has quit [Ping timeout: 245 seconds]
jaeckel has joined #m-labs
ohama has quit [Remote host closed the connection]