Hardware
The Icicle package controls testing devices. Your devices must have these settings for proper communication
| Model | baud rate | termination |
|---|---|---|
| Keithley 2410 | 9600 | LF |
| Keithley 2000 | 9600 | device default |
| HP34401A | 9600 | device default |
| Keysight E3633A | 9600 | device default |
The GUI embeds the Tessie webpage in the expert mode window, but the default page is too detailed for this view. A simplified HTML file, Gui/Assets/guiOSU.html, was created and must be uploaded to the Raspberry Pi in your coldbox at ~/tessie/node/test1/public/
This section only applies to UIC and OSU who have the f4t thermal chamber for thermal cycling of the modules (This is NOT the same thing as the UIC coldbox used for standard module testing!). You can add control of the thermal chamber to the GUI by adding in temp_chamber_resource to the siteConfig.py file.
temp_chamber_resource = "TCPIP::<ip_address>::SOCKET"where ip_address is the ip address of your thermal chamber which can be obtained through the settings menu on the f4t controller on the thermal chamber. This will allow you to select your thermal profile from the GUI and to stop the running of the profile from the GUI as well. A thermal profile must be loaded on the thermal chamber prior to using it with the GUI.
To monitor the temperature and humidity during cycles, we use a DHT22 sensor connected to an Arduino that sends data to a computer which logs the data and updates a plot on a webpage. Our process follows UIC's Process. Here is our tutorial.
This is the monitoring hardware used at OSU, though other devices will also work.
- Arduino MEGA 2560 R3
- DFROBOT DHT22 Temperature & Humidity Sensor v2
- DFROBOT Ethernet Shield V3.0 - requires replacing a file on your computer to properly run Arduino code
NOTE: To run the Arduino code, your model will likely need >2KB of SRAM, which the UNO R3 (most common model) does not provide. Most other boards fit this RAM requirement.
