在本文中，我们将给您介绍关于SAEJ2534Pass-ThruAPI的详细内容，此外，我们还将为您提供关于ApacheQpidJMS0.34.0，JavaMessageService客户端、bzoj2

在本文中，我们将给您介绍关于SAE J2534 Pass-Thru API的详细内容，此外，我们还将为您提供关于Apache Qpid JMS 0.34.0，Java Message Service 客户端、bzoj2253 纸箱堆叠、CentOS 安装 CDH 报缺少 cyrus-sasl-gssapi、MySQL-python、mod_ssl、openssl-devel 等包的错误、exec(),passthru()的知识。

本文目录一览：

• SAE J2534 Pass-Thru API
• Apache Qpid JMS 0.34.0，Java Message Service 客户端
• bzoj2253 纸箱堆叠
• CentOS 安装 CDH 报缺少 cyrus-sasl-gssapi、MySQL-python、mod_ssl、openssl-devel 等包的错误
• exec(),passthru()

SAE J2534 Pass-Thru API

 

 

Connects to the OBDII J1962 DLC and supports the following protocols.

1 CAN2 Single Wire
2 J1850PWM+ , J1850VPW
3 CAN2+
6 CAN+ (CAN-C only), SCI A Engine, 5v-20v out
7 ISO-9141 K-line, SCI A Engine, SCI A Trans, SCI B Engine
9 SCI B Trans, 5v-20v out or short-to-ground
10 J1850PWM-
11 CAN2- 5v-20v out
12 SCI B Engine 5v-20v out or short-to-ground
14 CAN- (CAN-C only), SCI A Trans 5v-20v out
15 ISO L Line, SCI B Trans, Short-to-ground

 

The PassThru device manufacturer supplies the hardware appliance and cable that connects to and communicates with the vehicle network.

The physical interface to the vehicle network is the SAE J1962 connector, which supports the various vehicle serial data protocols.

The following network layer protocols are supported:

ISO 9141
ISO 14230-4(KWP2000, Keyword Protocol)
SAE J1850 41.6 KBPS PWM(Pulse Width Modulation)
SAE J1850 10.4 KBPS VPW(Variable Pulse Width)
CAN(Controller Area Network, ISO 11898)
ISO 15765-4(CAN)
SAE J2610 DaimlerChrysler SCI(Serial Communications Interface)

 

J2534-1: Recommended Practice for Pass-Thru Vehicle Programming Last published version 12/2004

J2534-2: Optional Pass-Thru Features Last published version 04/2010

J2534-3: Conformance Test Cases for an SAE J2534-1 Device No published document

 

SAE J2534-1

defines an Application Program Interface (API) that can be used by Vehicle Manufacturers for reprogramming emission related modules. 
This interface also includes some capabilities that may not be required for reprogramming, 
but allows the interface to be used for other purposes without placing a significant burden on the interface manufacturers.

SAE J2534-2

defines optional features that takes advantage of the J2534-1 framework. 
It allows the interface (J2534) to be used for other purposes and includes features that are above and beyond emission related reprogramming needs. 
Many OEM’s wanted a standard for reprogramming other modules not “Emission Related”. 
Those instructions were added into -2. It also expands the scope of what a J2534 device can do. (ie: Diagnostics)

SAE J2534-3

defines a set of conformance test cases, which can be used to check an interface’s compliance with SAE J2534-1 Conformance test cases are planned for J2534-2 features 
also Some preliminary work has been done on the J2534-1 conformance test cases. 
No work has been initiated for the J2534-2 conformance test cases. 
There is no published standard yet.

J2534 framework includes application interfaces for the following functionality:

Network Initialization 
Basic Send and Receive 
Periodic Transmission Capability 
Message Filters 
Generic IO Control 
Protocol Specific IO Control 
Programming Voltage Supply 
Other Utility Functions

Protocols Supported by a fully compliant SAE J2534-1 Device

