AR488 Arduino-based GPIB adapter

[xardomain]

Ok,
decided to start with Artag version.
1) got PCB, GPIB connectors and Arduino micro pro from these places:
    - PCB https://oshpark.com/shared_projects/HrS1HLSE
    - GPIB EB67E connectors https://www.ebay.it/itm/Centronics-Plugs-Sockets-PCB-PCB-R-Angle-IDC-Panel-Mount-14-50-Way-EB0067/391507935311?ssPageName=STRK%3AMEBIDX%3AIT&var=660671677952&_trksid=p2057872.m2749.l2649
    - Arduino micro pro compatible https://www.amazon.it/gp/product/B07FQBQ4Z6/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

2) I have doubts about how to modifiy the config.h for the Micro Pro whatever I bought, either how to define the specific micro and what serial type I have to configure. I have attached a picture, with on the left the original config.h and on the right my mods. Could anybody please validate/correct it?

3) beside a USB cable there is should not be anything else needed, maybe a 3d printed enclosure,  right?

TIA.

Giuseppe Marullo
IW2JWW - JN45RQ

[xardomain]

Apparently problem solved.
Cannot test further, but it seems that the Micro got detected by KE5FX GPIB configurator.
Waiting for PCB and connector to arrive.

Thanks.

Giuseppe Marullo
IW2JWW - JN45RQ

[softfoot]

Very interesting project !! I ws particulaly intrigued by the tiny PCB mounted on the back of the connector.

Sadly, I have a rather complex 488 setup and a simple setup like that may not work. Has anyone made a pcb that has the SN75160 and SN75161 chips fitted that will support the software used here ??

Is there a schematic for this using an Uno/Mega ??

Best regards,
David

[rhb]

There is a schematic for using an Uno in the manual and photos of an example by me of a handwired version using ribbon cable earlier in the thread:

https://www.eevblog.com/forum/projects/ar488-arduino-based-gpib-adapter/msg2735644/#msg2735644

UPS just delivered the Uno shields @artag designed which I ordered from JLCPCB that map the Uno pins to a 24 pin header so you can use IDC ribbon cable and connectors to make custom cables to fit particular stacks of equipment without a lot of excess cable and fiddling.

You can get the Gerbers here:

https://oshpark.com/profiles/artag

I bought 5 of the Uno boards and 5 of the GPIB bus sniffer boards.

I'll try to get an example of the Uno shield assembled the next day or two.

BTW  The SMD Uno boards will source 200 mA total whereas the DIP ones will only source 100 mA.  Both will sink 200 mA and  source/sink 40 mA per pin.  Not quite a full 16 device GPIB, but good enough.

Have Fun!
Reg

[softfoot]

Yes I found the diagrams in the manual - should have looked there in the first place ;-)

I've just got the same people to spin an Uno shield with 75160/1 support. I'll post the outcome when they arrive.

Dave

[rhb]

Cool! 

I plan to use an AR488 per rack, so the limited capacity is not an issue for me.  I'll probably use a Pi with wired ethernet to control the AR488s for all the racks.

Reg

[Joern]

Hi
I just came across your project. Where can I find the documentation?
Can you also use your AR488 interface with the Keysight GPIB-VISA drivers? Or do I have to work with the Prologix driver?

[rhb]

The manual is on the github repository:

https://github.com/Twilight-Logic/AR488

I hope to solder up the Uno shield version here:

https://oshpark.com/profiles/artag

in the next day or two and  post pictures.

There is another  adapter design by @vindoline which is shown earlier in the thread.

It uses an extended Prologix command set which makes it very easy to control an instrument with the programming language of your choice just by reading and writing the USB serial port.

Have Fun!
Reg

[ogdento]

I finally built three adapters using artag's v3 board... they work awesome.  When I soldered them I held the connector and the arduino out a little bit (didn't push the parts all the way down onto the board etc) so I could more easily fit/fab a 3d case and further limit any potential for shorts.

