Scan list using Switch Executive

I have a number of signal routes using multiple switch cards that I have set up using switch executive. I want to create a scan list that will switch each of my routes in turn each time I see a hardware trigger on the trigger inputs of my switches.
I have looked at some examples in TestStand and can see that if I use the IVI Switch Step using the IVI Switching setting that I can set up a scan list but that seems to be only for one switch card, I have two that I need to route signals to a Digitizer. I can not see a way of using my routes set up using Switch Executive.
I can either use LabView2013 or TestStand 2013 to do this.
Some help would be most appreciated?
Wayne

Hi Wayne,
If I have understood your problem correctly, this VI in LabVIEW sound like it does what you are after.
NI Switch Route Trigger Input
Also at the bottom of this LINK are some examples of scan lists, perhaps you will be able to adapt this to your needs
Please let me know how you get on
Kevin R
Applications Engineer
National Instruments UK&Ireland

Similar Messages

Cannot connect to com1 in PXI2530 using Switch Executive

I have a PXI2530 configured using Switch Executive 2.10. The first 60 Channels are setup with my signal names on ch0 - ch59. Com0, 1, 2 and 3 are my Instrument connections. The IVI Driver Sessions has Driver Setup set to Topology:2530/1-Wire Octal 16x1 Mux.
When I try to configure either a Channel, Route or a Group, there is only a com0 pin and no com1, 2, 3, 4, 5, 6 or 7. There is no way to connect to any pin beyond ch15.
The configuration looks like it is setup for a 128:1 mux, but when I try to connect ch16 to com0, it cannot complete the route. Ch16 cannot be connected to com0 or any channel in the list. Any idea what I am doing wrong?
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

http://forums.ni.com/ni/board/message?board.id=320&message.id=633
Duplicate threadMessage Edited by Berto on 02-28-2006 12:15 PM

Cannot connect to com1 using Switch Executive

I have a PXI2530 configured using Switch Executive 2.10. The first 60 Channels are setup with my signal names on ch0 - ch59. Com0, 1, 2 and 3 are my Instrument connections. The IVI Driver Sessions has Driver Setup set to Topology:2530/1-Wire Octal 16x1 Mux.
When I try to configure either a Channel, Route or a Group, there is only a com0 pin and no com1, 2, 3, 4, 5, 6 or 7. There is no way to connect to any pin beyond ch15.
The configuration looks like it is setup for a 128:1 mux, but when I try to connect ch16 to com0, it cannot complete the route. Ch16 cannot be connected to com0 or any channel in the list. Any idea what I am doing wrong?
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

Michael,
What probably happened is that originally the NISE vd was created using the 128x1 topology. If the driver session is changed to another topology (like Octal 16x1 Mux) and saved the linked from the NISE vd and the old topology still exists until you close MAX and reopen it. When MAx opens it establishes a link between the NISE vd and driver session which remains in memory until MAX is closed and reopened.
Guy Ferraro
Switch Product Support Engineer
NI - USA

How do I associate switches in a four layer relay tree using Switch Executive

I have a three layer relay tree, controlled with a PXI-2567, to route an instrument input to 16 DUT channels. How do I create aliases in Switch Executive to turn the appropriate set of three relays on and off to route the input signal to one of the channels?

Bob,
Here is what you need to do to be able to call 2 end channels and create a route though 3 layers.
1) You have to tell NISE how the independent relays are connected to each other. You will do that by creating Hardwires.
2) You need to tell NISE that you want the channels connected to the hardwires to be used for routing. You will do that by marking the connected channels as "Reserved for Routing".
3) You can name the end channels according to your topology. COM for the single input channel and CH0 to CH15 for the output channels by creating aliases.
In the route editor, you will only need to create a route between COM and CHx and NISE will find the appropriate relays to close. In the route editor, if you only want to see the channels with an alias (COM, CH0, CH1 etc...) select in Options "Hide channels without aliases"

Route list in Switch Executive

How can I get (in LabVIEW) the list of the configured routes in Smy witch Executive session ?
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

There is a way of accessing the routes and route groups of a particular virtual device programaticaly. You will need to have session manager server installed.
1) Create an activeX session and connect to the session manager server 1.0.
2) Select "IInstrSessionMgr" for the Automation refnum
3) Enter your virtual device name in filter
4) Select "ReturnRouteGroups" or "ReturnRoutes" for Flags
5) Enter empty string in Category
6) Change the Variant to data (Array of string) to get the names of routes or route groups.
Regards
Attachments:
NISE_routes_and_route_groups.vi ‏71 KB