J1850 VPW (GM Class2, Chrysler OBD) 
J1850 PWM (Ford SCP) 
High Speed CAN ISO 15765-4 (Diag. On CAN) 
ISO 14230 (KWP) 
ISO 9141-2 
Chrysler SCI

Additional Protocols Currently Supported by the SAE J2534-2 Specifications

SAE J1939 
SAE J1708 
Single Wire CAN 
GM UART 
UART Echo Byte 
Ford MS-CAN
Honda Diag-H 
TP 2.0 
Fault Tolerant CAN

 

6.5.1 ISO 9141

The following specifications clarify and, if in conflict with ISO 9141, override any related specifications in ISO 9141: 

a. The maximum sink current to be supported by the interface is 100 mA. 
b. The range for all tests performed relative to ISO 7637-1 is –1.0 to +40.0 V. 
c. The default bus idle period before the interface shall transmit an address, shall be 300 ms. 
d. Support following baud rate with ±0.5% tolerance: 10400. 
e. Support following baud rate with ±1% tolerance: 10000. 
f. Support following baud rates with ±2% tolerance: 4800, 9600, 9615, 9800, 10870, 11905, 12500, 13158, 13889, 14706, 15625, and 19200. 
g. Support other baud rates if the interface is capable of supporting the requested value within ±2%. 
h. The baud rate shall be set by the application, not determined by the SAE J2534 interface. The interface is not required to support baud rate detection based on the synchronization byte. 
i. Support odd and even parity in addition to the default of no parity, with seven or eight data bits. Always one start bit and one stop bit.

j. Support for timer values that are less than or greater than those specified in ISO 9141 (see Figure 30 in Section 7.3.2). 
k. Support ability to disable automatic ISO 9141-2 / ISO 14230 checksum verification by the interface to allow vehicle manufacturer specific error detection. 
l. If the ISO 9141 checksum is verified by the interface, and the checksum is incorrect, the message will be discarded. 
m. Support both ISO 9141 5-baud initialization and ISO 14230 fast initialization. 
n. Interface shall not adjust timer parameters based on keyword values.

6.5.2 ISO 14230-4 (KWP2000)

The ISO 14230 protocol has the same specifications as the ISO 9141 protocol as outlined in the previous section. 
In addition, the following specifications clarify and, if in conflict with ISO 14230, override any related specifications in ISO 14230: 

a. The pass-thru interface will not automatically handle tester present messages. The application needs to handle tester present messages when required. 
b. The pass-thru interface will not perform any special handling for the $78 response code. 
Any message received with a $78 response code will be passed from the interface to the application. 
The application is required to handle any special timing requirements based on receipt of this response code, including stopping any periodic messages.

6.5.3 SAE J1850 41.6 KBPS PWM (PULSE WIDTH MODULATION)

The following additional features of SAE J1850 must be supported by the pass-thru device: 

a. Capable of 41.6 kbps and high speed mode of 83.3 kbps. 
b. Recommend Ford approved SAE J1850PWM (SCP) physical layer

6.5.4 SAE J1850 10.4 KBPS VPW (VARIABLE PULSE WIDTH)

The following additional features of SAE J1850 must be supported by the pass-thru device: 

a. Capable of 10.4 kbps and high speed mode of 41.6 kbps 
b. 4128 byte block transfer 
c. Return to normal speed after a break indication

6.5.5 CAN

The following features of ISO 11898 (CAN) must be supported by the pass-thru device: 

a. 125, 250, and 500 kbps 
b. 11 and 29 bit identifiers 
c. Support for 80% ± 2% and 68.5% ± 2% bit sample point 
d. Allow raw CAN messages. This protocol can be used to handle any custom CAN messaging protocol, including custom flow control mechanisms.

6.5.6 ISO 15765-4 (CAN)

The following features of ISO 15765-4 must be supported by the pass-thru device: 

