![]() I don't think PNG does internal checksum so byte errors would be hard to spot. And yes, both data files display just fine as PNG. ![]() It's very easy to "convert" the reply into the screenshot - just remove the leading 15 bytes (4 bytes from WriteBinayFile and 11 bytes from the scope header). Any ideas? Sure looks like a bug in VISA read or perhaps an incorrectly escaped reply from the scope? Then I tried to figure out what the problem may have been but I didn't get anywhere. This file contains important information about NI-Serial for Windows and LabVIEW Real-Time, including installation instructions, new features, a partial list of. I dumped the reply string into a binary file and set the scope to run so it show something else on the screen. You can see that 45864 bytes were received, which is exactly what was specified by the binary data header (45852 data bytes + 11 header bytes + 1 termination char) ![]() This normally works fine but yesterday I was getting a timeout error. Reading out the data in blocks of 65535 bytes until there is no more (see attached vi). I'm connecting to a Rigol DZ1000 Oscilloscope via USB and using the :DISP:DATA? ON,0,PNG command to grab a screenshot. Please note that once the Promira application detects a bus lock timeout, it will abort its I2C interface, even if the timeout condition is seen in the middle. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |