Lord_Nightmare has quit [Ping timeout: 246 seconds]
Lord_Nightmare has joined #glasgow
Shiz has quit [Ping timeout: 240 seconds]
GregNGM has quit [Ping timeout: 252 seconds]
GregNGM has joined #glasgow
Shiz has joined #glasgow
bvernoux has joined #glasgow
redstarcomrade has joined #glasgow
fibmod has joined #glasgow
redstarcomrade has quit [Quit: Connection closed for inactivity]
thaytan has quit [Ping timeout: 272 seconds]
<thasti>
Thanks Attie. This shows that pin IDs >7 are at least valid sometimes, but not how they would assign to the different ports (if I'm not missing something). Anyways I got my usecase working fine with this approach now, good to have a community in reach :)
<d1b2>
<Attie> np! glad you got it working / sorry for my delayed responses...
<thasti>
Another question/request for improvement could be: Is there any way of using ports at different voltages from the command line? My current hack involves supplying "-V 3.3" and then in the applet doing "device.set_voltage("B", 5.0)"
<d1b2>
<Attie> intriguing... mind me asking what you're interfacing with?
<d1b2>
<Attie> might be nice to record that as an issue on the repo (please feel free to submit with some info)
<d1b2>
<Attie> there are some things around the user interface that still need to be worked out, like how (if) to operate multiple applets concurrently
<thasti>
i chose the glasgow as the platform for an experimental setup at a particle accelerator - it needs to run multiple independent comms interfaces (5V-SPI to a DAC, 3.3V I2C/SPI to control some ASICs, 5.0V CMOS inputs from the accelerator, etc)
<thasti>
so far, it's serving me extremely well as a hardware platform - but since multi-applet-support isn't there yet I have all my interfaces integrated into a single applet
<d1b2>
<dragonmux> one thing you can do is supply your own voltage setting arguments or just entirely drop the -V and -M options for your applet and set the port voltages yourself as you're already doing for interface B
<d1b2>
<dragonmux> er.. s/interface/port/
<d1b2>
<dragonmux> it is supported to have the two ports at different voltages, so that would be fine
<thasti>
dragonmux: actually, -M or -V is a required argument, right?
<thasti>
trying without either gives me "one of the arguments -V/--voltage -M/--mirror-voltage --keep-voltage is required"
<d1b2>
<dragonmux> only if you run the function from the framework that adds those arguments to your applet's arg parser
<thasti>
ah, that would be `GlasgowApplet.add_run_arguments()`, I guess?
<thasti>
indeed, in my specific case I have no use for adjusting these voltages using the command line in the first place...
<d1b2>
<dragonmux> if you override add_run_arguments and don't call access.add_run_arguments(parser) in the overridden function then you have control over those
<thasti>
that's a good idea, i'll try that out
<d1b2>
<dragonmux> the access object is one of DireectArgumetns from glasgow.access.direct.arguments if you want to review the code being invoked
<d1b2>
<dragonmux> er.. with the t and n in Arguments the right way around, heh
<thasti>
:) found it
<thasti>
that does the trick, perfect
<d1b2>
<Attie> sounds like a fun project, thanks for sharing @thasti