Same parameter from different sources

alb · Post by **alb** » Fri Sep 23, 2011 10:11 am

Terry, Kristian, my experience is not the same. I've not been able to display simultaneous rotary & text gauges for:

J1939.XM500.Transmission Oil Temperature
J1939.Transmission.Transmission Oil Temperature

[PGN 65272 SPN 177]

XM500 is configured as source-address 255.
Transmission is an Allison CEC2 off-highway ECM on SA 3.

J1939.XM500 bounces between its value and the value matching the stable .Trasmission variable.

I have video of .XM500 bouncing between 149*F and 165*F while .Transmission holds rock-steady at 165*F. The averaged frequency of 5 events is roughly 1hz and avg. duty cycle breaks down as 83%-149*F, 17%-165*F. Does that make the gauge 83% reliable?

Are you doing something like this Terry?
Thanks gents.

Post by **ksaenz** » Fri Sep 23, 2011 11:12 am

Hello alb,

I split the topic because Terry's issue was a little different, he has DM1's coming from different sources.

I see you configured the XM500 to listen to any source address (255) and it is reading the same parameter from different sources.

Can you tell me which version of the PowerVision Configuration Studio you are using?
The latest released version is 2.2.10678 and it can be found here:
viewtopic.php?f=3&t=258

Regards,

ksaenz

alb · Post by **alb** » Fri Sep 23, 2011 11:22 am

Thanks Kristian. I was just amazed to find something pertaining to duplicate SPN's.

2.2.10525. I'll upgrade.

What next?

Post by **ksaenz** » Fri Sep 23, 2011 1:44 pm

Now try saving, creating, and loading a full install from version 2.2.10678.

The XM500 is configured to listen to any soure address (255) but it should skip the ones that are already assigned to another J1939 device.

Regards,

ksaenz

alb · Post by **alb** » Fri Sep 23, 2011 5:53 pm

Didn't seem to help. I thought I would see the new bootloader screen with the select file menu, but I got the same old red arrow/green arrow.

Post by **ksaenz** » Mon Sep 26, 2011 8:05 am

The full-install created by the configuration tool updates the OS, application, and configuration but not the bootloader, the unit will keep the same bootloader it already had.

The test configuration I used is attached. It has one gauge tied to the "Transmission Oil Temperature" parameter from "My Device" (SA 255) and the same parameter coming from "Transmission" (SA 3) does not affect it.

Regards,

ksaenz

alb · Post by **alb** » Mon Sep 26, 2011 6:27 pm

After I figured out the DB3 was set to PV450 and I was trying to put it on a PV750, I fixed that and it worked. I added a 2nd gauge to read side-by-side and they both were stable/independent.

Now, just have to figure out why my own DB3 isn't.

Possibly because I'm using a multi-config?

alb · Post by **alb** » Tue Sep 27, 2011 3:21 pm

None of my DB3s show a stable XM500.Transmission Temperature, including a brand new one seeded from "Blank Configuration". Even if I copy and paste the gauge from your Duplicate parameter.DB3 and replicate your Environment Setup.

Do I have to recreate the whole DB3 using a fresh Murphy Standard Configuration from V2.2.10678?

Why does your simple example work and not mine?

Thanks for all the support.

Post by **ksaenz** » Tue Sep 27, 2011 4:59 pm

Add the prameter Transmission Oil Temperature to the Transmission device.

alb · Post by **alb** » Wed Sep 28, 2011 9:45 am

You were right. That stabilized the gauge.

What's wrong with the original configuration now?

Thanks again.

Post by **ksaenz** » Wed Sep 28, 2011 1:35 pm

Hello alb,

I downloaded the attachment and removed it from the post to protect your configuration.

I noticed that in your configuration the XM500 device was defined before the Transmission device so here is what I did:
1 - Added a new device with source address 255 after the Transmission device.
2 - Added the same paramters from the XM500 device to the new device.
3 - Re-assigned the gauges from the XM500 device parameters to the new device parameters.
4 - Deleted the XM500 device.

With the new device defined after the transmission device the gauges act independent like in the example.

Regards,

ksaenz

alb · Post by **alb** » Thu Oct 06, 2011 5:04 pm

Thank you much. Worked as described.

Same parameter from different sources

Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources

Re: Same parameter from different sources