Recent changes to Home

Home modified by celberfeld

celberfeld — Mon, 11 Sep 2023 11:34:10 -0000

--- v34
+++ v35
@@ -3,7 +3,7 @@

 # Examples for Net Base Services library
-All examples work with or without tls communication. If tls connection is required, the addon 'CODESYS Security Agend' is mandatory to create certificates. To open the securty agend click at the bottom right on the securty agend symbol:[[img src=SecurtyAgent.png width=15%]]
+All examples work with or without tls communication. If tls connection is required, the addon 'CODESYS Security Agent' is mandatory to create certificates. To open the security agent click at the bottom right on the security agent symbol:[[img src=SecurtyAgent.png width=15%]]
 Select Devices -> there you can create a new certificate for NBSServer and also for Client, if NBSServer or NBSClient information is not available, a download in advance is required.

Home modified by fschneider

fschneider — Tue, 05 Sep 2023 13:18:14 -0000

--- v33
+++ v34
@@ -12,6 +12,7 @@
 ## Example for TCP Server <-> TCP Client
 The project contains two devices, a CODESYS Control Win V3 and a CODESYS Control Win V3 x64, each with one application in it to simulate a Server - Client relationship. Set up in Client -> CLIENT_PRG the client common name and the appropriate ip address, as well as for Server -> SERVER_PRG. If tls communication is not necessary the variable myTLSContext can be removed (SERVER_PRG and CLIENT_PRG). Server application (myServer) should be enabled first.

+ [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/DemoClientServerOptionProvider/DemoClientServerOptionProvider.project label=project]]
 ## Example for how to use IOptionProvider
 The project is based on TCP Server <-> TCP Client Example, but in client application there is an instance of ClientOptions(FB). This function block (is part of POU part) includes three options which are set during opening the socket. In declaration part of CLIENT_PRG the options are set with method SetOptionProvider().
 In server application there is no option set for TCP_Server (default value is used), but it can be done the same way. If udp communication is used, than the options can be set in udp peer, also with the same method SetOptionProvider().

Home modified by fschneider

fschneider — Tue, 05 Sep 2023 13:11:22 -0000

--- v32
+++ v33
@@ -11,12 +11,12 @@

 ## Example for TCP Server <-> TCP Client
 The project contains two devices, a CODESYS Control Win V3 and a CODESYS Control Win V3 x64, each with one application in it to simulate a Server - Client relationship. Set up in Client -> CLIENT_PRG the client common name and the appropriate ip address, as well as for Server -> SERVER_PRG. If tls communication is not necessary the variable myTLSContext can be removed (SERVER_PRG and CLIENT_PRG). Server application (myServer) should be enabled first.
-
-  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/TCP_Reader_TCP_Processor_TCP_Writer/TCP_Reader_TCP_Processor_TCP_Writer_Example.project label=project]]

 ## Example for how to use IOptionProvider
 The project is based on TCP Server <-> TCP Client Example, but in client application there is an instance of ClientOptions(FB). This function block (is part of POU part) includes three options which are set during opening the socket. In declaration part of CLIENT_PRG the options are set with method SetOptionProvider().
 In server application there is no option set for TCP_Server (default value is used), but it can be done the same way. If udp communication is used, than the options can be set in udp peer, also with the same method SetOptionProvider().
+
+  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/TCP_Reader_TCP_Processor_TCP_Writer/TCP_Reader_TCP_Processor_TCP_Writer_Example.project label=project]]

 ## Example for TCP Reader <-> TCP Processor <-> TCP Writer
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a TCP Server - TCP Client relationship. The server only returns the values which where send from the client. The client inclues an example where asynchronious read, process and write can be done via the function blocks NBS.TCP_Reader, NBS.TCP_Processor and NBS.TCP_Writer. The NBS.TCP_Processor is overwritten in this example to implement the ProcessStream method. Also this example shows a possibility to read, manipulate and write synchroniously via direct TCP_Client methods Read() and Write(), if xAsync is FALSE.

Home modified by fschneider

fschneider — Tue, 05 Sep 2023 13:10:23 -0000

--- v31
+++ v32
@@ -13,6 +13,10 @@
 The project contains two devices, a CODESYS Control Win V3 and a CODESYS Control Win V3 x64, each with one application in it to simulate a Server - Client relationship. Set up in Client -> CLIENT_PRG the client common name and the appropriate ip address, as well as for Server -> SERVER_PRG. If tls communication is not necessary the variable myTLSContext can be removed (SERVER_PRG and CLIENT_PRG). Server application (myServer) should be enabled first.

   [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/TCP_Reader_TCP_Processor_TCP_Writer/TCP_Reader_TCP_Processor_TCP_Writer_Example.project label=project]]