a. 125, 250, and 500 kbps 
b. 11 and 29 bit identifiers 
c. Support for 80% ± 2% bit sample point 
d. To maintain acceptable programming times, the transport layer flow control function, as defined in ISO 15765-2, must be incorporated in the pass-thru device (see Appendix A). 
If the application does not use the ISO 15765-2 transport layer flow control functionality, the CAN protocol will allow for any custom transport layer. 
e. Receive a multi-frame message with an ISO15765_BS of 0 and an ISO15765_STMIN of 0, as defined in ISO 15765-2. 
f. No single frame or multi-frame messages can be received without matching a flow control filter. 
No multi-frame messages can be transmitted without matching a flow control filter. 
g. Periodic messages will not be suspended during transmission or reception of a multi-frame segmented message.

6.5.7 SAE J2610 DAIMLERCHRYSLER SCI

Reference the SAE J2610 Information Report for a description of the SCI protocol.

When in the half-duplex mode (when SCI_MODE of TxFlags is set to {1} Half-Duplex), every data byte sent is expected to be "echoed" by the controller. 
The next data byte shall not be sent until the echo byte has been received and verified. 
If the echoed byte received doesn''t match the transmitted byte, or if after a period of T1 no response was received, the transmission will be terminated. 
Matching echoed bytes will not be placed in the receive message queue.

What is an API?

An API (Application Programming Interface) is a ''rendezvous point'' between two pieces of software.

For example, any Windows application (such as MS Word and Photoshop) can print to any printer.

How is this possible? The application and the printer driver communicate via an API. Even though each printer has different hardware,

all printer drivers ''look the same'' to Windows applications.

You are free pick any printer based on your preferences (color, size, durability, cost, speed) without worrying about software incompatibilities.

In a similar vein, the J2534 API makes all "car communications" hardware look the same.

The Software

The EPA is forcing car manufacturers to release software that updates the firmware on their cars.

The application must run on Windows and use the J2534 API to talk to the car.

Anyone can buy this software, even individual car enthusiasts.

The software must be sold ''for a reasonable price'', which will probably be a few hundred dollars.

The Hardware

A J2534 device plugs into a cars'' OBD connector on one side, and a computer on the other side.

These devices are not made by car manufacturers, but by any company that sees an opportunity.

Under the hood, the device must speak a myriad of different vehicle protocols (ISO9141, J1850VPW/PWM, CAN, etc.)

used by the different manufacturers. Each protocol has different voltage and timing requirements,

so this is no trivial task. Fortunately, each device comes with a software driver that implements the J2534 API.

Since the driver invisibly handles communication to the device, application software

writers don''t have to worry about the connection details or low-level car protocols.

 

http://www.drewtech.com/support/J2534/errorcodes.html

SAE J2534-2

SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emissionrelated control modules.

However, there is a need to support vehicles prior to the 2004 model year as well as non-emission related control modules.

The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 interface.

Apache Qpid JMS 0.34.0，Java Message Service 客户端

Apache Qpid JMS 0.34.0 已发布，Qpid JMS 是一个使用 Qpid Proton 协议引擎的 Java Message Service 客户端。支持基于 Apache Qpid Proton 协议引擎的高级消息队列协议 1.0（AMQP 1.0, ISO/IEC 19464, http://www.amqp.org），并实现了 AMQP JMS 在 OASIS 的映射。

更新内容

新特性和改进

• QPIDJMS-396 - 针对线程间事件信号的性能改进

Bug 修复

• QPIDJMS-393 - async send CompletionListener not signalled when sent while TX is in doubt

• QPIDJMS-394 - 当发送阻塞等待故障转移时，CompletionListener 会发出错误信号

• QPIDJMS-395 - 即使启用了故障转移，远程连接关闭也可能导致发送异常

发布主页和下载地址

bzoj2253 纸箱堆叠

<a href="https://www.lydsy.com/JudgeOnline/problem.php?id=2253" target="blank"><font size=5>题目链接</font></a>

题意

求三元组的严格上升子序列

思路

先考虑暴力$dp$一下

