From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Diminished support for PXIe-4331 in VS2013
pmac
Member
02-28-2014 08:27 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I am upgrading my system from VS2011 to VS2013. I have 7 PXIe-4331 bridge input modules installed across two PXIe-1075 chassis'. These modules were not natively supported in VS2011 and required a custom device add-on which was a free download from the ni website. The custom device fully supported the 4331 and was a very useful tool.
When I initiated the upgrade to VS2013 I went to the ni website for an updated version of the custom device and found that ni stopped updating it because the PXIe-4331 was natively supported starting with VS2012.
That's not entirely true. When I went to reconfigure my channels in VS2013 my only choice for bridge input was strain. The custom device offered a choice of strain, force, or pressure. All of the channels I am using are force or pressure inputs. Apparently, the force and pressure options were dropped when the custom device was implemented in VeriStand.
It's hard for me to believe that I am the first one to come up against this. Is anyone aware of a work around for this issue? Can the custom device for VS2011 be easily modified to work with VS2013?
Thanks
StephenB
Active Participant
03-03-2014 09:56 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hey Pmac,
When I deprecated the 433x custom device support I had forogtten about these measurement types. Sorry about that. I don't want to continue updating that custom device, so I will post a download on that page that adds in Force and Pressure to NIVS 2012 and 2013 in an hour or two.
Stephen B
StephenB
Active Participant
03-03-2014 11:17 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
StephenB
Active Participant
03-03-2014 11:29 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I also reported this as a feature request to NIVS as CAR #456029
Stephen B
StephenB
Active Participant
03-03-2014 12:06 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I just fixed a bug with pressure so if you already downloaded that, redownload it.
Also, I added torque for completeness.
Also, apparently this was already reported in CAR # 426506, so if you're tracking them... track that. The other one was closed as a duplicate
Also, I added torque for completeness.
Also, apparently this was already reported in CAR # 426506, so if you're tracking them... track that. The other one was closed as a duplicate
Stephen B
03-03-2014 12:40 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
OK, Thanks.
There are a couple of issues with the force plugin. I've been working over the phone with Ryan C. he said he would get with you about these.
Thanks for the update.
pmac
03-05-2014 12:46 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Stephen B,
There still seems to be a bug with the pressure plugin.
When I added a couple of pressure channels and deployed the SDF, error -307526 "The XML file provided is invalid." was reported in the deployment log.
Thanks
StephenB
Active Participant
03-05-2014 01:29 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hmm I just tried it and it works... Can you try clearing out the plugin and reinstalling it?
Stephen B
03-05-2014 02:09 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
OK. Now it works.
Thanks
rkbull
Member
03-21-2016 04:13 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Stephen
Any idea what happen to that post?
I am working with a 4339 and would like the force or custom voltage with excitation measurement type. I would also like the ability to use the shunt cal on the terminal block. I have a DAQ plugin for 2013 that adds support for shunt cals, but can't port it over to 2014 as the VIs are stripped.
Is there any documents that discuss creating these DAQ plugins?
Thanks.
Rob
Rob