+  
+## Example for how to use IOptionProvider
+The project is based on TCP Server <-> TCP Client Example, but in client application there is an instance of ClientOptions(FB). This function block (is part of POU part) includes three options which are set during opening the socket. In declaration part of CLIENT_PRG the options are set with method SetOptionProvider().
+In server application there is no option set for TCP_Server (default value is used), but it can be done the same way. If udp communication is used, than the options can be set in udp peer, also with the same method SetOptionProvider().

 ## Example for TCP Reader <-> TCP Processor <-> TCP Writer
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a TCP Server - TCP Client relationship. The server only returns the values which where send from the client. The client inclues an example where asynchronious read, process and write can be done via the function blocks NBS.TCP_Reader, NBS.TCP_Processor and NBS.TCP_Writer. The NBS.TCP_Processor is overwritten in this example to implement the ProcessStream method. Also this example shows a possibility to read, manipulate and write synchroniously via direct TCP_Client methods Read() and Write(), if xAsync is FALSE.

Home modified by fschneider

fschneider — Wed, 05 Apr 2023 07:08:26 -0000

Home modified by fschneider

fschneider — Wed, 05 Apr 2023 07:08:25 -0000

--- v29
+++ v30
@@ -21,7 +21,7 @@
   [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Peer_IPeer_Receive_Send/UDP_Receive_Send_Example.project label=project]]

 ## Example for UDP Receive <-> UDP Send
-The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a sychronious UDP Producer - UDP Consumer relationship. The producer application just returns the data which was received before, therefore the interface method of IPeer Receive() and Send() are used. Initially the producer creates a string and this sting is send to costumer. The costumer device also includes a peer and here the data is received via direkt method call of peer Receive2() (its similar to Recieve() but has one more output "eTransmission" to show if frame is e.g. unicast. Between receive and send a method ChangeStringValue is called to change the payload of the communication. Because its UDP its recommended to first enable Consumer and then Producer.
+The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a sychronious UDP Producer - UDP Consumer relationship. The producer application just returns the data which was received before, therefore the interface method of IPeer Receive() and Send() are used. Initially the producer creates a string and this sting is send to costumer. The consumer device also includes a peer and here the data is received via direkt method call of peer Receive2() (its similar to Recieve() but has one more output "eTransmission" to show if frame is e.g. unicast. Between receive and send a method ChangeStringValue is called to change the payload of the communication. Because its UDP its recommended to first enable Consumer and then Producer.

   [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Receive_UDP_Processor_UDP_Sender/UDP_Processor_Example.project label=project]]

Home modified by fschneider

fschneider — Mon, 03 Apr 2023 11:07:05 -0000

--- v28
+++ v29
@@ -18,7 +18,7 @@
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a TCP Server - TCP Client relationship. The server only returns the values which where send from the client. The client inclues an example where asynchronious read, process and write can be done via the function blocks NBS.TCP_Reader, NBS.TCP_Processor and NBS.TCP_Writer. The NBS.TCP_Processor is overwritten in this example to implement the ProcessStream method. Also this example shows a possibility to read, manipulate and write synchroniously via direct TCP_Client methods Read() and Write(), if xAsync is FALSE.
 Be aware that for this Server - Client relationship a TLS context is used, so its mandatory to import in the client the server certificate and vice versa. For unencrypted communication the NBS.TLSContext can be deleted.

-  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Peer_IPeer_Receive_Send/CheckUDPProcessor.project label=project]]
+  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Peer_IPeer_Receive_Send/UDP_Receive_Send_Example.project label=project]]

 ## Example for UDP Receive <-> UDP Send
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a sychronious UDP Producer - UDP Consumer relationship. The producer application just returns the data which was received before, therefore the interface method of IPeer Receive() and Send() are used. Initially the producer creates a string and this sting is send to costumer. The costumer device also includes a peer and here the data is received via direkt method call of peer Receive2() (its similar to Recieve() but has one more output "eTransmission" to show if frame is e.g. unicast. Between receive and send a method ChangeStringValue is called to change the payload of the communication. Because its UDP its recommended to first enable Consumer and then Producer.

Home modified by fschneider

fschneider — Mon, 03 Apr 2023 10:57:05 -0000

--- v27
+++ v28
@@ -18,9 +18,9 @@
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a TCP Server - TCP Client relationship. The server only returns the values which where send from the client. The client inclues an example where asynchronious read, process and write can be done via the function blocks NBS.TCP_Reader, NBS.TCP_Processor and NBS.TCP_Writer. The NBS.TCP_Processor is overwritten in this example to implement the ProcessStream method. Also this example shows a possibility to read, manipulate and write synchroniously via direct TCP_Client methods Read() and Write(), if xAsync is FALSE.
 Be aware that for this Server - Client relationship a TLS context is used, so its mandatory to import in the client the server certificate and vice versa. For unencrypted communication the NBS.TLSContext can be deleted.

-  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Receive_UDP_Processor_UDP_Sender/UDP_Processor_Example.project label=project]]
+  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Peer_IPeer_Receive_Send/CheckUDPProcessor.project label=project]]

-## Example for UDP Receive() and Send()
+## Example for UDP Receive <-> UDP Send
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a sychronious UDP Producer - UDP Consumer relationship. The producer application just returns the data which was received before, therefore the interface method of IPeer Receive() and Send() are used. Initially the producer creates a string and this sting is send to costumer. The costumer device also includes a peer and here the data is received via direkt method call of peer Receive2() (its similar to Recieve() but has one more output "eTransmission" to show if frame is e.g. unicast. Between receive and send a method ChangeStringValue is called to change the payload of the communication. Because its UDP its recommended to first enable Consumer and then Producer.

   [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Receive_UDP_Processor_UDP_Sender/UDP_Processor_Example.project label=project]]

