list of serial compatibility VI error codes?

[vsaone]

Where does one find a list of what the error codes mean for the serial compatibility VIs used for LV PDA serial communications?  The built-in help does not seem to reference this anywhare and when I use the PDA error handler VI all I get is the error number.

Thanks,

Jerry

[Ben]

The master list of error codes stopped being published years ago.

Pasting the error code into a error cluster on VI FP (on the target machine*), set the error bit then right click on the error cluster and select "Explain Error". That should give you a description of the error.

Ben

* On the target machine - Since error codes can be different on different platforms, trying to get the explanation of an error code on a different machine could be wrong or different. So if you get the error running on a cFP unit, make sure the error cluster you are using is on the FP of a VI for the proper target.

[vsaone]

Ben,

Thanks for the help but I do not seem to be able to get your method to work.  I am developing an application for a PDA, so I assume that the PDA is my "target machine".  I place an error cluster on the FP of the PDA app.  However when run the app I am not able to right-click on the error cluster either on the PDA or when in debugging step-mode on the PC development machine.  Sorry for not understanding - could you please clarify the steps to take in more detail?

Jerry

[Ben]

---

vsaone wrote:

Ben,

Thanks for the help but I do not seem to be able to get your method to work.  I am developing an application for a PDA, so I assume that the PDA is my "target machine".  I place an error cluster on the FP of the PDA app.  However when run the app I am not able to right-click on the error cluster either on the PDA or when in debugging step-mode on the PC development machine.  Sorry for not understanding - could you please clarify the steps to take in more detail?

Jerry

---

I was explaining how to find out what the error code means.

In the project...

1) Create a new VI on the target PDA.

2) Drop an error cluster on the FP of the new VI.

3) Type in the error code you want to translate.

4) Set the error boolean true.

5) Right-click on error cluster and select "Expalin Error"

After doing the above you should see a window that explains the error code. There is no need to run the VI to get the "Exaplain Error" to work.

Ben

[vsaone]

please forgive my thickheadedness, but how do I view a VI on the PDA if I don't run it?  I'm using LV PDA module, so all the development is done on the PC side. I thought the only way to view a VI on the PDA is to compile an executable and run it on the PDA or am I missing something simple?

[Ben · Accepted solution]

---

vsaone wrote:
please forgive my thickheadedness, ...

---

Don't worry about that!

I have never written an app for a PDA but I have supported others so I had to do a double-check.

In your project, right-click on the PDA target and choose New VI.

The FP that opens will open in the context of teh PDA.

At that point just follow the above directions (I verified these work).

Still just trying to help,

Ben

[vsaone]

Ben,

OK, I get it now and that was a trick I had yet to discover about LV.  However, the error code explanations that I am seeing do not make much sense.  Perhaps you can help me understand these two errors:

I get Error 55 when using the Serial Port Init VI if my COM port does not make a connection (I am trying to set up a bluetooth serial connection using COM8 on the PDA).  The "explain error" says this means "the network operation is in progress".  This does not seem to have anything to do with initializing a serial port and is also not very helpful for how to correct the problem?  I also get Error 8 when using Serial Port Read VI and the explain error says this means "File permissions error. You do not have correct permissions for the file."  Since I am not trying to read a file, this also doesn't make much sense.  Could I be seeing the wrong explanations since I am viewing the error explanations on the PC instead of on the PDA (I am doing this in a VI created as a Windows Mobile 5.0 Pocket PC Device in Project Explorer) or is this as good as it gets?

Jerry

[Ben]

Hi Jerry,

If I give you some good answers off hand I would, so let me make the following requests.

1) Start a new thread about those error codes (since those new questions and th searchers of the future may not find those error codes under your original Q tilte.)

2) If one of the above replies was helpful in your original Q, could you mark it as a solution?

I'll watch the forum to see how your error code question gets answered.

Have fun!

Ben

[vsaone]

Ben,

I marked your 2nd to last answer as a final solution to my original question and will post the questions about the meaning of the error codes in another thread.  My political commentary is that this procedure seems a very curious and obscure method for checking into error codes. I guess it is too much to ask that software creators provide complete, concise and straightforward user documentation of thier product.  NI has the "complete" part mostly handled, but the concise and straightforward leaves a bit of room for improvement IMHO. Thanks,

Jerry

[Ben]

---

vsaone wrote:

Ben,

I marked your 2nd to last answer as a final solution to my original question and will post the questions about the meaning of the error codes in another thread.  My political commentary is that this procedure seems a very curious and obscure method for checking into error codes. I guess it is too much to ask that software creators provide complete, concise and straightforward user documentation of thier product.  NI has the "complete" part mostly handled, but the concise and straightforward leaves a bit of room for improvement IMHO. Thanks,

Jerry

---

Thank you Jerry.

I used to have two 3-ring binders to hold all of the error codes possible in VMS version 4.0 (Virtual Memory System, an OS that ran on VAXes years ago). Those error coes only applied to a single hardware platform (the VAX).

LV runs on many hardware platforms each of which can report errors that can not happen on the other platforms. So rather than report every possible meaning of an error code, NI's error handler allows the error codes to be updated by every software package that can produce its own unique errors.

I hope this helps you understand some of the issue that are addressed by NI's way of doing things.

Have fun!

Ben