LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 200279, Motor control and Measurements

Solved!
Go to solution

Hello, 

 

Okay I will try this and update the post later. 

Thanks for all the help,

Best regards 

Julius 

0 Kudos
Message 11 of 16
(340 Views)

Hello Gerd,

 

I tried alot and figured almost everything out. Its working way better and more fluent. 

Sadly another problem occured. 

When im using the counter etc. without controlling the motor and rotate it by hand, the measurement of the angle is perfect! Also the measurement of the Torque is working. 

Julsbng_2-1705661852279.png

 

 

 

Unitl.... i start the motorcontrol. After starting, the angle measurement is going crazy and is raising even if the motor is not rotating. The analog Torque measurement is not impacted, just de digital measurement of the angle. 

The motor control is is a single digital output on one line. Can it be that i did something wrong in the program or could it be a electronical issue? Do i need to split the measuremnt and control on different devices so they dont interfer? I attached the VI in version 2019. 

Julsbng_1-1705661720894.png

 

Below you can see the settings of the DAQ Tasks. 

 

Julsbng_3-1705661988018.png

 

Julsbng_4-1705662030952.pngJulsbng_5-1705662055693.pngJulsbng_6-1705662100186.png

Julsbng_7-1705662182609.pngJulsbng_8-1705662189839.png

Julsbng_9-1705662258114.pngJulsbng_10-1705662295129.png

Thanks in advance.

 

Bets regards 

Julius

 

 

0 Kudos
Message 12 of 16
(312 Views)

Hi Julius,

 

you are using way too many ExpressVIs, I will not dig into all of them...

 

I recommend this article, just skip the first paragraph on DAQAssistent!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 13 of 16
(297 Views)

Hello,

 

I am aware that i am using many express Vi´s but this is the only way it worked for me. I tested alot and i didnt find another way for it to work as i want it to. 

When im not using Express vis the values rest all the time or the data type is not the right one...

 

Im really dont know how to do it better...

 

 

 

0 Kudos
Message 14 of 16
(292 Views)

Hi Julius,

 


@Julsbng wrote:

Im really dont know how to do it better...


Read the article linked in my previous message and then examine the DAQmx example VIs in LabVIEW's example finder...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 15 of 16
(288 Views)

Hello, 

 

the problem was not that I used too many express vis or so. The problem was that the grounds of the measurement and regulation were shared. 
that resulted in a noisy signal and manipulated the execution time as well. 
Im aware that it’s better not to use express vis etc and I’m fixing it. 

thanks for all the help especially for the hint with the Samples which caused an error.

 

best regards 

julius

0 Kudos
Message 16 of 16
(237 Views)