Vendor Dependent Mode VDM

Vendor dependent mode: switches the machine between customer and maintenance operation.

This specification describes the functionality of the services provided by the Vendor Dependent Mode (VDM) Service Provider under XFS, by defining the service-specific commands that can be issued, using the WFSGetInfo, WFSAsyncGetInfo, …

The opening of the first descriptive chapter of the 3.50 document, CWA 16926-11.

2.00First editionin every edition since

3QueriesWFS_INF_VDM_… in 3.50

5CommandsWFS_CMD_VDM_… in 3.50

5Eventsreported by the device in 3.50

Across the editions

Each edition of XFS 3.x has one part per device class. The table lists the editions that have a part for Vendor Dependent Mode and, for each, how many queries, commands and events the part defines. A dash means the edition has no part for this class.

Source: the message tables of each edition's document. Queries are the WFS_INF_ messages, commands the WFS_CMD_ messages, events the service, execute, user and system events.
Edition	CWA	Date	Queries	Commands	Events
2.00	CWA 13449	December 1998	2	4	4
3.00	CWA 14050	November 2000	2	4	4
3.10	CWA 15748	July 2008	3	5	5
3.20	CWA 16374	December 2011	3	5	5
3.30	CWA 16926	August 2015	3	5	5
3.40	CWA 16926	February 2020	3	5	5
3.50	CWA 16926	December 2022	3	5	5

The class-by-edition matrix shows every class side by side.

The 3.50 document

The part is published as CWA 16926-11. Like every XFS 3.x part it opens with chapters that describe the device and how an application uses it, then lists each query, command and event with its data, and closes with background chapters and the C header.

Before the messages

European Foreword p. 3
1 Introduction p. 7
2 Vendor Dependent Mode p. 9
3 References p. 16

The messages

3 queries, 5 commands and 5 events, 13 messages in all, each with its input and output data and its error codes.

Chapter numbers and page numbers are those of the document. CEN publishes the documents free of charge; see Sources.

How to read the numbers

In XFS 3.x an application asks a device about itself with a query (WFS_INF_… – status, capabilities, the forms a printer knows), makes it do something with a command (WFS_CMD_… – print, dispense, read a card), and learns about things that happen on their own from an event (a card taken, a door opened, a threshold reached). The counts above are taken from each document's message tables, so they show how the class grew from edition to edition. A count that does not change does not mean the messages did not: fields are added and meanings refined within a message, and that is not counted here.

Next: The device classes