Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The CWL includes software simulations of the CWM and the OKC. The simulations can be used for debugging a new CWL port since they minimize the number of "moving parts" required to exercise an OKE system.

The simulations are text-based Windows programs and are run from a command prompt. cwm.exe is the simulation for the CWM, and okc.exe is the simulation for the OKC. The simulated CWM and OKC communicate to each other via inter-process communication that simulates a network connection between them. The CWM simulation opens a serial comport on the Windows PC. An OKE system can connect their controller to the Windows PC serial port and communicate to the simulated CWM. The serial communication protocol used by the CWM and OKE simulators is the same that would run on real controller hardware.

There are two typical simulation scenarios:

  1. Run the OKC and CWM simulators on a PC and connect the PC with a serial connection to a controller board.

  2. Run the OKC, CWM, and OKE simulators all on the same PC. The PC requires 2 serial ports connected with a NULL modem cable.

CWM Simulation

 Click here to expand...

The CWM simulation can be run by opening a command prompt and changing to the ./sim directory in the ConnectWare Library distribution. The cwm.exe program takes three command line arguments. The first argument is the comport, the second argument indicates if the serial connection is full or half duplex, and the last parameter is the device ID of the simulated CWM.

> cwm

Arguments: cwm COM[0-9]* (FULL|HALF) <devId>

Example  : cwm COM8 FULL 0102030405060708

For example, to run the simulated CWM:

> cwm COM20 FULL 1122334455667788

To access the command menu of the simulated CWM press <Enter>.

Send Heartbeat, 'h'

Pressing the 'h' key will cause the simulated CWM to generate and immediately send a heartbeat message to the OKC.

Sending Ping, 'i'

Pressing the 'i' key will cause the simulated CWM to generate and immediately send a ping request to the OKE.

Change Baud Rate, 'b'

Pressing the 'b' key will cause the simulated CWM to change the baud rate at which it is communicating to the OKE. By default, the CWM simulator uses a baud rate of 115200. The OKE must match the baud rate of the CWM otherwise no messages will be received by the CWM.

Pause Outbound File Transfer, 'p'

Pressing the 'p' key will cause the simulated CWM to pause or un-pause an outbound file transfer for both the simulated CWM and the OKE. Use this to test that OKE implementations process outbound file transfer pauses gracefully. An actual CWM will pause an OKE only if the outbound telemetry queue becomes too full.

Toggle Net Connection, '1'

Pressing the '1' key will cause the simulated CWM to have or not have a working network connection to the OKC. This option allows implementors to test how their controller behave when the network connection to the OKC is not working.

Toggle Net Enable, '2'

Pressing the '2' key will cause the simulated CWM to enable or disable the network connection to the OKE.

Quit, 'q'

Pressing the 'q' key will cause the simulated CWM to exit.

OKC Simulation

 Click here to expand...

The OKC simulation can be run by opening a command prompt and changing to the ./sim directory in the ConnectWare Library distribution. The okc.exe program takes two command line arguments. The first argument is the device ID of the simulated CWM and the second argument is the device ID of the OKE system.

>okc

Arguments: okc <cwmId> <okeId>

Example  : okc 1122334455667788 0102030405060708

For example, to run the simulated OKC:

>okc 1122334455667788 0102030405060708

To access the command menu of the simulated OKC press <Enter>.

Send Heartbeat , 'h', 'H'

This causes the OKC simulator to send a heartbeat request to either the OKE or CWM. When connected the command target will immediately send a heartbeat.

Send Reset, 'r', 'R'

This causes the OKC simulator to send a reset to either the OKE or CWM. When connected the command target will immediately reset.

Send Flush, 'f', 'F'

This causes the OKC simulator to send a flush to either the OKE or CWM. When connected the CWM will flush its queues, an OKE will perform an implementation specific action.

Send File Directory, 'd', 'D'

This causes the OKC simulator to send a file directory request to either the OKE or CWM. When connected the command target will immediately send a directory listing.

Send File Read, 'g', 'G'

This causes the OKC simulator to send a file read for source.bin to either the OKE or CWM. When connected the command target will immediately start writing source.bin back to the OKC which will store it as source.bin.okc.

Send File Write, 'p', 'P'

This causes the OKC simulator to send a file write of source.bin to either the OKE or CWM. When connected the command target will immediately receive the file and save it appropriately.

Send File Delete, 'x', 'X'

This causes the OKC simulator to send a file delete to either the OKE or CWM. When connected the command target will immediately delete the requested file.