Switch Step Scan List

I am using the 2530B with dual 64x1 topology. In TestStand, I want to set up the IVI Switch Step to where it connects a channel off of each bank and then uses the DMM to record. In LabWindows I can use: "ch0->com0 & ch64->com4";
How would I do that using the IVI Switch Step? Under 'configure scan' then ScanList tab, I currently have ch0->com0 then ch64->com4 using No Action so that each set before DMM measures then each will disconnect with there own commands. Is there an easier way for this, although I have not tested this method? Forgive me if this seems common knowledge but this is first time I am using TestStand.

Are you asking about an easier way to disconnect the switch? If you could clarify some more about what you are trying to do, that would be great. Also, are you using Switch Executive?
Jacob R. | Applications Engineer | National Instruments

Switch Executive Libraries for LabVIEW 8.2

My company uses LabVIEW, TestStand, Switch Executive, and more. I'm in the process of setting up a new PC with LV8.2, TS3.5, and SE2.1. It seems, however, that this version of SE does not have libraries for LV8.2. There are directories on the CD for LV7.0, 7.1, and 8.0, but not 8.2. When I install, as expected, there is no option to get support for LV8.2-- only the other versions I listed. I need the nise.llb file but am not sure if I should just install the 8.0 version into my LabVIEW 8.2 directory. It just seems strange to me that the libraries for 8.2 are not there. Can someone please provide me some direction here?
I'm new here so please keep your responses at the "new college hire" level .
Thanks,
Greg

Hi TekGreg,
The attached file was written in the format of a KnowledgeBase document and details how you can use Switch Executive version 2.1 with LabVIEW 8.2. The workaround is simply to copy files from 8.0 to 8.2, but you want to make sure you copy them all. Let me know if you have further questions or if this does not resolve your issue!
Chad Erickson
Switch Product Support Engineer
NI - USA
Attachments:
Installing NI Switch Executive For LabVIEW 8.2.pdf ‏20 KB

Switch Executive error: -1074126826

The following error occasionally occurs when executing a Disconnect All TestStand step, Switch Executive:"Filename",Connect/Disconnect.
I Need a solution
Error, Error executing substep 'Post'. An error occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types' An error occurred while executing the step. Unexpected Error: Switch Executive failed to initialize for virtual device 'NLAWQAT_Rev01'. Details: NLAWQAT_Rev01_init returned an error: -1074126826 (0x%3). Source: TSIviStepTypes [Error Code: -1074126826, User-defined error code.]

Hi Ken,
does this occur if this switch is simulated too?
That error can sometimes point to a timeout error in trying to connect to the device itself.
Is there anything else going on at that point?
Does it occur even if you step your way through the sequence?
Does it ever occur on a cut down sequence?
You say a "Disconnect All" step. Do you mean you have a step type that does this (i.e. the IVI-C switch step type) or you have this set on the switching tab of another step type (i.e. using switch executive)?
What version of TestStand are you using?
What is the model and manufacturer of the switch? Can you provide the driver install for that switch?
Does it happen in the sequence editor, the operator interface or both? If both, which one does it happen in more?
Which IVI compliance package do you have installed, and what's your version of VISA.
Any other information you think is pertinent would also help.
Thanks
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Keep switch channel selected for multiple steps in a scan list

