Yes, there is info about that, but in my opinion refers mostly to I2C communication where you have to externally pull up the SDA and SCL lines. The Vref is an output pin which you can use to pull something up (not used in my application). Used mostly when you want to shift level logic between 845x and device connected. When using SPI, you are selecting I/O Voltage Level which is in my opinion the same thing, but you are doing it inside 845x. There is no info in datasheet regarding pulling up SPI lines. I see it this way.
Don't understand. You mean it will not work without any device connected? I think I should see the signal on MOSI Output even if nothing is connected.
Anyway! I found the solution. The NI 8452 module I use last time is damaged! I have in my company few of them, I took the next one and problem disappears.
Conclusion:
Properly installed device with proper driver for your LabView version (very important) should be enough to run SPI example and see how it's working.
http://digital.ni.com/public.nsf/allkb/3F9B7A67207EF793862574BF00764C9F
I tried to delete the topic, but I cannot. Anyway the problem was associated with Streams Names, which should be unique. Till you are using streams in LabView there is no need to build "Stream Name" as full URL,
"ni.dex://host_name:context_name/endpoint_name". Context_name is optional when Streams works in LabView, but it's necessary to have this name when you are building exe files. The context_name is the name that identifies which application context the endpoint resides in. If somebody need more info, everything is here: http://www.ni.com/white-paper/12267/en/
Dawid's post in NI USB 845x SPI Problem was marked as the answer