04-11-2024 09:38 AM
I'm setting the signal name as the frm.active property node.
04-11-2024 10:12 AM
The name of the property is Active Frame hence you must specify a frame name or otherwise it won't work.
04-11-2024 10:37 AM
Thanks for your continued replies.
Does this mean I need to put my source address (arbitration ID or hex equivalent) plumbed into the Frm.Active and the channel name plumbed into the Frm.J1939.AddFilt?
04-11-2024 11:00 AM
Wire Frame Name to the Frm.Active property and Source Address to AddrFilter.
See attachment.
04-15-2024 11:24 AM
When you say "Wire Frame Name to the Frm.Active" can you explain what the frame name is? I've been wiring in the channel name from the CAN database file...apparently this is not what is needed...and I don't know what this means. Does this mean I can't put a static channel name here...that the wired input needs to come from XNET Session>XNET Signal>XNET Session Frm.Active like in your updoaded VI?
And "Source Address to AddrFilter"...what format does this source address need to be in? I see in "Convert CAN Arb ID to J1939 ID" you are using a sequence of five or six processes to finally get the input for the source address...one step being "J1939 Filter Main".
Also, could you also upload the PGN field type def file? I pulled your previously linked VI's and they need this one additional file.
04-15-2024 06:45 PM
can you explain what the frame name is
Read FIBEX and the NI-XNET Database Editor Overview to understand how NI-XNET handles databases.
And "Source Address to AddrFilter"...what format does this source address need to be in?
The source address with a value of between 0 to 255. The SubVI Convert CAN Arv to J1939 ID.vi extracts this information automatically.
Also, could you also upload the PGN field type def file?
You can disconnect the type def. In case you don't know how to do it, I have attached the VI with type def removed.