FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
Tuesday
Hello
I have two identically configured virtual axis running on CtrlXCOREVirtual 2.6.9.
The DeviceStatus component of ArAxisStatus behaves as expected on one axis but not on the other.
e.g.
arAxisStatus_gb[].Data.DeviceStatus.Standstill;
arAxisStatus_gb[].Data.DeviceStatus.ActualVel;
arAxisStatus_gb[].Data.DeviceStatus.ActualPos;
arAxisStatus_gb[].Data.ActValues behaves as expected with both axis OK
Please see screenshot below:
Any ideas?
Thanks
Solved! Go to Solution.
Tuesday
Hello DCEN_Tony,
i could not reproduce your case. We check here twice... any it works like expected. Could a online-change be reasonable.... Did you already try a clean_all/new build/download? and start in clean conditions?
Well .. the arAxisStatus...data.devicestatus was introduced in 2V06 ... did you start from scratch or based on an former <2V06 project?
Bye
Tuesday
Thanks @CodeWasi
Yes I had tried all the usual stuff ...clean all / reset origin and reboot of the COREVirtual etc...still same. I started from scratch.
I have since tested on a real core (same app and software versions) though and could not reproduce issue either so hopefully its just something to do with virtualCORE I was using.
When should you use devicestatus v ActValues...Are there any differences?
Thanks
Wednesday
Hello @DCEN_Tony
If this problems occur again please check the data source of the DeviceStatus at the Datalayer to see if the problem comes form the AxisInterface inplementation or from the axis data itself...
Regards
Jochen