Skip to main content
The SDK can also configure the peripheral to remain idle, meaning the transaction process would begin from the peripheral’s end by sending the “Vend Request” with the relevant product (instead of having the peripheral enable the device’s reader upon a product selection, then having the device respond with “Begin Session” to the consumer’s card presentation and only then have the peripheral send the “Vend Request”). This page will guide you on implementing an always idle state in C SDK in more detail. To better explain this process, the code implementation is divided into the following steps:
  1. Include Libraries
  2. Set Up Macro and Global Variables
  3. Set Up Private Functions
  4. Add Initialization Functions
  5. Implement the Main Function
See the sections below for more details on each step.

Step 1: Include Libraries

Start by including the necessary libraries for the SDK. See the code block below:
C

Step 2: Setup Macro and Global Variables

The code below defines a macro for the module name used in logging/debugging and sets up the global variables that store configuration and session-related data.
C
Where:
  • config: Stores vending machine configuration.
  • session_product: Represents a single vending item.
  • session: Stores the session details.
  • menu: Stores menu-related settings.
  • com_id: Represents a communication ID.

Step 3: Set Up Private Functions

Implement helper functions for debugging, handling events, and processing transactions. The following sections provide more details.

Debug Output Function

This function determines the output stream for debug information, supporting different platforms:
  • Linux/X8: Uses printf().
  • STM32 microcontroller: Uses drv_usart_tx_data().
See the code below.
C
Where:
  • str: String that contains the debug information.

CPU Timer Tick

This function is called periodically (every 5-10ms) by the platform timer.
C
Where:
  • p: Pointer to optional parameter (unused in this function).
This function handles link events and logs relevant information.
C
Where:
  • event_id: Type of link event.
  • data: Pointer to optional parameter (varies based on event type).
The function will always return the boolean value __false as no success/failure is determined.

Vend Requests Handler

This function handles the session and the included items. See the code block below:
C

Vending Events Handler

This function handles vend events and logs relevant information.
C
Where:
  • event_id: Type of vend event.
  • data: Pointer to optional parameter. Varies based on event type.
This function will return a boolean value:
  • __false in most cases.
  • __true for vmc_vend_event_on_vend_approved to indicate a successful vend approval.

Step 4: Setup Initialization Functions

After adding the helper functions, you need to implement the functions to initialize the VMC configuration and the Menu Handler. See the sections below for more details.

Initialize VMC

This function initializes the VMC configuration and registers the event handlers. See the code below:
C
Since you want to leave the status in the always idle, set config.always_idle to __true.

Initialize Menu

Before initializing the menu, add the necessary handler functions. See the code below:
C
Now, you can initialize the menu, calling the handlers created before. See the code below.
C

Step 5: Implement the Main Function

Once all other parts are implemented, you can add the program’s main entry point, which initializes the link to the peripheral and the menu, then starts an infinite loop that runs the menu. See the code below:
C