02-09-2010 12:59 PM
LV_Pro wrote:The link is the same one I referenced in my earlier post, it is why I upgraded in October. I am using the "reset" that is described in that article, although it is more complex when you are using MAX tasks rather than doing it in LabVIEW.
Sorry, Just trying to help. Didn't mean to waste your time. Gosh you've gotta be getting frustrated!
02-10-2010 08:28 AM
Jeff, offering help is never a waste of my time. In this particular case, just having other people out there that are listening is a help. I really am not expecting any "magic bullet" solution, have a growing fear that it is the computer itself that may be the issue. Not sure how to sell that to the customer, might end up gong to WalMart and buying one, configuring it and then bringing it to them.
Thanks!
02-10-2010 09:47 AM
Cole,
Did you get any info from R&D, I'm not confident that the stuff we talked about has "solved" the problem.
02-15-2010 12:10 PM
Not a lot of experience with PCIe (vs PCI) boards. I guess my first question is, can a PCIe x1 board be used in a PCIe x16 slot. The @#%$!! HP computer that this test system is running on has all but the PCIe x16 slot blocked, the other two located under or too close to the power supply. The general concensus on correctig the problem I've been fighting in this thread is to move some of my USB off of the motherboard. Unfortunately this is made difficult by the above mentioned "design feature" that HP decided to incorporate. I guess my next question is whether anyone out there has any recommendations on a PCIe USB adapter board?
Growing rapidly older on this project! Not good, look at my avatar icon!
02-16-2010 12:22 PM
Hey Putnam,
I'm glad the x16 slot is at least open. You can use a x1 in a x16 slot, but you will only get the x1 performance. As far as which card to actually use, just try to stick with one that has the NEC chipset. We have seen the most reliable results with that chipset.
Officially, NI doesn't recommend one brand or specific card, but this guy on newegg.com has good reviews and should be plug and play. Let me know how that goes.
02-16-2010 03:07 PM
Unfortunately, as well as making all but the x16 slot unavailable, they also put it in a reduced height chassis. I ordered a StarTech PEXUSB4DP, will see if it is sufficient. Hope to have it installed this weekend, then maybe I can start worrying about other issues.
P
02-17-2010 06:08 PM
Good gosh Putnam,
Sorry to hear about everything you've gone through with this. Looking forward to hearing if everything will work for you.
02-18-2010 07:00 AM
An additional question. It has three available usb ports. Should I only put the USB6221 DAQ on it, only the USB-RS485/2 or both with all the non "DAQ" stuff on the motherboard's ports? The symptoms are that I loose comms with the DAQ or the serial ports, or both.
It is unfortunately being shipped to my home address, 125 miles the wrong way from my customer, but online purchase from a lot of vendors won't let you ship to other than the address on record with the credit card company. Then it is about 110 miles from there to the customer's. Glad I have a book on CD to listen to!
02-21-2010 11:39 PM
03-30-2010 08:28 AM - edited 03-30-2010 08:32 AM
I wanted to follow up with a status report. I did get a PCIe USB board, moved both of the NI devices, the USB6221 and the USB-RS485 units to it, and roughly a month later haven't seen the issues I was having. I don't know what the cause of the "glitches" on the motherboard's USB bus, but at least moving the critical ones off have seemingly cured the problem. I would like to say thank you to all that suggested cures, in particular to "Cole Train" and the NI R&D group that took the time to research this and come up with this answer, as well as keeping in touch with me "offline" to follow through.
I know that it isn't considered good form to mark your own post as the "answer", but as Cole Train's suggestion that has apparently resolved the problem was not given on the thread I will mark this as the solution to get the viewers, but as mentioned above, credit goes to him and the R&D team.
Thanks