Errors: 'Corrupted data. Resetting data reciever.' and 'Bad payload legth'.

[nathanaeloneill]

Hi Kevan,

I changed the ipv4 settings on the USB Ethernet dongle so the default gateway 10.0.0.1 was removed.

I also used the configurator to change the IP address of the LWDAQ driver from 10.0.0.38 to 10.0.0.39, so that there is no possibility of another laptop contacting the driver over institutional internet.

Unfortunately, the error is still there, with 3 seconds regularly dropping.

Do you have any other trouble shooting suggestions?

Thanks

Nat

[Kevan Hashemi]

Dear Nat,

> I changed the ipv4 settings on the USB Ethernet dongle so the default gateway 10.0.0.1 was removed.

Thank you.

> I also used the configurator to change the IP address of the LWDAQ driver from 10.0.0.38 to 10.0.0.39, so that there is no possibility of another laptop contacting the driver over institutional internet.

You still have two drivers with IP address 10.0.0.37.

> Unfortunately, the error is still there, with 3 seconds regularly dropping.

Which IP address is still giving you problems?

How many of the Neurorecorders are giving you problems?

> Do you have any other trouble shooting suggestions?

If IP address 38 is still giving you problems, change it to 10.0.0.40. Some other device on your local network may be trying to contact IP address 10.0.0.38 for some reason.

What are the IP addresses of the laptops? It could be that one of them has IP address 10.0.0.38 as well.

Best Wishes, Kevan

[nathanaeloneill]

Thanks Kevan.

The one I'm having problems with is the 10.0.0.38 (which I changed to 10.0.0.39). I will try 10.0.0.40. and change one of the others from 10.0.0.37 to stop any duplication .

I will check ip addresses of computer tomorrow, but this is set by IT and is static, it should not be anything like 10.0.0.38. it's something:192.xxx.xxx.xxx.

I will also try running it on wifi for a short time to see if that stops the errors. This will at least tell us if it's something on the local wired network.

Thanks again

Nat

[Kevan Hashemi]

Dear Nat,

> I will check ip addresses of computer tomorrow, but this is set by IT and is static, it should not be anything
> like 10.0.0.38. it's something:192.xxx.xxx.xxx.

I'm talking about the IP address of the laptops as assigned for the 10.0.0.x interface, not the IP addresses assigned by IT.

Best Wishes, Kevan

[nathanaeloneill]

Hi Kevan,

Sorry for the radio silence -- I was on holiday last week.

The problem has resolved. The solution to the problem is likely one of three things.
1) I changed the ethernet-to-usb dongle ip address to 10.0.0.40, to prevent any clashes. I did this 24 hours before going on holiday and errors were still present.
2)I installed windows updates. I did this immediately before going on holiday -- this may have resolved the error.
3)There are many fewer transmitters recording at the moment. Before my holiday, there were quite a few 4-channel HMTs are we had lots of other transmitters.

One, or a combination, of the above has now allowed us to record stably without the persistent error. I am unsure which of the above is responsible for the improvement. Should the error return, I should have a better idea of the cause (e.g. more transmitters added or overdue windows updates).

Thanks for your help

Nat

[Kevan Hashemi]

Dear Nat,

Thanks for your report.

The symptom of the problem was occasional loss of contiguous chunks of telemetry data. Because changing address to 10.0.0.40 failed to stop these losses, I'm going to say that was not the problem. Having a large number of transmitters would not, in itself, lead to loss of contiguous chunks of data. Pending Windows updates have always disrupted TCPIP communication. I don't understand why. I see two possibilities:

(A) The TCPIP interruptions are on-going, but because there are fewer transmitters, the buffer on the Octal Data Receiver is able to store all the data until such time as TCPIP communication resumes.

(B) The pending Windows updates were causing the interruptions. Now that you have installed the updates, the computer is reliable. In a few months, when more updates will be required, it may become unreliable again.

Of the two, I pick B as the most likely.

Best Wishes, Kevan