06-26-2012 12:05 PM
I have old rs-232 protocol that switches baud rates during a transmission. It uses a combination of standard CVI rs-232 commands (opencomconfig) and low level outp commands. The software will run perfectly using NI-serial 1.6, but does not function on ni-serial 3.6. The protocol is timing critical and I need the low level functions working. I used CVILowLevelSupportDriverLoaded (); which returned a 1 (drivers loaded). Any suggestions?
06-28-2012 10:18 AM
Are you using two machines with the different versions of NI Serial? Or have you upgraded and lost program functionality?
Are you experiencing any errors when using NI-Serial 3.6? Any screenshots or messages would be helpful. Is there a particular function that the program is hanging on?
06-28-2012 10:55 AM
I am using two identical test racks/pc's. One has 3.6 the other 1.6. The low level transmit commands do not function on the 3.6 driver. I do not see any error message, it just does not function.
06-29-2012 04:47 PM
What serial device are you communicating with? Non National Instruments devices, like a serial port, use other drivers.
On what function does the program hang on when you debug through it?
07-02-2012 06:05 AM
We have a propriatry protocol that changes baud rates when transmitting data. When connecting a scope to the TX line the code will transmit correctly on Serial 1.6 but transmit nothing when using serial 3.6.
07-03-2012 01:28 PM
After upgrading to NI Serial 1.6 did you disconnect and reconnect the scope? This updates the firmware.
You may also want to consider using PortMon to compare what is happening in both cases. Save that information so that we can refer to it later.
I'll swing this by some people in R&D to see what they have to say.
Is installing the newer version and installing the older version a possibility until we see what the problem is?
What are the specs for the test racks?
07-05-2012 05:37 AM
We have one PXI setup with the original cvi 7.0 using ni-serial 1.6, the remaining test equipment has been upgraded to later version of CVI and newer ni-serial drivers. The code will run on the original setup but will not on ni-serial 3.6 +. Before upgrading all our systems to the latest drivers we need to test our production test code prior to release. As of now we are stuck on this comport issue.
07-06-2012 12:58 PM
Could you perform an NI I/O Trace on each machine to campare the calls made in each case? Here are some details on NI I/O Trace.