Thanks for details.
I'm looking at the timing of your errors. I should have done so earlier. They are separated by several minutes. If there are two Neurorecorders accessing the same Octal Data Receiver, they cannot be on the same computer, or else they would conflict all the time. Nor can they be accessing the same Octal Data Receiver, because they would likewise conflict all the time. So it must be that there are two computers accessing two Octal Data Receivers, and these Octal Data Receivers share the same IP address, so that they conflict some of the time.
> Do setup3 you think it is finding driver from setup 2 through the institutes internet?
That's possible if the institute's internet is also using subnet 10.0.0.x, but I doubt that is the case.
> I'll double check the wiring tomorrow to confirm setup 3 hasn't been connected to setup 1's switch.
I think you mean Setup 3 might have been connected to Setup 2 (the one with the problem). If so, I would expect you to see the same problem in Setup 3. Do you see any warnings in the Neurorecorder of Setup 3? How about Setup 1?
I suggest you give the LWDAQ Drivers distinct addresses. You could try 10.0.0.37, 38, 39, and 40, while making sure that the local IP addresses of your three laptops are also distinct, such as 10.0.0.2, 3, and 4. You have a bunch of MicroSeven cameras in there as well, so you would have to make sure you don't conflict with those either, but it seems to me worth the trouble of removing this worry by giving your LWDAQ Drivers distinct IP addresses. To change the Driver IP addresses, use the .
Thank you for working on this problem. The intermittent data loss really messed with Rob Wyke's recent recordings of cortical spreading depressions.
Best Wishes, Kevan
PS. Another thing I want to note, although I don't think it's particularly relevant. When I was up in the animal house two weeks ago with Rob and Luiz trying to fix this problem in person, I wanted to clear the "router address" for the Ethernet interface of the computer that was skipping data. The router address (or "gateway") was set to 10.0.0.1. We don't want the computer trying to get to the outside world by using 10.0.0.1 as a gateway. But I was unable to delete the router address in that particular version of Windows. So it is possible that this particular machine will try to access the internet through 10.0.0.1. If it did, I don't see how that would cause problems for your telemetry, but it might cause problems for your file sharing over your institute's network.Statistics: Posted by Kevan Hashemi — Mon Jun 24, 2024 9:41 pm
]]>