Block 64 Discovery Application debugging
Log File Locations
The Block 64 application consists of three main components:
-
Service - Handles inventory management.
-
Front-End Interface - Provides user interaction.
-
Data Collection Process - Performs real-time data collection.
To troubleshoot issues, gather logs from the following locations:
-
Front-End Interface Logs
-
Path:
%appdata%\Block
(e.g.,C:\Users\username\AppData\Roaming\block64discovery\logs\main.log
)
-
-
Service Logs
-
Path:
C:\Windows\Temp\Block64
-
Files:
debug_log.log
,blockcoreYYYYMMDD.log
,slingshotYYYYMMDD.log
-
-
Real-Time Data Collection Logs
-
Path:
C:\Program Files (x86)\Block 64 Corporation\Block 64 Discovery\Python\Bitstream\daq_service.log
-
Note: Collect logs from all these locations before proceeding with further troubleshooting.
Manual Application Reset (Retain Data)
To restart the application without losing data:
-
Close the Interface: Click 'X' or 'Close'.
-
Remove from System Tray: Right-click the Block 64 icon and select 'Exit'.
-
Restart the Service:
-
Press
Windows + R
, typeservices.msc
, and press Enter. -
Locate Block 64, right-click it, and select 'Restart'.
-
Manual Application Reset (Wipe Data)
If a full reset is needed, follow these steps. This will delete all application data.
Important: Prefer using the "Wipe Data" function in the user interface if possible.
-
Quit the Application and Stop the Service: Follow the steps in the previous section.
-
Delete Application Data:
-
Navigate to
C:\Program Files (x86)\Block 64 Corporation\Block 64 Discovery
. -
Delete the following:
-
SqliteDB.db
-
temp-keys
(Entire Folder) -
MySql\data
(Entire Folder)
-
-
-
Restart the Service and Application:
-
Start the Block 64 service using
services.msc
. -
Launch the front-end application via Start → Block.
-
Common Problems and Solutions
Problem:
-
The dashboard displays "Could not connect to Block 64 Service!"
Solution:
-
Perform a Manual Application Reset (Retain Data).
-
If the issue persists, gather logs using the Log File Locations section.
-
Contact Block 64 Support for further assistance.