KSM-500 Frequently Asked Questions

FAQ header
KSM-500 Frequently Asked Questions

FAQ/030 KSM-500: I am unable to import a MatLab mat-file generated by kFlashCardXID

To avoid the issue with $ and matfile, you will have to rename the parameter. Then you need to click verify and use the new strategy file generated for data extraction. To rename the parameters, you can either:

  1. In kSetup, Right click over any ARINC message and select ‘view parameters’, – the '$' can be set to something else that MatLab will accept e.g. '_'
  2. Do a replace all in the XidML® file from $ to _ , then run verify on this new XidML file and again use the new strategy file generated for data extraction.

FAQ/031 KSM-500 - kProgram: ACRA ERROR :: Cannot find next baudrate

The message occurs when a configuration is verified or when the program button is pressed. It means that the parameters coming from the slaves were placed in the PCM frame too early and was not available to be read when required. The master/slave algorithm cannot find a higher bitrate to allow the parameter to be received to the master on time to ensure data coherency through the system.

For further information please refer to TEC/NOT/035 - Rules of PCM placement.

FAQ/032 KSM-500 - kProgram: How is the error "encountered impossible expiry" resolved?

This is a sign that there is a malfunction in the system (not necessary in that chassis).

Some steps for investigating the problem are as follows:

  1. Remove all the modules from the chassis and check the power lead and that 28V does not flick. The chassis can operate with an input voltage varying from +18V up to 40V. If the LED flickers without any modules in it and the 28V is stable then the chassis should be returned to Curtiss-Wright through the RMA process by sending a mail to acra-rma@curtisswright.com
  2. If the above is good, then replace the modules back into the chassis one at a time starting with the controller module such as the KAD/BCU/101 or KAD/BCU/105. Power up the chassis as each module is added to confirm if the LED is blinking. If the LED flickers after one of the modules is placed into the chassis then this module is faulty and should be returned to Curtiss-Wright through the RMA process at the address given above.
  3. If all the modules and chassis are good then the connectors on each module should be connected one by one until the faulty connection is found – in this instance, the cabling will need to be verified.

FAQ/033 KSM-500 - kProgram: Internal error occurs with the following info: File hwcal.app Line 296 – itsAddressCalSector==ADDRESS_CAL_TEMP

FAQ 31

This error is known to happen when the software is trying to communicate with the hardware during programming.

It is usually due to a bad communication link, such as a bad termination or a floating ground.

FAQ/034 KSM-500 - kProgram: kProgram compile error for KAM/MEM/003 due to an excessive number of parameters logged in the memory

kProgram reports an error when trying to compile a project with the memory module KAM/MEM/003 due to an excessive number of parameters logged in the memory: ACRA ERROR :: ModuleID(60742):Chassis=00-Slot=06 ( J8 )-Type=0742- Selector=00 Module 60742 has an invalid value of 24402 for 'number of parameters in acq cycle' Max value allowed is 16376

How is this issue overcome?

This problem happens because the KAM/MEM/003 module uses a buffer of 16K (16376) Words to log data into the CompactFlash Card. In each acquisition cycle the parameters are read from the backplane and stored in the 16K buffer for later storage to the CompactFlash Card. When trying to Compile a project in which more than 16K Parameters are to be logged into the memory module per acquisition cycle, the Compiler (Kc) will give the above error message and stop compilation. This problem occurs more often when using long acquisition cycles (even at low sampling frequencies), since more parameters have to be stored in the buffer during the acquisition cycle – e.g. logging 200 parameters at a moderate/slow rate of 100 samples/second results in 200samples x 100Hz = 20000 samples/second. If the acquisition cycle is 1 second, the number of parameters to be stored in the MEM buffer per acquisition cycle is higher than the maximum of 16K allowed, therefore Kc will report an error. Typically this will occur when there is a big difference between the fastest and slowest sample in a system.

To fix this problem two solutions are possible:

  1. Reduce the number of parameters or sampling rate of the parameters to be logged in the MEM
  2. Reduce the Acquisition Cycle

Usually the second solution is advisable since it will allow the user to record the required number of parameters at the desired sampling rate. In the previous example (20000 parameters/second) if the Acquisition Cycle is 500ms, only 10000 parameters will be stored in the buffer each Acquisition Cycle and the software will be able to compile the project without errors. If slow parameters are defining the slow acquisition cycle the solution is to over sample these to shorten the acquisition cycle.

FAQ/035 KSM-500: kProgram message error: ACRA ERROR :: Error programming loom 'acra_std_asys'

