Contribute
EN / USD
Log in / Join
32
of 76
TEP , The Engineering Projects , Image

syedzainnasir

TEP , The Engineering Projects , Rating 7.5 7.5 / 10
TEP , The Engineering Projects , Icon Level: Moderator
TEP , The Engineering Projects , Icon Joined: 20 Mar 2022
TEP , The Engineering Projects , Icon Last Active: 2:21 PM
TEP , The Engineering Projects , Icon Location: TEP , The Engineering Projects , Flag
TEP , The ENgineering Projects , Icon TEP , The ENgineering Projects , Icon TEP , The ENgineering Projects , Icon TEP , The ENgineering Projects , Icon
AF Inheritance on cRIO
TEP , The Engineering Projects , Calender Question: 07-Mar-2017
TEP , The Engineering Projects , Category In: LabView Projects
Hi all,

I have started to experiment more seriously with the Linked Network Actor, to communicate between cRIO and Windows. One thing I have noticed while developing my test projects is this:

When I create a class on the cRIO I can't change the Inheritance to the Actor.lvclass. It offers me no inheritance other than the default LVObject. When I create it on the Windows side I can change the inheritance to Actor Framework, but when I move it to the cRIO the Class locks. As a result, I can't check the inheritance or make changes to it.
Why is that? Is it really the idea, to code on the windows target and then move everything to the cRIO?

When I do this, it sometimes happens that the launcher on the cRIO opens all actors instead of just the one on the RIO.

Thanks in advance for all your input.
TEP , The Engineering Projects , Icon Answer: 0 TEP , The Engineering Projects , Icon Views: 150 TEP , The Engineering Projects , Icon Followers: 85
Small Bio
TEP , The Engineering Projects , Tags
PLC
Robot
STM32
Arduino
AI
ESP32
Ladder Logic
PLC Projects
Programming
Communicates STM32
PLC Projects
Communicates PLC
Font Style
Alignment
Indenting and Lists
Insert Media
Insert Items

Want to leave an answer!

Word Count :0 Draft Saved at 12:42 am.