Post by remmie » Jul 18 4:26pm
0x
In the early stages of the startup period, referred to as "walk-in," the Eltek rectifier transmits a specific message every ten seconds when it is not logged in. This involves an identifier and the serial number followed by 00 00. Users can choose a walk-in duration of either 5 or 60 seconds; I personally opted for 60 seconds, which aids in preventing sudden current spikes when initiating a charge.
For my specific rectifier (serial number) it appears as follows:
0x 0x14 0x14 0x71 0x11 0x08 0x20 0x00 0x00 (all HEX numbers).
Responding once with the message 0x 0x14 0x14 0x71 0x11 0x08 0x20 0x00 0x00 (your serial number and appended with 00) leads to receiving a total of 64 status messages every 0.2 seconds, until the system reverts to the interval of every ten seconds without further status messages. For consistent message relay, respond to the command at least every ten seconds to maintain the rectifier in a logged-in status.
The block of status data is as follows (as previously noted):
0x AA BB CC DD EE FF GG HH
where:
AA represents the intake temperature in Celsius,
BB shows the output current Low Byte,
CC is the output current High Byte (the total current in deci amps is calculated as * 0.1 Amp),
DD displays the output voltage Low Byte,
EE serves as the output voltage High Byte (voltage in centivolts is calculated as * 0.01 Volt),
FF signifies the input voltage Low Byte,
GG indicates the input voltage High Byte (the AC input voltage is reflected in volts),
HH is the output temperature in Celsius.
Once the walk-in period concludes, the status messages will change as follows:
0x AA BB CC DD EE FF GG HH for normal (Constant voltage) mode,
0x AA BB CC DD EE FF GG HH for Constant Current mode (current-limiting),
0xC AA BB CC DD EE FF GG HH indicating low input voltage while the mains are disconnected.
Each tenth message differs and contains:
0xNNPP 1B JJ KK LL MM NN PP 00,
NN and PP are derived from the last two bytes of the serial number. Understanding this has posed a problem during diagnostics; discrepancies arose in code for different units.
It leads me to believe this signals a request from the rectifier to remain "logged in."
In essence,
when the identifier begins with 0x, respond with the serial number embedded within the message (notably in 0x, the serial number takes the first six bytes and with 0xNNPP, it moves to occupy the second to seventh bytes).
Similarly, when the identifier begins with 0x, it conveys a status message.
Consistently maintaining this communication is integral for actively receiving status updates from the device, while also allowing command instructions.
The recognition of messages like 0x or 0xNNPP permits alterations to voltage and maximum current configuration,
so long as the rectifier is kept logged in, allowing one to send the message: 0x05FF AA BB CC DD EE FF GG HH.
Within this:
AA is the maximum current in Low Byte,
BB is the maximum current in High Byte,
CC and DD correspond to the measured voltage Low and High Byte respectively,
EE along with FF represent the desired voltage Low and High Bytes respectively,
GG and HH are for over-voltage protection Low and High Byte respectively.
As an example:
Sending 0x05FF 0x64 0x00 0x44 0x16 0x44 0x16 0x3E 0x17 will set the maximum current to 10.0 amps and change the voltage output to 57.0 Volts.
In theory, the rectifier retains this setting as long as it's logged in. Thus, the login command should ideally be sent only once, providing consistent power until logged out.
If a disconnection occurs, the rectifier will automatically revert to its original (default) settings for both voltage and maximum current.
To those interested in Open Source development, I have integrated an advanced Arduino code facilitating automatic serial detection and status message decoding. It operates an LCD enabling message display (2x16 characters) and features a push-button for adjusting maximum current output.
Happy tinkering to all!
Are you interested in learning more about emerson vertiv? Contact us today to secure an expert consultation!
All Comments ( 0 )