Test Adapter
1. Introduction
This page describes a Test Adapter-based provisioning workflow focused on structured controller testing. It is intended for production engineers and integration teams who need repeatable test execution and clear pass/fail traces.
For approach selection and method comparison, see Provisioning overview. This page focuses only on Test Adapter method details.
2. Core reference documentation
The central reference for this method is the Test Adapter documentation PDF:
- [Test Adapter Documentation (V1.40 / V1.43.0)](./End of Line%20Test%20Adapter%20Documentation%20V1.40%20(V1.43.0).pdf)
Use this PDF as the primary reference for adapter/API behavior, test endpoints, and execution details.
Additional background context:
- [Configuration, End-of-Line Testing and Firmware Update Installation (v1.0)](./End of Line_Configuration_and_Testing_1.0.pdf)
3. Configuration with test adapter application
For partial and fully automated medium and large-scale production, a test adapter application can be transferred and started on the RAM drive of the Charge Controller via SSH/SCP.
You will receive the test adapter application by contacting your technical account manager or by email.
-
Open a terminal in the directory that contains
ta_End of Linet_stripped.Copy the stripped End of Line test app to the controllerscp -O ta_End of Linet_stripped root@192.168.123.123:/tmp/ta_End of Linet_strippedExpected output:
root@192.168.123.123's password:
ta_End of Linet_strippedThe test adapter is now placed on the Charge Controller for execution.
-
To access the test adapter via the Config UI, execute the
ta_End of Linet_strippedfile on the Charge Controller.Connect to the Charge Controllerssh root@192.168.123.123Expected prompt:
root@192.168.123.123's password:Make the file executable:
chmod +x /tmp/ta_End of Linet_strippedStart the test adapter:
/tmp/ta_End of Linet_strippedWhen started, the application stops the Controller software application.
-
Open the test adapter interface at
http://192.168.123.123:8888.Through this interface, all hardware functions of the Charge Controller can be tested together with connected peripherals.
Some settings, such as the Master/Slave configuration, require the Controller software to interpret the newly applied configuration and perform a reboot to activate it. As a result, two reboots are necessary to fully apply the setting after the configuration process.