wait ms vi speedy33

[hostile]

When trying to program the speedy33 with labview I noticed that you are not allowed to use any of the timer fuctions like wait so many ms.   I am trying to emulate a uart that will recieve commands and need the capablitly to wait a certain amount of time beofre sending the command.  Is there a way around this ?

[DuffmanSays]

The Tick Count and Wait timing functions should both be available for you to program your application with LabVIEW DSP. Do you not see these on your functions pallet or does your code give you an error when you attempt to use these functions? I assume the VI you are working with is targeted to the Speedy-33 project?

[hostile]

We keep getting "type not supported by target" for anything involving timing or signal generation.  We are able to flash the speedy33 with simple VIs made up of for loops and setting a Di/o line high or low.  

[DuffmanSays]

According to the error message you listed, I believe the problem is with a numeric representation used in your application. Specifically, the LabVIEW DSP module allows for only certain representations of numeric values. If you are using a representation other than these supported values (such as U64), you will receive a similar error. Please take a look at the Data Types Not Supported by Embedded Targets knowledgebase that discusses this in more depth. If you double click the error when displayed on the error list, LabVIEW will show you the wire which contains the inappropriate data type.

As another test of the timing functions specifically, I would suggest constructing a while loop that writes an increasing U8 value to the LED bank. You can use the Wait VI (with a U32 constant or control) to set the rate of the updates. I have verified that this will successfully perform a binary count on the LEDs of the Speedy-33. Please post back if you still receive this error after taking a look at the data types used in your application. Thanks,

Mike D.
National Instruments
Applications Engineer

[hostile]

Even when using a control or constant of I32 type, I still get the error " wait (ms) not supported by target"
I am using 7.1 embedded labview with a target of speedy33.  any more help would be greatly appreciated.

[DuffmanSays]

This is quite confusing that you would still be getting an error for an unsupported feature. The comprehensive list of features supported by LabVIEW 7.1 Embedded does state that all timing VIs are supported. Would it be at all possible to post the code you have tried and possibly a screenshot of the error? I can take a look and test out the code on a Speedy-33. Thanks,

Mike D.

[hostile]

after upgrading labview from 8.0 to 8.2, the timer functions worked.

[DuffmanSays]

I am quite surprised to hear that these functions were not working for you in LabVIEW 8.0! While I thought you were working with LabVIEW Embedded 7.1, I would have found some documentation on an issue such as this one. I will definitely look further into whether this was a known issue in LabVIEW Embedded 8.0. Thank you for posting back about this. Good luck with your application!

Mike D.
National Instruments
Applications Engineer

[hostile]

to clear up the version.
We used a school license pack for Texas A&M.  It is a bunch of cds for labview 8.0, but it includes embeded 7.1.  so we were using embeded 7.1 for the speedy.  We then upgraded everything to 8.2 including the embeded and have not run into any more problems with the timer functions. 

Now we are in the process of trying to send data out of the speedy33 over a DI/O line as a uart.  This doesn't look possible though with out the ability to use the visa serial modules.   No access to a clock signal

thanks for the fast replies

[DuffmanSays]

Thanks very much for clarifying those versions. As I mentioned, I will look further to see if there was a known issue in LabVIEW 7.1 Embedded.

In regard to your application, I believe the speedy-33 could still be used as a UART, even if it does have limited functionality. You mentioned that you do not have access to the serial modules, but you may be able to build this protocol yourself. Essentially you can program the specific details of the protocol and control timing with waits. You should keep in mind the limitation of the smallest delay you can impose – 1ms. This may limit your total data rate, but it still may be possible to implement the protocol you desire. This was just a thought, good luck with your application!