LabVIEW
VISA TCPIP is difficult to be established
Solved!
As the PID settings, my way is not silly. Please refer to Lakeshore 336 Temperature controller and Cryocon 22C Temperature controller. For whole range of 2K--300K, usually one has to set several domains PID. These Temperature controllers have a PID table function and Ramping capability. If you want to sweep temperature with a speed of 5K/min or set Temperature point by point, the controllers automatic change PIDs by interpolating the PID tables. Instead of using the controller's PID table, what I am doing is programmatically set PID by interpolating a user defined PID file(table). Of cource I have a rule that every cycle if the last setted PID is the same as this time interpolated PID, it will not be written to the instrument.
PS: the VI your suggested misses some parts. It contains several channel(Devices). For example, one channel for system (VTI chamber), other for sample holder, etc.
Ok, clear, you can programmatically change PID values, but you need to do so only at certain times when you reach some temperature range limits, yep? So when your temperature is inside a certain interval where you can use a single PID param set, you should NOT change these parameters at EVERY reading iteration. I imagine, at the device hardware level, changing PID parameters requires more time than a simple result read out...?
I do not have time to examine your hardware and how exactly the device can be addressed using the driver VIs, but here is just an example with manual PID change, it might give you idea how to use a State Machine...The manual boolean control ("Change PID!") can be replaced by a temperature limit check, so you ONLY fire the PID settings VI when needed, and NOT at every iteration. Fix up the code with missing VIs as needed...But do not forget, the only repeated action should be the simple "Read results" VI...
