Details for DDEntity "160 - Section Control State"

160 - Section Control State Request changes

Definition	Specifies the actual state of section control. The value definitions are: Byte 1 (bitfield) Bit 0-1: 00 = manual/off, 01 = auto/on, 10 = error indicator, 11 = undefined/not installed. Bits 2-7: reserved, set to 0. Bytes 2-4: reserved, set to 0. The DDI shall support the On Change trigger so that the TC is able to get informed when the value gets changed by the Working Set Master. The TC shall active this trigger when using the DDI. See attachment for more information
Comment	In section control systems, the section control master and its clients need to be synchronized in terms of their general state or activation by the user (System activated/deactivated in individual setups). This DDE serves 2 purposes, one is to synchronize the section control state and the other is to enable a TC client to announce the support and initial state of its section control capabilities. Synchronisation by the section control master (TC) is done by setting the section control state of connected TC clients with a process data set value message with this DDE. It is recommended that TC clients reply their state immediately when such a message is received. The property flag "setable" and the trigger method "on change" should be used with this DDE. The state "manual/off" indicates that the device is in manual state and will ignore all control commands for section control. The "auto/on" state indicates that the client accepts the section control commands as far as its overall process state allows. Listed below are 4 example Use Cases for this DDE: Use case "Start up operation": 1. During a start up the implement shall set the SCS to ‘manual mode’. Use case "Auto request from TC": 1. The implement receives an ‘auto’ request from TC. 2. The implement shall check whether all setup conditions are fulfilled to allow section control. 3. If this check is ok: The implement may respond with ‘auto mode’ and set its internal SCS client to ‘auto mode’. 4. If this check not ok: The implement shall respond with ‘manual mode’. The internal state is still in manual mode. The TC may inform the operator accordingly. Use case "Manual request from TC": 1. The implement receives a manual request from TC. 2. If the implement is still in ‘auto mode’ the implement shall set its internal SCS client to ‘manual mode’. Use case "Loss of requirements for auto mode": 1. The implement internal setup conditions don’t allow for automatic section control anymore. 2. The implement shall set the internal SCS client to ‘manual mode’. 3. The implement shall send the SCS to inform the TC accordingly. On reception of this ‘manual mode’ the TC/Section Control Master may inform the operator accordingly.

Definition

Specifies the actual state of section control. The value definitions are: Byte 1 (bitfield) Bit 0-1: 00 = manual/off, 01 = auto/on, 10 = error indicator, 11 = undefined/not installed. Bits 2-7: reserved, set to 0. Bytes 2-4: reserved, set to 0. The DDI shall support the On Change trigger so that the TC is able to get informed when the value gets changed by the Working Set Master. The TC shall active this trigger when using the DDI. See attachment for more information

Comment

In section control systems, the section control master and its clients need to be synchronized in terms of their general state or activation by the user (System activated/deactivated in individual setups). This DDE serves 2 purposes, one is to synchronize the section control state and the other is to enable a TC client to announce the support and initial state of its section control capabilities. Synchronisation by the section control master (TC) is done by setting the section control state of connected TC clients with a process data set value message with this DDE. It is recommended that TC clients reply their state immediately when such a message is received. The property flag "setable" and the trigger method "on change" should be used with this DDE. The state "manual/off" indicates that the device is in manual state and will ignore all control commands for section control. The "auto/on" state indicates that the client accepts the section control commands as far as its overall process state allows. Listed below are 4 example Use Cases for this DDE: Use case "Start up operation": 1. During a start up the implement shall set the SCS to ‘manual mode’. Use case "Auto request from TC": 1. The implement receives an ‘auto’ request from TC. 2. The implement shall check whether all setup conditions are fulfilled to allow section control. 3. If this check is ok: The implement may respond with ‘auto mode’ and set its internal SCS client to ‘auto mode’. 4. If this check not ok: The implement shall respond with ‘manual mode’. The internal state is still in manual mode. The TC may inform the operator accordingly. Use case "Manual request from TC": 1. The implement receives a manual request from TC. 2. If the implement is still in ‘auto mode’ the implement shall set its internal SCS client to ‘manual mode’. Use case "Loss of requirements for auto mode": 1. The implement internal setup conditions don’t allow for automatic section control anymore. 2. The implement shall set the internal SCS client to ‘manual mode’. 3. The implement shall send the SCS to inform the TC accordingly. On reception of this ‘manual mode’ the TC/Section Control Master may inform the operator accordingly.

Typically used by Device Class(es)	0 - Non-specific system 4 - Planters /Seeders 5 - Fertilizer 6 - Sprayers

Unit Symbol	n.a. - not applicable
Bit Resolution	1
SAE SPN
CANBus Range	0 to 3
Display Range	0 to 3
Submit Date	2008-12-03
Submit By	Matthias Meyer
Submit Company	33 - John Deere
Revision Number	1
Current Status	ISO-Approved
Status Date	2009-02-05
Status Comments

Attachments

ISO11783-11-DDI-160-Section Control State-v2.pdf
43.62 KB	Upload: 2023-03-24 07:58:43

Status History

2009-02-05: ISO-Approved

Back