Here is the contents:<\/p>\n\n\n\n
- Introduction<\/li>
- Principles<\/li>
- Package files\n
- \n
- Structure<\/li>\n
- Descriptions<\/li>\n<\/ol>\n<\/li>
- Porting procedure<\/li>
- Porting file adaptation (OcfEmbeddedPort.h)\n
- \n
- Choosing memory area<\/li>\n
- Features enable\/disable<\/li>\n
- Required functions<\/li>\n<\/ol>\n<\/li>
- Protocol integration\n
- \n
- Dictionary publication<\/li>\n<\/ol>\n<\/li>
- Server protocol\n
- \n
- Server C++\n
- \n
- Serial server<\/li>\n
- Dictionary publication<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>
- Polling Example<\/li>
- RX only interrupt Example<\/li>
- RX\/TX interrupt Example<\/li>
- UDP server<\/li>
- Example<\/li><\/ol>\n\n\n\n
- Server C#\n
- \n
- Create a server in .NET application<\/li>\n
- Create a secure native server for .NET application (communication with AES encryption)<\/li>\n
- Execute the Ocf server (call cyclically)<\/li>\n<\/ol>\n<\/li><\/ul>\n\n\n\n
Let’s begin!<\/p>\n\n\n\n
1. Introduction<\/h2>\n\n\n\n
Ocf Server (OcfEmbedded) is necessary to use any Objectis products in order to connect your Client (it can be oStudio – Live Tuning<\/a> or your own application). You will find bellow the basic informations to set your Server.<\/p>\n\n\n\n
2. Principles<\/h2>\n\n\n\n
The embedded client application publishes variables and functions through helpful macros:<\/p>\n\n\n\n
\nOCFE_BEGIN(ocfEntries)\n\tOCFE_VARIABLE(VarStruct.D, OCFE_TYPE_SHORT)\n\tOCFE_VARIABLE(VarStruct.I, OCFE_TYPE_CHAR)\n\tOCFE_VARIABLE(VarBool, OCFE_TYPE_BOOL)\n\tOCFE_VARIABLE(VarShort, OCFE_TYPE_SHORT)\n\tOCFE_VARIABLE(VarInteger, OCFE_TYPE_INT)\n\tOCFE_VARIABLE(VarFloat, OCFE_TYPE_FLOAT)\n\tOCFE_VARIABLE(VarString, OCFE_TYPE_STRING)\n\tOCFE_VARIABLE_READONLY(VarChar, OCFE_TYPE_CHAR)\n\tOCFE_VARIABLE_READONLY(VarLong, OCFE_TYPE_LONG)\n\tOCFE_FUNCTION_VOID(VarFunction)\nOCFE_END\n<\/pre><\/pre>\n\n\n\n
After connecting the target to oStudio Live Tuning, the live debugger allows browsing of all the dictionary content and to use the variables or functions in watches, traces, etc.<\/p>\n\n\n\n
![\"ocfe_principles1\"](\"http:\/\/www.objectis-software.com\/support\/wp-content\/uploads\/2014\/01\/ocfe_principles1.jpg\")
<\/a><\/figure><\/div>\n\n\n\n![\"ocfe_principles2\"](\"http:\/\/www.objectis-software.com\/support\/wp-content\/uploads\/2014\/01\/ocfe_principles2.jpg\")
<\/figure><\/div>\n\n\n\n3. Package files<\/h2>\n\n\n\n
3.1 Structure<\/h3>\n\n\n\n
![\"ocfe_structure\"](\"http:\/\/www.objectis-software.com\/support\/wp-content\/uploads\/2014\/01\/ocfe_structure.jpg\")
<\/figure><\/div>\n\n\n\n3.2 Descriptions<\/h3>\n\n\n\n
The first step is to integrate the four OcfeEmbedded files into a project.<\/p>\n\n\n\n
- OcfEmbeddedPort.h (Porting file, editable to suit the platform)<\/li>
- OcfEmbedded.h (File to include in the main program file)<\/li>
- OcfEmbeddedProtocol.h (Protocol process header file)<\/li>
- OcfEmbeddedProtocol.c (Protocol process body file)<\/li><\/ul>\n\n\n\n
4. Porting procedure<\/h2>\n\n\n\n
- Make the protocol compile using the OcfEmbeddedPort file to adjust target specification (optional).
See chapter 5. : Porting file adaptation (OcfEmbeddedPort.h)<\/li> - Program the Serial or UDP server to establish a link between the server and the client.
See chapter 7. : Server protocol<\/li> - Publish variables and functions and connect oStudio Live Tuning
See chapter 6. : Protocol integration, which shows how to publish variables and functions
See oStudio – Live Tuning<\/a> to discover the full potential of this tool.<\/li><\/ol>\n\n\n\n5. Porting file adaptation (OcfEmbeddedPort.h)<\/h2>\n\n\n\n
The OcfEmbeddedPort.h porting file is in most cases ready to use. But if necessary, you can adapt the parameters of OcfEmbedded to suit your needs.<\/p>\n\n\n\n
5.1 Choosing memory area<\/h3>\n\n\n\n
With the compilation constant OCFE_MEMORY_AREA you can choose where the OcfEmbedded protocol process data is stored.
If you leave it blank, the data is placed to the default memory area.<\/p>\n\n\n\nStandard declaration:<\/p>\n\n\n\n
- You can let the compiler choose (most common use) :
#define OCFE_MEMORY_AREA <\/pre><\/pre> <\/li>
- You can also precise it :
#define OCFE_MEMORY_AREA __xdata <\/pre><\/pre>
or<\/p>
#define OCFE_MEMORY_AREA pdata <\/pre><\/pre> <\/li><\/ul>\n\n\n\n
5.2 Features enable\/disable<\/h3>\n\n\n\n
Several features are activated by default. But they can be disabled depending on the needs or capabilities of the processor.
To disable a feature, just comment it.<\/p>\n\n\n\n-
#define OCFE_ENABLE_FLOAT <\/pre><\/pre>
\u00a0<\/p>Enable float capability for the protocol. It must be activated to publish float variables.
Saves a little code memory space when disabled.<\/p> <\/li>
-
#define OCFE_ENABLE_DOUBLE <\/pre><\/pre>
\u00a0<\/p>
Enable double capability for the protocol. It must be activated to publish double variables.
Saves a little code memory space when disabled.<\/p> <\/li> -
#define OCFE_ENABLE_STRING <\/pre><\/pre>
\u00a0<\/p>
Enable string capability for the protocol. It must be activated to publish string variables (char array).
Saves a little code memory space and a little data memory space when disabled.<\/p> <\/li> -
#define OCFE_ENABLE_FUNCTION <\/pre><\/pre>
\u00a0<\/p>
Enable function invocation for the protocol. It must be activated to publish functions.
Saves a little code memory space when disabled.<\/p> <\/li> -
#define OCFE_ENABLE_FRAME_NUMERATOR <\/pre><\/pre>
\u00a0<\/p>
Enable frame numerator security for the protocol. This activates the frame number copy for the response to the client when it is queried, and thus enhances the robustness of the protocol.
Saves a little data memory space when disabled.<\/p> <\/li> -
#define OCFE_ENABLE_CHECKSUM <\/pre><\/pre>
\u00a0<\/p>
Enable checksum control security for the protocol. This activates the checksum for the reception and the transmission of each communication, which considerably enhances the robustness of the protocol
Saves a little data memory space and significant processing time when disabled.<\/p> <\/li><\/ul>\n\n\n\n5.3 Required functions<\/h3>\n\n\n\n
Other parameters are required functions for the protocol process. Normally they are all contained in the standard libraries compilers. But if needed, you can change the functions involved and replace them with your own.<\/p>\n\n\n\n
6. Protocol integration<\/h2>\n\n\n\n
6.1 Dictionary publication<\/h3>\n\n\n\n
First you have to define the dictionary of variables and functions that you want to publish. There are six macros used to do this. Example:<\/p>\n\n\n\n
\nOCFE_BEGIN(ocfEntries)\n\tOCFE_VARIABLE(VarStruct.D, OCFE_TYPE_SHORT)\n\tOCFE_VARIABLE(VarStruct.I, OCFE_TYPE_CHAR)\n\tOCFE_VARIABLE(VarBool, OCFE_TYPE_BOOL)\n\tOCFE_VARIABLE(VarShort, OCFE_TYPE_SHORT)\n\tOCFE_VARIABLE(VarInteger, OCFE_TYPE_INT)\n\tOCFE_VARIABLE(VarFloat, OCFE_TYPE_FLOAT)\n\tOCFE_VARIABLE(VarString, OCFE_TYPE_STRING)\n\tOCFE_VARIABLE_READONLY(VarChar, OCFE_TYPE_CHAR)\n\tOCFE_VARIABLE_READONLY(VarLong, OCFE_TYPE_LONG)\n\tOCFE_FUNCTION_VOID(VarFunction)\nOCFE_END\n<\/pre><\/pre>\n\n\n\n
![\"ocfe_dictionarypublication\"](\"http:\/\/www.objectis-software.com\/support\/wp-content\/uploads\/2014\/01\/ocfe_dictionarypublication.jpg\")
<\/figure><\/div>\n\n\n\n- \n
\nOCFE_BEGIN(dictionaryName)\n<\/pre><\/pre>\n
<\/p>\n
Declaration of a dictionary with name dictionaryName. Dictionary must be declared in an area accessible by the function that will publish it.
NB. You can use a specific memory area placement with xdata, pdata, __idata etc. keywords if necessary. e.g.<\/p>\nOCFE_BEGIN(xdata ocfEntries)<\/pre><\/pre>\n<\/li>
- \n
\nOCFE_END\n<\/pre><\/pre>\n
<\/p>\n
Must be placed at the end of the dictionary declaration<\/p>\n<\/li>
- \n
\nOCFE_VARIABLE(variableName, ocfeType)\n<\/pre><\/pre>\n
<\/p>\n
Allows the publication of a variable in read\/write mode. Specify the variable name and the ocfeType (c.f. 6.1.1 Ocfe variables type).
NB. The published variable must be accessible where the dictionary is declared.<\/p>\n<\/li> - \n
\nOCFE_VARIABLE_READONLY(variableName, ocfeType)\n<\/pre><\/pre>\n
<\/p>\n
Allows the publication of a variable in read only mode. Specify the variable name and the ocfeType (c.f. 6.1.1 Ocfe variables type).
NB. The published variable must be accessible where the dictionary is declared.<\/p>\n<\/li> - \n
\nOCFE_FUNCTION_VOID(functionName)\n<\/pre><\/pre>\n
<\/p>\n
Allows the publication of a function with no return value to be invoked by a client (oStudio). Specify the function name.
NB. The published function must be accessible where the dictionary is declared.<\/p>\n<\/li> - \n
\nOCFE_FUNCTION_RET(functionName)\n<\/pre><\/pre>\n
<\/p>\n
Allows the publication of a function with a return value to be invoked by a client (oStudio). Specify the function name.
NB. The published function must be accessible where the dictionary is declared.<\/p>\n<\/li><\/ul>\n\n\n\n<\/h4>\n\n\n\n
6.1.1 Ocfe variable type<\/h4>\n\n\n\n
There are several publishable types of variable. You must precise them in the dictionary declaration.<\/p>\n\n\n\n
- \n
\nOCFE_TYPE_BOOL\n<\/pre><\/pre>\n
<\/p>\n
To publish a Boolean representation of a variable. The source variable can be a BOOL or a char variable.<\/p>\n<\/li>
- \n
\nOCFE_TYPE_CHAR\n<\/pre><\/pre>\n
<\/p>\n
To publish a char ASCII character representation of a char variable.<\/p>\n<\/li>
- \n
\nOCFE_TYPE_SHORT\n<\/pre><\/pre>\n
<\/p>\n
To publish a short variable.<\/p>\n<\/li>
- \n
\nOCFE_TYPE_INT\n<\/pre><\/pre>\n
<\/p>\n
To publish a int variable.<\/p>\n<\/li>
- \n
\nOCFE_TYPE_LONG\n<\/pre><\/pre>\n
<\/p>\n
To publish a long variable.<\/p>\n<\/li>
- \n
\nOCFE_TYPE_FLOAT\n<\/pre><\/pre>\n
<\/p>\n
To publish a float variable.<\/p>\n<\/li>
- \n
\nOCFE_TYPE_DOUBLE\n<\/pre><\/pre>\n
<\/p>\n
To publish a double variable.<\/p>\n<\/li>
- \n
\nOCFE_TYPE_STRING\n<\/pre><\/pre>\n
<\/p>\n
To publish ASCII string representation of a char array variable.<\/p>\n<\/li><\/ul>\n\n\n\n
6.1.2 Example of declaration<\/h4>\n\n\n\n
\/\/Variables declaration :<\/p>\n\n\n\n
\nBOOL Light = TRUE;\ndouble MainVelocity = 2.12;\nlong HoursUsed = 23;\nchar Type[] = "Robot X22";\nchar RobotVersion[] = "V4.15";\nstruct\n{\n\tstruct\n\t{\n\t\tint X;\n\t\tdouble Y;\n\t\tlong Z;\n\t} AxisA;\n\tstruct\n\t{\n\t\tint X;\n\t\tdouble Y;\n\t\tlong Z;\n\t} AxisB;\n\tint Rotate;\n} Robot;\n\nvoid PowerEnable()\n{\n\tprintf("Power enabled\\n");\n}\n\nchar* FunctionWithReturn()\n{\n\tprintf("Function ret called correctly\\n");\n\treturn "Function ret called correctly";\n}\n\n<\/pre><\/pre>\n\n\n\n\/\/ Dictionary declaration:<\/p>\n\n\n\n
\nOCFE_BEGIN(ocfEntries)\n\tOCFE_VARIABLE(Light, OCFE_TYPE_BOOL)\n\tOCFE_VARIABLE(MainVelocity, OCFE_TYPE_DOUBLE)\n\tOCFE_VARIABLE(HoursUsed, OCFE_TYPE_INT)\n\tOCFE_VARIABLE_READONLY(Type, OCFE_TYPE_STRING)\n\tOCFE_VARIABLE_READONLY(RobotVersion, OCFE_TYPE_STRING)\n\tOCFE_VARIABLE(Robot.AxisA.X, OCFE_TYPE_INT)\n\tOCFE_VARIABLE(Robot.AxisA.Y, OCFE_TYPE_DOUBLE)\n\tOCFE_VARIABLE(Robot.AxisA.Z, OCFE_TYPE_LONG)\n\tOCFE_VARIABLE_READONLY(Robot.AxisB.X, OCFE_TYPE_INT)\n\tOCFE_VARIABLE(Robot.AxisB.Y, OCFE_TYPE_DOUBLE)\n\tOCFE_VARIABLE(Robot.AxisB.Z, OCFE_TYPE_LONG)\n\tOCFE_VARIABLE(Robot.Rotate, OCFE_TYPE_INT)\n\tOCFE_FUNCTION_VOID(PowerEnable)\n\tOCFE_FUNCTION_RET(FunctionWithReturn)\nOCFE_END\n<\/pre><\/pre>\n\n\n\n
7. Server protocol<\/h2>\n\n\n\n
7.1 Server C++<\/h3>\n\n\n\n
7.1.1 Serial server<\/h4>\n\n\n\n
There are two functions and one variable used for serial communication<\/p>\n\n\n\n
- \n
- \n
\nOcfeStreamContext\n<\/pre><\/pre>\n
<\/p>\n<\/dt>\n
- Is the type that must be used to declare the context variable for serial communication.<\/dd>\n
- \n
\nOcfeUInt16 OcfeCharacterReceived(\n OcfeVariableEntry* ocfeDictionnary,\n OcfeStreamContext *context,\n char c);\n<\/pre><\/pre>\n
<\/p>\n<\/dt>\n
- When you receive a character by a serial connection, you must pass it to the Ocfe protocol with this function.\n
<\/p>\n
Parameters<\/h5>\n
OcfeVariableEntry* ocfeDictionnar<\/pre><\/pre>\n
Is the pointer to the dictionary used.<\/p>\n
OcfeStreamContext *context<\/pre><\/pre>\n
Is the pointer to the StreamContext variable used.<\/p>\n
char* c<\/pre><\/pre>\n
Is the received character.<\/p>\n
Returns<\/h5>\n
A short representation of the amount of characters that are ready to be sent. You can use this value to know if the system is ready to send a response.<\/p>\n<\/dd>\n
- \n
\nOcfeUInt16 OcfeCharacterToSend(OcfeStreamContext *context, char* c);\n<\/pre><\/pre>\n
<\/p>\n<\/dt>\n
- \n
Parameters<\/h5>\n
This function is used to get the next Ocfe character to send.<\/p>\n
OcfeStreamContext *context<\/pre><\/pre>\n
Is the pointer to the current stream context.<\/p>\n
char* c<\/pre><\/pre>\n
Is the received character.<\/p>\n
Returns<\/h5>\n
A short representation of the amount of characters that are ready to be sent.<\/p>\n<\/dd>\n<\/dl>\n\n\n\n
7.1.2 Polling Example<\/h4>\n\n\n\n
This is an example in polling mode. Simply check the new received character from a serial connection and send it to the Ocf Embedded process.
When a character is ready to be sent by the Ocf Embedded process, it will be sent.<\/p>\n\n\n\n\nOcfeStreamContext streamContext;\nchar c;\n\n\/\/Main loop\nvoid ReadSendOcfeCycle()\n{\n\tif(ReadChar(&amp;c)) \/\/Read serial character received\n\t\t\/\/Transmit character in ocfe processing\n\t\tOcfeCharacterReceived(ocfEntries, &amp;streamContext, c);\n\n\t\/\/Get character to send in ocfe processed buffer\n\tif(OcfeCharacterToSend(&amp;streamContext, &amp;c))\n\t\tWriteChar(c); \/\/Write next character on serial com\n\n}\n\nwhile(1)\n{\n\tApplicationCycle(); \/\/Main application process\n\tReadSendOcfeCycle(); \/\/Ocfe protocol process (non blocking)\n}\n\n<\/pre><\/pre>\n\n\n\n7.1.3 RX only interrupt Example<\/h4>\n\n\n\n
This is an example in half interrupt mode. When a new character is received from a serial connection it is sent to the Ocf Embedded process.
When a character is ready to be sent by the Ocf Embedded process, it will be sent directly from the Rx ISR handle.<\/p>\n\n\n\n\n\/\/EUSART isr process\nvoid interrupt ISR()\n{\n\tstatic OcfeStreamContext streamContext;\n\tchar c;\n\n\tif(RXInterrupt) \/\/ Check if receive flag is set\n\t{\n\t\t\/\/Transmit character to Ocfe process\n\t\tif(OcfeCharacterReceived(ocfEntries, &amp;streamContext, ReceivedChar))\n\t\t{ \t\/\/while Ocfe is ready to send\n\t\t\t\/\/Get next character to send\n\t\t\twhile(OcfeCharacterToSend(&amp;streamContext, &amp;c)\n\t\t\t\tWriteChar(c); \/\/Send next character\n\t\t}\n\t}\n}\n<\/pre><\/pre>\n\n\n\n7.1.4 RX\/TX interrupt Example<\/h4>\n\n\n\n
This is an example in full interrupt mode. When a new character is received from a serial connection, it is sent to the Ocf Embedded process.
When a character is ready to be sent by the Ocf Embedded process, it will be sent directly from the Rx ISR handle. But only the first one will result in triggering Tx interrupts. The remaining characters will be sent by the Tx ISR handle.<\/p>\n\n\n\n\n\/\/EUSART isr process\nvoid interrupt ISR()\n{\n\tstatic OcfeStreamContext streamContext;\n\tchar c;\n\n\tif(RXInterrupt) \/\/ Check if receive flag is set\n\t{\t\/\/Transmit character to Ocfe process\n\t\tif(OcfeCharacterReceived(ocfEntries, &amp;streamContext, RCREG))\n\t\t{ \t\/\/if Ocfe is ready to send\n\t\t\t\/\/Get first character to send\n\t\t\tOcfeCharacterToSend(&amp;streamContext, &amp;c);\n\t\t\tWriteChar(c); \/\/Send first character\n\t\t\tTxInterruptEnable = 1; \/\/ Enable TX interrupt\n\t\t}\n\t}\n\tif(TXInterrupt) \/\/ Check if transmit flag is set\n\t{\n\t\t if(OcfeCharacterToSend(&amp;streamContext, &amp;c)) \/\/if Ocfe is ready to send\n\t\t\tWriteChar(c); \/\/Send next Ocfe character\n\t\t else\n\t\t\tTxInterruptEnable = 0; \/\/ Disable TX interrupt\n\t}\n}\n<\/pre><\/pre>\n\n\n\n7.1.5 UDP server<\/h4>\n\n\n\n
There is only one variable and only one function used for UDP communication.<\/p>\n\n\n\n
- \n
- \n
\nOcfePacketContext\n<\/pre><\/pre>\n
<\/p>\n<\/dt>\n
- Is the type which must be used to declare the context variable for UDP communication.\n
<\/p>\n<\/dd>\n
- \n
\nOcfeUInt16 OcfeExecute (\n\t\t\tOcfeVariableEntry* ocfeDictionnary,\n\t\t\tOcfeContext *context,\n\t\t\tOcfeUInt16 inputDataLength);\n\n\n<\/pre><\/pre>\n<\/dt>\n
- \n
Parameters<\/h5>\n
When you receive a packet from a UDP connection, you must pass it to the Ocfe protocol with this function.<\/p>\n
OcfeVariableEntry* ocfeDictionnary<\/pre><\/pre>\n
Is the pointer to the used dictionary.<\/p>\n
OcfeContext *context<\/pre><\/pre>\n
Is the pointer to the used PacketContext variable.<\/p>\n
OcfeUInt16 inputDataLength<\/pre><\/pre>\n
Is the received characters count.<\/p>\n
Returns<\/h5>\n
A short representation of the number of character that are ready to be sent.<\/p>\n<\/dd>\n<\/dl>\n\n\n\n
7.1.6 Example<\/h4>\n\n\n\n
This is an example in polling mode. Simply check the new received packets from the UDP connection and send it to the Ocf Embedded process.
You have to directly use the buffer of packetContext (packetContext.Buffer) and fill it with the new packet received from the UDP connection.
When a response packet is ready to be sent by the Ocf Embedded process, it will be sent.<\/p>\n\n\n\n\nint count;\nOcfePacketContext packetContext;\n\nOpenUdp();\n\nwhile(1)\n{\n\t\/\/Read udp message received\n\tcount = ReadUdp(&amp;udpSocket, packetContext.Buffer, sizeof(OcfeBuffer))\n\t\/\/Process message\n\tcount = OcfeExecute(ocfEntries, &amp;packetContext, count);\n\t\/\/Send udp response\n\tsendUdp(&amp;packetSocket, packetContext.Buffer, count);\n}\n\nCloseSocket(&amp;udpSocket);\n<\/pre><\/pre>\n\n\n\n7.2 Server C#<\/h3>\n\n\n\n
7.2.1 Create a server in .NET application<\/h4>\n\n\n\n
->TCP connexion also available<\/p>\n\n\n\n
\nPrototype :\npublic static OcfApiServer CreateOcfNativeUdpServer(\n\tInt32 port, object targetObject,\n\tInvocationAccess access = InvocationAccess.Public);\n\nSample :\nOcfApi.CreateOcfNativeUdpServer(10000, root, out server);\n<\/pre><\/pre>\n\n\n\n
7.2.2 Create a secure native server for .NET application (communication with AES encryption)<\/h4>\n\n\n\n
-> TCP connexion also available<\/p>\n\n\n\n
\nPrototype :\npublic static OcfApiServer CreateOcfNativeUdpEncryptedServer(\n Int32 port, string passphrase, object targetObject, InvocationAccess access = InvocationAccess.Public);\n<\/pre><\/pre>\n\n\n\n
7.2.2 Execute the Ocf server (call cyclically)<\/h4>\n\n\n\n
\nPrototype :\npublic static void ExecuteOcfServer(OcfApiServer server, TimeSpan timeout = TimeSpan.FromMilliseconds(1))\n\nSample :\nfor (;;)\n OcfApi.ExecuteOcfServer(server);\n<\/pre><\/pre>\n\n\n\n
Share this...<\/span>![\"Share](\"https:\/\/www.objectis-software.com\/support\/wp-content\/plugins\/simple-share-buttons-adder\/buttons\/somacro\/facebook.png\" "\\"facebook\\"")
Facebook<\/div><\/a>![\"Share](\"https:\/\/www.objectis-software.com\/support\/wp-content\/plugins\/simple-share-buttons-adder\/buttons\/somacro\/pinterest.png\" "\\"pinterest\\"")
Pinterest<\/div><\/a>![\"Share](\"https:\/\/www.objectis-software.com\/support\/wp-content\/plugins\/simple-share-buttons-adder\/buttons\/somacro\/twitter.png\" "\\"twitter\\"")
Twitter<\/div><\/a>![\"Share](\"https:\/\/www.objectis-software.com\/support\/wp-content\/plugins\/simple-share-buttons-adder\/buttons\/somacro\/linkedin.png\" "\\"linkedin\\"")
Linkedin<\/div><\/a><\/div><\/div><\/p>\n","protected":false},"excerpt":{"rendered":"Welcome on the Ocf Server (Ocf Embedded + OcfApiServer)’s User Guide. This post will help you to get started Ocf Server, from the installation to use instructions. You can also get the PDF here. Here is the contents: Introduction Principles Package files Structure Descriptions Porting procedure Porting file adaptation (OcfEmbeddedPort.h) Choosing memory area Features enable\/disable Required functions Protocol integration Dictionary publication Server protocol Server C++ Serial server Dictionary publication Polling Example RX only interrupt Example RX\/TX interrupt Example UDP server Example Server C# Create a server in .NET application Create a secure native server for .NET application (communication with AES Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[40],"tags":[21,52,23,42,47,36],"_links":{"self":[{"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/posts\/1522"}],"collection":[{"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/comments?post=1522"}],"version-history":[{"count":108,"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/posts\/1522\/revisions"}],"predecessor-version":[{"id":2085,"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/posts\/1522\/revisions\/2085"}],"wp:attachment":[{"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/media?parent=1522"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/categories?post=1522"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.objectis-software.com\/support\/wp-json\/wp\/v2\/tags?post=1522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- \n
- \n
- \n
- \n
-
- You can let the compiler choose (most common use) :
- Make the protocol compile using the OcfEmbeddedPort file to adjust target specification (optional).
- Server C#\n
- Server C++\n