UDS service ReadDataByIdentifier problem on remote computer (TeamViewer)

[waszniowski]

I have an odd problem with UDS communication. I have an application reading data from ECU via UDS. It is based on interfaces PCANBasic.dll, PCAN-ISO-TP.dll, PCAN-UDS.dll, PCAN-OBDII.dll
This application works properly on several computers (Windows 7 and 10) for a year. Now I am trying to run this application on Win10 computer remotely controlled via TeamViewer (I am at Europe, remote computer is in India). Three months ago there were no problem with this application started via TeamViewer, but now it do no work properly.
Here is the correct behavior of problematic part (logged on my computer):
18DA00F1 is application (UDS client)
18DAF100 is ECU (UDS server)

Code: Select all

   210       899.254 DT 18DA00F1 Rx 8  03 22 F1 80 55 55 55 55 		ReadDataByIdentifier 0xF180
    211       899.866 DT 18DAF100 Rx 8  10 0F 62 F1 80 53 57 31 		ECU will return longer string
    212       901.098 DT 0CF00400 Rx 8  FF FF 7D 00 00 FF FF 7D 		background communication
    213       901.647 DT 18DA00F1 Rx 8  30 0A 0A 55 55 55 55 55 		response can continue
    214       902.231 DT 18FF3500 Rx 8  00 00 FF FF FF FF FF FF 		background communication
    215       912.850 DT 18DAF100 Rx 8  21 30 30 33 56 30 30 33 		rest of the response
    216       920.314 DT 0CF00400 Rx 8  FF FF 7D 00 00 FF FF 7D 		background communication
    217       920.902 DT 18FF3500 Rx 8  00 00 FF FF FF FF FF FF 		background communication
    218       923.833 DT 18DAF100 Rx 8  22 50 5A AA AA AA AA AA	rest of the response

The same application on remote computer:

Code: Select all

  1781)      8280.7  Rx     18DA00F1  8  03 22 F1 80 55 55 55 55 		ReadDataByIdentifier 0xF180
  1782)      8281.6  Rx     18DAF100  8  10 0F 62 F1 80 53 57 31 		ECU will return longer string

Because UDSApi.WaitForService return PUDS_ERROR_CAN_ERROR, application continue by next id,

Code: Select all

  1783)      8289.6  Rx     18DA00F1  8  03 22 F1 81 55 55 55 55		ReadDataByIdentifier 0xF181

...
But short data (2 bytes) it reads successfully.
We are playing with this problem for a week. During this week we tested several computers. We saw several time that also long data was read successfully.
Why WaitForService after ReadDataByIdentifier fail in reading longer responses while it is able to read short (single message response)?
Thanks for any ideas,
Libor Waszniowski

[PEAK-Support]

Why should a remot session should influence a lokal CAN Communication ? We do not know ! Maybe you ask the Teamviewer people if they limit any timings while a session is running, but i do not believe so. For me it looks that it have absolutly nothing to do with using TeamViewer.

What happened if some people us the system local without running a TeamViewr session? does this work?

[waszniowski]

I also did not see any reason why TeamViewer should affect CAN communication. My latest observation is, that on a private laptop it works perfectly with TeamViewer, but on company laptop it works almost never, even without TeamViewer. Some company IT policy setting or antivirus?

[PEAK-Support]

yes, maybe - could you check with the taskmanager which application use a lot of CPU and/or memory - maybe it is a virus protection, firewall tool etc.