ADIN1110 evaluation board
As we have discovered previously, ADIN1110 differs from ADIN1100 PHYs we have used so far that it includes complete Ethernet adapter (both PHY and MAC functions). In this Challenge, we were provided with evaluation boards for both ADIN1100 and ADIN1110.
External box of ADIN1110 evaluation kit is very similar to that of ADIN1100
and inside there are two components: a board and USB cable
| {gallery}ADIN1110 |
|---|
|
|
192 meter test
Our next test would be connecting ADIN1110 evaluation board (that has on-board MCU and can serve a web page) with Raspberry PI - but before using CN-0575 shield, another interface will be used: USB 10BASE-T1L adapter that is included in AD-SWIOT1L-SL : AD-T1LUSB2.0, that is basically USB Ethernet adapter with included ADIN1100 PHY. It's block diagram is below:
Our test setup consists of
- Raspberry PI
- 10BASE-T1L USB adapter
- short run of MODBUS cable (included in AD-SWIOT1L-SL evaluation platform), later replaced with 48 meters of CAT5E UTP
- USB powered ADIN1110 evaluation board in a default configuration
and is (after configuring DHCP server on Raspberry PI, because default configuration of ADIN1110 evaluation board uses dynamic address) working, serving page as below:
From this page, some interesting data can be gathered:
As we can see, it has autonegotiated as slave/follower (which is consistent with default jumper setting of "prefer follower"), some quality metric is displayed and DHCP configuration is also present.
Then, 48 meters of UTP CAT5E cable was connected instead of MODBUS cable
and? everything still worked:
what is interesting - MSE metric is the same as using MODBUS cable...
Then - in line with wolfgangfriedrich suggestion - available UTP pairs were connected in series, giving effective distance of 192 meters (and additional crosstalk between pairs).
And? The system was still working:
What is interesting - MSE metric is still the same and autonegotiation resulted in Master role (despite configured preference for follower).
Unfortunately, on Raspberry PI side ever increasing counter of receive errors was observed:
No good - although TCP retransmission retrieves those lost packets, something is wrong:
but - ICMP echo from the host is not affected, not even a single ping is lost.
After some research initial setup (with 30 cm of MODBUS cable) was restored - and lost packets were also observed:
As a conclusion - ADIN1110 works on 192 meters of low quality cable. There is some packet loss but only in very specific situation: TCP data transmitted from ADIN1110, ICMP is not affected.
At this stage it seems that this problem is elsewhere: USB adapter or Raspberry PI or maybe ADIN1110 demo software?
Additional tests are needed