The only problem I had was all of the boards came with the 32u4 pin 21 smaller than all the others... had to drill it out with a pcb bit for the header to fit.


Here's the final assembly...

[artag]

Thanks, you're right - I will correct it.

Oddly, I didn't have a problem assembling it using the header pins supplied with a generic Chinese board. If extra pressure was needed to overcome that, I didn't notice.

However, if the pins you used were slightly larger it would be a nuisance.
 

[PixieDust]

Does anyone foresee any issues using jumper cables on the Uno side of things?

https://www.sainsmart.com/products/65pcs-dupont-jumper-wire-cable-of-different-length-color-for-arduino-mega2560-r3

Breadboards aren't great for high frequency stuff I hear, this is a similar solution to a breadboard?

I'll obviously solder the other end to the GPIB connector, but it's the Uno side I'm worried about.

[iXod]

I see this project & thread has been going for some time (over a year), but I have a basic question.

What are the advantages to building this GPIB-USB controller rather than buying a Prologix unit? Or is that the wrong question to ask? Is the answer “Just because we can”? (c;

Interesting to see the development and creative contributions to the group effort here.

Thanks.

[softfoot]

For me cost was a large factor, plus it's an interesting and useful project.
Dave

[rhb]

@PixieDust  The Uno side is tedious to do by hand which is why I asked @artag to layout an Uno shield.  The weather has been very mild here so I've been working in my shop which at the moment has no HVAC.  I've got @artag's Uno shields sitting waiting for me to solder up connectors and test.  I'm trying to straighten up the chaos in my house and lab, but I should be able to test the board in the next day or two.

You can find my hand wired version earlier in the thread.  It's a serious pain to wire. I had to redo several wires because I got confused about where they went and connected them to the wrong pins.

@IXod  There are two reasons:

An Uno based controller is ~$5 for the Uno and shield plus $5 per device for cable and GPIB connector.  That's a lot cheaper than a Prologix.

The source code is available, so you can fix bugs and add features.  I plan to add a temperature and humidity sensor to the Uno and commands to read that.  That hasn't happened yet because WaveyDipole  got rather busy making changes and I got busy with other stuff, so I decided I'd wait until things settled down a bit.

Have Fun!
Reg

[artag]

One prologix isn't too expensive. But I see this is best fitted as one per instrument (the prologix USB doesn't have proper buffers either) and that would cost a lot more.

[xardomain]

Ok,
everything arrived for building 3 interfaces with the Arduino micro clones, now the question:

- is there a detailed photo about the GPIB connector's orientation against the PCB? I see the square for pin1 of the Arduino micro correctly oriented in the upper left, but the square pint 1 for the connector apparently does not match (lower right, looking the PCB from above, GPIB facing down).

If I turn 180 degrees the GPIB it seems correctly oriented (pin 1 of the GPIB connected to pin4 of the Arduino micro), according to schematic.

I have the ar488promicro of https://oshpark.com/profiles/artag

Included a couple of phots, could anybody confirm this is the right orientation?

Thanks.

Giuseppe Marullo
IW2JWW - JN45RQ

[artag]

The square pad correctly shows pin 1 of the connector. There are two designs for the 32u4 board, the first has pin 1 at opposite ends (the layout was easier) and the later one, marked v3 on the silkscreen, has them at the same end.

Putting them at the same end was not for neatness : it's because if it's that way round, the USB cable exits from the board in the same direction as common GPIB cables. Sometimes, instruments have more space that way.

Both pcbs are the same circuit and both can be used with the same software if you don't care how the cable is routed. It sounds as though you have the earlier one and you should take the square pin 1 marker as correct for both pcb and socket.

The board should be assembled with the socket first, pushing the connector through from the unscreened side so the pins show on the silkscreened side. In fact this is the only way you can assemble it with pin 1 in the square pad. Then solder them. Once the arduino is in place you can't reach the pins.

