Electroglas 2001x Manual
Model: Electroglas Horizon 4085X OEM Manual for your reference S/N: W497088. Description: The ElectroGlas Horizon 4085X Automatic Wafer Prober System is a precision wafer positioning system capable of positioning for probe 5” through 8” wafers (125mm – 200mm). Jul 27, 2016 - Electroglas 2001X Prober. The Base Unit is an independent wafer probing unit which performs manual load, semiautomatic alignment.
I am controlling an Electroglas 4080 prober with GPIB and LabVIEW 7.0 on Solaris. When I execute a VISA Read STB, the result is always 0. I want to check the MAV bit in the status byte, and any query command should set this bit. For example on any other instrument: Write: *IDN? Read STB: 20 Read STB: 4. Onra chinoiseries rar.
The EG4080 does not respond to *STB?, *ESE?, or any of the other standard 488.2 queries other than *IDN? This makes me think that the documentation is wrong, and the interface is not 488.2 compliant. The only GPIB options available through the EG software are serial poll or parallel poll, and SRQ enable/disable. I have found a way to get my software working without polling the STB. VISA read is performed repetitively in a while loop with timout set to 50ms. Then I put the 'code' part of the error cluster into the select port of a case structure. If the error code matches a read timeout, the error is cleared. Billie holiday the complete commodore recordings rar extractor free.
There are two more parallel loops: one for UI input, and one consumer loop. The UI and VISA read loops generate commands and push them onto a queue, and the the commands are executed by the consumer loop. Since the reads are short, if it is necessary to write to the 4080 over the GPIB bus, it is only necessary to wait 50ms for the read to timeout, and then the write can be performed. IEEE488.2 compliant does require a small standard set of commands, c.f. Of which the Electroglas prober appears to respond only to *IDN? Attached is a version of the EG Commander External I/O Commands document, valid for versions 4.8 and up.
It may be wholly or partially applicable to your 4080 prober; most of commands work on my 4090 prober. Unfortunately I find no descriptions in this manual regarding the Electroglas prober behavior as regards status byte bits; i.e. How do I know when it has a message waiting? Best of luck with the manual. Sincerely, Leif S. Kirschenbaum, Ph.D.
The EG prober can act as a master by sending unsolicited messages to the host. The problem is that I need to be always listening for these messages, and still be able to send messages back to the prober when I want to. I have discovered a nasty problem, if the host is not actively waiting for a message on the GPIB bus when the EG prober sends the unsolicited message, the message evaporates and the program hangs because it is waiting for a message from the prober that never comes because the EG thinks it was already sent.
I am not sure if this is the way GPIB is supposed to work, I had assumed that the EG would just buffer the message until the host initiates a read, but this does not seem to be the case. When I use a VISA_read vi, it locks up the GPIB bus and prevents writes until it times out. I am using a 2 second timout, so after two seconds the VISA_read vi exits with an error that I clear programmatically. Then I have a chance to perform any pending writes, after which I read again for messages from the EG. The host is reading 99.99% of the time, and this seems to be good enough for my application. Earlier I had set the read timout to 50ms, and this was not enough, I was missing a lot of messages from the EG. I think the moral of this story is that GPIB is not a good bus if you have asynchronous two way communication.