Protocols

Custom / Editing Protocols

Custom protocols can be created by naming them with name.custom. this will ensure that they do not get overwritten when updating.

for example, say that you want to modify the eg4_v58 protocol without having to worry about updates overwritting it:

copy eg4_v58.json eg4_v58.custom.json
copy eg4_v58.input_registry_map.csv eg4_v58.input_registry_map.custom.csv
copy eg4_v58.holding_registry_map.csv eg4_v58.holding_registry_map.custom.csv

in the configuration for your transport:

protocol_version = eg4_v58.custom

Protocol Configuration - CSV / JSON

{protocol_name}.json contains default settings, releated to the transport. {protocol_name}.{registry_type}_registry_map.csv contains configuration for specific registry "type". {protocol_name}.registry_map.csv contains configuration for generic "registers".