| 1.Introduction In most cases, users would like to embed programming software to their application, and then control the programmer using their own application. SUPERPRO USB series programmers provide the specific DLL files for users to complete this performance. The users could call in the DLL files to complete almost all the SUPERPRO functions without the SUPERPRO programmer software. For example: a)Dynamically modify BUFFER data. In lots of applications, the individual byte contents for each chip are different. Traditionally, programming the chip is very inefficient since the BUFFER needs to be amended manually first. Each sensor will be tested by the comprehensive testing calibration system and then the calibration values will be stored in designated memory chips; serial number will be generated online for the products that need special electronic serial number. By calling DLL files, all of the above could be achieved in one step without human intervention.
b) Easy implementations in various areas such as vehicle maintenance, cell phones repair, and electronic appliances repair, etc.
c) Automated production lines and customization of products documentation, records and management system. 2. Requirements Please install the software correctly and copy the file spoem.dll to bin directory. (for example :\sp5000\bin)
For the devices with configuration words, firstly generate the configuration files in SUPERPRO software (see details later), then copy it to the appropriate path.
3. Basic procedures for calling DLL
Calling DLL is similar to the implementing procedures for SUPERRO software. The difference is that device configuration information needs to be generated in advance, and no online accessory settings are provided. The generating procedures are as follows:
a)Run SUPERPRO software,
b)Set device configuration,
c)Save project file,
d)Generate a dcf file with the same name as the project file. This dcf file is one of the entry parameters for calling DLL
After device configuration, DLL could be implemented
1) Initialization. Complete the initial configuration of the programmer
2) Communications with programmer
3) Selection of devices
4) Upload of files to the BUFFER
5) Device implementation Please install the software correctly and copy the file spoem.dll to bin directory. (for example :\sp5000\bin）
4. The class is exported from the spoem.dll (defined in spoem.h) |
 |
5. Demo (Test.exe)
1. Introduce how to use class：Compiling the demo needs spoem.h and spoem.lib.
Running the demo needs spoem.dll.
2. VC++ project of Test supposes the software of USB installed in the directory c:\sp5000 and spoem.dll in the directory c:\sp5000\bin.
3. The procedures to run the demo: Communication first (only run once),
Select Device -> Load Data File -> Program ( can run with the cycle function)
6. Discuss details
1. Initialize InitParameter(char* chSPDir)
Parameter: chSPDir = DLL the directory which the file spoem.h is in
Return: no
Note: Call one time and only one time
Befor exiting, call ExitSpDll().
Demo: BOOL CTestDlg::OnInitDialog()
2. Communication USBCommunication()
Parameter: no
Return: BOOL
Error:
Step: 1
Type: 0 No error or unknown error
1 directory is error (chSPDir) or lack of necessary files
2 Unauthorized
Demo: void CTestDlg::OnButtonTest()
|
|  |
| Note: How to get the authorization. Please send the ID shown in the following screenshot to Xeltek at techsupport@xeltek.com. It is not free to obtain the authorization. | |
|
|
| . 3. Select Device SelectDevice(char* chMFG,char* chDEV)
Parameter:Manufacturer, Device
Return:BOOL
Error:
Step: 2
Type: 0 No error or unknown error
1 Not Support this chip
2 Communication first or no programmer
3 chMFG error
4 chDEV error
|
| Note : chMFG,chDEV must be correct, including space character. If not sure, please see the file Sp5000u.txt in the directory Lib | |
|  and copy chMFG,chDEV. |
| 
Demo: void CTestDlg::OnButtonSelect() |
 |
| 4. Load Data File
|
|
 |
Load file with the name in the File Name.
5. Program
|
|
 |
| Note: Call BeginProgram(char* chAuto) will return immediately, not waiting end of programming. Call GetProgramStatus() to check programming status. In demo, using Settimer() to status. |
|
| 6. Insertion Test CheckPin();
Parameter：no
Return：BOOL
Error：
Step: 5
Type: 0 No error or unknown error
1 Communication first or no programmer
2 Select device first
3 Porgrammer is busy
4 No chip
5 Pins unmatched
6 Chip inserted upward
7 Chip inserted backward
8 Not support insertion test
Demo:void CTestDlg::OnButtonCheckpin()
|
 |
| 7. Load Data into Buffer directly
|
|
| 8. Set Operation Option |
|
 |
| 9. Cancel CancelProgram()
Parameter: no
Return: BOOL
Error：
Step: 7
Type: 0 No error or unknown error
1 Communication first or no programmer
2 Select device first
3 Porgrammer is busy
4 Cant cancel
10. Select TTL Devcie See Select Device，chMFG = TTLTEST ，chDEV= name of TTL device(22100)
Error：
Step: 8
Type: 0 No error or unknown error
1 Communication first or no programmer
2 chDEV error
Call Program
11. Check Error |
|
| |