Always look at the first error generated by kProgram. For this case, the first error was:

C00:J05:8a2 - Setting the NEEDS_REPROGRAM flag

ACRA WARNING :: Failed to program sector - will retry.

ACRA ERROR :: Failed to program sector

This error is due to the module in J5. kProgram cannot write or read correctly the EEPROMs. It will try 3 times per default. This issue can be due to:

  • Damage module. Change module to check if the module is damaged
  • Damage chassis. Change module slot or change the chassis
  • Damage controller. Change controller
  • Power consumption too high. Calculate the power consumption according to TEC-NOTE-049
  • Bad grounding
  • Bad programming link

FAQ/036 KSM-500: kProgram reports on the following error on the message server. How is it resolved?

FAQ 36

This error can happen for two reasons:

  • The setup contains the wrong backplane controller part number in the xidML XidML file compared to what is physically in the chassis. Example: kSetup or xidML XidML mentions KAD/BCU/101/B and physically, a KAD/BCU/101/C is used.

    Solution: Ensure with kDiscover that the physical part number in the chassis matches what is mentioned in kSetup or the xidML file using kDiscover.
  • Physically the system is setup to be programmed through Ethernet but SAM/DEC is selected in the kWorkbench Configuration Link:
FAQ 36b

Solution: Ensure the Configuration link is setup according to the programming wiring.

FAQ/037 KSM-500: kProgram: What is happening when such an error occurs : ACRA ERROR :: Offset=63 (zero-based) for 'DEC_0_J3_Ch0' exceeds max offset (28).?

This error is known to happen when the user left an empty location into the IENA packet as follows:

FAQ 37

That can happen if the user removed a module without going back to the IENA builder.

FAQ/038 KSM-500 - kProgram: What is happening when the following internal error occurs : ACRA ERROR: Could not create a "serviceable" fixup for?

ACRA WARNING :: Could not create a "serviceable" fixup for 1_P6511&&-2&&0 before tick 12 ACRA WARNING :: could not generate K3 for 1_P6511&&-2&&0 starting at clock 9 - expired at 12 ACRA WARNING :: could not schedule all transfers in this pass. Closing file C:\ACRA\kProgram\CACHE\ACRA_STD_ASYS\KAM_00\FMT_00\f0971/mytest.q00 . Removing schedule file C:\ACRA\kProgram\CACHE\ACRA_STD_ASYS\KAM_00\FMT_00\f0971/ mytest.q00 (-S not specified) ACRA ERROR :: Backplane placement failed. Note: placement failure may be due to positioning of message parameters in the IRIG-106 frame (thread management). ACRA ERROR :: KFRONT returned an error ACRA ERROR :: KC could not successfully generate all controller EEPROM images


It means the parameter 1_P6511 has to be placed later in the PCM. The parameter 1_P6511 is placed at the beginning of the PCM. It means the KAM- 500 has to schedule this parameter very early in the acquisition cycle. The parameter has to be transmitted at tick 12 (125ns =1 tick) but this parameter needs more time to be scheduled on the backplane.

Check if the parameter is coming from a bus monitor module. If it’s, ensure all the parameters from the same message are placed horizontally in the PCM to ensure the usage of BDMA.

For further information please refer to “TEC/NOT/035 - Rules of PCM placement

FAQ/039 KSM-500 - kProgram: What is happening when the following internal error occurs: ACRA ERROR :: Backplane placement failed.?

ACRA WARNING :: could not generate K3 for ADC14_22_J4_Ch3@@0_575&&- 64&&0 starting at clock 2505 - expired at 2501 ACRA WARNING :: could not schedule all transfers in this pass. Closing file C:\ACRA\kProgram\CACHE\ACRA_STD_ASYS\KAM_00\FMT_00\f0971/mytest.q00 . Removing schedule file C:\ACRA\kProgram\CACHE\ACRA_STD_ASYS\KAM_00\FMT_00\f0971/ mytest.q00 (-S not specified) ACRA ERROR :: Backplane placement failed. Note: placement failure may be due to positioning of message parameters in the IRIG-106 frame (thread management). ACRA ERROR :: KFRONT returned an error ACRA ERROR :: KC could not successfully generate all controller EEPROM images


It means the parameter ADC14_22_J4_Ch3 cannot be scheduled on time according to its PCM placement. This parameter is coming from a slave chassis but kProgram is failing on the master (see.q00 with 00 being the chassis ID).