Hi,
I have 3 switches (PXI-2575), one to apply a source to a given line, one to apply a sink, a one to apply a DMM. I have all three switches triggering off each other as well as a DMM (PXI-4070). I apply a source to any given line with the source switch and then cycle through other lines using the DMM switch. Problem is i want to keep the wear on the relays of the source switch to a minimum (for each cycle through the DMM lines I'm selecting same source pin multiple times!). Is there a command for scan lists or some way of setting up the switches so that this can be done?
I thought it might be possible to use the debounce command ';' on its own to signify that i don't want to change the channel selection but this does not appear to work, the DMM times out whilst waiting for a trigger on the second reading. Simplified example scan list that i currently have:
Break Mode: No Action
Source Switch: ch0->com;;;;~ch0->com & ch1->com...
DMM Switch: ch100->com;~ch100->com & ch101->com;~ch101->com & ch102->com;~ch102->com & ch103->com;~ch103->com & ch100->com...
I've also tried selecting the same channel in subsquent scan list entries which flags up error saying explicit connection already exists between the channels.
So is the only possibility just to needlessly wear out the relays?!

Hi leon007,
I can understand your desire to keep the wear on the relays of the Source switch to a minimum. I have a few questions, but we should be able to get the application working without needlessly wearing out the relays.
1. Can I assume you are using NI-SWITCH to program this application? If you are using the NI-DAQmx Switch API, please let me know.
2. When you state "I have all three switches triggering off each other as well as a DMM", can I assume (leaving out the Sink switch for now) the scan advanced output of the Source switch (TTL0) is sent to the trigger input of the DMM switch (TTL0), the scan advanced output of the DMM switch (TTL1) is sent to the trigger source of the DMM (TTL1), and the measurement complete destination of the DMM (TTL2) is sent to the trigger input of the Source switch (TTL2)?
3. If you are still having troubles after this post, I would like to know the following so I can assist in testing the issue: What versions of NI-DAQmx and NI-SWITCH do you have installed?
OK, that's it for my questions. Now for yours. Unfortunately, the debounce command ';' didn't work because it is simply a dummy entry - without creating a connection no scan advanced signal will be sent. I've noticed this is not documented well in our help file, and I apologize for that. However, attempting to create a connection where one already exists should be an error. Either the user is attempting to redundantly connect channels (which shouldn't happen if niSwitch Get Relay Position is used), or there is a driver issue.
To keep the relay wear to a minimum, I want to suggest a couple of ideas.
1. Use only one trigger line for the DMM's measurement complete and one trigger line for all the switches scan advanced outputs. To use this option, it cannot matter in your application which switch operates first, and which operates last. The switch that always makes a connection (the DMM switch) will send a scan advanced output trigger with a set scan delay (configured in niSwitch Configure Scan Trigger) that should accommodate for all the switches. This option may add delay in your application, but you will save relay life.
2. Use the DAQmx Switch API and the '&&' command between seperate switch connections. In the DAQmx Switch API, you use just one scan list for all switch modules. For example, we would perform the example scan list entries you provided with the following scan list:
/Source/ch0->com && /DMM Switch/ch100->com; ~/DMM Switch/ch100->com & /DMM Switch/ch101->com; ~/DMM Switch/ch101->com & /DMM Switch/ch102->com; ~/DMM Switch/ch102->com & /DMM Switch/ch103->com; ~/Source/ch0->com & /Source/ch1->com && ~/DMM Switch/ch103->com & /DMM Switch/ch100->com...
The above connects the Source switch CH0 to COM, waits for the relays to settle, connects the DMM switch CH100 to COM, sends the scan advanced output signal, and waits for the trigger input before executing the next scan list entry. This method will keep an order to the madness, as you will have the power to decide which switch operates first, and which operates last.
Let me know if I assumed anything incorrectly or if neither option works for you!
Chad Erickson
Switch Product Support Engineer
NI - USA

In Switch Executive am I better off using manual or execution

If I close a relay using Switch Exec ( IVI Switch) in Test Stand 4.0, take a measurement then open that relay am I better off using manual or execution for the "life" of the step?
I want to make sure the switch is open after the open relay step is executed.

