I have a problem with the Kirisun PT8100 mobile radios programming. When I connect the radio with the programming cable, and I read the current configuration of the radio using the KSP8100 v1.25 software, and try to save the configuration, I receive the following error “FRE2BCD ERROR!”. The programming software then quits. I have tried this with multiple programming cables, multiple PT8100 radios and on different computers. What is the cause of this and how do I resolve this as I do not get any response from Kirisun for technical support.
halo H.V,which country are u in?
Hi Mark, I am in South Africa. Is the error related to the regional settings on the PC?
Have the same problem here, also on different computers, different USB cables, different radios. One PC running Win7 64b, the other running XP Pro, 32b. The software runs fine on other computers however.
I am using ver 1.28 and also 1.29 of the software, same results. I am located in South Africa. The local distributors here have not experienced this problem.
Any ideas will certainly be welcome!
No one? This is very frustrating 
ews2k, is the dealer who sold you the radios unable to program them for you? I am in the US and am not familiar with the programming software for the Kirisun. Have you checked to make sure the USB cable is assigned to the correct COM port? Is it possible the cable is reading the radios from the correct port but attempting to write back through another one?
Hi Rick,
Apologies for only replying to you now, somehow I missed your message.
We are authorised radio dealers and have the correct s/w and prog cables.
I have tried with USB cables as well as RS232 cables (on suitable PCs) and experience the same problem. The local Kirisun agents are unable to resolve this and we are convinced that the problem is a MS one. This does not happen on all our PCs, just the two that I mentioned.
I suspect it might be a MS dot.net issue?
Forgot to add: I can certainly read the data from the radio, but am unable to either save it back to the PC nor write to the radio. This tends to strengthen my belief that this is more of a s/w problem, and probably MS, as I use the same version of the program successfully in other PCs.
-Eric
This is the log of the error file that appeared. I wonder if the problem does not lie with a “Database” (or lack thereof), as this appears to be where the program just stooped, provided the Fre2BCD error message and then exited itself?
<?xml version=“1.0” encoding=“UTF-16”?>
<DATABASE>
<EXE NAME=“KSP8100.exe” FILTER=“GRABMI_FILTER_PRIVACY”>
<MATCHING_FILE NAME="EngLish.dll" SIZE="1191936" CHECKSUM="0x92FD5734" BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="1, 0, 0, 1" FILE_DESCRIPTION="" COMPANY_NAME="" PRODUCT_NAME="" FILE_VERSION="1, 0, 0, 1" ORIGINAL_FILENAME="" INTERNAL_NAME="" LEGAL_COPYRIGHT="" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1" UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="10/13/2011 01:34:46" UPTO_LINK_DATE="10/13/2011 01:34:46" VER_LANGUAGE="Chinese (PRC) [0x804]" />
<MATCHING_FILE NAME="KSP8100.exe" SIZE="2236416" CHECKSUM="0x12794F16" BIN_FILE_VERSION="1.0.0.1" BIN_PRODUCT_VERSION="1.0.0.1" PRODUCT_VERSION="" FILE_DESCRIPTION="" COMPANY_NAME="" PRODUCT_NAME="" FILE_VERSION="" ORIGINAL_FILENAME="" INTERNAL_NAME="" LEGAL_COPYRIGHT="" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.1" UPTO_BIN_PRODUCT_VERSION="1.0.0.1" LINK_DATE="10/13/2011 01:35:04" UPTO_LINK_DATE="10/13/2011 01:35:04" VER_LANGUAGE="Chinese (PRC) [0x804]" />
<MATCHING_FILE NAME="Unwise.exe" SIZE="153088" CHECKSUM="0x64313F64" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/03/2002 15:14:30" UPTO_LINK_DATE="07/03/2002 15:14:30" />
</EXE>
<EXE NAME=“kernel32.dll” FILTER=“GRABMI_FILTER_THISFILEONLY”>
<MATCHING_FILE NAME="kernel32.dll" SIZE="990208" CHECKSUM="0xCC2C4544" BIN_FILE_VERSION="5.1.2600.6293" BIN_PRODUCT_VERSION="5.1.2600.6293" PRODUCT_VERSION="5.1.2600.6293" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.6293 (xpsp_sp3_gdr.121001-1622)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFBCBC" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.6293" UPTO_BIN_PRODUCT_VERSION="5.1.2600.6293" LINK_DATE="10/03/2012 04:58:13" UPTO_LINK_DATE="10/03/2012 04:58:13" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>
-Eric
Still have this problem. No one with any ideas?
Eric
You said you use the program successfully on other PCs. The question is, what is different with these systems?
From the error message you posted, it seems you are running Windows XP SP3. Are you using the same version of Windows on all of the PCs? If so, are they all set up with the same drivers, applications and services? Are all of the port drivers the same?
There are a lot of reasons why the same programming software would work on one computer and not another. It could be related to software, hardware, or both. Also, the programming software for your radio does not seem to be widely used, at least here in the US. Without details on the systems you are using and their configurations, it is difficult to troubleshoot the error, especially when using an application that is a bit obscure.
The fact that the software will run properly on one machine and not another indicates that there may be something different with the configuration between the two that may be causing the issue.
Since this forum primarily discusses the operation two way radios and not computers, it is a bit outside our scope to troubleshoot computer related issues. However, there are a few things you can try to determine if the issue is caused by the computer or the programming software.
[ol]
[li] Note and similarities and differences between all of the computers running the program.[/li][li] Which machines run the program with out issue? Which computers have the issue?[/li][li] Look for a common denominator with each set of computers, i.e. do all the ones that work use the same version of Windows, do they all use the same set of port drivers, do they all use the same port assignments, connections, etc.)[/li][li] Is there anything else running or not running on the computers that may prevent the programming software from writing back to the radio or otherwise get in the way? (AV programs, services disabled, stopped, or failing to load, other devices using the same ports or port numbers, etc.)[/li][li] is there any indication of a device conflict in the Device Manager that may affect or prevent full access to the ports used by the programming software?[/li][li] You suspect a possible MS dot.Net issue. Is the same version running on all PCs?[/li][li] Did you try uninstalling and re-installing the programming software on the effected machines to eliminate the possibility of a corrupt installation?[/li][/ol]
The issue could be due to a lot of things. These are just a few troubleshooting steps to get you started. We don’t deal with Kirisun so I cannot comment on the quality of their programming software, however it is no secret that some Chinese radio manufactures have a reputation for software that is poorly written. It is entirely possible that the software for this radio may be just a bit touchy.
Rick,
Problem solved!
I was trying unsuccesfully to run version 1.28 and then 1.29 of the software, when as an afterthought I figured I would try an older version of it and see what happens. After uninstalling the newer versions I installed an older version (Version 1.20) of the programming software and this works perfectly with an XP SP3 laptop!
All my XP computers are running SP3 with the latest updates as supplied by Microsoft and three of them are running Windows 7 professional. I can’t remember off-hand which version of the software is running on the other computers, pretty sure that I do actually run version 1.29 on a Windows 7 machine because we do need to program some 66-88 Midband versions of this radio as well, which I do not think the older version software is capable of.
Thanks for your words of advice Rick, I hope this experience will be of use to other chaps as well.
-Eric
That’s great news, Eric!
I’m glad to hear you were able to get it resolved. 