![]() Disconnecting from the GPIB bus is not enough to recover communication, only a power cycle will do the job. Instrument initiated plots initially start with the already discussed delay of about 10s and when the transfer is complete, the AR488 no longer reacts to commands like ++ver and 7470.exe crashes. The behavior is exactly the same as with CDC. Quote from: tom_iphi on April 07, 2020, 12:50:55 pm To make sure the issue is not related to the USB CDC port, I switched over to using the Leonardo hardware serial port (RXO, TXI lines) instead and hooked it up to a CH340 USB to serial converter, also directly plugged into the PC. Can you think of any more test I can do and any more data I can gather to help you fix this? Anything to be learned from AR488 debug output? Is it possible to run in over the CDC USB port but log the debug output over the hardware port to keep the streams separated and avoid debug data to interfere with normal operation? Best regards. So, this appears to be not some kind of "dirt effect" but a real firmware problem. And I made one more experiment: To make sure the issue is not related to the USB CDC port, I switched over to using the Leonardo hardware serial port (RXO, TXI lines) instead and hooked it up to a CH340 USB to serial converter, also directly plugged into the PC. USB directly plugged into the notebook USB port. BTW, are you still using the HC06 to wirelessly connect the Arduino to the PC, or is it directly connected via USB cable? Since I have observed with my own setup that USB hubs can cause problems, might I ask whether your 32u4 is connected via a USB hub? Have you tried connecting it directly into the PC? It seems unlikely given that the Prologix works, but just want to rule it out. ![]() It would appear then, that neither particular characters nor the size of the data is the issue. As you can see in the second attachment, after doing this and sending your data over GPIB, the plot was successfully received. I also realized that your PDF does actually contain the data in hex further below the text dump so I spent a little time manually extrapolating this into a file and formatting it so that it could be copied into and used by the sketch. It is possible, of course, to just load up the example file into 7470 program, but this was, in fact, sent from one AR488 to another over GPIB and captured from the receiving AR488 by the 7470 program. The 7470 program had no problem with reading the resulting plot (see the attached). I then copied and pasted the exported result directly into the sketch, compiled, uploaded and ran the test to send the data over GPIB. Had to write a small script to read the file and export the bytes to a hex representation of the data. ![]() Tom, I managed to encode one of the example plots (file 'HP t') into the sketch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |