Hi Andy,
I installed a WiFi network and very quickly rolled out the copper again as
It turned out the be too slow for anything other then Web Browsing, and
thats running on a 108Mb wifi!. The fact is, Wifi is awful for file
transfer. I found by asking around, most people reported 2MB files taking as
much as 20 minutes to transfer. I personally found files > 100MB are
impossibly tedious to transfer!
....However...
Wifi is great for not having to run cables.
I still think that your idea is good! - if you only have to transfer files
less then 1MB no more often then about once an hour (I am being quite
conservatice here), then you can do this with no problems, but you must
design your code so that the program checks...
1) that the network folder your looking for is accessable, if so then copy
the file
2) that the file got copied, if not raise a flag and keep trying
periodically.
Wifi Networks do go down intermittantly, usually for a few seconds. I guess
if some bright spark in the neighbourhood starts his two-stroke lawnmower,
your wifi card/dongle can drop connection!
Wifi works on 2.4 GHz, so microwave ovens are not good, neither are wireless
computer peripherals (mice etc), but it wont do too much harm (may lost 50%
of your bandwidth, but can still communicate). Your 868.3 MHz should be
fine, but I suggest you buy two USB interface cards (around �30 each) to
validate the idea before you go further. Remeber you will save Mega� if you
can avoid copper.
Lastly, Get lots of Wifi Repeaters if you have a large area, most specified
transfer rates are only good when both talking devices are within 2m. At 30m
distance I would only expect <1Mb/s transfer without a repeater!
Hope this sheds some light!!
Regards
Dave.
"Professor Barney"
wrote in message
news:1100128879.5lLLdmOokkHOwhrYFQJIdw@teranews...
> Hi folks,
>
> basically just looking for initial advice / experience here. I 'm a test
> engineer in a fairly large factory, where most of our test equipment runs
> LabVIEW. All of our test fixtures could in theory be networked, allowing
> central data collection and analysis which is very useful in our
> environment. Each spur to the main network however would be a considerable
> investment - running the cables, safety testing etc.. means each each spur
> ould cost upwards of $300.00.
>
> I have considered having one pc (with a wireless hub) as being a central
> data collection point, with test pc's running wireless dongles, and wonder
> if anyone has any pointers or experience (good or bad) they can share with
> me before I dive in????
>
> Just in case it is relevant, we do a considerable ammount of product
testing
> in the 868.3 MHz range, in shielded fixtures, close to the point of use -
> don't know if this could interfere with Bluetooth or not??
>
> All the best
>
> Andy
>
>
