garygid
Well-known member
LLS2 is a follow-on to the original LEAF Logging System (LLS),
which was based on the AVR-CAN board and the firmware
that was used in the GID-Meter.
The Atmel software CAN library that we used there, as it turned out,
was not designed to handle fast CAN Message traffic. A Message
arriving too soon after a preceeding Message... was lost. That did not
adversely impact most loggers because they, at least in the early
days of LEAF logging, were most interested in values that were
repeated many times in the typical data stream.
Those who bought the LLS logging systems knew of this problem,
and they will be able to upgrade to the LLS2 firmware, if they desire,
by simply re-flashing the firmware in their AVR-CAN boards.
Now we have developed "advanced" CAN firmware for Logging,
allowing for capturing multiple sequential CAN Messages. It
appears that we are now able to capture them all, with the new
firmware that we are using in the LLS2.
In some cases, streaming the data out if the AVR-CAN's RS232 port
can become the bottleneck, so we have provided for twice the
original 115,200 baud rate (which seemed sufficient for the
logging done with the GID-Meter).
So, the LLS2 has new improved firmware that should capture all
of the CAN Messages, and no longer misses those CAN messages
that come "immediately" after another CAN message.
The LLS2 is still based on the AVR-CAN board, usiing one board per
logging channel. One can log up to 4 channels symultaneously, for example,
the LEAF's EV, CAR, AV, and QC (requires special QC-tap) CAN buses.
Note: The "CAN_T" solder jumper on the factory-shipped AVR-CAN
board must be carefully "opened", to avoid unintended loading
of the CAN bus being monitored.
Tesla S Support:
The new firmware and new Interface Box support Logging experiments
with the Tesla S, with Power and one CAN bus from the OBD conector,
and a special Slow-CAN signal derived from the charging port's Pilot line.
A special adapter cable is needed to access and read the Pilot "CAN".
New features, each optional:
Jumper 1 slows the CAN processor to handle the Tesla S Pilot line
Jumper 2 appends a 2-byte Time-Stamp to each message
Jumper 3 runs the RS232 at 400k instead of about 115.2k baud
The LLS2 typically includes a 4-port RS232-to-USB adapter from EasySync,
and a custom Interface Box that connects to the vehicle OBD connector
(to access Power and the OBD pin pairs 1-9, 6-14, 12-13, and 3-11).
The Box can accept external Inputs on two DB9 male connectors, Inp1 and Inp2.
The Inp2 connector is prepared to accept the Tesla S Pilot-"CAN" Signal,
generated when SuperCharging or charging (with an adapter) from a QC station.
CAUTION:
There is much to be discovered, and you are totally responsible for any
use that you might make of the information in this thread, or attached,
or in a referenced document, or any other related information.
which was based on the AVR-CAN board and the firmware
that was used in the GID-Meter.
The Atmel software CAN library that we used there, as it turned out,
was not designed to handle fast CAN Message traffic. A Message
arriving too soon after a preceeding Message... was lost. That did not
adversely impact most loggers because they, at least in the early
days of LEAF logging, were most interested in values that were
repeated many times in the typical data stream.
Those who bought the LLS logging systems knew of this problem,
and they will be able to upgrade to the LLS2 firmware, if they desire,
by simply re-flashing the firmware in their AVR-CAN boards.
Now we have developed "advanced" CAN firmware for Logging,
allowing for capturing multiple sequential CAN Messages. It
appears that we are now able to capture them all, with the new
firmware that we are using in the LLS2.
In some cases, streaming the data out if the AVR-CAN's RS232 port
can become the bottleneck, so we have provided for twice the
original 115,200 baud rate (which seemed sufficient for the
logging done with the GID-Meter).
So, the LLS2 has new improved firmware that should capture all
of the CAN Messages, and no longer misses those CAN messages
that come "immediately" after another CAN message.
The LLS2 is still based on the AVR-CAN board, usiing one board per
logging channel. One can log up to 4 channels symultaneously, for example,
the LEAF's EV, CAR, AV, and QC (requires special QC-tap) CAN buses.
Note: The "CAN_T" solder jumper on the factory-shipped AVR-CAN
board must be carefully "opened", to avoid unintended loading
of the CAN bus being monitored.
Tesla S Support:
The new firmware and new Interface Box support Logging experiments
with the Tesla S, with Power and one CAN bus from the OBD conector,
and a special Slow-CAN signal derived from the charging port's Pilot line.
A special adapter cable is needed to access and read the Pilot "CAN".
New features, each optional:
Jumper 1 slows the CAN processor to handle the Tesla S Pilot line
Jumper 2 appends a 2-byte Time-Stamp to each message
Jumper 3 runs the RS232 at 400k instead of about 115.2k baud
The LLS2 typically includes a 4-port RS232-to-USB adapter from EasySync,
and a custom Interface Box that connects to the vehicle OBD connector
(to access Power and the OBD pin pairs 1-9, 6-14, 12-13, and 3-11).
The Box can accept external Inputs on two DB9 male connectors, Inp1 and Inp2.
The Inp2 connector is prepared to accept the Tesla S Pilot-"CAN" Signal,
generated when SuperCharging or charging (with an adapter) from a QC station.
CAUTION:
There is much to be discovered, and you are totally responsible for any
use that you might make of the information in this thread, or attached,
or in a referenced document, or any other related information.
