diff --git a/Changelog.txt b/Changelog.txt index 05aab72e8..196e10599 100644 --- a/Changelog.txt +++ b/Changelog.txt @@ -1,3 +1,21 @@ +commit 285a451d4bccf43c4981374238b854be9c296e10 +Author: saravanan +Date: Fri Jul 1 12:55:37 2016 +0530 + + Updated files for v3.0.0 + +commit 69530befe9ca80d8fbe609dba50fe0447563cbc4 +Author: saravanan +Date: Thu Jun 30 17:56:36 2016 +0530 + + BUSMASTER v3.0.0 changes + +commit 93f0f2805bbef626758a717ab176d47bc424bab4 +Author: Prathiba +Date: Tue Nov 17 12:07:30 2015 +0530 + + Version information updated + commit 41180fd99ae65bf8d2b683eb8095acb87c41b1f8 Author: Prathiba Date: Mon Nov 16 18:24:59 2015 +0530 diff --git a/Documents/4 Help_New/topics/stlin_struct.dita b/Documents/4 Help_New/topics/stlin_struct.dita index f8e31d2a3..5d99bec13 100644 --- a/Documents/4 Help_New/topics/stlin_struct.dita +++ b/Documents/4 Help_New/topics/stlin_struct.dita @@ -79,40 +79,6 @@

-

Input Parameters:

-

m_ucMsgTyp

-

0 - Sets message type as Header

-

1 - Sets message type as Response

-

m_ucChksumTyp

-

0 - Sets checksum type as Classic

-

1 - Sets checksum type as Enhanced

-

m_ucDataLen

-

dlc of the LIN message. Valid range of LIN data length is 0..8.

-

m_ucMsgID

-

LIN message identifier

-

m_aucData, m_auwData, m_aulData

-

Contains data bytes

-

m_sWhichBit

-

To access/update Data bytes

-

m_ulTimeStamp

-

Actual time stamp of the received message

-

m_ucChannel

-

Channel number

-

m_ucCRC

-

Checksum value of the received message

-

STLIN_Msg Example:

-

STLIN_MSG sMsg; - -sMsg.m_ucMsgTyp = 1; // Slave Response -sMsg.m_ucChksumTyp = 0; // Classic -sMsg.m_ucDataLen = 8; -sMsg.m_ucMsgID = 0x4; -sMsg.m_sWhichBit.m_aulData[0] = 10; // Lower 4 Bytes -sMsg.m_sWhichBit.m_aulData[1] = 20; // Upper 4 Bytes -sMsg.m_ucChannel = 1; - -// Send the message -SendMsg(sMsg);

Event Structure:

SEVENT_CHECKSUM_LIN Structure Definition

struct SEVENT_CHECKSUM_LIN @@ -144,31 +110,5 @@ SendMsg(sMsg);

};

Required Include header file is LINIncludes.h

-

Accessing database message signal values

-

Database message structures can be meaningfully interpreted. Database message structures will have signal members as defined in the database. Signal raw value can be directly assigned by using member of database message structure with the signal name.

-

LIN_Request is a database message that has signals Sig1, Sig2 and Sig3. Each signal is 2 bytes of length. To assign raw value of a signal use message name structure and use signal name as member.

-

// Message Declaration -LIN_Request sMsgStruct = { 1, 0, 8, 0x4, { 0, 0, 0, 0, 0, 0, 0, 0 } }; - -// Use signal member - -// Sig1 -sMsgStruct.m_sWhichBit.Sig_1 = 10; - -// Sig2 -sMsgStruct.m_sWhichBit.Sig_2 = 20; - -// Sig3 -sMsgStruct.m_sWhichBit.Sig_3 = 30; - -// Send the message now -SendMsg(*((STLIN_MSG *)&sMsg));

-

Right click on edit area of function editor. Select "Insert Message" or "Insert Signal" option to insert message structure or signal structure. Select the option "Yes, I want to declare selected message structure variable" option in the "Message and Signal List" to initialise message with its struct definition.

-

Required Include header file Unions.h

-

Note:

-

    -
  • Unions.h file will be automatically generated by BUSMASTER during database import.
    • -
  • This file will be in the database file directory
    • -

diff --git a/Sources/BUSMASTER/Application/BUSMASTER.rc b/Sources/BUSMASTER/Application/BUSMASTER.rc index f376af5fa..285ff4079 100644 --- a/Sources/BUSMASTER/Application/BUSMASTER.rc +++ b/Sources/BUSMASTER/Application/BUSMASTER.rc @@ -1780,7 +1780,7 @@ BEGIN IDS_INVALID_DB_PROMPT "Invalid database filename" ID_ACTIVE_DATABASE_NAME " " IDS_MESSAGE_NAME "Message Name" - IDS_VERSION "Ver 3.0.0Nightly158" + IDS_VERSION "Ver 3.0.0" IDS_HEADER "***NOTE: PLEASE DO NOT EDIT THIS DOCUMENT***\n\n\n***[START LOGGING SESSION]***\n" IDS_FOOTER "***[END LOGGING SESSION]***" IDS_CONNECT "&Connect\tF2"