for(int i = 1;i <= n;++i)
    for(int j = 1;j < i;++j)
        if(x[i] > x[j] && y[i] > y[j] && z[i] > z[j]) 
            f[i] = max(f[i],f[j] + 1)

考虑用$CDQ$分治优化这个$dp$。 大体思路是，先按照第一维排序，保证第一维是严格上升的。然后$CDQ$一下第二维。树状数组维护第三维(需要先离散化)。这里用到的是树状数组维护前缀最大值。 有两个$bug$调了很久。

bug1

直接套用了三维偏序的板子。其实这个题在$CDQ$的时候是不能像这样的

void cdq(int l,int r) {
    if(r <= l) return;
    cdq(l,mid),cdq(mid + 1,r);
    //……
}

因为在$cdq$右边之前，必须保证右边已经从左边获取过答案了。这就是求$LIS$与求三维偏序不同的地方。 正确操作应该是

void cdq(int l,int r){
    if(r <= l) return;
    cdq(l,mid);
    //……
    cdq(mid + 1,r)
}

其实这个$bug$挺$low$的，感觉自己智障了2333

bug2

因为题目中说必须是严格递增的。所以$mid$的位置就不能直接取中间了。 需要找到一个$x[mid]$与$x[mid + 1]$不同的位置。

代码

/*
* @Author: wxyww
* @Date:   2019-02-15 10:45:05
* @Last Modified time: 2019-02-16 15:29:12
*/
#include<cstdio>
#include<iostream>
#include<cstdlib>
#include<cstring>
#include<algorithm>
#include<queue>
#include<map>
#include<vector>
#include<ctime>
using namespace std;
typedef long long ll;
const int N = 300000 + 10;
map<int,int>ma;
ll read() {
    ll x=0,f=1;char c=getchar();
    while(c<''0''||c>''9'') {
        if(c==''-'') f=-1;
        c=getchar();
    }
    while(c>=''0''&&c<=''9'') {
        x=x*10+c-''0'';
        c=getchar();
    }
    return x*f;
}
int ls[N],tree[N];
struct node {
    int x[10],ans;
}a[N];
ll A,P,n;
int js;
void clear(int pos) {
    while(pos <= js) {
        tree[pos] = 0;
        pos += pos & -pos;
    }
}
void update(int pos,int x) {
    while(pos <= js) {
        tree[pos] = max(x,tree[pos]);
        pos += pos & -pos;
    }
}
int query(int pos) {
    int ret = 0;
    while(pos) {
        ret = max(ret,tree[pos]);
        pos -= pos & -pos;
    }
    return ret;
}
node tmp[N];
bool cmp(node x,node y) {
    if(x.x[1] != y.x[1])
     return x.x[1] < y.x[1];
    if(x.x[2] != y.x[2]) return x.x[2] < y.x[2];
    return x.x[3] < y.x[3];
}
bool cmy(node x,node y) {
    if(x.x[2] != y.x[2]) return x.x[2] < y.x[2];
    return x.x[3] < y.x[3];
}
void cdq(int l,int r) {
    if(r <= l) return;
    //保证右边第一维严格大于左边
    sort(a + l,a + r + 1,cmp);
    int mid = (l + r) >> 1;

    int tt = 1e9;
    for(int i = l;i < r;++i) if(a[i].x[1] != a[i + 1].x[1] && abs(mid - i) < abs(mid - tt)) tt = i;
    if(tt == 1e9) return;
    mid = tt;
    //保证两边第二维分别有序
    cdq(l,mid);
    sort(a + l,a + mid + 1,cmy);
    sort(a + mid + 1,a + r + 1,cmy);
    int L = l,R = mid + 1,now = l;
    while(L <= mid && R <= r) {
        if(a[L].x[2] <= a[R].x[2]) {
            update(a[L].x[3],a[L].ans);
            ++L;
        }
        else a[R].ans = max(a[R].ans,query(a[R].x[3] - 1) + 1),++R;
    }
    while(R <= r) a[R].ans = max(a[R].ans,query(a[R].x[3] - 1) + 1),++R;
    for(int i = l;i <= L;++i) clear(a[i].x[3]);
    cdq(mid + 1,r);
}
int main() {
    A = read(),P = read(),n = read();
    ll now = 1;
    int tot = 0;
    for(int i = 1;i <= n;++i)
        for(int j = 1;j <= 3;++j)
            ls[++tot] = a[i].x[j] = now = now * A % P,a[i].ans = 1;

    sort(ls + 1,ls + tot + 1);
    ma[ls[1]] = ++js;
    for(int i = 2;i <= tot;++i) if(ls[i] != ls[i - 1]) ma[ls[i]] = ++js;
    for(int i = 1;i <= n;++i) {
        for(int j = 1;j <= 3;++j)
            a[i].x[j] = ma[a[i].x[j]];
        sort(a[i].x + 1,a[i].x + 4);
    }

    cdq(1,n);
    int ans = 0;
    for(int i = 1;i <= n;++i) ans = max(ans,a[i].ans);
    cout<<ans;
    return 0;
}

