-

Y_Comm_Toolbox FB

Function block Description
Y_CO_CommunicationChannel
The Y_CO_CommunicationChannel function block is designed to manage an input stream of data from a TCP socket communication interface. It collects portions of data read in a cycle, and adds it to a circular buffer for further analysis. The Yt_CO_CommStruct structure must be initialized by the user to configure the necessary communication parameters.
Y_CO_ReName_CommandProcessor
The Y_CO_ReName_CommandProcessor function block is a user customizable function block that parses data from a circular buffer and copies it into a user defined structure of data to operate the machine. To use this function, copy and paste it into the main project, rename it, and customize it and populate the MachineData structure. It's designed to identify variable length commands in the CircularByteBuffer and process them on a case by case basis.
Y_CO_UpdatePointer
This is an internal function block used to update the pointers used to manage the circular buffer in command stream function blocks.
Y_CO_ReName_FTP_RecordData
This function works in combination with Y_CO_ReName_FTP_SendData. Both functions must be copied and pasted into the main project and slightly customized for use. This function is designed to continuously record data using two databanks. Together, Y_CO_ReName_FTP_RecordData and Y_CO_ReName_FTP_SendData handshake and synchronize operations such that Recording takes place in one databank while the FTP transfer takes place using the other databank. Files of nearly unlimited size can be created on an FTP Server. Customization consists of creating an application specific structure similar to "Yt_CO_ReName_RecordedUserData" in the main project which contains the specific data required by the application. This technique writes binary data to the file and therefore requires a program to read and interpret the same data structure. The data is non ASCII, unless converted to ASCII as part of customization using type conversion functions. Converting the data to ASCII on the motion controller is not recommended, especially if high speed recording is desired. Y_CO_ReName_FTP_RecordData typically executes in a faster task, even as fast as the motion network update rate if necessary, recording up to 1000 samples of data in each "DataBank." There are two Databanks; one which is being written to by Y_CO_FTP_RecordData, and the other which contains data being uploaded to the FTP server. Y_CO_Rename_FTPSendData can typically execute in a slower task or the DEFAULT task.
Y_CO_ReName_FTP_SendData
This function works in combination withY_CO_ReName_FTP_RecordData. Both functions must be copied and pasted into the main project and slightly customized for use. This function is designed to continuously record data using two databanks. Together, Yt_CO_ReName_FTP_RecordData and Yt_CO_ReName_FTP_SendData handshake and synchronize operations such that Recording takes place in one databank while the FTP transfer takes place using the other databank. Files of nearly unlimited size can be created on the FTP Server. Customization consists of creating an application specific structure similar to "Yt_CO_ReName_RecordedUserData" in the main project which contains the specific data required by the application. This technique writes binary data to the file and therefore requires a program to read and interpret the same data structure. The data is non ASCII, unless converted to ASCII as part of customization using type conversion functions. Converting the data to ASCII on the motion controller is not recommended, especially if high speed recording is desired. Y_CO_ReName_FTP_RecordData typically executes in a faster task, even as fast as the motion network update rate if necessary, recording up to 1000 samples of data in each "DataBank." There are two Databanks; one which is being written to by FTP_RecordData, and the other which contains data being uploaded to the FTP server. Y_CO_Rename_FTP_SendData can typically execute in a slower task or the DEFAULT task.Y_CO_ReName_
Y_CO_FTP_SendFile
This function block uses the FTP (File Transfer Protocol) to write a file to a specified FTP server. The File must already exist on the iC922x Controller's Flash or ramdisk for this function block to read and transfer data to the Destination FTP server. The File must be created by some other method, or refer to ReName_FTP_SendData which doesn’t require a pre existing file.
Y_CO_PrepareMessage
The Y_CO_PrepareMessage can be used to prepare a string message. This function block is used inside the Y_CO_SendEmail block.
Y_CO_SendEmail
This function block sends an e-mail via SMTP commands (Simple Mail Transfer Protocol) through a specified SMTP server. The output is highly configurable including multiple recipients, any message body structure, specified sender e-mail and name and other features listed below.
Y_CO_ModbusTCPClient This function blocks enables the controller as a Modbus TCP client.
Y_CO_ModbusTCPServer This function block enables the controller as a Modbus TCP server and starts listening to a client.

 


This help information is valid for iCube Engineer Online Help 2025.6

Copyright © 2025 YASKAWA EUROPE GmbH and © 2025 YASKAWA America, Inc.