pduapi_tcp.[so|dll] is a D-PUD API interface for communication with any PduApi Server like | Name | Description | +------------------------------------------------—|----------------------------------—| | pduapi_tcp_server_dll | Bridge to any D-PDU-API - DLL | | pduapi_vci_tcp | D-PDU-API Implementation from here | | pduapi_ota_switch | Diagnostics Over The Air - Switch |
Arguments for PDUConstruct(CHAR8* OptionStr, void *pAPITag)
Following key=value paris are accepted:
- pduapi_log_file={file}
- pduapi_log_level={fatal|error|warning|info|trace}
- pduapi_forward=key=value
- pduapi_tcp=host:port
- pduapi_terminate_on_destruct=1 : This value is forwared to the TCP-Server-Process and will NOT terminate this process.
- logging_syslog=0|1 : Log to syslog on linux
- pduapi_iso_version : compatibility modus: 2017, 2022, DTS_9. Current default: 2017
- pduapi_fwd_event=0|1 : by serialistation forward events with callback activation in stream Default: 1. Disable for debugging reasons.
Every heyvalue can also be set by environment variables. OptionStr overwrites the environment variable setting.
Example:
- PDUConstruct( "localhost:4711", NULL);
- PDUConstruct( "127.0.0.1:4711", NULL);
- PDUConstruct( "127.0.0.1:4711 pduapi_log_file=/tmp/mylog.txt", NULL);
- export pduapi_-# Environment variable "". Example:
- pduapi_tcp=localhost:4711
- pduapi_tcp=127.0.0.1:4711
- set the env-variable in our ystem environment ( Windows, Linux)
- call the process using the DLL like
Linux-$>pduapi_tcp=localhost:4711 /path/to/exe
Please have a look at the use Case: usecase_remote_vci.