J1939 References...
1 2 3 4 5 6
The MilCAN set of profiles
for military vehicles
MilCAN is the name given to a set of open standard interfaces, based on
CAN. It will facilitate the interconnection of subsystems within
military vehicles. MilCAN protocols are derived from the CUP protocol
developed by the German Bundeswehr, SAE J1939, and CANopen. Two variants
are defined: MilCAN A and MilCAN B. MilCAN A is based on the 29-bit CAN
identifier and has many similarities with SAE J1939, the major
difference being that MilCAN A has provision for deterministic data
transfer and can accommodate both synchronous and asynchronous data.
MilCAN B, on the other hand, is based on the 11-bit CAN identifier and
has the ability to make use of devices that have been designed for
CANopen.
MilCAN (Wikipedia)
MilCAN is a deterministic protocol that can be applied to Controller
Area Network (CAN) technology as specified by ISO 11898. MilCAN has been
defined by a group of interested companies and government bodies
associated with the specification, manufacture and test of military
vehicles. The MilCAN working group was formed in 1999 as a sub-group of
the International High Speed Data Bus - Users Group (IHSDB-UG) when a
need was recognised to standardise the implementation of CANbus within
the military vehicles community. The mission statement of this group was
“To develop, for various application classes in all military vehicles, a
common interface implementation specification based on CANbus”. Meetings
are held approximately every six months, hosted by one of the group
members. Although initially developed for the military land systems
domain, MilCAN may be applied wherever there is a requirement for
deterministic data transfer.
What is MilCAN?
MilCAN is a
deterministic protocol that can be applied to Controller Area Network
(CAN) technology as specified by ISO 11898. Although initially developed
for the Military Land Systems domain, MilCAN may be applied wherever
there is a requirement for deterministic data transfer.
Research into the
Extensions required to the MilCAN protocol for its use in Safety
Critical Systems
MilCAN is the name given to an
open standard interface, based on CANbus technology that facilitates the
interconnection of subsystems within military vehicles. CANBus has
emerged as the de-facto databus standard for use in low-cost,
low-data-rate applications. MilCAN defines two variants MilCAN A and
MilCAN B. MilCAN A is based on 29 bit Identifiers and has many
similarities with SAE J1939, the major difference is that MilCAN A has
allows for deterministic data transfer and can accommodate both
synchronous and asynchronous data. MilCAN B is based on 11 bit
identifiers and has the ability to make use of devices that have been
designed for CANopen. MilCAN B specifically excludes the use of
asynchronous data.
MilCAN Certification
The integration of the MilCAN protocol in
military vehicles by numerous companies and consortiums has had as a
result the increase of MilCAN-based devices both as COTS and customised
systems. The choice of MilCAN for sub-systems integration in FRES TDPs
has also spawned more development on MilCAN enabled systems and
networks. With MilCAN being primarily a software component its
implementation is proprietary to the developer with each party operating
their own MilCAN stack in their systems. The MilCAN Working Group (MWG)
has appointed six members to form a Conformance sub-group and draft the
requirements for compliance testing of MilCAN. The Conformance sub-group
is composed by Thales Optronics, GD (UK), Ultra Electronics, Accutest,
QinetiQ, and the Vetronics Research Centre (VRC).
ISO 11783: AN ELECTRONIC COMMUNICATIONS PROTOCOL
FOR AGRICULTURAL EQUIPMENT
During the past decade, manufacturers of agricultural
equipment have increasingly turned to electronics to provide products
with improved functionality, productivity, and performance to customers.
Electronic content in agricultural equipment has increased. A natural
consequence of adding electronic components to agricultural equipment
has been realization of the advantages of allowing the components to
communicate. A hitch controller on a tractor, for example, may
communicate with a transmission and engine c o n t roller to allow
optimized performance. Electronic communications can be used to
coordinate machine components, allow information to be shared among
components of a machine, and allow control systems to be distributed
across components of a machine. The cost of adding communications is a
small part of the cost of standalone electronics, but may add
significantly to the functionality, productivity, and performance of the
machine.
