1. Manuals
  2. Brands
  3. PE micro Manuals
  4. Motherboard
  5. Cyclone Series
  6. Developer's manual

PE micro Cyclone Series Developer's Manual

Automated control package
Hide thumbs
Table of Contents

Advertisement

Quick Links

Cyclone Automated Control Package
Developer‟s Manual
Copyright 2016, P&E Microcomputer Systems, Inc. All rights reserved.
Visit us on the web at http://www.pemicro.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Cyclone Series and is the answer not in the manual?

Questions and answers

Related Manuals for PE micro Cyclone Series

Summary of Contents for PE micro Cyclone Series

  • Page 1 Cyclone Automated Control Package Developer‟s Manual Copyright 2016, P&E Microcomputer Systems, Inc. All rights reserved. Visit us on the web at http://www.pemicro.com...
  • Page 2 Cyclone Automated Control Package Document Version History Version Date Notes Added information about Cyclone Universal 5.89 29 April 2016 and Cyclone Universal FX Updated Document Version History 5.73 10 December 2015 Updated “P&E Software Licensing System” Updated MSVC# Project 5.52 4 August 2015 Updated “check_STARTED_cyclonepromax_status”...

  • Page 3: Table Of Contents

    Cyclone Automated Control Package CONTENTS 1 Introduction ......................5 1.1 Introduction to Cyclone Launch ..............5 1.2 Introduction to the Cyclone Control DLL ............6 1.3 Introduction to RS232 / Ethernet Communication Protocols......6 1.4 Library Files Included .................. 7 1.5 P&E Compatible Hardware................
  • Page 4 Cyclone Automated Control Package 4.5.1 reset_cyclonepromax ..............32 4.5.2 get_firmware_version ..............32 4.5.3 get_image_description ..............33 4.5.4 compare_image_with_file .............. 34 4.5.5 erase_all_cyclone_images ............35 4.5.6 add_image_to_cyclone ..............36 4.5.7 update_image_with_file ..............37 4.5.8 count_cyclonepromax_images ............37 4.5.9 toggle_power_no_background_entrance ........38 4.5.10 set_cyclonepromax_media_type ...........

  • Page 5: Introduction

    Cyclone Automated Control Package 1 Introduction Thank you for installing P&E‟s Cyclone Automated Control Package! You now have a set of tools that will allow you to automate your production programming process like never before. Included in this package are: ...

  • Page 6: Introduction To The Cyclone Control Dll

    Cyclone Automated Control Package 1.2 Introduction to the Cyclone Control DLL The dynamic link library included in this package allows you to create an application on the PC that can directly control one or more P&E Cyclone units. These interface routines are designed to be compiled into visual and non visual applications running on Windows operating systems.

  • Page 7: Library Files Included

    Cyclone Automated Control Package 1.4 Library Files Included Due to the various calling conventions that currently exist, P&E provides the developer with two different versions of the Cyclone Control DLL. The example programs include header files which use the “cdecl” calling convention. The user must modify these header files if they wish to use the “stdcall”...

  • Page 8: Versions

    Cyclone Automated Control Package 1.6 Versions The Cyclone Automated Control Package product is split into three separate versions. While this manual is written to support all three versions, it is important to note the following limitations: Basic Edition  DLL only supports controlling a single Cyclone unit ...

  • Page 9: Software License

    Cyclone Automated Control Package 2 Software License 2.1 License for Basic and Professional Editions This software and accompanying documentation are protected by United States Copyright law and also by International Treaty provisions. Any use of this software in violation of copyright law or the terms of this agreement will be prosecuted.

  • Page 10: License For Enterprise Edition

    Cyclone Automated Control Package 2.2 License for Enterprise Edition This software and accompanying documentation are protected by United States Copyright law and also by International Treaty provisions. Any use of this software in violation of copyright law or the terms of this agreement will be prosecuted.

  • Page 11: P&E Software Licensing System

    Cyclone Automated Control Package 2.3 P&E Software Licensing System When Cyclone Launch or the Cyclone Control DLL is used for the first time, a popup form will be shown prompting the user to enter the relevant information to activate the software. Please refer to the original packaging for the necessary installation code.

  • Page 12: Getting Started With The Cyclone Control Dll

    Cyclone Automated Control Package 3 Getting Started with the Cyclone Control DLL This section outlines the steps you need to take to begin developing your own custom application and offers tips and suggestions to get the Cyclone Control DLL working with your P&E hardware smoothly. 3.1 Example Programs Located in the installation directory of the package, you will find three example programs that you can use as a reference for your own application.
  • Page 13 Cyclone Automated Control Package MSVC# 2005+ Projects INSTALLDIR\msvcsharp2005\multiple_cyclone_programming.cs Once added to the project workspace, the namespace of the class may optionally be modified to match the namespace of your project. The project (visual_sap_control.sln) has been tested in Microsoft Visual Studio Community 2015.

  • Page 14: Initialization

    Cyclone Automated Control Package 3.3 Initialization Loading the DLL (C/C++ Projects only) Before calling any routines from the DLL, the DLL must be loaded into memory. To do this, the following function has been provided in the included header files. Refer to Chapter 4 of this manual for a detailed description of this function.

  • Page 15: Finalization

    Cyclone Automated Control Package 3.4 Finalization Before closing the application, it is recommended that the session with the P&E hardware be terminated and the DLL unloaded from memory. These calls should always be made before the application closes: disconnect_from_cyclonepromax( ); close_all_ports( );...

  • Page 16: Typical Usage

    Cyclone Automated Control Package 3.6 Typical Usage Figure 3-1: Typical programming procedure flow chart Figure 3-1 describes the most common sequence of calls to the DLL after successfully connecting to the Cyclone unit. Step 1: Initiate programming operations. “START_execute_all_commands” carries out the programming operations defined in the stand-alone image stored on the Cyclone unit.

  • Page 17: External Memory Storage Support

    Cyclone Automated Control Package 3.7 External Memory Storage Support Some Cyclones support external memory storage (either Compact Flash or SDHC). The Cyclone Control DLL and Cyclone Launch both support images residing on external memory cards. The following functions/commands are used to switch between Cyclone internal Flash and external memory: Cyclone Control DLL : set_cyclonepromax_media_type Cyclone Launch : MEDIATYPE=n and ALLMEDIATYPE=n...

  • Page 18: Application Programming Interface (Api)

    Cyclone Automated Control Package 4 Application Programming Interface (API) This chapter describes the API of the “CYCLONE_CONTROL.DLL” in detail. Note that certain functions in the API are not supported in the Basic Edition of the DLL. Please refer to section 1.6 of this manual for more details. In each section, the function prototypes are given in the following order: Delphi C/C++...

  • Page 19: Dll Loading / Unloading Calls

    Cyclone Automated Control Package 4.2 DLL Loading / Unloading Calls 4.2.1 load_dll bool load_dll(void); Loads the CYCLONE_CONTROL.DLL into memory and gives the user access to all of the functions available in the library. This routine must be called before any of the other routines can be called. This routine is only required for C/C++ applications and is defined in the file “multiple_cyclone_programming.cpp”.

  • Page 20: Enumerate_All_Ports

    Cyclone Automated Control Package 4.2.3 enumerate_all_ports procedure enumerate_all_ports; void enumerate_all_ports(void); void enumerate_all_ports(void); Performs all necessary initialization in order to successfully communicate with a Cyclone unit. This function needs to be called once, before the first call to “connect_to_cyclonepromax”. 4.2.4 close_all_ports procedure close_all_ports;...

  • Page 21: Cyclone Connecting / Disconnecting Calls

    Cyclone Automated Control Package 4.3 Cyclone Connecting / Disconnecting Calls 4.3.1 connect_to_cyclonepromax function connect_to_cyclonepromax(port_type : longword; identifier_type : longword; port_identifier : pchar) : longword; unsigned long connect_to_cyclonepromax(unsigned long port_type, unsigned long identifier_type, char* port_identifier); UInt32 connect_to_cyclonepromax(UInt32 port_type, UInt32 identifier_type, String port_identifier); This function opens a session with a Cyclone unit and tests the connection.
  • Page 22 Cyclone Automated Control Package If identifying by name, the string should contain the name of the Cyclone unit. If identifying by port and the Cyclone is connected by USB, the string should be USB# where # is 1…8. If the Cyclone is connected by Ethernet, the string should be in the format of xxx.xxx.xxx.xxx, where xxx = 0…255.

  • Page 23: Connect_To_Cyclonepromax_By_Ip

    Cyclone Automated Control Package 4.3.2 connect_to_cyclonepromax_by_ip function connect_to_cyclonepromax_by_ip(port_identifier : pchar) : longword; unsigned long connect_to_cyclonepromax_by_ip(char * port_identifier); UInt32 connect_to_cyclonepromax_by_ip(String port_identifier); This function is a legacy call and should not be used for new applications. “connect_to_cyclonepromax” should be used instead. This call opens a session with a Cyclone unit that is connected via Ethernet by its IP address.

  • Page 24: Disconnect_From_Cyclonepromax

    Cyclone Automated Control Package 4.3.3 disconnect_from_cyclonepromax function disconnect_from_cyclonepromax(cyclonepromaxhandle : longword) : boolean; bool disconnect_from_cyclonepromax(unsigned long cyclonepromaxhandle); bool disconnect_from_cyclonepromax(UInt32 cyclonepromaxhandle); When processing is complete, the session with the Cyclone unit should be terminated. Calling this routine with the appropriate handle terminates the session.

  • Page 25: Set_Com_Port

    Cyclone Automated Control Package 4.3.5 set_COM_port function set_COM_port (COM_port_number : longword) : boolean; bool set_COM_port (unsigned long COM_port_number); bool set_COM_port (UInt32 COM_port_number); Sets the COM port that should be used for serial communications. By default, COM1 is automatically selected. If a different COM port is to be used, this function should be called prior to calling “connect_to_cyclonepromax”.

  • Page 26: Controlling Cyclone Programming

    Cyclone Automated Control Package 4.4 Controlling Cyclone Programming 4.4.1 START_execute_all_commands function START_execute_all_commands(cyclonepromaxhandle : longword; image_id : byte) : boolean; bool START_execute_all_commands(unsigned long cyclonepromaxhandle, unsigned char image_id); bool START_execute_all_commands(UInt32 cyclonepromaxhandle, byte image_id); A Cyclone unit may have several independent programming images in non-volatile memory.

  • Page 27: Start_Dynamic_Program_Bytes

    Cyclone Automated Control Package 4.4.2 START_dynamic_program_bytes function START_dynamic_program_bytes(cyclonepromaxhandle longword; target_address : longword; data_length : word; buffer : pointer) : boolean; bool START_dynamic_program_bytes( unsigned long cyclonepromaxhandle, unsigned long target_address, unsigned short data_length, char *buffer); bool START_dynamic_program_bytes(UInt32 cyclonepromaxhandle, UInt32 target_address, UInt16 data_length, byte[ ] buffer); Sometimes, in addition to the large amount of static data being programmed into a target from the Cyclone, it is advantageous for the calling application to program small sections of unique data dynamically.

  • Page 28: Check_Started_Cyclonepromax_Status

    Cyclone Automated Control Package 4.4.3 check_STARTED_cyclonepromax_status function check_STARTED_cyclonepromax_status( cyclonepromaxhandle : longword) : longword; unsigned long check_STARTED_cyclonepromax_status(unsigned long cyclonepromaxhandle); UInt32 check_STARTED_cyclonepromax_status(UInt32 cyclonepromaxhandle); Checks to see if the Cyclone unit has completed a programming operation started with either the “START_execute_all_commands” or “START_dynamic_program_bytes” routines. After this call returns with completed value, “get_last_error_code”...

  • Page 29: Dynamic_Read_Bytes

    Cyclone Automated Control Package 4.4.4 dynamic_read_bytes function dynamic_read_bytes(cyclonepromaxhandle : longword; target_address : longword; data_length: word; buffer: pointer) : boolean; bool dynamic_read_bytes(unsigned long cyclonepromaxhandle, unsigned long target_address, unsigned short data_length, char *buffer); bool dynamic_read_bytes(UInt32 cyclonepromaxhandle, UInt32 target_address, UInt16 data_length, byte [ ] buffer); Reads a specified number of bytes from a specified memory address of the target processor.

  • Page 30: Get_Last_Error_Code

    Cyclone Automated Control Package 4.4.5 get_last_error_code function get_last_error_code(cyclonepromaxhandle : longword) : word; unsigned short get_last_error_code(unsigned long cyclonepromaxhandle); UInt16 get_last_error_code(UInt32 cyclonepromaxhandle); Returns the last error code recorded by a Cyclone unit. Refer to section 5 for all possible error codes. @param The handle of the Cyclone unit from which cyclonepromaxhandle to request the error code.

  • Page 31: Pro_Set_Active_Security_Code

    Cyclone Automated Control Package 4.4.7 pro_set_active_security_code function pro_set_active_security_code(cyclonepromaxhandle: longword; buffer : pointer) : boolean; bool pro_set_active_security_code(unsigned long cyclonepromaxhandle, char *buffer); bool pro_set_active_security_code(UInt32 cyclonepromaxhandle, byte [ ] buffer); Sets the security code used by the Cyclone Pro to enter monitor mode for HC908 targets.

  • Page 32: Configuration / Image Maintenance Calls

    Cyclone Automated Control Package 4.5 Configuration / Image Maintenance Calls 4.5.1 reset_cyclonepromax function reset_cyclonepromax(cyclonepromaxhandle : longword; reset_delay_in_ms : longword) : boolean; bool reset_cyclonepromax(unsigned long cyclonepromaxhandle, unsigned long reset_delay_in_ms); bool reset_cyclonepromax(UInt32 cyclonepromaxhandle, UInt32 reset_delay_in_ms); Used to reset the Cyclone hardware. This routine is a legacy call and does not need to be called by the application.

  • Page 33: Get_Image_Description

    Cyclone Automated Control Package 4.5.3 get_image_description function get_image_description(cyclonepromaxhandle : longword; image_id : byte) : pchar; char *get_image_description(unsigned long cyclonepromaxhandle, unsigned char image_id); String get_image_description(UInt32 cyclonepromaxhandle, byte image_id); Checks the description of a particular image stored on the selected media type. (Cyclone internal Flash or external memory card) This description is specified by the user when the image is first created.

  • Page 34: Compare_Image_With_File

    Cyclone Automated Control Package 4.5.4 compare_image_with_file function compare_image_with_file(cyclonepromaxhandle : longword; aFile : pchar; image_id : byte) : boolean; bool compare_image_with_file(unsigned long cyclonepromaxhandle, char *aFile, unsigned char image_id); bool compare_image_with_file(UInt32 cyclonepromaxhandle, String aFile, byte image_id); Compares an image stored on the selected media type (Cyclone internal Flash or external memory card) against a .SAP file created with the Cyclone Image Creation Utility.

  • Page 35: Erase_All_Cyclone_Images

    Cyclone Automated Control Package 4.5.5 erase_all_cyclone_images function erase_all_cyclone_images(cyclonepromaxhandle : longword) : boolean; bool erase_all_cyclone_images(unsigned long cyclonepromaxhandle); bool erase_all_cyclone_images(UInt32 cyclonepromaxhandle); Erases all images stored on the selected media type. (Cyclone internal Flash or external memory card) This function should not be constantly called, as this will shorten the lifespan of the non-volatile flash memory.

  • Page 36: Add_Image_To_Cyclone

    Cyclone Automated Control Package 4.5.6 add_image_to_cyclone function add_image_to_cyclone(cyclonepromaxhandle : longword; aFile : pchar) : longword; unsigned long add_image_to_cyclone(unsigned long cyclonepromaxhandle, char *aFile); UInt32 add_image_to_cyclone(UInt32 cyclonepromaxhandle, String aFile); Adds a specified stand-alone programming image into the selected media type. (Cyclone internal Flash or external memory card) The image files have a .SAP file extension and are created with the Cyclone Image Creation Utility.

  • Page 37: Update_Image_With_File

    Cyclone Automated Control Package 4.5.7 update_image_with_file function update_image_with_file(cyclonepromaxhandle : longword; aFile : pchar) : boolean; bool update_image_with_file(unsigned long cyclonepromaxhandle, char *aFile); bool update_image_with_file(UInt32 cyclonepromaxhandle, String aFile); Updates an existing image stored on the selected media type (Cyclone internal Flash or external memory card) with a new .SAP image file on the host PC.

  • Page 38: Toggle_Power_No_Background_Entrance

    Cyclone Automated Control Package 4.5.9 toggle_power_no_background_entrance function toggle_power_no_background_entrance( cyclonepromaxhandle : longword) : boolean; bool toggle_power_no_background_entrance(unsigned long cyclonepromaxhandle); bool toggle_power_no_background_entrance(UInt32 cyclonepromaxhandle); Toggles the output target power of the Cyclone unit. The signals used to enter background mode are also tristated during this time. This call is normally used to power down and power up the target so that the processor is running normally after programming.

  • Page 39: Set_Cyclonepromax_Media_Type

    Cyclone Automated Control Package 4.5.10 set_cyclonepromax_media_type procedure set_cyclonepromax_media_type(new_media_type : byte); void set_cyclonepromax_media_type(unsigned char new_media_type); void set_cyclonepromax_media_type(byte new_media_type); Cyclone stand-alone images may be stored on the Cyclone‟s internal Flash memory or on an external memory card. This function selects one of the two media types.

  • Page 40: List Of Error Codes

    Cyclone Automated Control Package 5 List of Error Codes The following error codes are returned from the “get_last_error_code” function call in the DLL. Note the “0x” prefix indicates that the corresponding error code is in hexadecimal format. Success: 0x0000: Programming operations completed without error. Application handling related error codes: 0x00A0: BM is not pre-configured.
  • Page 41 Cyclone Automated Control Package Execution related error codes: 0x0001: Unable to detect target communication speed. 0x0002: Unable to enter debug mode. 0x0003: Operation cancelled by user. 0x0004: Error writing data byte block. 0x0005: Error writing data byte block. 0x0006: Error during execution. 0x0007: Error enabling module.
  • Page 42 Cyclone Automated Control Package 0x7007: Error during programming the trim value. 0x7008: Error during verify trim value 0x7009: Trim value is $00 or $FF 0xEEEE: Error during communication with Cyclone...

  • Page 43: Cyclone Launch

    Cyclone Automated Control Package 6 Cyclone Launch The Cyclone Automated Control Package includes an application that controls Cyclone operations through the use of simple script files. This application is very easy to set up and use and offers functionality very similar to using the Cyclone Control DLL directly.

  • Page 44: Startup

    Cyclone Automated Control Package 6.1 Startup a) Connect all Cyclone units to the PC via RS232, USB, or Ethernet. Any combination of different connections is allowed. The exception is that only one RS232 serial port connection can be used; no more than one Cyclone can be connected via the RS232 serial port.

  • Page 45: Command-Line Parameter Examples

    Cyclone Automated Control Package 6.2 Command-Line Parameter Examples CYCLONE_LAUNCH.exe config_script.cfg ! The Cyclone executes all operations specified in the “config_script.cfg” file. The CYCLONE_LAUNCH application remains open if any error occurs. CYCLONE_LAUNCH.exe config_script.cfg -O output_log.txt The Cyclone executes all operations specified in the “config_script.cfg” file and logs all results to the “output_log.txt”...

  • Page 46: Configuration Script File

    Cyclone Automated Control Package 6.3 Configuration Script File The configuration file contains two types of commands. The first type is SETUP commands which configures the communication port between the PC and the Cyclone units. The second type is Operation commands which carry out the pre- configured Cyclone operations.
  • Page 47 Cyclone Automated Control Package SETRESETDELAY=resetdelay Specifies the amount of reset delay used when a Cyclone unit is reset using the “ALLRESET” or “RESET” commands. “resetdelay” is the number of milliseconds to delay, and must be greater or equal to 5500. Increasing this delay is important if using the USB interface, which requires extra time to reenumerate when the Cyclone is reset.
  • Page 48 Cyclone Automated Control Package PORT=y Specifies the port that should be used for contacting all subsequent Cyclone units. The value of y may be: - Subsequent Cyclones will be contacted via USB ETHERNET - Subsequent Cyclones will be contacted via Ethernet SERIAL - Subsequent Cyclones will be contacted via Serial CYCLONE=identifier...

  • Page 49: Operation Commands That Control All Connected Cyclones

    Cyclone Automated Control Package 6.3.2 Operation Commands that Control All Connected Cyclones These commands affect all Cyclone units connected by the “CYCLONE=identifier” setup command. Many of these commands are ideal to use when multiple Cyclone units have identical images and configuration. ALLRESET Resets all connected Cyclone units.

  • Page 50: Operation Commands That Control A Single Cyclone

    Cyclone Automated Control Package 6.3.3 Operation Commands that Control a Single Cyclone These commands affect a single connected Cyclone unit. The “SELECT [identifier]” command must first be used to select the appropriate Cyclone prior to using the other commands in this section. SELECT [identifier] Selects the Cyclone unit that will be controlled until the next “SELECT [identifier]”...
  • Page 51 Cyclone Automated Control Package PUTDYNAMICDATA [address] [data] Performs programming of dynamic data with the selected Cyclone unit. [address] is the starting memory address. [data] are the bytes of data to be programmed. All values should be in hexadecimal format. No more than 255 bytes may be programmed this way. A Cyclone unit may only use this command after it has performed its “START”...

  • Page 52: Examples

    Cyclone Automated Control Package 6.4 Examples The configuration (.cfg) file should be a pure ASCII file with one command per line. Comments must be preceded by a semicolon „;‟ character. 6.4.1 Typical Usage ; Setup commands OPENTYPE=IP SETTIMEOUT=60 ;Configure for 1 minute timeout PORT=USB CYCLONE=192.168.1.1 ;...

  • Page 53: Controlling Multiple Cyclones

    Cyclone Automated Control Package 6.4.2 Controlling Multiple Cyclones ; Setup commands OPENTYPE=IP SETTIMEOUT=60 ;Configure for 1 minute timeout PORT=USB CYCLONE=192.168.1.1 IMAGENUM=2 CYCLONE=192.168.1.2 IMAGENUM=2 PORT=ETHERNET CYCLONE=192.168.1.3 IMAGENUM=3 ; Operation commands ALLSTART This example connects to three separate Cyclone units. Two units are connected via USB (192.168.1.1 and 192.168.1.2) and the third is connected via Ethernet (192.168.1.3).

  • Page 54: Programming Dynamic Data

    Cyclone Automated Control Package 6.4.3 Programming dynamic data ; Setup commands SETCOMPORT=1 ;Use COM1 OPENTYPE=NAME SETTIMEOUT=60 ;Configure for 1 minute timeout PORT=SERIAL CYCLONE=PE_PRO1 IMAGENUM=1 ; Operation commands START PUTDYNAMICDATA 1080 45 44 49 53 4F 4E Here, a Cyclone is connected via the Serial port and is identified by name rather than IP address.

  • Page 55: Executing More Than 1 Image On The Same Cyclone

    Cyclone Automated Control Package 6.4.4 Executing more than 1 image on the same Cyclone ; Setup commands OPENTYPE=NAME SETTIMEOUT=60 ;Configure for 1 minute timeout PORT=ETHERNET CYCLONE=PE_PRO1 IMAGENUM=1 CYCLONE=PE_PRO2 IMAGENUM=1 ; Operation commands ALLSTART SELECT PE_PRO1 IMAGENUM=2 START Two Cyclone units are connected via Ethernet and both Cyclone units execute their first image.

  • Page 56: Image Management

    Cyclone Automated Control Package 6.4.5 Image Management ; Setup commands OPENTYPE=IP SETTIMEOUT=60 ;Configure for 1 minute timeout PORT=USB CYCLONE=209.61.110.143 CYCLONE=209.61.110.144 ; Operation commands ALLERASEIMAGES ALLADDIMAGE C:\Images\Image1.SAP In this last example, two Cyclone units connected via USB have their images erased and a new image is added to both Cyclone units. This type of script should only be executed when images need to be updated.

  • Page 57: Dos Error Codes

    Cyclone Automated Control Package 6.5 DOS Error Codes If the Cyclone Control Utility encounters a fatal configuration error, such as not being able to contact a specified Cyclone or providing invalid commands in the configuration script, the utility will halt immediately. However, if a Cyclone has an error while it is executing an image, the utility will still continue to process script commands for all other Cyclone units that do not have errors.
  • Page 58 Cyclone Automated Control Package 0x00C1: Specified Ethernet IP address is incorrect. 0x00C7: The Cyclone PRO device is not ready. Please check power and connections. 0x00C8: Error in configuration script. 0x00C9: Error erasing Cyclone images 0x00CA: Error adding a Cyclone image Execution related error codes: 0x0001: Unable to detect target communication speed.
  • Page 59 Cyclone Automated Control Package 0x6004: Error during user functions. 0x7003: Error calculating trim value. 0x7004: Trim value is not calculated. 0x7005: Program Word Algorithm is not supported for writing the trim value. 0x7006: Program Byte Algorithm is not available for writing the trim value. 0x7007: Error during programming the trim value.

  • Page 60: Sample Batch File

    Cyclone Automated Control Package 6.6 Sample Batch File Here is an example of calling Cyclone Launch and testing the error code return in a simple batch file. Sample batch files are given for most Microsoft Windows Operating Systems below. Windows NT/2000/XP/Vista/7/8/10: CYCLONE_LAUNCH test.CFG if errorlevel 1 goto bad goto good...

  • Page 61: Cyclone Communication Protocols

    Cyclone Automated Control Package 7 Cyclone Communication Protocols Included with the Cyclone Automated Control Package Enterprise Edition are documents describing the serial port RS232 and Ethernet communication protocols used by the Cyclone. Knowing these protocols allows the developer to manually send individual byte packets which will be interpreted by the Cyclone as commands.

This manual is also suitable for:

Cyclone universal fxCyclone universalCyclone proCyclone maxCyclone for armCyclone for renesas ... Show all

Table of Contents