@CedArctic my thinking behind this is this: one doesn't always know from machine to machine what drive letter a usb drive will be assigned. If the USB drive ends up with a letter besides the one coded in the digispark, then the script is broken before it is even plugged in. This is altered to allow powershell to find the assigned drive letter via volume label and then copy temp.csv. The digispark script has also been condensed to further lessen the time of exposure.
@CedArctic my thinking behind this is this: one doesn't always know from machine to machine what drive letter a usb drive will be assigned. If the USB drive ends up with a letter besides the one coded in the digispark, then the script is broken before it is even plugged in. This is altered to allow powershell to find the assigned drive letter via volume label and then copy temp.csv. The digispark script has also been condensed to further lessen the time of exposure.