| Products > Test Equipment |
| Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30) |
| << < (11/74) > >> |
| rsjsouza:
--- Quote from: Fungus on April 14, 2017, 10:12:46 am --- --- Quote from: rsjsouza on April 13, 2017, 10:59:45 pm --- --- Quote from: Fennec on April 12, 2017, 03:46:45 pm ---PNG screenshot with thumb-drive and printer button takes 2 1/2 MINUTES ! --- End quote --- One detail: at a certain point in the firmware merry-go-round, the DS4000 series had the same issue. I found out that FAT32 pendrives were terribly slow while FAT16 was very fast. Perhaps you could try this with your DS1000Z? --- End quote --- Was it the exact same pendrive formatted both ways? --- End quote --- I don't own a DS1000Z and that was definitely an issue on the DS4000 at a certain point that manifested itself similarly to what was reported by Fennec - all bases covered (different brands, sizes and formats). |
| bitseeker:
--- Quote from: frozenfrogz on April 14, 2017, 10:24:18 am --- --- Quote from: Fungus on April 14, 2017, 10:12:46 am ---If it can handle FAT32 then I don't see why the drive size would make any difference at all. :-// --- End quote --- Actually it does and there is no problem at all writing to: USB Stick CNMemory "Spaceloop" PCI Device ID: 0x268c PCI Revision ID: 0x0009 PCI Vendor ID: 0x8086 32Gb, FAT32 formatted via OS X Disk Utility Can not remember having any trouble writing to USB sticks, apart from ExFAT, OS X Extended,... formatted media. So as long as it is FAT16/32 formatted – no problem at all. --- End quote --- There are definitely issues reading/writing some USB stick/thumb/pen drives. There was a bit of discussion about it back in 2015 having to do with media, allocation table, and cluster sizes: https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg782838/#msg782838 |
| frozenfrogz:
I am aware of that and maybe I expressed poorly what I meant. This was more in regard to "32Gb should not be a problem if FAT32 works". There definitely needs to be evaluation done on what kind of USB sticks are affected and if we can pin it down to a certain chipset or what-do-I-know :) Yesterday I added this silently to the original post where this issue is taking up space número diez in the bug list. For know, the only work around seems to be trying out different brands and stick with one that gets the job done. |
| rstofer:
I have been using an Imation 2 GB Clip device and I can save a .png image in about 5 seconds. I'm pretty sure this is FAT16. It also takes about 5 seconds on a Cruzer Glide 256 GB which is FAT32. I have no idea what is inside either of these devices but they sure seem to work for me! I have a much smaller stick that I use for software upgrades. No reason, really, it's just that I don't want to get things confused so I have this stick dedicated to the purpose of upgrading. |
| BravoV:
From Rigol manual : |
| Navigation |
| Message Index |
| Next page |
| Previous page |