CentOS 安装 CDH 报缺少 cyrus-sasl-gssapi、MySQL-python、mod_ssl、openssl-devel 等包的错误

一、在由于之前公司 cd 系统环境都是 ubuntu，但是目前要在云服务器上搭建 cdh 环境，经测试发现在云环境下的 ubuntu 系统中搭建 cdh 集群。集群很不稳定（可能由于云虚拟机自身的问题，因为服务器是第三方提供的），后来转用 CentOS 系统，集群就稳定很多，但是第一次在 CentOS 下搭建 cdh，报了一些，经过几番查找解决了不少问题；下面是安装过程包缺少依赖包的问题解决：

第一：错误

第二：下载缺少的依赖包

首先要安装，yum 的一个工具，yum-utils  :    yum install yum-utils

然后就可以使用使用 yumdownloader  xxxx.rpm  下载需要的包了

第三：安装对应的包：

rpm -ivh cyrus-sasl-gssapi-2.1.23-15.el6_6.2.i686.rpm --force --nodeps

rpm -ivh cyrus-sasl-gssapi-2.1.23-15.el6_6.2.x86_64.rpm --force --nodeps

 

rpm -ivh redhat-lsb-4.0-7.el6.centos.i686.rpm --force --nodeps

rpm -ivh redhat-lsb-4.0-7.el6.centos.x86_64.rpm --force --nodeps

rpm -ivh redhat-lsb-core-4.0-7.el6.centos.x86_64.rpm --force --nodeps

 

rpm -ivh mod_ssl-2.2.15-60.el6.centos.4.x86_64.rpm --force --nodeps

 

rpm -ivh MySQL-python-1.2.3-0.3.c1.1.el6.x86_64.rpm --force --nodeps

 

rpm -ivh openssl-devel-1.0.1e-57.el6.i686.rpm --force --nodeps

rpm -ivh openssl-devel-1.0.1e-57.el6.x86_64.rpm --force --nodeps

 

rpm -ivh rpcbind-0.2.0-13.el6_9.1.x86_64.rpm --force --nodeps

 

rpm -ivh python-psycopg2-2.0.14-2.el6.x86_64.rpm --force --nodeps

exec(),passthru()

php文件调用系统命令，在终端中直接执行这个php文件是可以执行的，在web服务器中访问这个文件就没有反应，是什么问题。权限问题吗？还是什么。。。

今天关于SAE J2534 Pass-Thru API的分享就到这里，希望大家有所收获，若想了解更多关于Apache Qpid JMS 0.34.0，Java Message Service 客户端、bzoj2253 纸箱堆叠、CentOS 安装 CDH 报缺少 cyrus-sasl-gssapi、MySQL-python、mod_ssl、openssl-devel 等包的错误、exec(),passthru()等相关知识，可以在本站进行查询。

本文标签：

• SAE_J2534
• Pass_Thru_API
• Vehicle_Communication
• Automotive_Interface