Hello Everyone,

This could be operator error, or I am missing a new setting somewhere, however I have observed the following behaviour and would appreciate feedback.

Loading a MSTD MPC-20 configuration bundled with PowerVision 2.8.10491 I can change the TSC1 source address with Advanced Engine Settings -> J1939 Address Claim. It let's me change the displayed value, and when I back out of the menu's and power cycle the MPC-20. In CANCapture I observe that everything is on source address 234, and in the MPC-20 menu the value is saved as 234, except for the TSC1 message, the TSC1 message remains at source address 3.
In the MPC-20, the setting Advanced Engine Settings -> J1939 Address Claim appears to no longer be linked to the broadcast TSC1 source address value.



Loading a MSTD MPC-20 configuration bundled with PowerVision 2.7.10475 I can change Advanced Engine Settings -> J1939 Address Claim from 3 to 234, back out to the main display page, power cycle the MPC-20, and in CANCapture observe that the source address of the TSC1 message is no longer 3 but instead 234.
I took a look at the new Engine Control App located under the Applications tab, in PowerVision 2.8.10491, and of the 55 variables in the list I don't see an inclusion for something like the variable CANPort1.Address.

Please advise.

Discovered that the TSC1 priority and source address have been disassociated from CANPort1.Address.

These values are located in variable TSC1 Message ID.

I created a new calculation event under TSC1 Message ID called Calculate TSC1 Message ID with the following calculation,

201326592 (i.e. 0C000000) + CANPort1.Address

And then went to the menu manager and under Advanced Engine Settings -> J1939 Address Claim, child menu item setup, set Fire On Leave to the calculation event Calculate TSC1 Message ID.

This did not work.

I ended up temporarily defaulting the value of TSC1 Message ID to 0C0000EA for my purposes, and that works, but I do think there is significant value to being able to end user change the TSC1 source address.

Hello Ocelot,

Thank you for bringing this up. We really need a magic document that explains the effects of the PowerVision Configuration Studio firmware/application changes. Many engineers like to research and solve the problem, but don't like to document. ;)

You are correct that the source address on the TSC1 message needs to be configurable and according to J1939, the source address should be the address claimed by the MPC-20. That being said, there are several ECUs that require that the TSC1 have a particular source address and they aren't particular about the source address of other messages transmitted to them. That is why there is the disconnect today. We had customers who were changing the source address and then the TSC1 throttling quit working.

As a work around, you should be able to do something similar to what is done in the MPC10 config. On the TSC1 Message ID, there is a calculation event, Update PDUS. It is fired in the Splash Screen state machine at start up. It is also fired when the ECU Source Address changes and the CANPort1.Address is changed. I'm not sure it this fixes everything you need, but it should be close.

Another issue that some of our configs have with the TSC1 has to do with the PDU-S part of the PGN. Up until now, the standard configs just set the PDU-S to x00 without regard to the ECU address. This does not conform to the J1939 standard specification for the TSC1 PGN. We get away with being out of spec because most engine ECUs are at source address x00 or don't care.

We are expecting to release a patch as soon as the standard config for the MPC20r2 has finished validation test. Expect some differences between the MPC-20 and MPC-20r2 standard configs as related to the TSC1 settings/capabilities. The MPC-10 is already different.

As always, we are sorry for confusion and inconvenience. If you can find that magic document, we would really appreciate knowing where it is...

I took a look at how the TSC1 source address was manipulated in the MPC-10 and basically implemented the same thing in the MPC-20 configuration I was working on.

That did work.

Thank you for your time.