Then fit the arduino, on header pins. The silkscreen writing should be upright and visible, the arduino with the components on top and the connector pointing upwards so TX0 goes to the square pin.  As ogdento notes, pin 21 will be a bit tight.

See also https://www.eevblog.com/forum/projects/ar488-arduino-based-gpib-adapter/msg2728612/#msg2728612

I'm not sure why you think GPIB pin 1 should connect to arduino pin 4. Pin 4 is ground. GPIB pin 1 connects to arduino pin 6 (D3). Maybe you're comparing it with one of the other layouts ?

Many of the pin assignments differ between modules because the module pins themselves are different. The 32u4 version tries to assign them to maximise software efficiency. Make sure you select the correct board type in the arduino IDE as explained by WaveyDipole !
 

[xardomain]

Artag,
many thanks for your explanation. forget about the pin1-pin4, I have included another photo, is it the correct way to solder the GPIB connector?
I have the first attempt at a 3d enclosure, at this moment it is very basic(see photo), I hope to improve it.

Thanks in advance.

Giuseppe Marullo
IW2JWW - JN45RQ

[artag]

Artag,
many thanks for your explanation. forget about the pin1-pin4, I have included another photo, is it the correct way to solder the GPIB connector?

Yes, that's correct. Ogdento also mentioned leaving the connector fairly high on the pins to give space for a rim on a casing - that could be worth considering. Perhaps even a 2-part casing where the first part is trapped under the connector and the second part clips or slides onto it.

Be careful of the USB wire - most micro boards use surface-mount connectors that aren't very strongly fixed to the board. Strain relief for the plug / cable would be helpful.
 

[softfoot]

Hi, I am running AR488 on an UNO with a shield carrying a 75160/1 and it seems to work OK into my TEK744A on address 7. I am issuing commands via a terminal emulator att 115200baud. eg if I issue the following :-
  ++mode 1
  ++addr 7
  ++auto 1
  *idn?
it correctly prints the scope's ID string.

However, I cannot get the HP7470A emulator to work with the 744A ... the emulator displays a red banner saying receiving data but when I press the hardcopy button on the scope the count stays at 0.

The scope s set for GPIB, address 7, "hardcopy only" mode and the emulator is set for "listen-only" and "wait for device initiated print".

What am I doing wrong?   

TIA
Dave

[KE5FX]

Hi, I am running AR488 on an UNO with a shield carrying a 75160/1 and it seems to work OK into my TEK744A on address 7. I am issuing commands via a terminal emulator att 115200baud. eg if I issue the following :-
  ++mode 1
  ++addr 7
  ++auto 1
  *idn?
it correctly prints the scope's ID string.

However, I cannot get the HP7470A emulator to work with the 744A ... the emulator displays a red banner saying receiving data but when I press the hardcopy button on the scope the count stays at 0.

The scope s set for GPIB, address 7, "hardcopy only" mode and the emulator is set for "listen-only" and "wait for device initiated print".

What am I doing wrong?   

TIA
Dave

The usual problem is failure to select HPGL as the output format.  Either that, or it is expecting to address a 7470 plotter that isn't in listen-only mode (usually address 5 is the expected default).   

However, I'd suggest using host-requested plotting on those scopes.  For host-requested plotting with 7470.EXE:

• Hit Shift -> Display -> Config -> I/O and select Talk/Listen with a valid address (e.g., 3).   
  
• Hit Shift -> Hardcopy and ensure that HPGL is selected in the Format menu.
  
• Run 7470.EXE and select Acquire->Acquire from supported device at address 3.
  

Result:



Or simply run TDSBMP.BAT, which will also require Talk/Listen mode:







Notice that TDSBMP.BAT has set the scope back up for color .BMP output, so if you want to switch back to 7470.EXE, you will have to remember to put it back to HPGL.

[softfoot]

Thanks for the reply ... I am doing exactly what you did with 7470.exe but with the AR488 in mode 0 it does nothing when I press HARDCOPY on the scope.

