June 2020, Beta Release - Release 4

Quote:

---

Originally Posted by Ninety8C5

I did what you suggested and got the two files I've attached. They both say no USB device connected but if I open Scan & Tune it sees the V2 fine.

---

Don't worry about the "device not found" exceptions. That's just EFILive looking for additional devices (like an AutoCal device) and not finding any.

After you start EFILive Explorer, the EFILive_Hapi.exe process (i.e. the EFILive Control Panel) should start automatically. After the EFILive Control Panel has started, click on the small FlashScan icon in the System Tray, on the Windows Task Bar near the clock display. That should open the EFILive Control Panel main window. Select the [F8: Trace] tab page and click [Save Trace], then post that trace file.

Attachment 23455

Regards
Paul

Here's the trace file from the control panel. I had to add the ".txt" to the file so I could upload it.

The trace files shows EFILive Explorer attempting to read the files/folders from the root directory on FlashScan's file system (SD Card or internal memory if no SD Card is inserted)

It is not seeing a correctly formatted FAT32 file system.

Is it possible that the SD Card was formatted on some other system? EFILive is seeing this:

EFILive
System Volume Information

then for some reason EFILive Explorer stops looking for files on the FlashScan device - possibly because the file system is corrupted from that point onwards.

What EFILive Explorer should be seeing is:

EFILive
|-.
|-..
|-Scan
|-Tune

Can you try formatting the Data file system on your FlashScan V2 device?
You have to do that using the on-board option: F4: Options -> F2: File System -> F3: Format File Sys
WARNING: By formatting the SD Card, you will lose all data files (scan and tune) and configuration files stored on the FlashScan device, if you are using an SD Card and you want to save any files from the SD Card before it is formatted use a PC or laptop with an SD Card reader to attempt to read the files from the SD Card (assuming the SD CArd can still be read).

Regards
Paul

That fixed it !

Thanks again,
Walter