Never Ending Story? VAGCOM-Adapter | Posts 16+

BERT wrote:

Hi, I have a tool that allows you to address RTS (L-line) and TXD (K-line) connections both statically and dynamically. If there is interest, I could email that document to a central point of contact.

Hi Bert.

I would also be very interested in that.

If the licensing allows it, I would pass it on to Rainer, in case he can/wants to make it available for download. Then you would save yourself a lot of emails with the same content.

ulf wrote:

BERT wrote: Hi there, I have a tool that allows you to address RTS (L-line) and TXD (K-line) connections both statically and dynamically. If there is interest, I could email that document to a central point of contact. Hi Bert. I would also be very interested in that. If it is possible from a licensing perspective, I would pass it on to Rainer, in case he can/wants to make it available for download. Then you would save yourself many emails with the same content.

Hello,

Don't forget this problem: /viewtopic.php?p=10101&highlight=#10101

If there are any problems with the license, I can (if I have time) create a small program myself to handle it.
Windows provides the following API functions for this purpose:

Code:

The EscapeCommFunction function directs a specified communications device to perform an extended function. BOOL EscapeCommFunction(   HANDLE hFile,  // handle to communications device   DWORD dwFunc   // extended function to perform ); Parameters hFile Handle to the communications device. The CreateFile function returns this handle. dwFunc Specifies the code of the extended function to perform. This parameter can be one of the following values: Value Meaning CLRDTR Clears the DTR (data-terminal-ready) signal. CLRRTS Clears the RTS (request-to-send) signal. SETDTR Sends the DTR (data-terminal-ready) signal. SETRTS Sends the RTS (request-to-send) signal. SETXOFF Causes transmission to act as if an XOFF character has been received. SETXON Causes transmission to act as if an XON character has been received. SETBREAK Suspends character transmission and places the transmission line in a break state until the ClearCommBreak function is called (or EscapeCommFunction is called with the CLRBREAK extended function code). The SETBREAK extended function code is identical to the SetCommBreak function. Note that this extended function does not flush data that has not been transmitted. CLRBREAK Restores character transmission and places the transmission line in a nonbreak state. The CLRBREAK extended function code is identical to the ClearCommBreak function. Return Values If the function succeeds, the return value is nonzero. If the function fails, the return value is zero. To get extended error information, call GetLastError.   und The SetCommBreak function suspends character transmission for a specified communications device and places the transmission line in a break state until the ClearCommBreak function is called. BOOL SetCommBreak(   HANDLE hFile   // handle to communications device ); Parameters hFile Handle to the communications device. The CreateFile function returns this handle. Return Values If the function succeeds, the return value is nonzero. If the function fails, the return value is zero. To get extended error information, call GetLastError.

Best regards, Rainer.

Rainer K. wrote:

But don't forget this problem: /viewtopic.php?p=10101&highlight=#10101

Hi Rainer,

It's already clear, but with controlled impulses, one could at least measure the delay of the positive and negative flanks between TXD, K-line, and RXD using only an oscilloscope, and then optimize it under real conditions using a potentiometer – i.e., by connecting the adapter to a diagnostic PC.

That would be a step in the right direction.

Hi there.

License issue:

The program is custom-made. It uses a DLL from B. Kainka, which can be downloaded from the internet, to avoid having to deal with the API directly.
(The DLL uses the API and is compatible with NT, 2000, and should also work with XP.)

The program was initially created to test the execution times, including the influence of the computer system.

I will send it to Rainer. He can then distribute it for testing.

Okay, then.