Supported platforms: CODESYS 2.3

 

 

ISOBUS VT pool is created using the Jetter ISO-designer™. MultiTool Creator adds the needed initializations for the device.

 

 

 

 

1. Import ISOBUS VT application parts to CODESYS 2.3 project

 

To add ISOBUS code template to the CODESYS project, run Edit > Macros > Import ISOBUS. Running the macro

• adds ISOBUS programs, object handlers and a template program for data/alarm masks

• updates object pool  (downloaded binary)

• updates code template’s list of object pool’s objects (global variables > ISOBUS VT > ISOBUS_CANx > IsobusExportVtInfo)

 

 

When importing ISOBUS files, CODESYS requests to overwrite objects. Answer Yes to these pop-ups.

 

2. Create user init and update programs

 

The VT client program ISOBUS_CANx_IsobusVt requires own programs for user initialization and update code. These programs are called in ISOBUS_CANx_IsobusVt (PRG) actions actInit and actUpdate.

 

Add two programs (ST language recommended) with the following names (x according to the CAN interface)

• ISOBUS_CANx_IsobusVtInitUserCode (PRG)

• ISOBUS_CANx_IsobusVtUpdateUserCode (PRG)

 

ISOBUS_CANx_IsobusVtInitUserCode (PRG) is used, for example, to initialize ISO-designer elements such as buttons and numeric input/output fields.

ISOBUS_CANx_IsobusVtUpdateUserCode (PRG) is called each program cycle after VT client is updated.

 

 

3. Add data mask handler program

 

The template ISO-Designer project for VT client includes one working set and one data mask (named as DataMask_1000). Each VT data/alarm mask requires its own handler program into CODESYS project which is called when the mask is active.

 

Data/Alarm mask handler program are required to have predefined inputs and outputs. Import ISOBUS macro generates names for each mask to ISOBUS_CANx_Main_MaskHandler declaration part as a comment.

 

The easiest way to make a handler program is to

1. copy-paste a template program called TEMPLATE_HANDLER (PRG)

2. copy data mask handler name from ISOBUS_CANx_Main_MaskHandler program comment: ISOBUS_CANx_MaskHandler_DataMask_1000_ID1000

 

A complete project looks like this:

 

 

4. Build project

The project is now ready to be build. Build the CODESYS project but don't download it to the unit yet.

 

5. Make ISOBUS VT pool with Jetter ISO-designer™

Object pool is edited with 3rd party program Jetter ISO-designer™. MultiTool adds a template ISOBUS pool project for ISO-designer™ to {DeviceFolder}\ISOBUS\Jetter\IsobusVtObjectPool.jvw.

 

Open this project file by double-clicking it (Jetter ISO-designer™ should be installed). To build the ISO-Designer template project, select Build > Build project 'IsobusVtObjectPool'.

 

 

 

6. Import ISOBUS VT files to CODESYS 2.3

Run Import ISOBUS macro described below every time you have made changes to Jetter ISO-designer™ project or to the language XML.

 

 

In CODESYS 2.3 device project, run Edit > Macros > Import ISOBUS

 

When importing ISOBUS files, CODESYS requests to overwrite objects. Answer Yes to these pop-ups.

Check from Globals, that the updated exp file is imported:

 

 

 

7. Download object pool to device

ISOBUS import macro creates also a binary file which is downloaded to the unit. This binary contains ISOBUS related data, for example, object pool. The binary file is downloaded with CANmoon. Open CANmoon and  select Configuration > Actions > Download > Software.

 

Note that CANopen is recommended to be initialized to find the unit with CANmoon scan.

 

 

 

Select object pool binary file {DeviceFolder}\ISOBUS\python\BinaryMaker\Downloaded.bin and download it to the unit.

 

8. Download application to device

Download CODESYS application normally to the device and reboot the device:

1. Check the control unit communication parameters

   - By default, the units have CODESYS communication node-ID 126 (download node-ID), Application node-ID 127

2. Define the communication parameters to CODESYS Online > Communication Parameters...

 

 

3. Login and download with CODESYS Online > Login

4. Power cycle the control unit each time after dowloading CODESYS application and object pool.

 

9. Connect VT to bus

Connect VT to the same CAN bus with the unit (VT can be connected all times to the bus when updating application or object pool). When VT is started, the device downloads the pool to VT and starts to use it.

 

 

