Additional NI Software Idea Exchange

When using the Read/Write Variables to INI File step in VBAI and not selecting the Ethernet option the code that is generated still includes this step and therefore requires the Ethernet IP toolkit to run the code.  I suggest that when the box is uncheck then the generated code not require this toolkit becuase the VIs are going unused.  

Hello,

I believe that we should create and API for NI I/O trace so that customers with automated production lines can automate a report logging response to a failure  In the case where a production line experiences a UUT failure, these customers could programmatically rerun the specific test that failed last, open I/O trace, start recording, test communication with a device, stop recording, and log the results when a failure is experienced.  This could even be used with G or CVI code module, not just TestStand.  That way if say the VI experiences a particular error after running subVI "testme", the API could be usted to start recording, re-run "testme", stop recording, and to generate a report.  I understand that certain users only use IO trace occasionally, so an API would not be necessary for them, however, with customers who may have to trouble shoot numerous UUTs off of a production line, this could be a great help.

Regards,

Shawn

Currently, NI Motion does not allow users to set the proportional gain (or any gain) less than one probably due to the fixed point math on the motion control cards. Many systems, especially those using ultra-high resolution encoders as feedback, are unstable with gains greater than one. Also, any system approaching the need to use Kp close to one will be extremely sensitive to the tuning process and will likely be difficult to optimize. An extremely simple solution to this problem is to add the ability to use Input and Output scale factors to the PID loop. Specifically, scaling the error term input to the PID controller for the input scale factor and the commanded output to the D/A or PWM's for the output scale factors. Even the ability to scale by factors of two would solve most issues. If only one scale factor could be implemented the output scale factor would be more useful as the input scale factor will effectively decrease the feedback resolution on a fixed point system. Other modern controllers utilize this strategy.

A quick search of the forums finds several people with this problem.

http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/tuning-servo-system/m-p/139507/highlight/tru...

http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/Is-there-any-way-to-drcease-the-open-loop-ga...

http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/MAX-Reducing-Encoder-Resolution/m-p/1030934/...

http://forums.ni.com/t5/Motion-Control-and-Motor-Drives/7344-PID-proportional-gain-1-but-actuator-st...

Thanks!