Small Lab (SLab) release

[Vic20]

@Vic20

I am sorry, but I am am not able to contrinute to the code. I have already done one mistake by thinking that I could use A3 in stead of D13 for DAC2. My mistake came about when I looked at these 2 pinout diagrams, noting that my board had an analog pin 3 while yours did not:

https://os.mbed.com/media/uploads/adustm/nucleo_f303re_arduino_left_2016_7_22.png

https://os.mbed.com/media/uploads/adustm/nucleo_f446re_arduino_left_2016_7_22.png

Then when taking a coser look I realized that the reason you use D13 with the reduced range caused by the led is that all boards only have one analog output A2.

AFAIK both the F303RE and F446RE have the DAC outputs at A2 and D13
As D13 is connected to the user LED in both cases, you need to mess with solder bridges or add gain in the D13 DAC driver.

So I will not try to change anything yet. (I have looked at the user guide / data sheet, and things like (Arduino pin) A3 port PB0 ADC12_IN8 (303-board) ADC3_IN12 (446-board) tells me little more than that it is some mux/ADC stuff).

Yes, ADCs are muxed. For instance PB0, connected to arduino pin A3 is the input number 8 of both ADCs #1 and #2 in the 303 board. But in the MBED code you only need to indicate which are the pins associated to the four ADC inputs SLAB uses.

In addition to your DAC/ADC I will try to get these Arduino/Python based projects running in order to control vintage devices and DIY hardware for experimental physical electronics:

https://github.com/mathiashelsen/agipibi

https://pypi.python.org/pypi/instrumentino

Seems interesting

[Vic20]

I strongly suggest supporting Python 3 - you will need to do it in the future anyway and it is best to do it while the codebase is still small. Porting a large pile of old code is not fun. If you need some help or advice on this front, feel free to PM me, I have quite a bit of Python experience.

I have taken your suggestion seriously and I'm now proud to announce the 1.3 release of the SLab system.
https://github.com/R6500/SLab
It now should run without problems both in Python 2.7 and Python 3.x

[rstofer]

Regarding the transistor family of curves:  Am I correct in using 330k Ohm for the base resistor and 1k Ohm for the collector resistor?  FWIW, I am using a 2N3904 and I don't recall the documentation specifying a particular transistor.

Code: [Select]

dc.iDeviceCurve(1.0,3.0,0.25,0.0,3.2,0.1,ri=330.0)

For some strange reason, I only get 4 curves versus 8 and my graph scales don't extend as far as those in the documentation.

In any event, this project is neat!  I have a lot to read but, so far, the Examples are working out fine.  Except Example 12 and that will turn out to be operator error...

OOPS!  Forgot the picture...

[janoc]

I strongly suggest supporting Python 3 - you will need to do it in the future anyway and it is best to do it while the codebase is still small. Porting a large pile of old code is not fun. If you need some help or advice on this front, feel free to PM me, I have quite a bit of Python experience.

I have taken your suggestion seriously and I'm now proud to announce the 1.3 release of the SLab system.
https://github.com/R6500/SLab
It now should run without problems both in Python 2.7 and Python 3.x

Excellent!  Thanks a bunch! 

[rstofer]

For some strange reason, I only get 4 curves versus 8 and my graph scales don't extend as far as those in the documentation.

What's actually happening is that the top trace has the other 4 traces buried under it.  Not exactly, but close enough they can't be seen unless I zoom in to a rectangle.

I need to think about what that means.  I did a few print statements to convince myself that I was looping enough times and generating 8 traces of data - which I am.  But the last few blocks look pretty much alike.

Maybe I'm saturating the transistor.