0
Answered

J1939 Address Claim / Start Address

Metalfor 9 years ago in IQANdesign updated by Gustav Widén (System support) 4 years ago 9
Hello, I'm working with a J1939 project in which I want to use a MD4-7 as an instrument cluster. The Cluster must have the chance to make address claim in J1939 with the 23 address. Is that possible? Regards. Diego.
Answer

New property on the J1939 bus for address claim introduced in IQANdesign 5.02. Forces IQAN master modules to claim their J1939 address before starting other J1939 communication.

0
Answered

jframe input polling question

Zach 9 years ago in IQANdesign updated by Gustav Widén (System support) 9 years ago 1
On some machines I have a polling request set for every 500ms.
I wondered how often polling happens by default if I don't use the polling request.

Sometimes I have polling for engine hours, battery voltage, and fuel used.
Sometimes I don't.
I would like to know what to consider for determining when I should.
J1939 is configured for 250kbs.
I have 2 second timeouts.
I thought that the protocol went through each pgn to see if there was information to be exchanged, then it got the information from each pgn.
So if my timeout is 2 seconds, then I would think polling every 500ms would not be something worth doing.
-1

Online Edits

Caola, Robert 3 years ago in IQANdesign updated by Gustav Widén (System support) 3 years ago 1

It would be nice to be able to go online with the PLC and make changes. Our system is getting pretty robust in design and it would be a great troubleshooting tool. It also would be in line with what some other automation companies are doing, such as Rockwell and Siemens. 

-2
Completed

IQANdesign 4.03.26 withdrawn

Ulrik Zakariasson (Software development) 8 years ago in IQANdesign updated 8 years ago 1

A problem with the recently released IQANdesign 4.03.26 was discovered earlier today. The problem occurs with systems that includes one or more XA2 modules, where these modules may not be initialized correctly. We have decided to withdraw this release till the problem has been corrected.


If you have already upgraded, please switch back to 4.02.16.