Author Topic: AR488 Arduino-based GPIB adapter  (Read 286361 times)

0 Members and 11 Guests are viewing this topic.

Offline serg-el

  • Regular Contributor
  • *
  • Posts: 144
  • Country: ru
Re: AR488 Arduino-based GPIB adapter
« Reply #475 on: May 29, 2020, 12:04:23 pm »
Incomprehensibility detected.
GPIB Toolkit  version 1.981 , released March 26, 2020.

When you start the HP 7470A Emulator ver 2.05, it sets the mode
++eos 0
++mode 0
++eoi 1

Next, when you press the key 'w' command is sent
++loc
in 'device' mode, it is naturally not supported :(

Where is the mistake?  :-//

Code: [Select]
00004349 2020-05-29 14:45:58,5908227 +127,2577056 IRP_MJ_CREATE - process 5936 () DOWN 0x00000000
00004350 2020-05-29 14:45:58,5961393 +0,0053166 IRP_MJ_CREATE UP 0x00000000
00004351 2020-05-29 14:45:58,5962220 +0,0000827 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR DOWN 0x00000000
00004352 2020-05-29 14:45:58,5962281 +0,0000061 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR UP 0x00000000
00004371 2020-05-29 14:45:58,5964757 +0,0000065 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE DOWN 0x00000000 00 c2 01 00 ....
00004372 2020-05-29 14:45:58,5964785 +0,0000028 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE UP 0x00000000
00004373 2020-05-29 14:45:58,5964838 +0,0000053 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR DOWN 0x00000000
00004374 2020-05-29 14:45:58,5964863 +0,0000025 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR UP 0x00000000
00004375 2020-05-29 14:45:58,5964910 +0,0000047 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL DOWN 0x00000000 00 00 08 ...
00004376 2020-05-29 14:45:58,5964941 +0,0000031 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL UP 0x00000000
00004377 2020-05-29 14:45:58,5964983 +0,0000042 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS DOWN 0x00000000 00 00 00 00 11 13 ......
00004378 2020-05-29 14:45:58,5965008 +0,0000025 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS UP 0x00000000
00004379 2020-05-29 14:45:58,5965050 +0,0000042 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW DOWN 0x00000000 09 00 00 00 80 00 00 80 36 43 00 00 36 43 00 00 ........6C..6C..
00004380 2020-05-29 14:45:58,5981180 +0,0016130 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW UP 0x00000000
00004381 2020-05-29 14:45:58,5981281 +0,0000101 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 ....................
00004382 2020-05-29 14:45:58,5981309 +0,0000028 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_TIMEOUTS UP 0x00000000
00004401 2020-05-29 14:45:58,5982019 +0,0000062 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE DOWN 0x00000000 00 c2 01 00 ....
00004402 2020-05-29 14:45:58,5982046 +0,0000027 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE UP 0x00000000
00004403 2020-05-29 14:45:58,5982100 +0,0000054 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_RTS DOWN 0x00000000
00004404 2020-05-29 14:45:58,5982125 +0,0000025 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_RTS UP 0xc0000023
00004405 2020-05-29 14:45:58,5982197 +0,0000072 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR DOWN 0x00000000
00004406 2020-05-29 14:45:58,5982220 +0,0000023 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR UP 0x00000000
00004407 2020-05-29 14:45:58,5982267 +0,0000047 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL DOWN 0x00000000 00 00 08 ...
00004408 2020-05-29 14:45:58,5982295 +0,0000028 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL UP 0x00000000
00004409 2020-05-29 14:45:58,5982334 +0,0000039 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS DOWN 0x00000000 00 00 00 00 11 13 ......
00004410 2020-05-29 14:45:58,5982357 +0,0000023 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS UP 0x00000000
00004411 2020-05-29 14:45:58,5982396 +0,0000039 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW DOWN 0x00000000 01 00 00 00 40 00 00 80 36 43 00 00 36 43 00 00 ....@...6C..6C..
00004412 2020-05-29 14:45:58,6001203 +0,0018807 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW UP 0x00000000
00004413 2020-05-29 14:45:58,6809154 +0,0807951 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 76 65 72 0d 0a ++ver..
00004416 2020-05-29 14:45:58,7356431 +0,0000101 IRP_MJ_READ UP 0x00000000 41 A
00004418 2020-05-29 14:45:58,7356582 +0,0000028 IRP_MJ_READ UP 0x00000000 52 R
00004420 2020-05-29 14:45:58,7356654 +0,0000025 IRP_MJ_READ UP 0x00000000 34 4
00004422 2020-05-29 14:45:58,7356724 +0,0000025 IRP_MJ_READ UP 0x00000000 38 8
00004424 2020-05-29 14:45:58,7356791 +0,0000025 IRP_MJ_READ UP 0x00000000 38 8
00004426 2020-05-29 14:45:58,7356858 +0,0000025 IRP_MJ_READ UP 0x00000000 20
00004428 2020-05-29 14:45:58,7356925 +0,0000025 IRP_MJ_READ UP 0x00000000 47 G
00004430 2020-05-29 14:45:58,7356992 +0,0000025 IRP_MJ_READ UP 0x00000000 50 P
00004432 2020-05-29 14:45:58,7357062 +0,0000028 IRP_MJ_READ UP 0x00000000 49 I
00004434 2020-05-29 14:45:58,7357129 +0,0000028 IRP_MJ_READ UP 0x00000000 42 B
00004436 2020-05-29 14:45:58,7357193 +0,0000025 IRP_MJ_READ UP 0x00000000 2d -
00004438 2020-05-29 14:45:58,7357260 +0,0000025 IRP_MJ_READ UP 0x00000000 55 U
00004440 2020-05-29 14:45:58,7357420 +0,0000118 IRP_MJ_READ UP 0x00000000 53 S
00004442 2020-05-29 14:45:58,7357492 +0,0000028 IRP_MJ_READ UP 0x00000000 42 B
00004444 2020-05-29 14:45:58,7357568 +0,0000034 IRP_MJ_READ UP 0x00000000 20
00004446 2020-05-29 14:45:58,7357643 +0,0000028 IRP_MJ_READ UP 0x00000000 2c ,
00004448 2020-05-29 14:45:58,7357716 +0,0000028 IRP_MJ_READ UP 0x00000000 20
00004450 2020-05-29 14:45:58,7357794 +0,0000036 IRP_MJ_READ UP 0x00000000 76 v
00004452 2020-05-29 14:45:58,7357872 +0,0000031 IRP_MJ_READ UP 0x00000000 65 e
00004454 2020-05-29 14:45:58,7357950 +0,0000030 IRP_MJ_READ UP 0x00000000 72 r
00004456 2020-05-29 14:45:58,7358029 +0,0000031 IRP_MJ_READ UP 0x00000000 73 s
00004458 2020-05-29 14:45:58,7358096 +0,0000025 IRP_MJ_READ UP 0x00000000 69 i
00004460 2020-05-29 14:45:58,7358166 +0,0000026 IRP_MJ_READ UP 0x00000000 6f o
00004462 2020-05-29 14:45:58,7358233 +0,0000026 IRP_MJ_READ UP 0x00000000 6e n
00004464 2020-05-29 14:45:58,7358300 +0,0000026 IRP_MJ_READ UP 0x00000000 20
00004466 2020-05-29 14:45:58,7358367 +0,0000025 IRP_MJ_READ UP 0x00000000 35 5
00004468 2020-05-29 14:45:58,7358436 +0,0000027 IRP_MJ_READ UP 0x00000000 2e .
00004470 2020-05-29 14:45:58,7358504 +0,0000028 IRP_MJ_READ UP 0x00000000 30 0
00004472 2020-05-29 14:45:58,7358571 +0,0000026 IRP_MJ_READ UP 0x00000000 20
00004474 2020-05-29 14:45:58,7358638 +0,0000026 IRP_MJ_READ UP 0x00000000 23 #
00004476 2020-05-29 14:45:58,7358705 +0,0000025 IRP_MJ_READ UP 0x00000000 31 1
00004478 2020-05-29 14:45:58,7358772 +0,0000025 IRP_MJ_READ UP 0x00000000 20
00004480 2020-05-29 14:45:58,7358842 +0,0000028 IRP_MJ_READ UP 0x00000000 30 0
00004482 2020-05-29 14:45:58,7358909 +0,0000026 IRP_MJ_READ UP 0x00000000 2e .
00004484 2020-05-29 14:45:58,7358976 +0,0000025 IRP_MJ_READ UP 0x00000000 34 4
00004486 2020-05-29 14:45:58,7359043 +0,0000025 IRP_MJ_READ UP 0x00000000 38 8
00004488 2020-05-29 14:45:58,7359110 +0,0000025 IRP_MJ_READ UP 0x00000000 2e .
00004490 2020-05-29 14:45:58,7359180 +0,0000028 IRP_MJ_READ UP 0x00000000 32 2
00004492 2020-05-29 14:45:58,7359247 +0,0000025 IRP_MJ_READ UP 0x00000000 34 4
00004494 2020-05-29 14:45:58,7359314 +0,0000025 IRP_MJ_READ UP 0x00000000 0d .
00004496 2020-05-29 14:45:58,7359384 +0,0000028 IRP_MJ_READ UP 0x00000000 0a .
00004497 2020-05-29 14:45:58,7903279 +0,0543895 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 65 6f 73 20 30 0d 0a ++eos 0..
00004499 2020-05-29 14:45:58,8996860 +0,1084811 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 6d 6f 64 65 20 30 0d 0a ++mode 0..
00004502 2020-05-29 14:45:59,2043744 +0,2500027 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004503 2020-05-29 14:45:59,2043867 +0,0000123 IRP_MJ_READ UP 0xc0000120
00004504 2020-05-29 14:45:59,2043948 +0,0000081 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004505 2020-05-29 14:45:59,2590512 +0,0546564 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 65 6f 69 20 31 0d 0a ++eoi 1..
00004508 2020-05-29 14:46:00,3372438 +0,9975756 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004509 2020-05-29 14:46:00,3372564 +0,0000126 IRP_MJ_READ UP 0xc0000120
00004510 2020-05-29 14:46:00,3372648 +0,0000084 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004512 2020-05-29 14:46:01,3570307 +0,9979429 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004513 2020-05-29 14:46:01,3570433 +0,0000126 IRP_MJ_READ UP 0xc0000120
00004514 2020-05-29 14:46:01,3570528 +0,0000095 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004516 2020-05-29 14:46:02,3805158 +0,9980992 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004517 2020-05-29 14:46:02,3805312 +0,0000154 IRP_MJ_READ UP 0xc0000120
00004518 2020-05-29 14:46:02,3805399 +0,0000087 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004520 2020-05-29 14:46:03,4040105 +0,9978760 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004521 2020-05-29 14:46:03,4040230 +0,0000125 IRP_MJ_READ UP 0xc0000120
00004522 2020-05-29 14:46:03,4040353 +0,0000123 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004524 2020-05-29 14:46:04,4274981 +0,9975095 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004525 2020-05-29 14:46:04,4275095 +0,0000114 IRP_MJ_READ UP 0xc0000120
00004526 2020-05-29 14:46:04,4275179 +0,0000084 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004528 2020-05-29 14:46:05,4509938 +0,9980992 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004529 2020-05-29 14:46:05,4510058 +0,0000120 IRP_MJ_READ UP 0xc0000120
00004530 2020-05-29 14:46:05,4510153 +0,0000095 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004532 2020-05-29 14:46:06,4744719 +0,9959925 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004533 2020-05-29 14:46:06,4744837 +0,0000118 IRP_MJ_READ UP 0xc0000120
00004534 2020-05-29 14:46:06,4744906 +0,0000069 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004536 2020-05-29 14:46:07,4979735 +0,9975472 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004537 2020-05-29 14:46:07,4979880 +0,0000145 IRP_MJ_READ UP 0xc0000120
00004538 2020-05-29 14:46:07,4979967 +0,0000087 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004540 2020-05-29 14:46:08,5214514 +0,9979688 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004541 2020-05-29 14:46:08,5214678 +0,0000164 IRP_MJ_READ UP 0xc0000120
00004542 2020-05-29 14:46:08,5214771 +0,0000093 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004544 2020-05-29 14:46:09,5449443 +0,9979880 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004545 2020-05-29 14:46:09,5449563 +0,0000120 IRP_MJ_READ UP 0xc0000120
00004546 2020-05-29 14:46:09,5449694 +0,0000131 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004548 2020-05-29 14:46:10,5840674 +0,9931751 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004549 2020-05-29 14:46:10,5840817 +0,0000143 IRP_MJ_READ UP 0xc0000120
00004550 2020-05-29 14:46:10,5840937 +0,0000120 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004552 2020-05-29 14:46:11,6075447 +0,9981115 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004553 2020-05-29 14:46:11,6075576 +0,0000129 IRP_MJ_READ UP 0xc0000120
00004554 2020-05-29 14:46:11,6075684 +0,0000108 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004556 2020-05-29 14:46:12,1153852 +0,4997333 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004557 2020-05-29 14:46:12,1154101 +0,0000249 IRP_MJ_READ UP 0xc0000120
00004558 2020-05-29 14:46:12,1154224 +0,0000123 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004559 2020-05-29 14:46:12,1700698 +0,0546474 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 6c 6f 63 0d 0a ++loc..
00004562 2020-05-29 14:46:12,2247743 +0,0000129 IRP_MJ_READ UP 0x00000000 55 U
00004564 2020-05-29 14:46:12,2247849 +0,0000025 IRP_MJ_READ UP 0x00000000 6e n
00004566 2020-05-29 14:46:12,2247921 +0,0000025 IRP_MJ_READ UP 0x00000000 72 r
00004568 2020-05-29 14:46:12,2247989 +0,0000026 IRP_MJ_READ UP 0x00000000 65 e
00004570 2020-05-29 14:46:12,2248056 +0,0000026 IRP_MJ_READ UP 0x00000000 63 c
00004572 2020-05-29 14:46:12,2248125 +0,0000025 IRP_MJ_READ UP 0x00000000 6f o
00004574 2020-05-29 14:46:12,2248195 +0,0000028 IRP_MJ_READ UP 0x00000000 67 g
00004576 2020-05-29 14:46:12,2248262 +0,0000025 IRP_MJ_READ UP 0x00000000 6e n
00004578 2020-05-29 14:46:12,2248329 +0,0000025 IRP_MJ_READ UP 0x00000000 69 i
00004580 2020-05-29 14:46:12,2248396 +0,0000025 IRP_MJ_READ UP 0x00000000 7a z
00004582 2020-05-29 14:46:12,2248466 +0,0000028 IRP_MJ_READ UP 0x00000000 65 e
00004584 2020-05-29 14:46:12,2248533 +0,0000028 IRP_MJ_READ UP 0x00000000 64 d
00004586 2020-05-29 14:46:12,2248600 +0,0000028 IRP_MJ_READ UP 0x00000000 20
00004588 2020-05-29 14:46:12,2248667 +0,0000025 IRP_MJ_READ UP 0x00000000 63 c
00004590 2020-05-29 14:46:12,2248734 +0,0000025 IRP_MJ_READ UP 0x00000000 6f o
00004592 2020-05-29 14:46:12,2248801 +0,0000025 IRP_MJ_READ UP 0x00000000 6d m
00004594 2020-05-29 14:46:12,2248869 +0,0000026 IRP_MJ_READ UP 0x00000000 6d m
00004596 2020-05-29 14:46:12,2248936 +0,0000026 IRP_MJ_READ UP 0x00000000 61 a
00004598 2020-05-29 14:46:12,2249003 +0,0000026 IRP_MJ_READ UP 0x00000000 6e n
00004600 2020-05-29 14:46:12,2249072 +0,0000027 IRP_MJ_READ UP 0x00000000 64 d
00004602 2020-05-29 14:46:12,2249139 +0,0000027 IRP_MJ_READ UP 0x00000000 0d .
00004604 2020-05-29 14:46:12,2249207 +0,0000026 IRP_MJ_READ UP 0x00000000 0a .
00004606 2020-05-29 14:46:12,4747722 +0,2498474 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004607 2020-05-29 14:46:12,4747910 +0,0000188 IRP_MJ_READ UP 0xc0000120
00004608 2020-05-29 14:46:12,4747993 +0,0000083 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004610 2020-05-29 14:46:12,9747897 +0,4999728 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE DOWN 0x00000000 02 00 00 00 ....
00004611 2020-05-29 14:46:12,9748012 +0,0000115 IRP_MJ_READ UP 0xc0000120
00004612 2020-05-29 14:46:12,9748104 +0,0000092 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_PURGE UP 0x00000000
00004613 2020-05-29 14:46:12,9748238 +0,0000134 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_CLR_DTR DOWN 0x00000000
00004614 2020-05-29 14:46:12,9754549 +0,0006311 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_CLR_DTR UP 0x00000000
00004615 2020-05-29 14:46:12,9754694 +0,0000145 IRP_MJ_CLOSE DOWN 0x00000000
00004616 2020-05-29 14:46:12,9774188 +0,0019494 IRP_MJ_CLOSE UP 0x00000000
00004617 2020-05-29 14:47:37,6668899 +84,6975801 IRP_MJ_CREATE - process 2568 (putty.exe) DOWN 0x00000000
00004618 2020-05-29 14:47:37,6723356 +0,0054457 IRP_MJ_CREATE UP 0x00000000
00004635 2020-05-29 14:47:37,6724541 +0,0000062 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE DOWN 0x00000000 00 c2 01 00 ....
00004636 2020-05-29 14:47:37,6724571 +0,0000030 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_BAUD_RATE UP 0x00000000
00004637 2020-05-29 14:47:37,6724700 +0,0000129 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_RTS DOWN 0x00000000
00004638 2020-05-29 14:47:37,6724728 +0,0000028 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_RTS UP 0x00000000
00004639 2020-05-29 14:47:37,6724781 +0,0000053 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR DOWN 0x00000000
00004640 2020-05-29 14:47:37,6724806 +0,0000025 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_DTR UP 0x00000000
00004641 2020-05-29 14:47:37,6724848 +0,0000042 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL DOWN 0x00000000 00 00 08 ...
00004642 2020-05-29 14:47:37,6724881 +0,0000033 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_LINE_CONTROL UP 0x00000000
00004643 2020-05-29 14:47:37,6724923 +0,0000042 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS DOWN 0x00000000 00 00 00 00 11 13 ......
00004644 2020-05-29 14:47:37,6724948 +0,0000025 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_CHARS UP 0x00000000
00004645 2020-05-29 14:47:37,6724990 +0,0000042 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW DOWN 0x00000000 01 00 00 00 40 00 00 00 6c 86 00 00 9b 21 00 00 ....@...l....!..
00004646 2020-05-29 14:47:37,6743420 +0,0018430 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_HANDFLOW UP 0x00000000
00004647 2020-05-29 14:47:37,6743496 +0,0000076 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_TIMEOUTS DOWN 0x00000000 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ....................
00004648 2020-05-29 14:47:37,6743526 +0,0000030 IRP_MJ_DEVICECONTROL: IOCTL_SERIAL_SET_TIMEOUTS UP 0x00000000
00004650 2020-05-29 14:47:42,2104258 +4,5358159 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 6c 6f 63 ++loc
00004652 2020-05-29 14:47:42,2114119 +0,0000388 IRP_MJ_WRITE DOWN 0x00000000 0d .
00004654 2020-05-29 14:47:42,2153306 +0,0029895 IRP_MJ_READ UP 0x00000000 55 U
00004656 2020-05-29 14:47:42,2153717 +0,0000065 IRP_MJ_READ UP 0x00000000 6e n
00004658 2020-05-29 14:47:42,2153923 +0,0000030 IRP_MJ_READ UP 0x00000000 72 r
00004660 2020-05-29 14:47:42,2154122 +0,0000028 IRP_MJ_READ UP 0x00000000 65 e
00004662 2020-05-29 14:47:42,2154314 +0,0000027 IRP_MJ_READ UP 0x00000000 63 c
00004664 2020-05-29 14:47:42,2154504 +0,0000025 IRP_MJ_READ UP 0x00000000 6f o
00004666 2020-05-29 14:47:42,2154694 +0,0000028 IRP_MJ_READ UP 0x00000000 67 g
00004668 2020-05-29 14:47:42,2154887 +0,0000028 IRP_MJ_READ UP 0x00000000 6e n
00004670 2020-05-29 14:47:42,2155074 +0,0000025 IRP_MJ_READ UP 0x00000000 69 i
00004672 2020-05-29 14:47:42,2155262 +0,0000026 IRP_MJ_READ UP 0x00000000 7a z
00004674 2020-05-29 14:47:42,2155454 +0,0000028 IRP_MJ_READ UP 0x00000000 65 e
00004676 2020-05-29 14:47:42,2155644 +0,0000025 IRP_MJ_READ UP 0x00000000 64 d
00004678 2020-05-29 14:47:42,2155834 +0,0000028 IRP_MJ_READ UP 0x00000000 20
00004680 2020-05-29 14:47:42,2156024 +0,0000028 IRP_MJ_READ UP 0x00000000 63 c
00004682 2020-05-29 14:47:42,2156217 +0,0000028 IRP_MJ_READ UP 0x00000000 6f o
00004684 2020-05-29 14:47:42,2156404 +0,0000025 IRP_MJ_READ UP 0x00000000 6d m
00004686 2020-05-29 14:47:42,2156594 +0,0000025 IRP_MJ_READ UP 0x00000000 6d m
00004688 2020-05-29 14:47:42,2156784 +0,0000028 IRP_MJ_READ UP 0x00000000 61 a
00004690 2020-05-29 14:47:42,2156971 +0,0000028 IRP_MJ_READ UP 0x00000000 6e n
00004692 2020-05-29 14:47:42,2157158 +0,0000028 IRP_MJ_READ UP 0x00000000 64 d
00004694 2020-05-29 14:47:42,2157346 +0,0000026 IRP_MJ_READ UP 0x00000000 0d .
00004696 2020-05-29 14:47:42,2157538 +0,0000028 IRP_MJ_READ UP 0x00000000 0a .
00004698 2020-05-29 14:47:49,1101189 +6,8943489 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 6d 6f 64 65 ++mode
00004700 2020-05-29 14:47:49,1104187 +0,0000422 IRP_MJ_WRITE DOWN 0x00000000 0d .
00004702 2020-05-29 14:47:49,1133322 +0,0019905 IRP_MJ_READ UP 0x00000000 30 0
00004704 2020-05-29 14:47:49,1133729 +0,0000067 IRP_MJ_READ UP 0x00000000 0d .
00004706 2020-05-29 14:47:49,1133942 +0,0000031 IRP_MJ_READ UP 0x00000000 0a .
00004708 2020-05-29 14:47:53,5701226 +4,4567119 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 6d 6f 64 65 20 31 ++mode 1
00004710 2020-05-29 14:47:53,5704246 +0,0000413 IRP_MJ_WRITE DOWN 0x00000000 0d .
00004712 2020-05-29 14:47:57,8221312 +4,2507878 IRP_MJ_WRITE DOWN 0x00000000 2b 2b 6c 6f 63 ++loc
00004714 2020-05-29 14:47:57,8224304 +0,0000391 IRP_MJ_WRITE DOWN 0x00000000 0d .

 

Offline KE5FX

  • Super Contributor
  • ***
  • Posts: 2017
  • Country: us
    • KE5FX.COM
Re: AR488 Arduino-based GPIB adapter
« Reply #476 on: May 30, 2020, 04:13:58 am »
Back on 18th March in post #397 KE5FX did say he would add that feature. On his website I can see that the toolset was updated on 20th March (v1980) and again on the 26th March (v1981). I downloaded it to have a look, but could not see the ++lon feature implemented it yet so we will have to wait until the next release I think.

Actually it got added but I don't seem to have remembered to document it in connect.ini.  Run the GPIB configurator, select 'Edit CONNECT.INI', and add the following line, and see if that helps?

Code: [Select]
enable_LON 1
(It should actually default to 1 if that line isn't present.)

Incomprehensibility detected.
GPIB Toolkit  version 1.981 , released March 26, 2020.

When you start the HP 7470A Emulator ver 2.05, it sets the mode
++eos 0
++mode 0
++eoi 1

Next, when you press the key 'w' command is sent
++loc
in 'device' mode, it is naturally not supported :(

Where is the mistake?  :-//

It won't send anything at all until you hit 'w',  and then ++loc will be transmitted when the 'w' operation finishes (meaning a plot arrives or you hit a key to stop waiting.)  In principle it shouldn't send ++loc in this case, but Prologix adapters in device mode will ignore it, and all others should as well.
 

Offline xardomain

  • Contributor
  • Posts: 18
  • Country: it
Re: AR488 Arduino-based GPIB adapter
« Reply #477 on: May 30, 2020, 07:33:35 pm »
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
 
The following users thanked this post: Miti

Offline xardomain

  • Contributor
  • Posts: 18
  • Country: it
Re: AR488 Arduino-based GPIB adapter
« Reply #478 on: May 31, 2020, 12:21:09 am »
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
 

Offline softfoot

  • Contributor
  • Posts: 46
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #479 on: June 06, 2020, 12:43:10 pm »

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
Grumpy Old Software/Hardware Engineering Git
Dave
 

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3506
  • Country: us
Re: AR488 Arduino-based GPIB adapter
« Reply #480 on: June 08, 2020, 10:18:27 pm »
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
« Last Edit: June 08, 2020, 10:31:23 pm by rhb »
 

Offline softfoot

  • Contributor
  • Posts: 46
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #481 on: June 08, 2020, 11:03:16 pm »
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
Grumpy Old Software/Hardware Engineering Git
Dave
 

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3506
  • Country: us
Re: AR488 Arduino-based GPIB adapter
« Reply #482 on: June 08, 2020, 11:49:43 pm »
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
 

Offline Joern

  • Newbie
  • Posts: 1
  • Country: de
Re: AR488 Arduino-based GPIB adapter
« Reply #483 on: June 16, 2020, 10:16:22 am »
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?
 

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3506
  • Country: us
Re: AR488 Arduino-based GPIB adapter
« Reply #484 on: June 16, 2020, 12:25:31 pm »
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
 

Offline ogdento

  • Regular Contributor
  • *
  • Posts: 151
  • Country: us
Re: AR488 Arduino-based GPIB adapter
« Reply #485 on: June 19, 2020, 09:24:57 pm »
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.
1004913-0

Here's the final assembly...
1004915-1
 
The following users thanked this post: artag

Offline artag

  • Super Contributor
  • ***
  • Posts: 1250
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #486 on: June 20, 2020, 11:23:37 am »
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.
 
 
The following users thanked this post: ogdento

Offline PixieDust

  • Frequent Contributor
  • **
  • Posts: 265
  • Country: au
Re: AR488 Arduino-based GPIB adapter
« Reply #487 on: June 21, 2020, 02:44:56 am »
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.
« Last Edit: June 21, 2020, 02:53:00 am by PixieDust »
 

Offline iXod

  • Frequent Contributor
  • **
  • Posts: 350
  • Country: us
Re: AR488 Arduino-based GPIB adapter
« Reply #488 on: June 21, 2020, 03:28:14 pm »
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.
« Last Edit: June 21, 2020, 03:42:08 pm by iXod »
 

Offline softfoot

  • Contributor
  • Posts: 46
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #489 on: June 21, 2020, 04:04:22 pm »

For me cost was a large factor, plus it's an interesting and useful project.
Dave
Grumpy Old Software/Hardware Engineering Git
Dave
 

Offline rhb

  • Super Contributor
  • ***
  • Posts: 3506
  • Country: us
Re: AR488 Arduino-based GPIB adapter
« Reply #490 on: June 21, 2020, 09:08:31 pm »
@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
 

Offline artag

  • Super Contributor
  • ***
  • Posts: 1250
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #491 on: June 22, 2020, 08:46:46 am »
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.
 

Offline xardomain

  • Contributor
  • Posts: 18
  • Country: it
Re: AR488 Arduino-based GPIB adapter
« Reply #492 on: June 26, 2020, 03:28:26 pm »
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

 

Offline artag

  • Super Contributor
  • ***
  • Posts: 1250
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #493 on: June 26, 2020, 05:22:36 pm »
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 !
 
 

Offline xardomain

  • Contributor
  • Posts: 18
  • Country: it
Re: AR488 Arduino-based GPIB adapter
« Reply #494 on: June 26, 2020, 07:47:13 pm »
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
 

Offline artag

  • Super Contributor
  • ***
  • Posts: 1250
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #495 on: June 26, 2020, 08:06:32 pm »
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.
 
 
The following users thanked this post: Sprock

Offline softfoot

  • Contributor
  • Posts: 46
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #496 on: June 28, 2020, 03:38:17 pm »
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?    |O

TIA
Dave
Grumpy Old Software/Hardware Engineering Git
Dave
 

Offline KE5FX

  • Super Contributor
  • ***
  • Posts: 2017
  • Country: us
    • KE5FX.COM
Re: AR488 Arduino-based GPIB adapter
« Reply #497 on: June 29, 2020, 08:51:40 am »
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?    |O

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.
 

Offline softfoot

  • Contributor
  • Posts: 46
  • Country: gb
Re: AR488 Arduino-based GPIB adapter
« Reply #498 on: June 29, 2020, 11:14:32 am »
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
 
« Last Edit: June 29, 2020, 12:08:36 pm by softfoot »
Grumpy Old Software/Hardware Engineering Git
Dave
 
The following users thanked this post: ducus

Offline KE5FX

  • Super Contributor
  • ***
  • Posts: 2017
  • Country: us
    • KE5FX.COM
Re: AR488 Arduino-based GPIB adapter
« Reply #499 on: June 29, 2020, 12:26:06 pm »
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?

 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf