PROTOCOL

Supported by Ginmake 1.44 and later, GIN file version 3.24 or later.

[PROTOCOL, <type> {,<MAX_READ> {,<MAX_WRITE>}} ][PROTOCOL:<conn>, <type> {,<MAX_READ> {,<MAX_WRITE>}} ]
1#define MAX_READ_USB 256
2#define MAX_WRITE_USB 4
3
4// [PROTOCOL GemsExtended, 2, 2]
5// [PROTOCOL:LIBUSB, GemsExtended, MAX_READ_USB, MAX_WRITE_USB]

‘conn’ refers to the connection type to which to associate the protocol. If this field is not supplied, then the default protocol is defined. See [CONNECTION].

’type’ may be one of: Gems13bit [Existing protocol] GemsExtended [Extended address/size protocol]

‘MAX_READ’[optional]: Maximum number of data bytes that can be requested from the ECU in a single read command. Default is 2.

‘MAX_WRITE’[optional]: Maximum number of data bytes that can be written to the ECU in a single write command. Default is 2 for connection specific protocols and 1 for the default protocol (can be set directly or overridden with [WORDWRITES] which sets this to ‘2’).

See the Gemscom Protocol Specification for more details on the protocol implementations.

It is perfectly legal to specify different protocol types for different connections which aids the development process - the code in the ECU can be more gradually converted over to use newer protocols. Additionally, there may be different hardware buffering constraints for different connection types.