From PlcWiki

Revision as of 11:59, 30 July 2013 (view source) Petr.zalabak (Talk | contribs) (Created page with '= Kernel configuration file = The main configuration of the Kernel process is stored in the file /usr/local/plc/etc/plc_krnl_''project''.cfg. == Sending of backflush == The back…') ← Older edit		Revision as of 21:42, 6 February 2014 (view source) Petr.zalabak (Talk | contribs) Newer edit →
Line 18:		Line 18:
	= plan_''project''.cfg =		= plan_''project''.cfg =
		+
		+	= Operation data scripts =
		+	It is possible to create bash scripts which are executed by special events. The location of these scripts is defined by the Kernel configuration parameter
		+	OperationDataScriptsDir = "/usr/local/plc/bin/operation_data_scripts"
		+	It is its default value.
		+
		+	== Operation scripts ==
		+	These scripts are executed when the operation sends its data to the kernel. The Client parameter
		+	Operation.''name''.SendDataToKernel = Yes
		+	is needed.
		+	The name of the script needs to be same like an operation ID (for example /usr/local/plc/bin/operation_data_scripts/AB3).
		+	== Workplace scripts ==
		+	These scripts are executed when the product is completed on the workplace. Nothing is needed to specify in the Client configuration.
		+
		+	The name of the script needs to be same like a workplace ID (for example /usr/local/plc/bin/operation_data_scripts/AB).
		+	== Special events scripts ==
		+	There are some special scripts, which are executed by following events:
		+	{| class="wikitable"
		+	|
		+	! Event
		+	! Name of the script
		+	|-
		+	| Start of assembly
		+	| START_OF_ASSEMBLY
		+	|-
		+	| End of assembly
		+	| END_OF_ASSEMBLY
		+	|-
		+	| Rework requested
		+	| REWORK_REQUESTED
		+	|-
		+	| Rework finished
		+	| REWORK_FINISHED
		+	|-
		+	| Rework cancelled
		+	| REWORK_CANCELLED
		+	|}
		+
		+	If the script has a general feature, it is useful to use just a soft link named like the operation and it can point to the real script.

---

Revision as of 21:42, 6 February 2014

Contents 1 Kernel configuration file 1.1 Sending of backflush 1.1.1 Kernel data 1.1.2 PMC data 2 PartDistribution.cfg 3 plan_project.cfg 4 Operation data scripts 4.1 Operation scripts 4.2 Workplace scripts 4.3 Special events scripts

Kernel configuration file

The main configuration of the Kernel process is stored in the file /usr/local/plc/etc/plc_krnl_project.cfg.

Sending of backflush

The backflush data can be created either by the Kernel, or it can be prepared by a PMC data flow when the data are being received.

Kernel data

PMC data

# It is possible to backflush the product using the PMC dataflow. PMC will prepare the datafile                                                       
# in time when the data are received to Clever system and place it to the defined DirQueue. When                                                      
# the product assembly is finished, the Kernel crates the flag file and PMC DirQueue sends the                                                        
# datafile to JIS.                                                                                                                                    
#EndAssemPMCFlagDir = /usr/local/plc/var/pmc/backflushdirq                                                                                            
# The flag file can be created by a done operation as well.                                                                                           
DoneOperationPMCFlagDir.OC2 = /usr/local/plc/var/pmc/backflushdirq                                                                                    

PartDistribution.cfg

plan_project.cfg

Operation data scripts

It is possible to create bash scripts which are executed by special events. The location of these scripts is defined by the Kernel configuration parameter

OperationDataScriptsDir = "/usr/local/plc/bin/operation_data_scripts"

It is its default value.

Operation scripts

These scripts are executed when the operation sends its data to the kernel. The Client parameter

Operation.name.SendDataToKernel = Yes

is needed. The name of the script needs to be same like an operation ID (for example /usr/local/plc/bin/operation_data_scripts/AB3).

Workplace scripts

These scripts are executed when the product is completed on the workplace. Nothing is needed to specify in the Client configuration.

The name of the script needs to be same like a workplace ID (for example /usr/local/plc/bin/operation_data_scripts/AB).

Special events scripts

There are some special scripts, which are executed by following events:

	Event	Name of the script
Start of assembly	START_OF_ASSEMBLY
End of assembly	END_OF_ASSEMBLY
Rework requested	REWORK_REQUESTED
Rework finished	REWORK_FINISHED
Rework cancelled	REWORK_CANCELLED

If the script has a general feature, it is useful to use just a soft link named like the operation and it can point to the real script.