I can cause the scope to dump the screen in plotter mode in talk/listen mode via a terminal prog with :
  ++mode 1
  ++auto 1
  ++addr 7               // My scope is on
  ++read_tmo_ms 15000
  hardcopy start

I can also dump the screen in talk only mode with :
  ++mode 0
  ++addr 5
  ++lon 1

and then pressing hardcopy on the scope.

But nothing seems to work with the emulator.

I'll try the bat file later today.

***UPDATE*** I tried TDSBMP.BAT -- it didn't work -- it just sat there "waiting for transmission to start". 
Does it make assumptions about the AR488's settings ??

As far as I can tell the AR488 is working OK since I can access the scope and dump the screen via a terminal emulator.
Not a great day :-(

Regards,
Dave
 

[KE5FX]

As far as I can tell the AR488 is working OK since I can access the scope and dump the screen via a terminal emulator.
Not a great day :-(

No clue on the AR488 specifically, I'm afraid -- I grabbed those two screenshots with the Prologix dongle that I normally keep on the back of my TDS 694C. 

No assumptions are made about the Prologix adapter's settings, all of the programs configure it to do what they need.  Can you talk to the scope using the terminal command line in the GPIB configurator app (prologix.exe)?  It should look like this (hint: try 'Restore factory default settings' first, then select Controller mode and enter 3 in the Configuration area before trying to send the *IDN? query):



If you issue a query command from the DOS prompt, as shown below, does that do anything?

[artag]

It sounds as though some setup used for the prologix doesn't work quite the same on the ar488.

Could you capture the traffic between the PC and the interface using something like https://docs.microsoft.com/en-us/sysinternals/downloads/portmon so we can see where it gets stuck ?

[serg-el]

Code: [Select]

00001347 2020-06-29 17:36:42,9660941 +13,6866627 IRP_MJ_CREATE - process 44368 (7470.exe) DOWN 0x00000000
00001348 2020-06-29 17:36:42,9812575 +0,0151634 IRP_MJ_CREATE UP 0x00000000
00001349 2020-06-29 17:36:42,9813058 +0,0000483 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR DOWN 0x00000000
00001350 2020-06-29 17:36:42,9822685 +0,0009627 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR UP 0x00000000
00001369 2020-06-29 17:36:42,9824903 +0,0000061 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE DOWN 0x00000000 00 c2 01 00 ....
00001370 2020-06-29 17:36:42,9832625 +0,0007722 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE UP 0x00000000
00001371 2020-06-29 17:36:42,9832874 +0,0000249 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR DOWN 0x00000000
00001372 2020-06-29 17:36:42,9842758 +0,0009884 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR UP 0x00000000
00001373 2020-06-29 17:36:42,9843017 +0,0000259 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL DOWN 0x00000000 00 00 08 ...
00001374 2020-06-29 17:36:42,9852619 +0,0009602 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL UP 0x00000000
00001375 2020-06-29 17:36:42,9852725 +0,0000106 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS DOWN 0x00000000 00 00 00 00 11 13 ......
00001376 2020-06-29 17:36:42,9852770 +0,0000045 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS UP 0x00000000
00001377 2020-06-29 17:36:42,9852815 +0,0000045 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW DOWN 0x00000000 09 00 00 00 80 00 00 00 00 04 00 00 00 04 00 00 ................
00001378 2020-06-29 17:36:42,9872577 +0,0019762 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW UP 0x00000000
00001379 2020-06-29 17:36:42,9872801 +0,0000224 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_TIMEOUTS DOWN 0x00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ....................
00001380 2020-06-29 17:36:42,9872840 +0,0000039 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_TIMEOUTS UP 0x00000000
00001399 2020-06-29 17:36:42,9873597 +0,0000062 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE DOWN 0x00000000 00 c2 01 00 ....
00001400 2020-06-29 17:36:42,9882528 +0,0008931 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE UP 0x00000000
00001401 2020-06-29 17:36:42,9882603 +0,0000075 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_RTS DOWN 0x00000000
00001402 2020-06-29 17:36:42,9882634 +0,0000031 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_RTS UP 0xc000000d
00001403 2020-06-29 17:36:42,9882710 +0,0000076 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR DOWN 0x00000000
00001404 2020-06-29 17:36:42,9892532 +0,0009822 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR UP 0x00000000
00001405 2020-06-29 17:36:42,9892596 +0,0000064 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL DOWN 0x00000000 00 00 08 ...
00001406 2020-06-29 17:36:42,9902721 +0,0010125 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL UP 0x00000000
00001407 2020-06-29 17:36:42,9902779 +0,0000058 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS DOWN 0x00000000 00 00 00 00 11 13 ......
00001408 2020-06-29 17:36:42,9902810 +0,0000031 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS UP 0x00000000
00001409 2020-06-29 17:36:42,9902849 +0,0000039 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW DOWN 0x00000000 01 00 00 00 40 00 00 00 00 04 00 00 00 04 00 00 ....@...........
00001410 2020-06-29 17:36:42,9922502 +0,0019653 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW UP 0x00000000
00001411 2020-06-29 17:36:43,0682197 +0,0759695 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 76 65 72 0d 0a ++ver..
00001414 2020-06-29 17:36:43,1199939 +0,0000154 IRP_MJ_READ UP 0x00000000 41 A
00001416 2020-06-29 17:36:43,1200042 +0,0000034 IRP_MJ_READ UP 0x00000000 52 R
00001418 2020-06-29 17:36:43,1200115 +0,0000031 IRP_MJ_READ UP 0x00000000 34 4
00001420 2020-06-29 17:36:43,1200184 +0,0000028 IRP_MJ_READ UP 0x00000000 38 8
00001422 2020-06-29 17:36:43,1200254 +0,0000031 IRP_MJ_READ UP 0x00000000 38 8
00001424 2020-06-29 17:36:43,1200324 +0,0000031 IRP_MJ_READ UP 0x00000000 20
00001426 2020-06-29 17:36:43,1200394 +0,0000031 IRP_MJ_READ UP 0x00000000 47 G
00001428 2020-06-29 17:36:43,1200467 +0,0000031 IRP_MJ_READ UP 0x00000000 50 P
00001430 2020-06-29 17:36:43,1200536 +0,0000030 IRP_MJ_READ UP 0x00000000 49 I
00001432 2020-06-29 17:36:43,1200606 +0,0000031 IRP_MJ_READ UP 0x00000000 42 B
00001434 2020-06-29 17:36:43,1200676 +0,0000031 IRP_MJ_READ UP 0x00000000 2d -
00001436 2020-06-29 17:36:43,1200746 +0,0000034 IRP_MJ_READ UP 0x00000000 55 U
00001438 2020-06-29 17:36:43,1200816 +0,0000031 IRP_MJ_READ UP 0x00000000 53 S
00001440 2020-06-29 17:36:43,1200886 +0,0000031 IRP_MJ_READ UP 0x00000000 42 B
00001442 2020-06-29 17:36:43,1200955 +0,0000030 IRP_MJ_READ UP 0x00000000 20
00001444 2020-06-29 17:36:43,1201025 +0,0000030 IRP_MJ_READ UP 0x00000000 2c ,
00001446 2020-06-29 17:36:43,1201092 +0,0000028 IRP_MJ_READ UP 0x00000000 20
00001448 2020-06-29 17:36:43,1201162 +0,0000031 IRP_MJ_READ UP 0x00000000 76 v
00001450 2020-06-29 17:36:43,1201235 +0,0000034 IRP_MJ_READ UP 0x00000000 65 e
00001452 2020-06-29 17:36:43,1201302 +0,0000031 IRP_MJ_READ UP 0x00000000 72 r
00001454 2020-06-29 17:36:43,1201372 +0,0000031 IRP_MJ_READ UP 0x00000000 73 s
00001456 2020-06-29 17:36:43,1201441 +0,0000030 IRP_MJ_READ UP 0x00000000 69 i
00001458 2020-06-29 17:36:43,1201511 +0,0000030 IRP_MJ_READ UP 0x00000000 6f o
00001460 2020-06-29 17:36:43,1201581 +0,0000031 IRP_MJ_READ UP 0x00000000 6e n
00001462 2020-06-29 17:36:43,1201648 +0,0000028 IRP_MJ_READ UP 0x00000000 20
00001464 2020-06-29 17:36:43,1201721 +0,0000031 IRP_MJ_READ UP 0x00000000 35 5
00001466 2020-06-29 17:36:43,1201788 +0,0000031 IRP_MJ_READ UP 0x00000000 2e .
00001468 2020-06-29 17:36:43,1201858 +0,0000031 IRP_MJ_READ UP 0x00000000 30 0
00001470 2020-06-29 17:36:43,1201928 +0,0000031 IRP_MJ_READ UP 0x00000000 20
00001472 2020-06-29 17:36:43,1201997 +0,0000030 IRP_MJ_READ UP 0x00000000 23 #
00001474 2020-06-29 17:36:43,1202064 +0,0000030 IRP_MJ_READ UP 0x00000000 31 1
00001476 2020-06-29 17:36:43,1202134 +0,0000030 IRP_MJ_READ UP 0x00000000 20
00001478 2020-06-29 17:36:43,1202204 +0,0000031 IRP_MJ_READ UP 0x00000000 30 0
00001480 2020-06-29 17:36:43,1202274 +0,0000031 IRP_MJ_READ UP 0x00000000 2e .
00001482 2020-06-29 17:36:43,1202344 +0,0000031 IRP_MJ_READ UP 0x00000000 34 4
00001484 2020-06-29 17:36:43,1202414 +0,0000031 IRP_MJ_READ UP 0x00000000 38 8
00001486 2020-06-29 17:36:43,1202484 +0,0000031 IRP_MJ_READ UP 0x00000000 2e .
00001488 2020-06-29 17:36:43,1202553 +0,0000030 IRP_MJ_READ UP 0x00000000 32 2
00001490 2020-06-29 17:36:43,1202852 +0,0000260 IRP_MJ_READ UP 0x00000000 34 4
00001492 2020-06-29 17:36:43,1202944 +0,0000033 IRP_MJ_READ UP 0x00000000 0d .
00001494 2020-06-29 17:36:43,1203017 +0,0000033 IRP_MJ_READ UP 0x00000000 0a .
00001495 2020-06-29 17:36:43,1707564 +0,0504547 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 65 6f 73 20 30 0d 0a ++eos 0..
00001497 2020-06-29 17:36:43,2723221 +0,1010410 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 6d 6f 64 65 20 30 0d 0a ++mode 0..
00001500 2020-06-29 17:36:43,8241127 +0,5000256 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00001501 2020-06-29 17:36:43,8241283 +0,0000156 IRP_MJ_READ UP 0xc0000120
00001502 2020-06-29 17:36:43,8241389 +0,0000106 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00001503 2020-06-29 17:36:43,8748945 +0,0507556 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 65 6f 69 20 31 0d 0a ++eoi 1..
00001506 2020-06-29 17:36:45,4491980 +1,4997987 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00001507 2020-06-29 17:36:45,4492159 +0,0000179 IRP_MJ_READ UP 0xc0000120
00001508 2020-06-29 17:36:45,4492304 +0,0000145 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00001510 2020-06-29 17:36:46,9716613 +1,4996070 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00001511 2020-06-29 17:36:46,9716795 +0,0000182 IRP_MJ_READ UP 0xc0000120
00001512 2020-06-29 17:36:46,9716949 +0,0000154 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00001514 2020-06-29 17:36:47,4775493 +0,4998092 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00001515 2020-06-29 17:36:47,4775652 +0,0000159 IRP_MJ_READ UP 0xc0000120
00001516 2020-06-29 17:36:47,4775792 +0,0000140 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00001518 2020-06-29 17:36:47,9775637 +0,4999546 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00001519 2020-06-29 17:36:47,9775799 +0,0000162 IRP_MJ_READ UP 0xc0000120
00001520 2020-06-29 17:36:47,9775938 +0,0000139 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00001521 2020-06-29 17:36:47,9776081 +0,0000143 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_CLR_DTR DOWN 0x00000000
00001522 2020-06-29 17:36:47,9782219 +0,0006138 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_CLR_DTR UP 0x00000000
00001523 2020-06-29 17:36:47,9782358 +0,0000139 IRP_MJ_CLOSE DOWN 0x00000000
00001524 2020-06-29 17:36:48,0820387 +0,1038029 IRP_MJ_CLOSE UP 0x00000000


Code: [Select]

;----------------------------------------------------------------------
;If you have a Prologix GPIB-USB or other serial interface, you can
;modify the interface_settings line below to specify the interface's COM port and
;communications settings for use with the KE5FX GPIB Toolkit utilities.
;
;TCP/IP devices including the Prologix GPIB-LAN adapter can be supported by
;specifing their IP address or DNS name
;
;National Instruments GPIB interfaces other than GPIB0 may also be supported
;by editing interface_settings accordingly
;
;Examples:
;
;  interface_settings  GPIB1
;  interface_settings  com3:baud=115200 parity=N data=8 stop=1
;  interface_settings  ke5fx.dyndns.org
;  interface_settings  192.168.1.103:1234
;
;To configure CONNECT.INI for use with your Prologix adapter, you can also use
;the PROLOGIX.EXE configurator included with the GPIB Toolkit distribution. 
;
;NOTE: If you have an older Prologix board with DIP switches, you will need
;to set is_Prologix to 0 (below), since it cannot be automatically configured
;by the GPIB Toolkit applications.  In case of difficulty, you can also
;download the legacy version of the GPIB Toolkit from the following link:
;[url]http://www.ke5fx.com/gpib/setup148.exe[/url]
;----------------------------------------------------------------------

interface_settings  COM7:baud=115200 parity=N data=8 stop=1

;----------------------------------------------------------------------
;Fields below have no effect if National Instruments adapter is in use
;----------------------------------------------------------------------

;
;The is_Prologix flag should be set to 0 if you are using a non-Prologix
;serial or TCP/IP interface, such as a different adapter brand, or a direct RS-232
;cable connection to your instrument.  Setting is_Prologix to 0 will prevent
;the Toolkit applications from transmitting Prologix-specific commands
;that will not be understood by the adapter or instrument in use
;

is_Prologix    1

;
;Some older Prologix boards may need a delay after writes to avoid
;buffer-overflow problems.  Use 0 milliseconds for no delay
;

write_delay_ms       100

;
;Prologix controllers can reset the device to local operation when the
;GPIB connection is closed, but since most GPIB Toolkit applications use the
;Prologix adapter in auto-read mode (++auto 1), the final ++loc command has
;the effect of addressing the instrument to talk.  This can cause error
;messages or connection problems with some equipment.  You can avoid
;this behavior by setting reset_to_local to 0 to avoid transmitting
;an ++loc command altogether, or by setting restore_auto_read to 0 to
;force the Toolkit applications to leave auto-read disabled when they exit
;
;force_auto_read defaults to 1, as required by a number of older GPIB Toolkit
;applications.  If you receive warning messages such as "Addressed to talk with
;nothing to say" when using the command line tools, you may be able to eliminate
;them by setting force_auto_read to 0.  Otherwise this parameter should be left
;at its default value
;
;restore_auto_read defaults to 0.  If set to 1, the Toolkit applications
;will restore the previous ++auto state at shutdown time.  This may be
;necessary if you are running other applications that expect auto-read mode
;to be enabled
;

enable_LON 1

reset_to_local       0
force_auto_read      1
restore_auto_read    0


Unfortunately does not work.
Only when submitting a forced command ++LON 1  works.