The issue here is not because the parameter should be placed later even if it can help the compilation but it’s certainly due to the slow read parameters placed before it. Try to arrange the parameters to follow the rules of PCM placement.

For further information please refer to “TEC/NOT/035 - Rules of PCM placement“.

FAQ/040 KSM-500: How can you change the revision of a PCM transmitter module, such as the KAD/BCU/101/C, in KSM-500 on an existing configuration while still preserving the PCM frame?

  1. Load the XidML configuration file as usual. In this example, the KAD/BCU/101 module is the controller.
  2. Double click on KAD/BCU/101 and then select the Frame Builder button
  3. Select the File menu and then ‘Save As’
  4. Select a file save name, for example ‘MyBCUFrame’, then save again with another name, for example ‘MyTempBCUFrame’
    Save the frame screen shot
  5. Exit the frame builder
  6. Change the module to KAD/BCU/101/B
  7. Select the Frame builder button
  8. Select the option from an existing frame
    FAQ 40
  9. Select ‘MyBCUFrame’. Note: MyTempBCUFrame will have been removed – that’s why you saved it twice in step 4.
    Frame Wizard select frame
  10. Select Finish.

You have now setup changed the revision of the PCM transmitter module while still preserving the original PCM frame i.e. your parameters remain as defined in the BCU/101 PCM frame.

FAQ/041 KSM-500: There is no KAM/ADC/113 available in kSetup, can I select the KAD/ADC/113

Yes, the KAM/ADC/113 and KAD/ADC/113 have the same module type. This is true for any KAM/KAD module.

FAQ/042 KSM-500: During the KSM-500 installation the error: "Internal Error 2711" appears. How is this resolved?

This error indicates Microsoft Installer (MSI) Engine's control files need to be cleaned up. It is usually caused by a recent installation that did not install completely or was cancelled during the installation. To resolve this:

  1. Run Microsoft fix it: http://support.microsoft.com/mats/program_install_and_uninstall/

There's also a version in the same link above for PCs not connected to internet called portable Microsoft Fix it.

FAQ/043 KSM-500: During the KSM-500 installation, the message: "Error 1905 (easygrid.ocx)" or "cannot load DLL when double clicking in a module in kSetup" appears under XP. How is this resolved?

CPU XD (or Execute Disable) prevents certain buffer overruns as managed by the operating system.

  1. Execute Protection Disable (XD) via boot.ini (HP and Dell)
    FAQ 43
    FAQ 43

    [operating systems] multi(0) … WINDOWS="Microsoft Windows XP Professional" /noexecute=AlwaysOff

    FAQ 43
    FAQ 43
    FAQ 43

    [operating systems] multi(0) … WINDOWS="Microsoft Windows XP Professional" /noexecute=optin

    1. Right-click on My Computer and select Properties.
    2. Select the Advanced tab at the top of the window (seen below)
    3. Select the Settings Button in the Startup and Recovery field.
    4. Select the Edit Button. This will populate the boot.ini in Notepad for editing.
    5. Edit the boot header in boot.ini by changing the "/noexecute=optin" to "/noexecute=AlwaysOff" (as seen below).
    6. Select File -> Save and close Notepad.
    7. Click OK on the Startup and Recovery window.
    8. Click OK on the System Properties window.
    9. Reboot the system.
    10. Install KSM-500.
    11. Go to Windows Start Menu -> Run
    12. Type regsvr32 \ksetup\easygrid.ocx
    13. Click Ok:
    14. Repeat steps 1 through 4 above.
    15. Change the boot header back to its original form (as seen below):
    16. Repeat steps 6 – 9 above.
  2. Alternative procedure for Dell systems - Execute Protection Disable (XD) via BIOS
    1. Access the BIOS on your system by restarting your computer and pressing F2 during the BIOS POST test (a Dell splash screen will appear).
    2. Under the hierarchy to the left, scroll down to Security
    3. Under CPU XD Support, switch the flag from Enabled to Off
    4. Press Esc, and save the BIOS settings before exiting.
    5. After the reboot, you should be able to install KSM-500
    6. If the error still occurs, proceed to the second correction

FAQ/044 KSM-500: During the KSM-500 installation, the message: "Error 1905 (easygrid.ocx)" or "cannot load DLL when double clicking in a module in kSetup" appears while using Microsoft's Windows 7 OS. How is this resolved?

Before installing KSM-500, you should disable Windows’ Data Execution Security (DEP) 7 or Procedure for registering the DLL. Proceed as follows:

