Prev: Divergence application
Next: Reading a Header txt file
From: Stephen on 29 Jul 2010 17:57 Gordon Weast <gweast(a)mathworks.com> wrote in message <i2son2$hug$1(a)fred.mathworks.com>... > Stephen, > > How big is your outputlog? There can be issues with very large > log transfers. You can split it up by transferring smaller > ranges. > > data1 = target.outputlog(1:10000); > data2 = target.outputlog(10001:20000); > etc. > > Then put them all together. > > Do you have trouble getting smaller pieces of the outputlog? > > If this workaround doesn't work, then please contact tech support > and we'll look deeper into it. I can transfer ~0.5 MB of data without issue, but larger datasets cause the error. Breaking up the outputLog into parts doesn't work. Even if I issue the command "data1 = target.outputLog(1,1)" the error is thrown and nothing is returned. On a different machine with different hardware (single core processor, less RAM, etc), data transfers of ~55 MB complete in ~8 seconds; however, when I try to extract only one byte from that larger dataset (ie, data1 = target2.outputLog(1,1)), it still takes ~8 seconds. Appears as if it's still transferring the entire dataset over the network. Thank you for your help. Let me know if you have any other suggestions. My thought is that I'll have to get a different motherboard anyways that will allow use of the second core, so hopefully with the new motherboard, the data transfer problem will go away. Any suggestions on a motherboard that will work with an Intel Core 2 Duo E8500 3.16 GHz and enable xpc's use of the second core?? |