Send Set Time, 't', 'T'

This causes the OKC simulator to send a set time message to either the OKE or CWM. When connected the command target will immediately set their time as requested.

Send Ping, 'i', 'I'

This causes the OKC simulator to send a ping message to either the OKE or CWM. When connected the command target will immediately send a matching ping message.

Quit, 'q'

Pressing the 'q' key will cause the simulated OKC to exit.

OKE Simulation

 Click here to expand...

The CWL contains a full OKE Windows port and simulation. Implementors may use the OKE simulation to get familiar with the CWL and to experiment with creating heartbeat messages. The Visual Studio environment may be used to step through and debug the modified OKE simulation.

Implementors may choose to modify the stock OKE simulator and create a full simulation of their specific equipment so that it is easier to test the integration with the OKC when certain states or errors conditions are time consuming or difficult to generate.

The OKE simulation requires a serial port just like the CWM simulation, therefore the Windows PC needs two physical serial ports connected with a NULL modem cable to allow communication with each other.

The OKE simulation can be run by opening a command prompt and changing to the ./sim directory in the ConnectWare Library distribution. The oke.exe program takes three command line arguments. The first argument is the comport, the second argument indicates if the serial connection is full or half duplex, and the last parameter is the device ID of the simulated OKE.

> oke

Arguments: oke COM[0-9]* (FULL|HALF) <devId>

Example  : oke COM8 FULL 0102030405060708

For example, to run the simulated OKE:

> oke COM19 FULL 0102030405060708

To access the command menu of the simulated OKE press <Enter>.

Send Heartbeat, 'h'

Pressing the 'h' key will cause the simulated OKE to generate and immediately send a heartbeat message to the OKC.

Request File, 'G'

Pressing the 'G' key will cause the simulated OKE to generate and immediately send a file read request for file.bin to the OKC. If file.bin exists in the same directory as the OKC simulator then it will write the file back to the OKE, which will save the file as file.bin.oke.

Send File, 'P'

If file.bin exists in the simulated OKE directory, pressing the 'P' key will cause the simulated OKE to start a file write of file.bin to the OKC. The OKC will save the file as file.bin.okc.

Request Scan, '1'

Pressing the '1' key will cause the simulated OKE to send a command to the CWM to start a net scan. If the CWM supports scanning it will report the results of the scan within 10s. By default, the CWM simulator reports as a WiFi network, but it can be built for MiWi mode as well.

Request Net Status, '2'

Pressing the '2' key will cause the simulated OKE to send a command to the CWM to report net status. The CWM will report status immediately. By default, the CWM simulator reports as a WiFi network, but it can be built for MiWi mode as well.

Config Custom WiFi Network, '3'

Pressing the '3' key will cause the simulated OKE to send a command to the CWM to configure a custom WiFi network. You will be prompted to enter an SSID and PSK. The OKE must subsequently request status to verify if the configuration change was accepted. By default, the CWM simulator reports as a WiFi network, but it can be built for MiWi mode as well.

Config Custom WiFi Network, '4'

Pressing the '4' key will cause the simulated OKE to send a command to the CWM to configure WiFi SAP network. The OKE must subsequently request status to verify if the configuration change was accepted. By default, the CWM simulator reports as a WiFi network, but it can be built for MiWi mode as well.

Config IP Network Settings, '5'

Pressing the '5' key will cause the simulated OKE to send a command to the CWM to configure DHCP or static IP settings by prompt. The OKE must subsequently request status to verify if the configuration change was accepted. By default, the CWM simulator reports as a WiFi network, but it can be built for MiWi mode as well.

Quit, 'q'

Pressing the 'q' key will cause the simulated OKE to exit.

Building Simulators on Windows

The simulators were built using Microsoft Visual Studio Community 2019 with the C/C++ tools. At the top level ConnectWare directory there is a solution file called ConnectWare.sln that contains projects for the three simulators.

Normally implementors will not need to rebuild the OKC or CWM simulators since precompiled versions are included in the sim directory. However, some implementors may find it useful to use and extend the OKE simulator as a way to prototype and debug parts of their application code.

To build the OKE simulator right click on the _OpenKitchenEquipment_OKE project in the Solution Explorer pane and click Set as StartUp Project. To change the default command line parameters, go to Project->Properties->Debugging and modify the Command Arguments field. On the toolbar you can launch the debugger by clicking the Local Windows Debugger option.

  • No labels