Disable DEP:

  • Click Start
  • Click All Programs
  • Click Accessories
  • Right Click on Command Prompt
  • Left click on Run as Administrator
  • On the command prompt window, type the following: bcdedit.exe /set {current} nx AlwaysOff
  • Hit enter and you should see the confirmation: Operation Completed Successfully
  • Reboot and DEP should be off.
FAQ 44

You should see a success message after you enter the command.

Install KSM-500

Register easygrid.ocx

  1. Locate Command Prompt from Start>All Programs>Accessories.
  2. Right click the Command Prompt and choose "Run as Administrator" from the context menu.
  3. Now execute regsvr32 c:\acra\ksetup\easygrid.ocx assuming the KSM-500 software was installed under the default directory c:\acra

If errors still occur, contact Acra support detailing the errors encountered.

FAQ/045 KSM-500: Error 1603 appears while installing KSM-500. How is this resolved?

FAQ 45

The InstallShield software used to install KSM-500 generates this error. To resolve the issue:

1) Ensure you have full administrator privileges when you install the KSM-500 software.
Follow the steps on the following link: http://consumer.installshield.com/kb.asp?id=Q111019

FAQ/046 KSM-500: I’m using a KSM-500 software version for which the KAD/ADC/113/B is not supported. Could I reprogram the module type to a KAD/ADC/113?

Yes. Please contact support to get the instructions how to reprogram the module type.

The matrix of modules that have the successors with the same EEPROM setup, backplane register set and backplane timings as its predecessor is shown below. From the software’s point of view, the modules for which the only difference is the module type are:

KAD/ADC/113 => KAD/ADC/113/B
KAM/MEM/103 => KAM/MEM/103/B
KAD/ADC/105 => KAD/ADC/105/B
KAD/ADC/109/B/S1 => KAD/ADC/109/C/S1
KAD/ADC/109/B/S2 => KAD/ADC/109/C/S2
KAD/ADC/106/B => KAD/ADC/106/C
KAD/ADC/109/B/QB350 => KAD/ADC/109/C/QB350
KAD/BCU/101/B => KAD/BCU/101/C
KAD/DAC/001 => KAD/DAC/001/B
KAM/TCG/102/B => KAD/MSB/103/B
KAD/MSB/103 => KAM/TCG/102/C
KAD/BCU/105/B => KAD/BCU/105/C
KAD/UTL/102 => KAD/UTL/102/X1
KAD/UTL/102/X1 => KAD/UTL/102/X2
KAD/ADC/011/B => KAD/ADC/011/C
KAD/ADC/117 => KAD/ADC/117/B
KAD/ADC/126 => KAD/ADC/126/B
KAD/EBM/101 => KAD/EBM/101/B

Please refer to the module datasheet to know the difference between the actual module and its predecessor.

FAQ/047 KSM-500: The message "'37.202381' is not a valid floating point value" appears when Frame Builder is run. How is this resolved?

KSM-500 is designed to support Windows English Regional Options, whereby a comma ',' is used to separate thousands and a period '.' is used for floating points. French PCs and Spanish PCs are set up the opposite way around. To resolve this:

  1. Go to Control Panel.
  2. Open Regional and Language Options and click Customize.
    FAQ 47
  3. In all fields change all periods to commas and change all commas to periods and then click Apply.

FAQ/048 KSM-500: What information should I provide to acra-support@curtisswright.com if I want to report a software issue?

Please provide the following:

  1. The name and the version number of the tool used. You can find the version number by opening the readme file under the KSM-500 installation. For example, if an issue has been seen with kSetup, open ksetup_readme.pdf and note the version number
  2. The XidML file used. You will find the XidML file under the task directory under the KSM-500 installation. Please compress the file (in the .zip format preferably) before sending it by email. You may also want to rename the .zip extension to .piz to ensure your mail server doesn’t remove the file.
  3. Instructions for the Curtiss-Wright Dublin Support department to recreate the issue. Don’t hesitate to provide us with some screenshots in a word document to make the instructions clearer.
  4. The log file with the error displayed. To retrieve this information
    FAQ 48
    message server screen shot
    1. Double click on the Message Server icon:
      message server icon screen shot
    2. Press the CTRL and A keys to select all the text from the message server then press the CTRL and C keys to copy the text.
      message server screen shot
    3. To copy this information into an email or document, press the CTRL and V keys
  5. Paste all the information in the above steps into an email, or into a document and then attach this to an email, and send it to acra-support@curtisswright.com