10. Troubleshooting

Device doesn't download pool to VT

Go online with CODESYS 2.3 and check the following issues.

 

Open Program ISOBUS_CAN1_IsobusVt and open POU as shown in image below.

 

Variable	Description	Reason to error	Resolution
vtClient::o_LicenseOk	Flag value must be TRUE. This flag tells if device has ISOBUS license activated.	Unit ISOBUS license is not activated.	Please contact Epec to order a unit with ISOBUS license activated.
vtClient::o_EcuStatus::State	Value ISOBUS_VT_CLIENT_HANDLING_UI tells that vtClient is downloaded pool successfully to unit and it can be used.	Any other state informs error for example in address claiming or pool download.	No exact resolution for this error.
vtReadBinaryData::o_Error	Value ISOBUS_ERR_SUCCESS tells that vtClient has read pool binary successfully from device flash.	For some reason pool read from flash is failed.	Try to download pool again with CANmoon.

 

 

11. Continue with training project from Epec Extranet to use ISO-Designer elements and make functionalities into CODESYS application.

 

 

 

 

 

1. Create user init and update PRGs

Add the following programs to the project. ISOBUS_CAN{X}_IsobusVtInitUserCode is used, for example, to initialize ISO-designer elements such as buttons and input fields. Every data mask requires it's own handler program.

Name	Type	Related option	Description
ISOBUS_CAN{X}_IsobusTcInitUserCode	PRG	TC client	Called after ISOBUS TC client is initialized. {X} is used CAN interface.
ISOBUS_CAN{X}_IsobusTcUpdateUserCode	PRG	TC client	Called after ISOBUS TC client is updated. {X} is used CAN interface.

 

2. Import ISOBUS VT files to CODESYS 2.3

Run Import ISOBUS macro described below every time you have made changes to Jetter ISO-designer™ project, or to the language xml.

 

 

In CODESYS 2.3 device project, run Edit > Macros > Import ISOBUS

 

When importing ISOBUS files, CODESYS requests to overwrite objects. Answer Yes to these pop-ups.

 

Check from Globals, that the updated exp file is imported:

 

3. Build project

The project is now ready to be build. Build the CODESYS project but don't download it to the unit yet.

 

Project looks something like this.

 

4. Download object pool to device

ISOBUS import macro creates also a binary file which is downloaded to the unit. This binary contains ISOBUS related data, for example object pool. Binary file is downloaded with CANmoon. Open CANmoon and  select Configuration > Actions > Download > Software.

Note that CANopen must be initialized to use CANmoon.

 

 

 

Select binary file {DeviceFolder}\ISOBUS\python\BinaryMaker\Downloaded.bin and download it to the unit.

 

 

5. Download application to device

Download CODESYS application normally to the device and reboot the device.

 

6. Connect TC to bus

Connect TC to the same CAN bus with the unit (TC can be connected all times to the bus when updating application or object pool). When TC is started, the device downloads the pool to TC and starts to use it.

 

7. Initializations in user code

It is possible to set different values in TC object pool. These values are set online when pool is downloaded. Code examples for these settings:

 

Implement serial number:

 

 ISOBUS_CAN1_IsobusTc.i_ClientSerialNumber := '1234567';

 

 

Implement TC client pool serial number:

 

 ISOBUS_CAN1_IsobusTc.i_ClientSwVersion := 'My sw version is 1234.45567';

 

 

Default value for DPT:

 

 G_ISOBUS_CAN1_OBJECT_DDI_LIST[G_ISOBUS_CAN1_DDI_ID_DPT_Seed_drill_body_Maximum_working_width_70].Value:= 4000;

 

 

8. Troubleshooting

Device doesn't download pool to VT

Go online with CODESYS 2.3 and check the following issues.

 

Open Program ISOBUS_CAN1_IsobusTc and open POU as shown in image below.

 

Variable	Description	Reason to error	Resolution
vtClient::o_LicenseOk	Flag value must be TRUE. This flag tells if device has ISOBUS license activated.	Unit ISOBUS license is not activated.	Please contact to Epec to order a unit with ISOBUS license activated.
tcClient::o_EcuStatus::State	Value ISOBUS_TC_CLIENT_ACTIVE tells that tcClient is downloaded pool successfully to unit and it can be used.	Any other state informs error for example in address claiming or pool download.	No exact resolution for this error.
tcReadBinaryData::o_Error	Value ISOBUS_ERR_SUCCESS tells that tcClient has read pool binary successfully from device flash.	For some reason pool read from flash is failed.	Try to download pool again with CANmoon.

 

 

