IVI Foundation Meeting Minutes 1 May 2011 IVI Foundation Meeting Summaries May 18-20, 2011 San Diego, CA Table of Contents CHAPTER 1 MEETING ATTENDEES ............................................................................................................... 2 CHAPTER 2 IVI DATA CONVERSION WORKING GROUP – MEETING MINUTES ................................ 3 CHAPTER 3 VISA.NET WORKING GROUP .................................................................................................... 7 CHAPTER 4 IVI MARKETING MEETING MINUTES .................................................................................. 12 CHAPTER 5 TECHNICAL COMMITTEE ....................................................................................................... 25 CHAPTER 6 IVI BOD MEETING MAY 20, 2011 ............................................................................................. 39
Yves mentioned the discussion from the IVI.NET meeting about adding classes providing the IVI defined
values for string properties (such as Trigger Source). David Rohacek (NI) presented a proposal where
instead of using the type string, a strong type is used which allows IntelliSense to show possible values.
Unfortunately, attributes like Trigger Source are also used as indexes to a repeated capability collection.
In such cases, support of virtual names complicates the issue singnificantly the decision about this is
postponed.
IviDigitizer specification change proposal
We reviewed the specification change proposal:
- The proposed text for the ConfigureActiveTriggerSource IVI-C only high level function was agreed upon.
- For the new values for the Reference Oscillator Source attribute, Evan will check whether we must distinguish between PXI and PXIe for the 10 MHz reference. Even though these are on physically different lines, a given instrument will use one or the other depending on its own form factor – never both.
- Yves will check whether we will have to rev the interfaces (COM and .NET) following these changes. According to Kirk, we do not need to rev the interfaces, yet the version of the type libraries will be increased.
IviFgen
We reviewed the latest updates to the IviFgen Rev 5.0 draft (since March 15th draft). All editorial changes
that were reviewed were accepted in the document (tracking changes is on).
IVI Foundation Meeting Minutes 6 May 2011
There is still the last appendix (B Interchangeability checking rules) to be completed and reviewed.
Schedule for IviFgen Rev 5.0:
completion of prototyping
final formal review
vote
publication
shared components
Due to technical difficulties (WebEx and IP phone internet connections lost) we did not discuss the
schedule. Prototyping of IVI-C is currently in progress by NI, and IVI.NET prototyping is scheduled by
Agilent. In any case, before the final vote a full prototyping of the IVI-COM interfaces is required as well to
validate the syntax.
Action Items Created:
Owner Action Item Status
Evan Check if we need to distinguish between PXI and PXIe for the 10 MHz
reference.
Yves Do we need to rev the COM and .NET interfaces because we’re
adding new enum values? Check with John Harvey & Kirk Fertitta
No need. But will
increase the
version number on
the type libraries.
Yves Publish the latest IviFgen draft on WG page.
Next Meeting
The next meeting would be on May 25th according to our bi-weekly schedule, however Evan won’t be
able to join. I propose to work on the action items communicating with email and skip next week’s
meeting. The next phone conference will thus be scheduled for June 8th, 4:30 pm (Central European
Time). Yves will send out a reminder at the beginning of that week.
11:45-12:30 - Intro to Interfaces (Outstanding Issues & Action Items)
01:30-05:30 - Interface Definition
Agenda, Thur. May 19
On the 19th we will use the remainders of the IVI.NET and VISA meetings for VISA.NET.
10:30-12:30 - Continue working through interfaces
03:30-05:00 - Continue working through interfaces
05:00-05:30 - Wrap up action items and schedule review
IVI Foundation Meeting Minutes 9 May 2011
Review Action Items
Date Added Description Assigned To / Updates Target Date
General
02-08-2011 Set up phone meetings for the next
four months, starting Feb. 17, 2011.
John Harvey
DONE
02-11-2011
02-08-2011 Create documentation plan, including
some sample IVI.NET documentation
for style review.
John Harvey
DONE
TBD, before
May meeting
02-08-2011 Schedule a few intermediate updates
for the conflict resolution & GRM in
regular phone meetings.
John Harvey TBD, before
May meeting
Specification and Infrastructure
John gave a presentation on the initial organization and issues related to the VISA.NET specification.
Comments were captured in the presentation and in the specification. John will send out a copy of the
spec after returning to work next Wednesday (May25), and post to the VISA.NET WG page.
Conflict Resolution
Jim Piotrowski gave a presentation on conflict resolution. John will post the slides to the VISA.NET WG
page.
The current conflict resolution mechanism distinguishes interface type, number, and resource class. Joe
noted that this may not be enough resolution for PXI (and perhaps TCPIP).
There was discussion about the impact of side-by-side VISA.NET implementations. The consensus was
that version should be included in the conflict resolution data. The user could specify version in the
conflict resolution table, or if it were not specified, the most recent would be used.
There is an open question related to handling multiple .NET framework versions. There are several
scenarios that need to be handled.
A new .NET framework comes out, and vendor A supports the new version but vendor B doesn’t. How does conflict resolution work.
Are particular versions of VISA.NET from the same vendor specific to a particular .NET framework version.
IVI Foundation Meeting Minutes 10 May 2011
Intro to Interfaces
John showed a slide with the session interfaces, and the group made some minor edits.
John reviewed the issues that have arisen during the process of editing interfaces. Dan identified some
items that were NI extensions, which Kirk will review and delete from the interfaces offline.
John will post the slide and the interface issues list to the VISA.NET WG web page.
Interface Definition
Kirk led the discussion of interface definition and made changes directly in the VISA.NET assemblies. We
captured some additional issues in the Interface Issues list.
May 19 Morning – Continued where we left off on Wed.
In discussing how buffers are flushed, both NI and Agilent verified that their VISAs flush the buffer as
soon as the buffer is full.
We raised the question of whether the buffer flushing behavior of VISA and VISA.NET needed to match.
The consensus was that they did not need to match.
Problem – If the user intends an END to be sent with the last byte of data, and the last byte is not a line
feed, they could run into the following: If by chance the last byte of data happens to just fill up the
buffer, then the data would be flushed automatically, without END being sent. If the next operation is
an explicit flush, there would be no data in the buffer to attach the END to, and the END would never be
sent. The correct approach is to make sure that the END is always specified in the same method call as
the character that should have the END attached.
For VISA.NET, the correct behavior is:
Multiple calls to FlushWrite – If there is anything in the buffer, the first flush empties the buffer and subsequent flush calls do nothing.
If the user sends an END, the buffer should be flushed.
WriteBinaryAndFlush – Make sure that an END is always sent, even if the number of bytes in the buffer exactly matches the size of the buffer. With the previous item, this means that this always flushes the buffer.
FlushWrite (if we keep it) does not have an End parameter, and never sends END. It performs a flush, and if the End property is set, it disables it before flushing, and then re-enables it. Note that we are currently in favor of deleting it, but Dan would like to investigate the possible implications before finalizing this decision. We will delete it unless NI sees a specific reason to keep it.
Delete FlushRead and replace with SkipUntilEnd. Skip expresses better than Flush, since Skip is not just a buffer operation – it is also consuming data from the instrument.
o There is a setting in VISA C that allows discarding read buffer data without pulling from the instrument. Do we need to include a similar capability in the VISA.NET API? The NI .NET API has a DiscardUnreadData method – it is not clear what this does.
IVI Foundation Meeting Minutes 11 May 2011
Meeting Schedule
The next phone meeting will be May 26, 2011. John will send out a reminder, the meetings are already
set up. The normal time is 9:00 Mountain time.
Action Items
Date Added Description Assigned To / Updates Target Date
General
2011-05-18 Send out current drafts of documents to VISA.NET
WG and post to VISA.NET WG page.
VISA.NET spec.
Session Interfaces slide.
Conflict Resolution slides.
Interface Issues list.
John Harvey 2011-05-27
2011-05-19 Investigate & determine the exact behavior of VISA
regarding sending END to instruments when buffers
are exactly full – does a flush automatically occur
just because of the buffer being full (even if
another character has not been sent to the buffer),
and is an END appended? We need to know this to
define the VISA.NET behavior on WriteLine and
FlushWrite, and we may need to look at the
implementation of VISA.
Pete Stone
Dan Mondrik
2011-05-19 INITIAL
LOOK – Both VISAs flush
the buffer as soon as
the buffer is full.
2011-05-26
IVI Foundation Meeting Minutes 12 May 2011
Chapter 4 IVI Marketing Meeting Minutes
General Meeting Info: Date of Meeting: May 19-20, 2011
Location: San Diego, CA
Chairperson: Jared Aho
Minutes Prepared By: Jared Aho
Meeting Attendees:
Name Company Attended
Jared Aho National Instruments Y
Kirk Fertitta Pacific MindWorks Y
Bob Helsel IVI Foundation Y
Jochen Wolle Rohde & Schwarz Y
Rob Purser The Mathworks Y
Mike Wadzita Tektronix N
Joe Mueller Agilent Y
John Harvey Agilent Y
John Ryland Keithley Y
Jason Schares Rockwell Collins Y
Santanu Kumara Tektronix N
Eric Lord Pacific Power Source N
Kevin Lam Ametek Programmable Power N
Eric Wetjen The MathWorks N
Tom Fay Agilent N
Yves Maumary Agilent Y
Evan Cone National Instruments N
Jon Bellin National Instruments Y
IVI Foundation Meeting Minutes 13 May 2011
Jim Piotrowski National Instruments Y
Vesna Jadric National Instruments N
David Rohacek National Instruments N
Deborah Homan Agilent Y
Anshul Arora Tektronix N
Don Essner DRS N
Vinod Cherian The Mathworks N
Mike Woodring Pacific Mindworks Y
IVI Foundation Meeting Minutes 14 May 2011
Discussion Topics:
Roll Call
Review of action items from previous meeting
New Business
Update to IVI GSG Project Master
Summary of New Action Items
Proposed Next Meeting: June 22, 2011, 1 PM EST, Conference Call
Send updated IVI GSG PDF documents to Bob June 2011 In Progress
Bob H Post completed IVI GSG chapters to the web June 2011 In Progress
IVI GSG
Content
Owners
All IVI GSG Videos to be reviewed during June
meeting (post by June 20, 2011) June 2011 Open
IVI GSG
Content
Owners
Send release candidate footage to Bob for
final production End of June
2011 Open
Bob H/ Joe M Provide update on HiSLIP pres release August 2011 Open
John H Circulate IVI .NET press release, GSG, and
updates to IVI WP prior to October meeting October
2011 Open
Eric L/ Ray M Circulate AC Power press release draft in time
for review during in-person meeting October
2011 Open
Jared A Review schedule of press releases for 2011 October
2011 Open
Jared A Discuss Autotestcon activities at a future MC
meeting August 2011 Open
IVI Foundation Meeting Minutes 21 May 2011
ADDENDUM
IVI GSG VIDEO PROJECT MASTER
Guidelines and Consensus Points for All Videos
Length: 10 minutes maximum (including open, body, close)
o Opening: 1 minute
o Body: 7-8:30 minutes
o Closing: 15-30 seconds
Format
o Recording software: Camtasia
o Volume control: We can try to edit this post-processing. Just make sure your voice is
not clipping.
o Microphone: Headset mic
o OS: Microsoft Windows 7
o Screen resolution: 1280 x 720, output to the full resolution in which it’s recorded
(720p)
o Appearance: Have a clean desktop and Internet toolbar. Use standard Microsoft
desktop background, and use standard Windows Blue menu bar and window color.
o Video file format: AVI
o Video hosting tool: TBD by Jared
Opening Section
o Set basic expectations – what’s the point of the video, and then the outline to follow
o Benefit statement
o Accessing and installing the drivers
o The IVI webpage – Resources page and all that’s included
Body Section
o Use the Getting Started Guide as the GUIDE; model the body after what’s already
included and use consistent terminology
o Focus on the driver and how to use the driver in the environment, but not the
environment
o Follow the outline that’s in the GSG (this outline will be introduced during the Opening)
Closing Section
o Additional information on installing drivers
o Additional information on advanced content
IVI Foundation Meeting Minutes 22 May 2011
General Points of Discussion
o It takes about 2 days to record 8 minutes of quality content
o Smooth, slow, tone of voice; speak precisely and avoid slang; avoid humor
o Use a script, it will likely be reused
o No slides in the body
o GSG Videos will not be created for environments that do not have GSG PDF document
o Owners: your GSG PDF document must be updated, sent to Bob, and posted along with
the videos
o The same example you create or reference in the video should be made available to be
posted online along with the PDF and video
Things to Look Into Further
o Convenient ways of including the verbal script along with the video/audio
o Include an example or code snippet along with GSG document and video
IVI GSG Video Project Plan
Status or Due Date
Using IVI with… Owner GSG
PDF
Update
GSG
Video
v1
GSG
Video
v2
GSG Video
Release
Candidate
GSG Video
Final
(including
opening /
closing)
Opening and
Closing Segments
Bob H May
2011
Before
April
Meeting
April 2011 Included w/
others
Visual C++ John H May
2011
May
2011
June 2011 August 2011
C# Joe M May
2011
May
2011
June 2011 August 2011
VB .NET Joe M May
2011
May
2011
June 2011 August 2011
LabVIEW Jared A Done Done Before
April
April 2011 May 2011
IVI Foundation Meeting Minutes 23 May 2011
Meeting
LabWindows/CVI Jared A Done Done Done April 2011 May 2011
MATLAB Rob P May
2011
May
2011
June 2011 August 2011
Measure Foundry REMOVE
PAWS REMOVE
Visual Basic 6.0 Joe M May
2011
May
2011
June 2011 August 2011
VEE Pro Deborah
H
May
2011
May
2011
June 2011 August 2011
Deliverables Send to
Bob,
Bob to
post
Review
with IVI
MC
Review
with IVI
MC
Review
with IVI
MC, Send
to Bob
Bob final
production,
Review with
IVI MC, post
to web, Press
release for
Autotestcon
in September
Summary of ALL Action Items for IVI GSG Video Project:
Owner Action Item Deadline Status
Jared A Review NI’s IVI GSG Video v2 at March conf
call March 2011 Done
Bob H Review Opening and Closing segments at
March conf call March 2011 Done
Jared A/Bob
H
Review Opening/Closing segmens, and
LabVIEW and LabWindows/CVI release
candidates April 2011 Done
Jared A/Bob
H
Complete LabVIEW and LabWindows/CVI IVI
GSG Videos by May meeting May 2011 In Progress
IVI Foundation Meeting Minutes 24 May 2011
Owner Action Item Deadline Status
IVI GSG
Content
Owners
Send updated IVI GSG PDF documents to Bob May 2011 In Progress
Bob H Post completed IVI GSG chapters to the web May 2011 In Progress
IVI GSG
Content
Owners
All IVI GSG Videos v1/v2 to be reviewed during
May meeting May 2011 Delayed
Until June
IVI GSG
Content
Owners
All IVI GSG Videos release candidates to be
reviewed June 2011 Open
IVI GSG
Content
Owners
Send release candidate footage to Bob for
final production June 2011 Open
Bob H Finish final production of videos and send for
review August 2011 Open
Jared A Press release on availability of IVI GSG Videos August 2011 Open
Bob H
Complete IVI GSG Video project by posting
content and sending press release during
Autotestcon
September
2011 Open
IVI Foundation Meeting Minutes 25 May 2011
Chapter 5 Technical Committee
General Meeting Info: Date of Meeting: May 20, 2011
Location: San Diego
Chairperson: Jon Bellin
Minutes Prepared By: Jon Bellin (finalized by Vesna Jadric)
Topics To Be Discussed:
Review Agenda
Review Voting Members In Attendance
Patent Call
Approve minutes from the February 2011 Technical Committee Meeting
Review outcome of recent eVotes, IPR Declarations, Editorial Changes, and Reviews
Review Action Items from Previous Meeting
Review Spec Status Document
Working Group Topics
Vote on IVI-6.1: IVI High-Speed LAN Instrument Protocol (HiSLIP)
IVI.NET Shared Components 1.0 availability
New Business
Discuss Upcoming Meetings
New Action Items
Voting Members In Attendance
Present Organization Name Name
Aeroflex Corporation Mark Meldrum
X Agilent Technologies Joe Mueller
Ametek Programmable Power Kevin Lam
BAE Systems Wade Lowdermilk
DRS-SSI Don Essner
Keithley Instruments John Ryland
X National Instruments Jon Bellin
IVI Foundation Meeting Minutes 26 May 2011
Present Organization Name Name
Nokia Torben Christensen
X Pacific MindWorks, Inc. Kirk Fertitta
Pacific Power Source, Inc. Eric J. Lord
X Rohde & Schwarz Jochen Wolle
X Rockwell Collins Jason Schares
X Tektronix Santanu Pradhan
X Teradyne, Inc. Teresa Lopes
X MathWorks, Inc. Rob Purser
TYX/EADS Chris Gorringe
VTI Instruments Tom Sarfi
There are 8 voting members in attendance, which satisfies the requirements for a quorum of 5
Voting Members. (Quorum is 25% of Voting Members. There are currently 17 Voting Members.)
Patent Call Please be aware that this meeting is being held under the Intellectual Property Rights policy adopted
by IVI Foundation. If you do not have a copy of this policy, please see me during this meeting. You
may also view and download a copy of that policy at the Organization>>Legal Documents section of
the Consortium website.
At this time, I would ask that anyone in attendance inform me if they are personally aware of any
claims under any patent applications or issued patents that would be likely to be infringed by an
implementation of the specification or other work product that is the subject of this meeting. You
need not be the inventor of such patent or patent application in order to inform us of its existence,
nor will you be held responsible for expressing a belief that turns out to be inaccurate.
IVI Foundation Meeting Minutes 27 May 2011
Approve minutes from the February 2011 Technical Committee Meeting The minutes from the February 2011 Technical Committee Meeting are posted on the IVI
Foundation web site.
No issues were brought up with the minutes. The minutes are accepted.
Review outcome of recent IPR Declarations, eVotes, and Reviews
IviScope Editorial Changes
On February 16th, Vesna Jadric announced IviScope editorial changes via the email below
components to 1.0. It agreed to do this in conjunction with other modifications it intends to complete in
July. The plan is to release version 1.0 on approximately August 15, depending on the results of testing.
IVI Digitizer Specification – Minor Changes
Resolution (2011-05-20:#02): The IVI Digitizer working group moves that we make two minor changes
to the IVI Digitizer specification. The first is the addition of a high-level C function for configuring the
Active Trigger Source attribute. The second is the addition of two new enum values for the Oscillator
Reference Source attribute: the PXI 10MHz and 100MHz references.
7 YES votes. 0 NO votes. The resolution is approved.
Action Item: Vesna to add this to the In Progress tab on the Life Cycle document.
New Business
Ambiguity Between Physical and Virtual Names
John Harvey posed the following issue:
Imagine a scope with three channels with physical names, C1, C2, and C3.
In the scope COM API, you could type scope.Channels[“C1”].Configure(…);
Now suppose that you have a second scope with three channels, C0, C1, and C2. Now suppose that, in
order to make the second scope interoperate with the first, you define virtual names for the three
channels, “C1” for physical name “C0”, “C2” for physical name “C1”, “C3” for physical name “C2”, so that
now the virtual names for the second scope match the physical names for the first. So we have:
Scope 2 Scope 2
IVI Foundation Meeting Minutes 34 May 2011
Virtual Physical
C1 C0
C2 C1
C3 C2
We’ve identified two opportunities for error with this configuration.
1. The driver may map virtual name to physical name and then make calls to other channel
methods or properties using the physical name. For example, the implementation of some
method may re-enter the driver by accessing properties. However, if the method and property
both translate from virtual names to physical names the conversion may be applied twice
(resulting in C2 => C1 => C0).
2. A client may use GetNames() to get a list of physical names. If the client then turns around
and uses a physical name where a virtual name is accepted, and the physical name is also a
virtual name, the driver will treat the name as a virtual name and map it to the corresponding
physical name.
Some of our drivers exhibit #1. WRT #2, since the IVI API’s all specify that the get_Name() function
return the physical name, any software that discovers the names using get_Name() will attempt to call
the driver with physical names. However, if the driver client had defined virtual names that replace the
physical names, the API will treat these names as virtual names and re-map them giving an incorrect
result. We suspect that NI Switch Executive works this way.
Since the configuration server allows you to use a virtual name that is identical to a physical name for
the same repeated capability, this is not a theoretical situation.
Section 5.9.2 of IVI-3.1 says that drivers shall replace virtual identifier with its matched string even if the
virtual identifier is also a valid physical identifier. It also says that the driver do this replacement only
once per each call by the user. Notice that if drivers did this, problem #1 would not occur.
Resolution (2011-05-20:#03): Joe Mueller moves that the Technical Committee create a subcommittee
to assess and make a recommendation to solve or mitigate the problem with overlap between virtual
and physical identifiers. Teresa Lopes seconded.
IVI Foundation Meeting Minutes 35 May 2011
5 YES votes. 0 NO votes. The resolution is approved.
Jon Bellin volunteered to chair the subcommittee. John Harvey, Joe Mueller, Kirk Fertitta volunteered to
participate.
Action Item: Jon Bellin or Vesna Jadric to set up first conference call by June 30, 2011.
Flaw in VISA Formatted I/O Definition
During the VISA.NET Working Group meeting, it was discovered that a corner exists in which END might
not be sent with a block of data even though the user requested it to be via the SendEnd property. The
case that was discussed would occur if the following are true:
the client’s call to one of Write functions exactly fills the buffer
the client’s intention was that such call was to be sent to the instrument with END on the last
byte
the client enabled the SendEnd property
Normally (i.e., when the buffer is not exactly full), END is sent with the last byte when the user calls
Flush. However, in this corner case, the buffer is empty when the user calls Flush. This is because VISA
automatically flushes the buffer when it becomes full (and before the attempts to write additional
bytes). When this automatic flushing occurs, END is not sent even if the SendEnd property is enabled.
The behavior was confirmed by visual inspection of the Agilent and NI implements of VISA C.
Joe Mueller out that the problem could occur whenever the buffer is flushed by something other than
an explicit call to Flush by the user. This might occur if, for example, the VISA implementation had a
policy of automatically flushing the buffer when it was within 8 bytes of being full.
IVI Foundation Meeting Minutes 36 May 2011
Resolution (2011-05-20:#04): Joe Mueller moves that VISA working group make a proposal to solve or
mitigate this problem, to determine if it exists in VISA COM, and to avoid it in VISA.NET. Teresa Lopes
seconded.
7 YES votes. 0 NO votes. The resolution is approved.
Action Item: Dan Mondrik to initiate the effort.
Proposal for a File Format Working Group
Rob Purser proposed that we create a File Format working group with the following charter:
Overview
The File Format working group will investigate and propose a standard file format for the
interchange of data (such as waveforms and spectra) between instruments, and between
instruments and software applications. The exchange of instrument configuration information
(other than what is needed to interpret the data in the file) is outside the charter of this working
group.
Statement of Work
The activities of the working group will include:
Investigation of existing file formats that could be used to represent data for Test and
Measurement instruments.
Selection and definition of one or more file formats for instruments to transfer data.
If the working group elects to pursue, definition of standard APIs associated with reading and
writing the file format(s).
If the working group elects to pursue, development of a shared component and source code
associated with reading and writing the file format(s).
Writing of specifications describing the items above
Development of a self certification test suite and reference implementations and examples of
the file format
At this time, the working group is not requesting standard numbers be assigned, but it is likely that
one or more chapters will be required to develop this standard.
IVI Foundation Meeting Minutes 37 May 2011
Support and Proposed Chairperson
This working group would be chaired by Rob Purser of MathWorks. The creation of the group is
supported by Agilent, MathWorks, Rohde & Schwarz, and Tektronix. The chairperson will call for
other member companies to consider participating.
Rob Purser volunteered to serve as chairman.
Resolution (2011-05-20:#05): Rob Purser moves that we create a File Format working group with the above charter. Joe Mueller seconded.
7 YES votes. 0 NO votes. The resolution is approved.
Action Item: Vesna to add this to the In Progress tab on the Life Cycle document.
Discuss Upcoming Meetings The next meeting will be October 17th – 19th (Monday – Wednesday) in Austin.
Working Group Time
IVI.NET ¼ day
IVI Virtual Name / Physical Identifier issue ¼ day
Technical Committee Meeting and BoD ½ day
Marketing Committee General ¼ day
Shared Components Management 1 hr
VISA ¼ day
VISA.NET 1 day
VISA Automatic Flushing Issue 1 hour
Data Conversion - FGen ½ day
File Format ½ to 1 day
DataConversion can conflict with anything except File Format and Technical Committee/BoD.
IVI Foundation Meeting Minutes 38 May 2011
Criteria for IVI meeting locations (from Feb 2010 TC meeting minutes):
For US meetings:
Major airport hub that allows most members a non-stop flight (examples: Denver, Dallas, Orlando, Las Vegas, Chicago, St Louis, Los Angeles, Atlanta)
Hotel journey is 20 minutes on Google maps.
Sleeping room price should target $100 but not exceed $130. Willing to go higher on sleeping room price if it is walking distance to restaurants and avoids rental car.
Internet bundled into the cost.
Tentative cities for 2012:
Feb 2012 – Atlanta or Los Angeles
May 2012 – Munich
October 2012 – Boston
Summary of Action Items Created at the May 2011 Technical Committee Meeting
Owner Action Item Status
Vesna Jadric Assign a spec # for VISA PXI Plug-in Specification. It
should be in the form of IVI-6.?.
Vesna Jadric Add the IVI Digitizer Minor Specifications work
(Resolution 2011-05-20:#02) to the In Progress tab of
the Lifecycle Status spreadsheet.
Vesna Jadric Add the File Format working group (Resolution 2011-
05-20:#05) to the In Progress tab of the Lifecycle
Status spreadsheet.
Jon Bellin,
Vesna Jadric
Set up first conference call (by June 30, 2011) on the
IVI Virtual/Physical Identifier issue.
Dan Mondrik Initiate effort on VISA Automatic Flushing issue
IVI Foundation Meeting Minutes 39 May 2011
Owner Action Item Status
Adjourn
Meeting Adjourned.
Chapter 6 IVI BoD Meeting May 20, 2011
Called to order at: 13:51 2011-05-20
IVI Foundation Meeting Minutes 40 May 2011
Directors in attendance
Present Director Company
Don Essner DRS Sustainment Systems, inc
X Rob Purser MathWorks
X Kirk Fertitta Pacific MindWorks, Inc.
X Jason Schares Rockwell Collins
John Ryland Keithley
X Joe Mueller Agilent Technologies
X Jon Bellin National Instruments
X Jochen Wolle Rohde & Schwarz
Quorum is a majority of directors. 6/8 satisfies the requirement.
Agenda Review
IVI BOD MEETING MAY 20, 2011
1. DIRECTORS IN ATTENDANCE
2. AGENDA REVIEW
3. REMINDER OF THE IP POLICY, ANTI-TRUST, AND DUTY OF TRUST OF DIRECTORS
4. RESOLUTIONS PASSED BY ELECTRONIC MEANS SINCE LAST MEETING
5. INPUTS REGARDING MINUTES OF PREVIOUS MEETING
5.1 ACTION ITEMS FROM PREVIOUS MEETING
6. RECOMMENDATION FROM TC THAT THE BOD APPROVE HISLIP
7. SHARED COMPONENT WORKING GROUP – SOURCE CODE CONTROL NEED
8. FINANCIAL REPORT
Reminder of the IP Policy, Anti-trust, and Duty of Trust of Directors
IVI Foundation Meeting Minutes 41 May 2011
The IVI Foundation has an IP policy that could require that some of your corporations’ IP be
licensed to the IVI Foundation and its members at no cost. Every participant in the IVI meetings
should be familiar with the obligations that participation in the standard incurs on your company.
Every member of the consortium is encouraged to familiarize themselves with legal requirements
regarding anti-trust violations. Members need to be cautious and refrain from discussing markets
and pricing.
Directors have a duty to the IVI Foundation. They are legally and ethically obligated to do the
“right thing” for the IVI Foundation since they serve as a principal of that organization, if this
conflicts with other responsibilities such as their duty to their employer, they need to take
appropriate actions to resolve the conflict of interest.
Resolutions passed by electronic means since last meeting
No motions were passed by the Board of Directors since the last face-face meeting:
Inputs Regarding Minutes of Previous Meeting
None expressed
Action Items from Previous Meeting
ITEM OWNER UPDATE
Draft letter to Scott Rust with thanks for
years of service to IVI
Bob Helsel Done
Recommendation from TC that the BoD approve HiSLIP
IVI Foundation Meeting Minutes 42 May 2011
TC moves that the BoD approve the proposed HiSLIP 1.1 specification here:
