07-13-2010 02:25 PM
no solution???
07-13-2010 02:46 PM
If that is the code that is generating the serial data, then the following modification to the example I showed you will read the values:
07-13-2010 04:16 PM
WHY DIDNOT you put visa write?
i need it in another stage or it will affect
07-13-2010 04:46 PM
What are you talking about? What VISA Write?
07-13-2010 05:05 PM
how did you do visa read in your modified example and you dont know visa write
i mean write string
07-13-2010 06:13 PM
The microprocessor code you uploaded does not require a write to send data. It's always sending data, which is the ADC_Read(0). It reads the port in each iteration. If it sees a "g" character it sets portd, bit 7 high, whatever that means. I don't see how this is related in any way to the ADC reading and sending of the value over the serial port. Did you write that code?
Adc_Read(0)
07-14-2010 09:58 AM
i wrote it , but i send g to microcontroller when an action happened in lab view
your example work well but it display yhe plot too fast , i made delay and it it give error
so i used string to unsigned byte array that u used ,i used it in basic read write and it doing well
but i cant detect the frequency do you know about it?
07-14-2010 10:32 AM
What do you mean it displays the plot too fast, and what error did you get?
07-14-2010 12:52 PM
the wave pass too fast on display may be it reads too many bytes so i made delay too see it
and message error appear
dont care
i used it in basic one and it go well
how to measure the frequency
i used tone in express but it didnt work
07-14-2010 01:20 PM
How many packets of data is your controller sending per second?
If you are just banging out bytes as fast as possible, and LabVIEW code is running fast enough to keep up, then yes, data is going to be just flying across a chart. And if you put in a delay to slow it down, then the error you are getting is probably due to a buffer overflow. I don't know why you didn't post the error code like Smercurio asked. Providing answers to the questions you are asked will help give you more relevant information and answers to whatever your original questions might be. Also, don't say things like "it didn't work". Tell us how it didn't work. Was there an error? Were there results that just didn't match what you expected? You got zeroes, no data? What?
What kind of frequency are you trying to measure? Is any kind of timing information provided as a part of the serial data stream? If you are trying to figure out a frequency based on the raw data coming packet by packet from your serial port, I don't know how good that analysis will be since you are basically just relying on the speed of your communication protocol to be the time base of your data.