1. Import ISOBUS files to CODESYS 2.3

In CODESYS 2.3 device project, run Edit > Macros > Import ISOBUS

 

When importing ISOBUS files, CODESYS requests to overwrite objects. Answer Yes to these pop-ups.

 

2. Create user init and update PRGs

Add the following programs to the project. User programs can be used for application specific code.

 

Name	Type	Description
ISOBUS_CAN{X}_TecuInitUserCode	PRG	Called after ISOBUS TECU is initialized. {X} is used CAN interface.
ISOBUS_CAN{X}_TecuUpdateUserCode	PRG	Called after ISOBUS TECU is updated. {X} is used CAN interface.

 

Complete project looks like below.

Note that ISOBUS folder may have other programs too if you have more than one ISOBUS component initialized.

 

 

3. Download application to device

Download CODESYS application normally to the device and reboot the device.

 

 

4. Connect TECU to bus

Connect TECU to the same CAN bus with the unit (TECU can be connected all times to the bus when updating application). When TECU and device are connected to the same bus, PGN messages will be received.

 

TECU message data can be accessed by application through Codesys Resources tab > ISOBUS variable list > G_ISOBUS_CAN{X}_Data.TECUData (see image below).

 

For code use case examples see ISOBUS_ImplementTECUFacilities (FB) topic in ISOBUS library's software manual (Epec Programming and Libraries manual, available in Epec Extranet).

 

 

5. Troubleshooting

Measurement values cannot be received from TECU

Go online with CODESYS 2.3 and check the following issues.

 

Open Program ISOBUS_CAN1_TECU and open POU as shown in image below.

 

Variable	Description	Reason to error	Resolution
implementTECU::o_LicenseOk	Flag value must be TRUE. This flag tells if device has ISOBUS license activated.	Unit ISOBUS license is not activated.	Please contact to Epec to order a unit with ISOBUS license activated.
implementTECU::o_Errors	Value depends on error. ISOBUS_ERR_SUCCESS tells that there is no errors.	Message initialization could have failed or license is missing.	Please contact Epec with specific error code.

 

 

 

 

1. Import ISOBUS files to CODESYS 2.3

In CODESYS 2.3 device project, run Edit > Macros > Import ISOBUS

 

When importing ISOBUS files, CODESYS requests to overwrite objects. Answer Yes to these pop-ups.

 

2. Create user init and update PRGs

Add the following programs to the project. User programs can be used for application specific code.

 

Name	Type	Description
ISOBUS_CAN{X}_DiagInitUserCode	PRG	Called before ISOBUS diagnostic is initialized. {X} is used CAN interface.
ISOBUS_CAN{X}_DiagUpdateUserCode	PRG	Called after ISOBUS diagnostic is updated. {X} is used CAN interface.

 

Complete project looks like below.

Note that ISOBUS folder may have other programs too if you have more than one ISOBUS component initialized.

 

 

 

3. Configuring diagnostic messages

MultiTool Creator does not currently support ISOBUS diagnostic PGN configuration but it can be done in Codesys.

 

Diagnostic message configurations can be accessed by application through Codesys Resources tab > ISOBUS variable list > G_ISOBUS_CAN{X}_Data.DiagConfig (see image below).

 

 

Below is an example of initialization code which can be added to ISOBUS_CAN1_DiagInitUserCode PRG. The messages are defined in ISO 11783-12 standard.

CFF message's Enabled flags state depend on which ISOBUS components are used by application.

Diagnostic messages are sent to bus only on request by other devices (except DM1 log).