Hi Clint,
2nd Question: Exclusions
For mutual exclusions, you create a list of channels that should never connect to one another.
For set exclusions, you create two lists of channels. Channels from the first list should never connect to channels of the second list. For example, a set exclusion can be used to separate a high-power DC and RF signal.
In reference to the 2 to 4 relays: if they were closed at the same time, would the result be a connection between channels? If so, then you want to create an Exclusion of type Mutual and add these channels to the list.
1st Question: Aliases
The easy answer to the copy/paste question is to use the integrated Excel import/export feature. You can export your Virtual Device to file and open it in Microsoft Excel. From there, you can edit your configuration and copy the necessary aliases from one Route Group to a new one (using Excel's simple text editing features and/or advanced formulas). When you are satisfied with your changes, you can import your configuration back to a new or existing Virtual Device.
However, I believe the whole purpose of copying aliases between Route Groups was to create exclusions for one Route Group, but not the other. This is not possible. Exclusions can be created for the Virtual Device, and this exclusion then applies for all the Route Groups in that Virtual Device.
If you want one Route Group that obeys an exclusion, and a second Route Group that ignores the same exclusion, then one way to do this would be to create two individual Virtual Devices; the first Virtual Device configured with exclusions, the second not.
By the way, you can do this using the aforementioned Excel import/export feature.
Hope this helps. Let me know if you have further questions!
Chad Erickson
Switch Product Support Engineer
NI - USA

NI-2530B Switch Scan List

I am having issues with the 2530B reading in my scan list. I have had no issues until now. In Test Stand I create a scan list, Example: "ch0->com0 & com0->pcom1 & ch16->pcom1;". When I intialize, configure, initiate, etc the switch acts correctly. When I send it a scan list, Example: "ch0->com0 & com0->pcom1 & ch16->pcom1; ~ch0->com0 && ch1->com0;" (With mode using Software Trigger) it does not read anything in the list and does not open/close any switches. I have used this switch for awhile now but some odd reason I am having issues with it right now and can not figure it out.
To go a little farther, I use GetRelayPosition to step through each relay to check after I initiated the scan. When I use the second example scan, I get a response back of NISWITCH_VAL_OPEN (10) for all relays, but when I use the first scan, the one that works correctly, I get no repsonse back from GetRelayPosition and the return value stays at '0'. Everything seems odd. I have been using the Switch for months now and created hundreds of scan lists of different types but not sure why I am having these problems now.

Correct about relay position while scanning, but once I abort I can check then also correct? If so, that is what I did and still got the '10' for the one not working correctly and '0' for the one that worked instead of '11'. I am using Test Stand and using niswitch32 dll to call the functions. I have my own dll I create the scan list in. And yes, when I include ';' output signal to wait for software triggers that is the scan lists not working correctly. IIf my scan list just contains one scan through, it works. Which is odd because I have been using this switch, funcitons, and my own scan lists for months and not sure why this is happening now. I can include some code but the only code would be creation of a scan list and I provided what it looks like above.
InitWithTopology ( "Name", "2530/Independent", False, True, handle);
ConfigureScanTrigger (handle, 0.0, software trigger (3), none (0));
Create My Scan List
ConfigureScanList (handle, list, none(0) );
InitiateScan(handle);
Measure from external dmm
When my scan lists look like:
com0->pcom1 & com2->pcom3 & ch16->pcom1 & ch32->com2 & ch1->com0 & ch49->pcom3;
The DMM takes the correct reading and everything works.
When my scan lists looks like (Or anything involving multiple triggers):
com0->pcom1 & com2->pcom3 & ch16->pcom1 & ch32->com2 & ch1->com0 & ch49->pcom3; ~ch1->com0 & ch0->com0; ~ch49->pcom3 & ch48->pcom3 &
It does not work and nothing responds. It does not stop at the first output signal ';' and wait for a trigger as I do not even get a reading like the first scan list.

Conflict using simultaneously IVI Switch and Switch Executive ?

Hi,
I use IVI Switch and Switch Executive libraries in an Labwindows CVI project, and I meet some problems :
I call SE lib for InitSession/CloseSession/FindRoute and Connect/Disconnect (apply to any switch devices in the SE configuration).
I call IVI Switch lib for SelfTest and Reset (apply to a single device).
But when I do an IVI Switch Reset then a Switch Executive Connect or Disconnect, an error occurs : Switch Executive seems to ignore what IVI Switch operations do to the device ?
Also, can you tell me if :
niSE_OpenSession performs a self test for the devices in the config ? A reset ?
niSE_CloseSession performs a reset for the devices in the config ?
Thanks.

Hello,
the niSE session talks to underlying IVI drivers using the IVI Switch session underneath, so any additional opening of IVI Switch session to the same device will cause the two driver sessions (that keep the information about the state of the hardware connections) to be either one or both out of synch with the actual hardware state). Because of the architecture of the underlying IVI drivers, niSE session cannot know if and what someone did to the instrument using IVI Switch session.
Therefore, it is not adviseable to use IVI Switch session while having another session open to the same device. If you need to use the invasive operations - which is anything that changes the state of the device, such as Reset and possibly self-test (self-test may be implemented as an operation that cycles relays and it may not but you can't be sure), you must make sure that one session is open and closed before another type of session is open.
The ni Switch Executive Open Session calls IviSwtch_init (with ID Query and Reset set to true) and CloseSession closes the IVI Switch sessions with the call to Close. The niSE session does not make calls to either reset or self-test explicitly.
Always attempt to perform all the operations on the same piece of hardware using the same API. If you need to reset switches, use the niSE_DisconnectAll function. If you need to perform the self-test operation, open a session to IVI Switch and perform the self-test, and then close it before opening the session to niSE virtual device.
There is also a back-door possibility that you can obtain the IVI Switch session that has been open for the constituent devices by niSE, but you must make sure that whatever you do with that session leaves the state of the switch intact when you get back to making calls to the niSE session. If unsure, you can always call niSE_DisconnectAll() as the first thing coming back to the niSE session to ensure that the state stored in niSE session matches the state on the actual hardware.
Again, it is best not to use both sessions, but rather pick one and try to perform all operations with it before switching to another type of session.
Srdan Zirojevic

Switch Executive 2.0 and Deployment 3.0

I have Switch Executive 2.0 on my development computer producing the exported [switch].XML file.
Are there any problems or issues with importing this switch configuration file into
NI-Switch deployment version 3.0?
Background:A previous project using 2.0 into a 2.0 deployment worked fine.
Now my attempt to deploy into a deployment computer with a recently purchased NI-Switch deployment 3.0
does not configure the same switches properly.
The switch configuration Validation process does not work. It gives a cannot find IVI switches errors.
Scott Youngren

Hi Scott,
This error is common when the IVI configuration does not match on the development and deployment machine.
1. On the deployment machine, verify the IviConfigurationStore.xml file has been copied to the correct location.
The IVI Configuration Store XML file includes the IVI Logical Names and Driver Sessions information that can be seen in MAX.  With IVI Compliance Package 2.1.2 (which is installed with NI Switch Executive 2.0):
C:\Program Files\IVI\Data\IviConfigurationStore.xml
With IVI Compliance Package 3.2 (which is installed with NI Switch Executive 3.0):
C:\Documents and Settings\All Users\Application Data\IVI Foundation\IVI\IviConfigurationStore.xml
2. If you are using NI switches, then additionally verify the DAQmx device names in MAX (under Devices and Interfaces) match on the development and deployment machine.
Each IVI Driver Session configures a hardware asset, and the hardware asset is basically a pointer to the DAQmx Resource Descriptor (also known as a DAQmx device name). If the listed Resource Descriptors shown on the hardware tab of the IVI Driver Sessions do not match the DAQmx device names under Devices and Interfaces, you will get an error.
Let me know if this does not resolve your issue!
Chad Erickson
Switch Product Support Engineer
NI - USA

Update Switch Configuration from Switch Executive 2.1 to 3.5

Hi everybody,
I tried to update from Switch Executive 2.1 to 3.5 and had to find out, that my configurations have stoppped working. To me, it looks like 3.5 doesn't like my IVI configuration for the switching modules.
The Verify function in MAX tells me that the PXI cards are not accessible. The frontpage of the switch configuration shows no configurations / terminal blocks.
Since the configuration consists of nine matrix cards with a lot of hardwires, I'd really appreciate a way to properly import the old configurations (xml files are available)
Any ideas?
Cheers
Oli
Programming languages don't create bad code, programmers create bad code....
Solved!
Go to Solution.

Hey Oli,
Background:
By default, NISE 3.5 and later use the DAQmx API (instead of IVI) to directly control switch modules. This is different from previous versions, which required setting up an IVI session for each NI Switch module. You can still use IVI with NI Switch modules in NISE 3.5 and later, but this is not the default behavior.
The KB Sebastian referenced lists three different upgrade paths to use exported IVI Virtual devices in NISE 3.5 and later. As you've discovered, NISE 2.1 has fewer export formats, so we'll need to take the following steps:
Assumptions:
You have virtual devices created in NISE 2.1 (file format doesn't matter).
IVI Sessions and Logical names haven't been setup on your NISE 3.5 machine:
Action items:
Create IVI sessions and logical names. You could manually create the IVI sessions (as mentioned in the KB), but there's a MUCH easier method:
Right click on the NISE Virtual Devices tab and select 'Create New':
Click the 'auto create IVI devices' button. A dialogue will pop up... just click yes:
The NISE Create Virtual device window should now look like this:
Notice that we now have IVI devices. Sweet! So now just click cancel (yes, cancel)... we only used this dummy virtual device to simplify the IVI creation process.
If you look in MAX, it'll appear as if there still aren't any IVI devices:
Fear not, all we need to do is refresh. To do this, hit F5, and voila!:
So now all you need to do is change the IVI Logical name to whatever your old IVI Logical name was and then import as normal.
At this point, you should be operational using IVI devices in NISE 3.5 (if not, post up). If you'd like to go one step further and upgrade to purely DAQmx calls, just follow the steps in the 'Upgrading from IVI to NI-DAQmx' section. Note that once you've upgraded to DAQmx, you'll only be able to use exported Virtual devices with NISE 3.5 and later.
Have a great day!
-John Sullivan
Analog Engineer

I would appreciate it if someone could advise me as to the optimum resolution, dimensions and dpi for actual photographic slides that I am scanning for use in a Keynote Presentation, that will be projected in a large auditorium. I realize that most proje

I would appreciate it if someone could advise me as to the optimum resolution, dimensions and dpi for actual photographic slides that I am scanning for use in a Keynote Presentation, that will be projected in a large auditorium. I realize that most projectors in auditoriums that I will be using have 1024 x 1200 pixels, and possibly 1600 x 1200. There is no reference to this issue in the Keynote Tutorial supplied by Apple, and I have never found a definitive answer to this issue online (although there may be one).
Here’s my question: When scanning my photographic slides, what setting, from 72 dpi to 300 dpi, would result in the best image quality and use up the most efficient amount of space?
Here’s what two different photo slide scanning service suppliers have told me:
Supplier No. 1 tells me that they can scan slides to a size of 1544 x 1024 pixels, at 72 dpi, which will be 763 KB, and they refer to this as low resolution (a JPEG). However, I noticed when I looked at these scanned slides, the size of the slides varied, with a maximum of 1.8 MB. This supplier says that the dpi doesn’t matter when it comes to the quality of the final digital image, that it is the dimensions that matter. They say that if they scanned a slide to a higher resolution (2048 x 3072), they would still scan it at 72 dpi.
Supplier No. 2: They tell me that in order to have a high quality image made from a photographic slide (starting with a 35 mm slide, in all cases), I need to have a “1280 pixel dimension slide, a JPEG, at 300 dpi, that is 8 MB per image.” However, this supplier also offers, on its list of services, a “Standard Resolution JPEG (4MB file/image – 3088 x 2048), as well as a “High Resolution JPEG (8 MB file/image – 3088x2048).
I will be presenting my Keynotes with my MacBook Pro, and will not have a chance to try out the presentations in advance, since the lecture location is far from my home, so that is not an option.
I do not want to use up more memory than necessary on my laptop. I also want to have the best quality image.
One more question: When scanning images myself, on my own scanner, for my Keynote presentations, would I be better off scanning them as JPEGs or TIFFs? I have been told that a TIFF is better because it is less compressed.
Any enlightenment on this subject would be appreciated.
Thank you.

When it comes to Keynote, I try and start with a presentation that's 1680 x 1050 preset or something in that range. Most projectors that you'll get at a conference won't project much higher than that and if they run at a lower resolution, it's better to have the device downsize your Keynote. Anything is better than having the projector try and upsize your presentation... you work hard to make it look good, and it's mangled by some tired Epson projector.
As far as slides go, scan them in at 150 dpi or better, and make them at least the dimensions of your presentation. Keynote is really only wanting 72dpi, but I do them at 150, just in case I need to print out the presentation as a handout later, and having the pix at 150 dpi gives me a little help with their quality on a printer.
You'd probably have to drop in the 150 versions again if you output the Keynote to .pdf or Word or something, but at least you have the option.
And Gary's right (above) go ahead and scan them as TIFFs. Sooner or later you'll want to do something else with these slides (like make something for an iPad or the like) and having them as TIFFs keeps your presentation looking good.
Finally, and this is a big one, get to the location for your presentation ahead of time if you can, and plug the laptop in and see what you get. There's always connection problems. Don't let the AV bonehead tell you everything will work just fine ('... I don't have any adapters for a Mac...') . See it for yourself... you're the one that's standing up there. Unless it's your boss, then you better be really sure it works.

Scan list using Switch Executive

Similar Messages

Maybe you are looking for