Home modified by fschneider

fschneider — Mon, 03 Apr 2023 10:51:51 -0000

--- v26
+++ v27
@@ -7,23 +7,28 @@
 Select Devices -> there you can create a new certificate for NBSServer and also for Client, if NBSServer or NBSClient information is not available, a download in advance is required.

-
  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/TCP_Server_TCP_Client/TCP_Server_TCP_Client.project label=project]]

 ## Example for TCP Server <-> TCP Client
 The project contains two devices, a CODESYS Control Win V3 and a CODESYS Control Win V3 x64, each with one application in it to simulate a Server - Client relationship. Set up in Client -> CLIENT_PRG the client common name and the appropriate ip address, as well as for Server -> SERVER_PRG. If tls communication is not necessary the variable myTLSContext can be removed (SERVER_PRG and CLIENT_PRG). Server application (myServer) should be enabled first.
-
-
-  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Receive_UDP_Processor_UDP_Sender/UDP_Processor_Example.project label=project]]
- 
-## Example for UDP Processor
-The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a UDP Producer - UDP Consumer relationship. In the Conusmer application there is a UDP_Processor in it, which extends the NBS.UDP_Processor, so this function block implements the interface method ProcessPacket. In this method (which is called from interface) some data is processed.

   [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/TCP_Reader_TCP_Processor_TCP_Writer/TCP_Reader_TCP_Processor_TCP_Writer_Example.project label=project]]

 ## Example for TCP Reader <-> TCP Processor <-> TCP Writer
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a TCP Server - TCP Client relationship. The server only returns the values which where send from the client. The client inclues an example where asynchronious read, process and write can be done via the function blocks NBS.TCP_Reader, NBS.TCP_Processor and NBS.TCP_Writer. The NBS.TCP_Processor is overwritten in this example to implement the ProcessStream method. Also this example shows a possibility to read, manipulate and write synchroniously via direct TCP_Client methods Read() and Write(), if xAsync is FALSE.
 Be aware that for this Server - Client relationship a TLS context is used, so its mandatory to import in the client the server certificate and vice versa. For unencrypted communication the NBS.TLSContext can be deleted.
+
+  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Receive_UDP_Processor_UDP_Sender/UDP_Processor_Example.project label=project]]
+
+## Example for UDP Receive() and Send()
+The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a sychronious UDP Producer - UDP Consumer relationship. The producer application just returns the data which was received before, therefore the interface method of IPeer Receive() and Send() are used. Initially the producer creates a string and this sting is send to costumer. The costumer device also includes a peer and here the data is received via direkt method call of peer Receive2() (its similar to Recieve() but has one more output "eTransmission" to show if frame is e.g. unicast. Between receive and send a method ChangeStringValue is called to change the payload of the communication. Because its UDP its recommended to first enable Consumer and then Producer.
+
+  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/UDP_Receive_UDP_Processor_UDP_Sender/UDP_Processor_Example.project label=project]]
+ 
+## Example for UDP Consumer <-> UDP Processor <-> UDP Producer
+The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a UDP Producer - UDP Consumer relationship. In the Conusmer application there is a UDP_Processor in it, which extends the NBS.UDP_Processor, so this function block implements the interface method ProcessPacket. In this method (which is called from interface) some data is processed.
+
+

 ## System requirements and restrictions
 |System requirements and restrictions  | Info|

Home modified by fschneider

fschneider — Thu, 30 Mar 2023 12:01:48 -0000

--- v25
+++ v26
@@ -19,7 +19,8 @@
 ## Example for UDP Processor
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a UDP Producer - UDP Consumer relationship. In the Conusmer application there is a UDP_Processor in it, which extends the NBS.UDP_Processor, so this function block implements the interface method ProcessPacket. In this method (which is called from interface) some data is processed.

-
+  [[download url=https://forge.codesys.com/svn/prj,codesys-example,nbs,code/TCP_Reader_TCP_Processor_TCP_Writer/TCP_Reader_TCP_Processor_TCP_Writer_Example.project label=project]]
+  
 ## Example for TCP Reader <-> TCP Processor <-> TCP Writer
 The project contains two devices, two CODESYS Control Win V3 x64, each with one application in it to simulate a TCP Server - TCP Client relationship. The server only returns the values which where send from the client. The client inclues an example where asynchronious read, process and write can be done via the function blocks NBS.TCP_Reader, NBS.TCP_Processor and NBS.TCP_Writer. The NBS.TCP_Processor is overwritten in this example to implement the ProcessStream method. Also this example shows a possibility to read, manipulate and write synchroniously via direct TCP_Client methods Read() and Write(), if xAsync is FALSE.
 Be aware that for this Server - Client relationship a TLS context is used, so its mandatory to import in the client the server certificate and vice versa. For unencrypted communication the NBS.TLSContext can be deleted.