For DM1 use case example, see ISOBUS_SPNFMI_ToDTC (FUN) topic in ISOBUS library's software manual (Epec Programming and Libraries Manual, available in Epec Extranet).

 

 

 (*Configure ICC PGN*)

 G_ISOBUS_CAN1_Data.DiagConfig.Certification.TestProtocolYear := 2016;

 G_ISOBUS_CAN1_Data.DiagConfig.Certification.TestProtocolRevision := 2;

 G_ISOBUS_CAN1_Data.DiagConfig.Certification.LaboratoryID := 0;

 G_ISOBUS_CAN1_Data.DiagConfig.Certification.LaboratoryType := ISOBUS_LAB_TYPE_SELF;

 G_ISOBUS_CAN1_Data.DiagConfig.Certification.ReferenceNumber := 20000;

 (*Configure ECUID PGN*)

 G_ISOBUS_CAN1_Data.DiagConfig.EcuIdentification.ECU_PartNumber := 'E30E3606-23';

 G_ISOBUS_CAN1_Data.DiagConfig.EcuIdentification.ECU_SerialNumber := DWORD_TO_STRING(SYSTEM_SerialNumber);

 G_ISOBUS_CAN1_Data.DiagConfig.EcuIdentification.ECU_Location := 'Implement';

 G_ISOBUS_CAN1_Data.DiagConfig.EcuIdentification.ECU_Type := DWORD_TO_STRING(SYSTEM_ControlUnitType);

 G_ISOBUS_CAN1_Data.DiagConfig.EcuIdentification.ECU_Manufacturer := 'Epec Oy';

 G_ISOBUS_CAN1_Data.DiagConfig.EcuIdentification.ECU_HardwareID := '000215';

 (*Configure SOFT PGN*)

 G_ISOBUS_CAN1_Data.DiagConfig.SwIdentification.ECU_FW := SYSTEM_FW_VERSION;

 G_ISOBUS_CAN1_Data.DiagConfig.SwIdentification.Application_SW := 'App sw 1.23.4';

 (*Configure DIAG PGN*)

 G_ISOBUS_CAN1_Data.DiagConfig.DiagProtocol.Protocols[1] := ISOBUS_DIAG_ISO_11783;

 (*Configure PII PGN*)

 G_ISOBUS_CAN1_Data.DiagConfig.ProductIdentification.PI_Code := '123456789';

 G_ISOBUS_CAN1_Data.DiagConfig.ProductIdentification.PI_Brand := 'DemoBrand';

 G_ISOBUS_CAN1_Data.DiagConfig.ProductIdentification.PI_Model := 'Model ABC';

 (*Configure CFF PGN*)

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_MinCF.Enabled := TRUE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_MinCF.Generation := 1;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_MinCF.Options[1] := ISOBUS_CFF_OPT_MINCF_NONE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TECUBasicClient.Enabled := TRUE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TECUBasicClient.Generation := 1;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TECUBasicClient.Options[1] := ISOBUS_CFF_OPT_TECU_BAS_CLASS2;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TECUBasicClient.Options[2] := ISOBUS_CFF_OPT_TECU_BAS_F;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TECUBasicClient.Options[3] := ISOBUS_CFF_OPT_TECU_BAS_L;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_UTClient.Enabled := TRUE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_UTClient.Generation := 2;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_UTClient.Options[1] := ISOBUS_CFF_OPT_UT_NONE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCBasicClient.Enabled := TRUE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCBasicClient.Generation := 1;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCBasicClient.Options[1] := ISOBUS_CFF_OPT_TC_BAS_NONE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCSectionClient.Enabled := TRUE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCSectionClient.Generation := 1;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCSectionClient.NumOfBooms := 1;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCSectionClient.NumOfSections := 2;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCGeoClient.Enabled := FALSE;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCGeoClient.Generation := 1;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCGeoClient.SupportedChannels := 1;

 G_ISOBUS_CAN1_Data.DiagConfig.CFFunctionalities.CFF_TCGeoClient.Options[1] := ISOBUS_CFF_OPT_TC_GEO_NONE;

 

 

4. Download application to device

Download CODESYS application normally to the device and reboot the device.

 

 

5. Troubleshooting

Diagnostic messages are not sent when requested

Go online with CODESYS 2.3 and check the following issues.

 

Open Program ISOBUS_CAN1_Diagnostic and open POU as shown in image below.

 

Variable	Description	Reason to error	Resolution
implementDiagnostic::o_LicenseOk	Flag value must be TRUE. This flag tells if device has ISOBUS license activated.	Unit ISOBUS license is not activated.	Please contact Epec to order a unit with ISOBUS license activated.
implementDiagnostic::o_Errors	Value depends on error. ISOBUS_ERR_SUCCESS tells that there is no errors.	Message initialization could have failed or license is missing.	Please contact Epec with specific error code.

 

Source file topic100343.htm

Last updated 13-Jun-2024