I am having trouble communicating with a Peterbilt that has a PACCAR/DAF MX11 engine. I am using 4.07 software.
Is there any chance my communication problems might be on the IQAN side?

Just for my curiosity.

When I am setting up the gauges and what nots for the display. I notice that for the display on the MD4 I can see and display all of the sensors on any of the masters without doing a APPOUT/IN or JFIN. This tells me that those values are always being transmitted between the masters. But, if I want to use the same data values into an Application logic circuit on another master then I have to do a APPOUT/IN or JFIN. If all this data is circulating on the master or diagnostic bus anyway, why do we have to transit it again for use in the application logic? I'm building a multi master system with one md4 and two mc43.

Can I pack multiple signals / parameters into the APP OUT parameter so as to send more infomration in one message?  Then unpack it on the other side. For example, if I have a lot f digital signals I want to share arround multiple MC43 modules, sending only one APP OUT is far more sensible than making multiple APP OUT's ?  Kind of like a J1939 PGN with SPNs inside.

In the main menu is the Preferences tab, can I add functions there for example a different display mode option.

Like choose another display mode between classic and new.

Is it possible for one MD4 to have multiple J1939 SA addresses? For example one SA (SA=0 or 1) to communicate to another MD4( SA=39) and another SA (SA=49) to communicate to engine and transmission?

At a given cycle time, is it possible to determine if a J1939 CAN frame has just been received? I am aware CAN frame blocks return a boolean indicating if their frame is new or not. However I believe this only works if the CAN frame has an enabled time out. Is it possible not to have a time out and still be able to determine if a CAN frame is new or not?

My goal is to not implement a time out, yet still be able to distinguish a CAN frame that has not been updated for a while from a CAN frame that is continuously being updated with identical values.

Thanks,

Hello,

I am working with a MC43, that controls a relay (a DOUT LS) that maintains the 24V power supply to the MC43 (enabled by a timer relay before that).

If the MC43 shuts down, it can't be turned back on, without re-toggling (manually) the timer relay. This behavior is perfectly fine except for firmware updates. I can send a IQAN project remotely, but when the firmware update is finished the MC43 systematically reboots, then looses its 24V. Is there a configuration that prevent this behavior?

Thanks.

I have an integer parameter inside of my initialization group that drives the Source Address for my TSC1 channel.

That IP channel is supposed to change it's default value depending on the truck engine model (decided in an adjustable state).

The truck state is set to DD and the default value for the Engine SA IP channel SHOULD change to 231, but it is staying at 7.  I've reset power and I cannot make it come off of anything other than the default mode default value.

Any help would be greatly appreciated.

It would be nice to be able to see what adjust group a certain parameter channel is part of directly from within the application logic.

Dear all,

Let me explain the problem and I hope someone could give me an idea how to fix it.

I have a transmission that goes to force neutral with no obvious reasons.

Attached is two picture of CAN trace on the bus.

FF20 is sent from our controller to the transmission and FF23 is what I get from the transmission.

As you can see for some reason the all bytes are changing to Fs what may cause this behavior.

In the controllers Log I see "running indication J1939 error" and althoug I am not 100% sure I believe this is relatet to the listed above. Can someone explain what this error stands for ?

Thank you in advance, all support will be appreciated.