Solution: This issue has been fixed in V38!
FlushFileBuffers blocking call removedClearCommError()Solution: This is a COM port hang issue. Try the following:
Solution: This indicates COM port communication failure.
Solution: CTS (Clear To Send) signal is not active. This is normal and handled automatically in V38.
The application will skip the write operation when CTS is not asserted, preventing data loss. No action needed!
Get-Content .\app_v37.log -Tail 60 -Wait
Get-CimInstance Win32_SerialPort | Where-Object { $_.Name -match '^COM\d+$' } | Select-Object Name,Status
Get-PnpDevice | Where-Object { $_.FriendlyName -like "*CH34*" } | Select-Object FriendlyName,Status
Get-PnpDevice | Where-Object { $_.ClassGuid -eq (Get-PnpDeviceClass -Name Serial).ClassGuid } | Select-Object FriendlyName,Status,Manufacturer
devmgmt.msc)Get-PnpDevice | Where-Object { $_.ClassGuid -eq (Get-PnpDeviceClass -Name USB).ClassGuid } | Select-Object FriendlyName,Status
Send test command to display through terminal:
# Send hex value 0x41 (display reset)
$port = "COM5" # Change to your COM port
$data = [byte[]]::new(6)
$data[0] = 0
$data[1] = 0
$data[2] = 0
$data[3] = 0
$data[4] = 65 # 0x41 in decimal
$data[5] = 197 # Command terminator
# Open serial port and send command
$serial = New-Object System.IO.Ports.SerialPort($port, 230400)
$serial.Open()
$serial.Write($data)
$serial.Close()
Get-Process | Where-Object { $_.ProcessName -like "*Turing*" } | Select-Object ProcessName,Id,CPU,WorkingSet
# Add this to PowerShell script for monitoring:
Add-Content "COM_Monitor.log" "$(Get-Date) - Bytes sent: $sentBytes - Last error: $lastError"
If screen is completely frozen:
Ctrl+Shift+Esc → Find “Turing35NeonStableV38.exe” → End task# Stop application
Stop-Process -Name "Turing35NeonStableV38" -Force
# Wait for COM port to release
Start-Sleep -Seconds 5
# Disconnect and reconnect USB
# ... manually disconnect/reconnect cable ...
# Restart application
.\Turing35NeonStableV38.exe --test
app_v37.log for any CTS warningsIf issues persist after trying all troubleshooting steps:
app_v37.log in application directory