FAQ/049 KSM-500: What should I do when the DOS window with the title "C:\Windows\microsoft.net\framework\ v2.0.50727\regasm" after KSM-500 installation doesn't close?

An older version may already be installed ion the computer; KSM-500 doesn't see the need to reinstall again. You should

  • Uninstall any version of the .NET framework that might be in the computer.
  • Reinstall KSM-500.

FAQ/050 KSM-500: When I run Discover, I get this error message "Module in KAM-500 DAU 0 slot 3 has failed its bit walk test." How can I resolve it?

The answer is not straight forward as it can have different causes: Programming link

  1. If you have a spare BCU you could rule out the BCU as being a problem by replacing it and trying Discover again.
  2. If you have a spare SAM/DEC you could rule it by replacing it and trying Discover again.
  3. Check that the KAM-500 is grounded. Refer to TEC/NOT/063 - Grounding of the KAM-500.
  4. Check your programming cable. Refer to the BCU and SAM/DEC datasheet for the pin out and check with an ohm-meter. If the cable got bent, the shield might be touching the programming line.

Module fault

  1. If the issue remains, remove all the modules (apart from the BCU) and run Discover. If this is successful then add the modules one by one, running Discover each time. This will tell us which module is at fault if it is a hardware fault.
  2. If the issue remains, it could be a chassis fault. You could rule out the chassis being a problem by replacing it and trying Discover again.

Diverse fault

If the issue remains, please contact acra-support@curtisswright.com with the results of the suggested tests above.

  1. Check if there is any dirt or foreign matter either on the backplane connectors of the chassis or the connectors of the modules themselves. It can be cleaned with a paintbrush or the like.
  2. Visually check the connectors in the chassis to ensure that they are giving good contact. One of the spring loaded connectors in the backplane connector may have gotten widened – thus giving a bad contact. In that case carefully straighten the connector with a pin or something similar ensuring you take proper ESD precautions.

FAQ/051 KSM-500: When opening some KSM-500 tools, I get a "Too many open files" error:

Too many open files screenshot
  1. Go to Control Panel.
  2. Open BDE Administrator.
BDE Administrator

3. Edit MAXFILEHANDLES to read 256 at least.

FAQ/079 KSM-500: How do I install KSM-500 under the 32bit version of Windows 7?

The 32 bit version of Windows 7 supports kSetup1.14. The steps to install it are as follows:

1) Uninstall any previous version of KSM-500

2) Ensure you have full access to write and read on main drive and this folder is not set to "Archive".

3) Set the User Account Control so the 'User Account Control settings' are set to ‘Never Notify me’:

  • Select Windows Start menus and navigate to Control Panel -> System and Security
  • Under 'Action Centre' list, select ‘Change User Account Control Settings’
  • Move the slider to ‘Never Notify’

4) Change ‘Driver Signature Enforcement’:

  • On Windows boot, press F8
  • Select option 'Disable Driver Signature Enforcement': Allows drivers containing importer signature to be loaded.

5) Install Microsoft’s .NET 4 framework. .NET Framework 4.0 is not installed during KSM-500 suite installation on Windows 7 32-bit OS. It can be manually installed from the subfolder in the installation.\KSM\ISSetupPrerequisites\{5C4CB9D4-9B57-45D4-BC56-0BC2CA8325F0

6) Install KSM-500 as Administrator.

  • Right click on setup.exe and select 'run as Administrator'. Note: you will get a 'Class not registered' error when using kSetup if not installed as administrator

7) Allow kDiscover, kProgram and kFetch through the Firewall, Public and Private network or disable the Firewall. To give the programs permission:

  • Select Windows Start menu and navigate to Control Panel -> System and Security and select ‘Allow a program through Windows Firewall’ under the ‘Windows Firewall section.
  • Click on the Add another program
  • Select kDiscover.exe, Click Add.
  • Repeat for kProgram.exe, Enable.exe and kFetch.exe.
  • Run all KSM-500 tools As Administrator (Right-click properties of exe, run as Administrator)

8) Disable ‘Data Execution Prevention’. For this, execute the following at the command prompt:

  • Select Windows Start menu. Select All Programs -> Accessories and Right Click on Command Prompt
  • Left-click on Run as Administrator
  • Click the Allow button if it asks you for permission
  • Type this into the command prompt window: bcdedit.exe /set {current} nx AlwaysOff
  • Hit enter and you should see the confirmation ‘Operation Completed Successfully’
  • Reboot the PC