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?

Is there a way to extract the Machine ID from a clone if the filename has been overwritten?

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.

Any plans on developing CAN bus I/O distribution blocks rated for outside use with either M12 or Deutsch connectors?

Is there a way to save an image of display from Simulation as an PNG or SVG.  We would like to use them in our user manual and would allow for a professional looking image.

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.