LabVIEW
binary to ascii from 10 bit ADC
There is no such thing as "ASCII format". Any formatted output is necessarily ASCII, so you should probably be a bit more specific.
- How does the original 10bit data look like? (10 booleans, U16 masked to 10 bits, binary string, etc.)
- How should the output look like? (binary string, human redable formatted output, etc.)
Best would be if you could attach a simple example that contains typical input data in a control (as default value) or diagram constant. Also explain how the output should look like. Thanks! 🙂
Waveform graphs don't display "ASCII data". You just need to cast your raw string to the correct numeric data type, possibly built a waveform, and send it to the waveform graph.
@MF Hussin wrote:
... Then convert it to ASCII to display the waveform. ...
you should use the Byte Array to String function:
This will convert an array of U8 into a string of ASCII codes
Ton
Message Edited by TonP on 02-16-2007 08:58 AM
LabVIEW user groep 
Simply have a look at your code, nothing makes much sense.
- Server: Why are you possibly formatting your numbers as binary (a series of ASCII characters 0 or 1) instead of sending the raw binary string?
- Server: You are casting the size to a string (4 bytes) but then only send the last byte formatted as binary text. You are stripping 32bits of potential information to 8 bits, then use 64 bits to transfer that information.
- Server: you are casting 200 DBLs (1600bytes) and take only the last byte, which you send as binary formatted text, again using 8 bytes worth of information.
- Client: For the size, you are only reading four characters of binary formatted text, i.e. only 4 bits of information (!). You are casting four binary formatted characters as I32 Giving you a random, very large number.
- Client: Now you try to read a very large number of characters (see above), but you were actually sending only 8 bytes of binary formatted text, so that's all there is.
- Client: These 8 bytes you scan as binary and convert them to U8, which you are casting back to a string with 1 (!) character. 1 byte!
- Client: for some reason, you are casting this single byte to an array of DBLs. Unfortunately, there isn't even enough information for a single DBL element.
You seem to have a difficult time understanding the difference between binary string, binary formatted text, typcasting, formatting to string, scanning from string and seem to randomly mix these operation. They mean very different things!
Your FOR loops have autoindexing input tunnels, but plain output tunnels, thus you are only retaining the information from the last iteration.
All you have to do is typecasting your size and data to a string each, send it via the network, and typecast it back to the original datatype on the receiving end. Try it! 🙂
You seem to have used the shipping example "simple data client|server" which basically does exactly want you want already. For some reason, you mutiliated the data handling beyond recognition. 😉 Go back to the virgin example code, it is working and does all you are trying to do already. Really! 😄
Message Edited by altenbach on 02-17-2007 09:07 AM
