PLUS+1 User Forum

PLUS+ Tools => PLUS+1 Service Tool => Topic started by: Marbek_Elektronik on March 06, 2015, 07:13:48 PM

Title: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: Marbek_Elektronik on March 06, 2015, 07:13:48 PM
Hi,
If there are many can-bus members, maybe with different protocolls:
(Danfoss controller, sensors, motors,.....)

Is it possible, there might be a crash if service-tool communicates with the Danfoss-controllers?

I have read out following IDs, which service tool is used in communication:
0xCDA00F1
0xCDB32F1
0x1BC78FFF

Does the service-tool disturb the communication?
Title: Re: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: hgb1992 on March 11, 2015, 01:44:52 PM
Hello!

In past we had no Problem with CANopen and J1939 together. Tricky is to manage 11bit and 29bit identifier on one bus - this should be avoided!
From me Point of view Service Tool should  not affect other communication, if you havn't double used identifier (Service Tool uses a defined ID range).

KR, Benedikt
Title: Re: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: Marbek_Elektronik on March 11, 2015, 03:37:08 PM
Hi Benedikt,

why it is thricky to manage 11bit and 29bit identifier on one bus?
I think it is no problem.
In past we have sent 11 bit messages from one controller to another (ID: 0x400 and then 8 bytes for example) and in parallel there was J1939 and a canopen device. - no problem!


The second question is, if service tool disturbs another device. Is it possible?

Title: Re: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: spittet on March 16, 2015, 04:55:55 AM
Hello!

In past we had no Problem with CANopen and J1939 together. Tricky is to manage 11bit and 29bit identifier on one bus - this should be avoided!
From me Point of view Service Tool should  not affect other communication, if you havn't double used identifier (Service Tool uses a defined ID range).

KR, Benedikt

You said Service Tool uses a defined ID range. Is it possible to tell us what are these ID range? With this information, we will make sure that the same ID isn't used by our application.

Thanks

Sam
Title: Re: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: Marbek_Elektronik on June 04, 2015, 03:14:30 PM
I have seen this:
0xCDA00F1
0xCDB32F1
0x1BC78FFF

Service Tool uses KWP2000 protocol to the controllers.
I don't know more about this protocol.
Title: Re: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: Daniel on June 08, 2015, 08:52:28 AM
Hi Bernd

Typical range for Service tool is 0xCDA0000 to 0xCDBFFFF.

0x1BC78FFF is from the UDS protocol.


Best regards
Daniel
Title: Re: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: Morten Christensen on June 08, 2015, 12:16:26 PM
If you have many CAN-BUS nodes on the network, then you properly also have a "high" CAN-BUS load. I have seen the "Service Tool" load the CAN-BUS up to 50-60% - So that could be your problem?
Title: Re: Does Service-Tool runs in parallel with all other can-modules? CANopen, J1939
Post by: Daniel on August 19, 2015, 10:07:25 AM
Hello

The amount of bus load "added" by Service tool to a system depends on how many signals that are currently logged on a page and how often the signal values are requested (how short the Requested log period is set).

When logging, Service tool requests the ECUs to send data about the currently logged signals for each log period. So if the Requested log period is set to 100 ms, Service tool will try to send the request each 100 ms.
A lower value on the Requested log period will hence increase the bus load, and each added logged signal on a page will also slightly add more load to the bus.

Service tool does only send requests for the signals that are on the currently opened page.

Best regards
Daniel
PLUS+1® Helpdesk