Teledyne LeCroy BTTracer_Trainer - BTTrainer Users Manual - Manual (Page 240)

222
CATC BTT RAINER 2.11 C HAPTER
User’s Manual
Return value
• “Success”
• “Failure”
• “Failed: Busy”
• “Failed: Invalid handle”
• “Failed: Invalid parameter”
• “Failed: Media busy”
• “Failed: Not connected”
• “Failed: Packet too small”
Comments
Sends a file to the OBEX directory of the server.
If directory names are included in either path argument, be sure to use
double-slashes to separate components (e.g., “temp1\\temp2\\file-
name.txt”). Using single slashes will cause errors.
Note that the second argument may be omitted, in which case the object
will be stored to the server’s OBEX directory with the same name it has on
the client.
Examples
In these examples, the server’s OBEX directory is assumed to be
c:\obexdir.
#store file to "file.txt" in server’s OBEX directory
# (i.e., c:\obexdir\file.txt)
OBEXClientPut("c:\\temp\\file.txt");
#store file to "newfile.txt" in server’s OBEX dir
# (i.e., c:\obexdir\newfile.txt)
OBEXClientPut("c:\\temp\\file.txt", "newfile.txt");
#store file to "newfile.txt" in temp dir under OBEX dir
# (i.e., c:\obexdir\temp\newfile.txt)
OBEXClientPut("c:\\temp\\file.txt", "temp\\newfile.txt");
RemotePath Path and name
of object to be
stored on
server.
Name-only
portion of
LocalPath
argument
Path is relative to server’s OBEX directory.
Example: If the server’s OBEX directory is
C:\Temp, a RemotePath of “file.txt” would cause
the server to save the file to “C:\Temp\file.txt”.
Note that you cannot save a file to an absolute
path on the server.
Parameter Meaning Default Value Comments