Skip to content

Commit c0033bc

Browse files
word change
1 parent a95a158 commit c0033bc

1 file changed

Lines changed: 2 additions & 30 deletions

File tree

README.md

Lines changed: 2 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,7 @@ The system is currently validated with industry-standard hardware, covering a re
116116
| **Dielectric Analysis** | **Keysight E4980A** | C-V Analysis and Magnetodielectric characterization. | 20 Hz - 2 MHz |
117117
| **Pyroelectric** | **K6517B** + **Temp Controller** | Current vs Temp (detecting Curie temperature). | $10^{-15}$ A Resolution |
118118

119-
*While the current implementation drives specific instruments, the underlying framework is hardware agnostic. Researchers need only replace specific SCPI commands to utilize the suite with different models.*
119+
*While the current implementation drives specific instruments, the underlying framework is highly customizable. Researchers need only replace specific SCPI commands to utilize the suite with different models.*
120120

121121
### Module Previews
122122

@@ -133,7 +133,7 @@ The system is currently validated with industry-standard hardware, covering a re
133133

134134
---
135135

136-
## Pre-requisites: The VISA Driver "Catch-22"
136+
## Pre-requisites: The VISA Driver
137137

138138
> [!WARNING]
139139
> **A VISA Backend is Required:** `PyVISA` is a Python wrapper, not a driver. For PICA to communicate with hardware, you **must** install a VISA backend on your system first. If you attempt to run the software on a clean machine without a VISA implementation, it will fail to find the instruments. This is the most common failure point for new instrument control setups.
@@ -163,11 +163,6 @@ PICA is structured as a standard Python package.
163163
pip install .
164164
```
165165

166-
*Note: The base installation of PICA does not include `gpib-ctypes`, which is only required for specific GPIB hardware on Linux systems (e.g., linux-gpib). If you need this functionality, install it separately:*
167-
```bash
168-
pip install .[gpib]
169-
```
170-
171166
*Note: Ensure you have the NI-VISA drivers installed on your host machine to allow `PyVISA` to communicate with the hardware.*
172167

173168
## Running the Software
@@ -184,29 +179,6 @@ PICA is structured as a standard Python package.
184179
pica-cli
185180
```
186181

187-
---
188-
## Common Issues & Troubleshooting
189-
190-
This section covers the most common issues encountered when using PICA.
191-
192-
### 1. VISA Timeout Error or Resource Not Found
193-
194-
This is the most frequent issue and usually indicates a problem with the connection between the computer and the instrument. Follow these steps to resolve it:
195-
196-
1. **Check Physical Connections:** Ensure all cables (GPIB, USB, Ethernet) are securely connected to both the instrument and the computer.
197-
2. **Use the VISA Scanner:** Run the **VISA Instrument Scanner** utility from the PICA launcher.
198-
* If the instrument appears in the list, the connection is working. Note the correct VISA address.
199-
* If the instrument does **not** appear, PICA cannot see it. Proceed to the next steps.
200-
3. **Power Cycle the Instrument:** Turn the instrument off, wait a few seconds, and turn it back on. This can often resolve temporary communication hangs.
201-
4. **Restart the Computer:** If the problem persists, a full restart can resolve driver or backend issues.
202-
* Shut down the computer completely, leaving the instrument turned off.
203-
* Start the computer.
204-
* Once the system is fully booted, run the PICA VISA scanner.
205-
* Turn on the instrument.
206-
5. **Check Drivers and Communication Mode:**
207-
* Ensure you have the correct VISA backend installed (see [Pre-requisites](#pre-requisites-the-visa-driver-catch-22)).
208-
* If using a different communication interface (e.g., switching from GPIB to USB), verify that the necessary drivers are installed and that the instrument is configured for that mode.
209-
210182
---
211183
## Running Tests
212184

0 commit comments

Comments
 (0)