ID | Known Issue |
---|
Configuration |
147986
Return | MAX hangs if a previously mapped motion controller on a remote target can no longer be found on the network.
Workaround: None.
Reported Version: 7.6 | | Resolved Version: N/A | | Added: 08/03/2009 |
|
176545
Return | Error -70208 on PCI-7390 motion controllers after mapping the Shutdown signal in MAX.
When you map the shutdown signal (E-Stop) to an available digital input on the IO Mapping tab in MAX, you will get error -70208 (I/O Resource Configuration Error) in MAX after trying to initialize the controller more than once.
Workaround: Go into MAX and change the initialization preferences so that "IO Mapping" is not part of the initialization process.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 08/03/2009 |
|
184721
Return | Deceleration incorrectly greyed out on axis 2 of the PCI-7390 in MAX.
You cannot configure the axis 2 deceleration when the Units setting on the Trajectory Settings tab is set for revolutions.
Workaround: Change your units from revolutions to counts or set your deceleration value from your programming environment instead of from MAX.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 12/15/2009 |
|
197081
Return | Torque offset incorrectly applied when using onboard commutation.
Applying a torque offset while using onboard commutation causes both analog outputs to offset by the same amount when an offset is configured for the first analog output. For example, if Axis 1 is set for onboard commutation and you configure Axis 1 to have a torque offset of 1 V, both analog output 1 and analog output 3 have a torque offset of 1 V. Since torque offsets are commonly used to compensate for a DC offset in an amplifier, you should be able to apply the torque offset on each analog output separately.
Workaround: None.
Reported Version: 8.1 | | Resolved Version: N/A | | Added: 12/15/2009 |
|
197526
Return | Incorrect encoder used for the phase commutation of the motor when using dual-loop feedback with onboard commutation.
When commutating a brushless servo motor using an encoder, the encoder mounted to the shaft of the motor should be used for commutation. If you are using dual encoders, the secondary encoder is the encoder that is typically mounted to the shaft of the motor. However, the NI 7350 boards always use the primary encoder for commutation (even when the system is configured to use dual encoders).
Workaround: None.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 12/15/2009 |
|
33205
Return | Rebooting an RT PXI controller containing a PXI-73xx motion controller causes the mapped devices to show a red X, even after fully booting up.
If you are using a PXI-73xx motion controller in a PXI system and reboot the controller, the boards show a red X on them, even after the controller has finished rebooting and the PXI-73xx motion controllers are working normally.
Workaround: Click the PXI-73xx motion controller in MAX and the red X disappears.
Reported Version: 7.3 | | Resolved Version: N/A | | Added: 12/15/2009 |
|
282060
Return | Using pasted initialization settings causes the motion controller to become inaccessible.
Switching motion controller settings by copying and pasting the settings file within the Initialization Settings dialog box causes the controller to become unusable after rebooting the computer.
Workaround: Export the settings to a .nce file by selecting File>>Export, copy the exported file, and reimport the copied file. Alternatively, you can export the settings to an XML file by right-clicking the settings and selecting Initialization Settings>>Export Settings from the shortcut menu.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 07/29/2011 |
|
Installation |
181794
Return | Updating from NI-Motion 7.2.1 using Portable Configuration Files doesn't work correctly for NI 7344 motion controllers.
When updating to NI-Motion 7.7 or later from NI-Motion 7.2.1, if you have previously imported settings for the NI 7344 controller using NI Portable Configuration files (.nce files), you must reimport the NI 7344 controller settings after you update NI-Motion. Symptoms of this issue that appear after updating NI-Motion are receiving error -70038 (NIMC_internalSoftwareError) when you initialize the controller and the Control Loop Settings tab not appearing in MAX.
Workaround: None.
Reported Version: 7.3 | | Resolved Version: N/A | | Added: 08/03/2009 |
|
195823
Return | Upgrading from NI-Motion 8.0 to NI-Motion 8.1 does not work automatically for the NI PCI-7390.
When upgrading from NI-Motion 8.0 to NI-Motion 8.1 on a PCI-7390, the motion controller is unusable in MAX because the NI-Motion driver is not automatically updated.
Workaround: Update the NI-Motion driver software for the PCI-7390 manually using the Windows Device Manager.
Reported Version: 8.1 | | Resolved Version: N/A | | Added: 12/15/2009 |
|
Runtime |
118667
Return | Back to back finite buffered contour moves do not work.
Workaround: Call Stop Motion with Stop Type set for Halt between each finite buffered contour move.
Reported Version: 7.6 | | Resolved Version: N/A | | Added: 08/03/2009 |
|
121634
Return | Unable to use one onboard program to stop a second onboard program.
Workaround: Share a variable between the two onboard programs and use that variable as a way to inform the second onboard program that it needs to stop execution.
Reported Version: 7.6 | | Resolved Version: N/A | | Added: 08/03/2009 |
|
152350
Return | Cannot read encoder position after enabling the encoder in MAX.
When you disable the axis and enable the encoder in MAX, Read Encoder Position incorrectly returns error -70122 (Encoder Disabled Error).
Workaround: Enable the encoder programmatically using the Enable Encoder VI/function after calling Initialize Controller.
Reported Version: 7.7 | | Resolved Version: N/A | | Added: 08/03/2009 |
|
34139
Return | Using Configure Axis Resources to switch feedback on the fly results in the PID parameters switching even if the feedback is not changed.
On the NI 7350, if you have configured a second set of PID parameters for use when the feedback switches, calling Configure Axis Resources switches the PID parameters, regardless of whether or not the feedback input is different from one call to the next.
Workaround: Put Configure Axis Resources into a subVI and use a functional global to keep track of which feedback is being using by the NI 7350.
Reported Version: 7.6 | | Resolved Version: N/A | | Added: 08/03/2009 |
|
187677
Return | Building a LabVIEW executable from a VI containing "Load Accel/Decel in RPS/sec.flx" will fail.
Workaround: Use "Load Accel/Decel.flx" instead of "Load Accel/Decel in RPS/sec.flx" and convert from counts/steps per second to revolutions per second programmatically.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 12/15/2009 |
|
33296
Return | Blending with blend factors greater than 10 may result in move complete being asserted at the wrong time.
Workaround: Only use blend factors that are less than 10 or ignore the move complete parameter if the actual position of the axis is not equal to the target position of the axis.
Reported Version: 7.5 | | Resolved Version: N/A | | Added: 12/15/2009 |
|
225507
Return | The Read Motion I/O Data VI/function returns error -70037 (NIMC_irrelevantAttributeError) with NI 7330 and NI 7340 motion controllers.
Calling the Read Motion I/O Data VI with an NI 7340 (but not an NI 7344) returns error -70037 on first call. If this VI or function is used with an NI 7330, the error is returned after setting the attribute parameter to home input active.
Workaround: Use the Read Home Input Status VI or function instead.
Reported Version: 8.1 | | Resolved Version: N/A | | Added: 08/02/2010 |
|
172412
Return | Activating the shutdown input on an NI 7350 controller does not stop the step output.
If you are using the step/direction outputs and activate the shutdown input, step signals can still be generated. The inhibit line is set correctly, so the drive should not respond to the step signals.
Workaround: Make sure that your drive's enable/inhibit signal is wired to the inhibit output of the NI 7350.
Reported Version: 8.0 | | Resolved Version: N/A | | Added: 09/05/2012 |
|