08-02-2011 08:52 AM
08-03-2011 02:18 PM
vgravel,
Depending on where you are trying to pass data to there are a number of options: FIFO, Network Streams, Shared Variables etc.
Here is a good over view of Real-Time communication methods: http://zone.ni.com/devzone/cda/tut/p/id/3105
And here are some other articles which may help:
http://digital.ni.com/public.nsf/allkb/4C0DD3F01279A34286256F86007F031A?OpenDocument
http://digital.ni.com/public.nsf/allkb/7AE7075AF1B2C58486256AED006A029F?OpenDocument
http://zone.ni.com/devzone/cda/tut/p/id/12267
I hope this gets you going 🙂
08-04-2011 08:03 AM
Hello Samuel,
I'm trying to pass data to a laptop/desktop computer for saving and display purpose.
The amount of data is 1920000 I16 per seconds... I'm able to pass this amount of data but I will have to be able to at least double that amount in a near future.
From what I've read, casting to string and sending by TCP/IP is the best way to do that. I cannont lose any of these data (so UDP is not an option).
This is way i'm wondering if there is a way to compress those string to get a better throughput.
Thanks!
Vincent
08-04-2011 02:16 PM
Hi,
I cant think of an explicit way to compress strings for TCP/IP for Real-Time systems, but one of the links above may be helpful in determining the best way to pass the amount of data your requesting. Here is also an article on Optimizing TCP/IP in Real-Time:
http://digital.ni.com/public.nsf/allkb/DA6777E0180003D0862569900059C048?OpenDocument
🙂
08-04-2011 04:04 PM
The amount of data is 1920000 I16 per seconds
Thats 4 MBytes or 32 Mbits per sec. You obviously need at least a 100 Mbps net to handle that.
Keep in mind that random data does not compress as well as ASCII text. If you need lossless compression, your savings are likely to be 20% at best. Is the CPU overhead for compressing and decompressing that amount of data worth the savings?
Blog for (mostly LabVIEW) programmers: Tips And Tricks