x electroglas eg x wafer prober. Electroglas model b motorized manual prober. Electroglass x semiautomatic prober. Manufacturer: Electroglas. MANUAL LOAD PROBER AUTOMATICALLY PROBES UP TO A 6″ (mm) WAFER INCLUDES LOW PROFILE TABLE AND. This item has been sold – Electroglas X ELECTROGLAS X PROBER MANUAL LOAD WITH 6″ CHUCK FOR UP TO 6″ WAFERS. (IEEE OPITON.
|Published (Last):||20 May 2017|
|PDF File Size:||1.87 Mb|
|ePub File Size:||10.59 Mb|
|Price:||Free* [*Free Regsitration Required]|
I want to check the MAV bit in the status byte, and any query command should set this bit.
Electroglas prober manual – Google Docs
For example on any other electroglaas Documents are listed by category below. Instructional videos are available by clicking on the icons and entering your login and password as assigned.
This makes me think that the documentation is wrong, and the interface is not 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.
There are two more parallel loops: The UI and VISA read loops generate commands and push them electrglas a queue, elecfroglas the the commands are executed by the consumer loop. Since the reads are short, if it is necessary to write to the over the GPIB bus, it is only necessary to wait 50ms for the read to timeout, and then the write can be performed. It may be wholly or partially applicable to your prober; most of commands work on my prober.
Unfortunately I find no descriptions in this manual regarding the Electroglas prober behavior as regards status byte bits; i. How do I know when it has a message waiting? Best of luck with the manual.
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 electrogglas, 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. Then I have a chance electroblas perform 201x pending writes, after which I read again for messages from the EG. The host is reading Earlier I had set the read timout to 50ms, and this was not enough, I was missing a lot of messages from the EG.
EMTS/Electroglas 2001X P/S Automatic Wafer Prober
I think the moral of this story is that GPIB is not a good bus if you have asynchronous two way communication. Luckily is seems my workaround is good enough for my purposes. MD0S0 lasts until either: Since this option can take the value of -1 I am assuming that this means that the prober will never time out; i. You may have a similar configuration setting in a menu or a configuration file on the EG I would assume that even the unsolicited messages such as the BC1 message I receive when loading the first wafer from a cassette will assert this bit.
On my prober, SRQ is set to ‘disabled’. It would be great if there were some setting of the prober so that unsolicited messages would wait for a GPIB read from the host. My big problem right now is that if the host is not actively reading when the onsolicited message is sent, the message is gone and the program hangs. The typical sequence is: This tells the host to start testing the die.
If the host misses the TS message, the program hangs forever, because the host thinks it is still waiting on the prober to finish moving. The action loop runs the test, logs data, and sends GPIB messages to the prober. I guess my design flaw was to design the read loop to just repetitively read until timout and add commands to the QSM when a message is recieved from the prober. What I should do is make a functional global that tracks exactly what state the prober is in, and use that to determine if the read loop will read or just do nothing.
I assume someone somewhere has made a control program for the likely in Rocky Mountain Basic or C I would be curious to know how they solved this issue of duplex communication using GPIB. January December Author Write something about yourself. No need to be fancy, just an overview.
Powered by Create your own unique website with customizable templates.