Connect ADP3450 via Ethernet on Linux CentOS7

[JerryM]

Hello! I am trying to configure my ADP3450 to stream data via ethernet on Linux CentOS7. The latest version of Adept Runtime is not compatible with CentOS7 and had to fall back to these versions:

Adept Runtime: 2.19.2

Waveforms: 3.16.3

I am able to use Waveforms with the ADP3450 connected via USB. While connected via USB, if I click on Settings->Device Manager->Network I get the following message:

Could you please help me solve this issue? Thank you!

 

[attila]

Hi @JerryM

Could you use newer OS ?
The network support probably requires newer software version and this requires newer glibc than CentOS7 has.

[JerryM]

Hi @attila,

Thanks for the reply. Updating to a newer OS would be my last resort, but if you think nothing can be done on CentOS7, I'll try to upgrade.

[malexander]

@JerryM Adept Runtime 2.19.2 was released in October of 2018. The first internal release of the Adept Runtime to support Ethernet is 2.21.0, which was released in August of 2020. Many feature enhancements and bugfixes were made between then and August 2021, when version 2.26.1 was released. If you want network connectivity to work reliably then you need to install Adept Runtime 2.26.1 or newer.

Thanks,
Michael
 

Adept Runtime for Linux 2.26.1 (08/05/2021):
    1. Fixed a bug that caused device table entries whose hostname couldn't be
       resolved not to be returned in the list of enumerated devices.
    2. Defined error codes ercNameResolutionFailed, ercHostUnreachable,
       ercConnectionTimeout, and ercAuthenticationFailed and modified several
       internal routines so that a more appropriate error code would be set when
       one of the account management, SetInfo, or GetInfo calls fails.
    3. Added the ability to override the global enable/disable TLS setting by
       appending ":ENABLE_TLS" or ":DISABLE_TLS" to the end of a TCPIP
       connection string.
    4. Added support for the Digital Discovery to use VID=0x1443 and PID=0x7004.

Adept Runtime for Linux 2.25.1 (07/20/2021):
    1. Removed the requirement for a connection to be secured with TLS when
       sending credentials to a device. The connection will be encrypted with
       TLS if the device supports it, but TLS is no longer required. At the time
       of this release only the Analog Discovery Pro 3450 and Analog Discovery
       Pro 3250 support TLS, and TLS only supported in Linux mode on those
       devices.
    2. Removed the requirement for a connection to be secured with TLS when
       sending account management commands to a device. The connection will be
       encrypted with TLS if the device supports TLS, but TLS is no longer
       required for account management commands to be sent to the device. At the
       time of this release only the Analog Discovery Pro 3450 and Analog
       Discovery Pro 3250 support TLS, and TLS only supported in Linux mode on
       those devices.

Adept Runtime for Linux 2.24.1 (07/13/2021):
    1. Extended the DMGR API set to include the following functions:
       DmgrDvcTblClear
    2. Changed the way that the device table is enumerated in order to fix a
       bug that resulted in DVC/EDVC entries being created for device table
       entries prior to device discovery being completed. This issue would only
       show up when the DVC/EDVC entries were fetched immediately after being
       created while performing a non-blocking enumeration. In order to fix this
       bug it was necessary to require that all device table entries include
       both the transport type (TPT) and communication protocol (PTC) in their
       DTP field. Any device table entry that does not include both TPT and PTC
       is ignored.
       
       Existing device table entries will need to removed and recreated. If
       Adept no longer sees your device table entries then it's likely that they
       only included the transport type and not the protocol. Please download
       the "Adept Utilities" package and execute "dadutil tblclr" to remove the
       old entries. You can then create new entries using "dadutil tbladd".

Adept Runtime for Linux 2.23.2 (07/09/2021):
    1. Modified "install.h" to fix a bug that resulted in the UDEV rules not
       being properly generated on CentOS 8.4.
    2. Modified "install.h" to update the firewall rules to allow the mdns
       service after discovering that the default firewall rules on some
       non-debian distributions (CentOS and OpenSUSE) do not allow the mdns
       service even though they ship with the service enabled.
    3. Modfied RPM post install script to update the firewall rules when
       necessary so that MDNS can be used for discovering network devices.

Adept Runtime for Linux 2.23.1 (06/28/2021):
    1. Added the ability to discover network devices using Multicast DNS
       Service Discovery. Network devices that register the appropriate service
       name will be discovered through MDNS-SD. Devices that do not support
       MDNS-SD can still be discovered using UDP broadcast. This is 100%
       transparent to the user.
    2. Modified NENUMRESP to add support for V2 fields by reducing the size of
       the "ver" field from 4 bytes to 2 bytes. The upper two bytes are now
       set asside for compatible devices to return additional information known
       as the "V2 fields". These additional fields include information about
       client authentication, control channel TLS, and data channel TLS
    3. Added "V2 fields" to the EDVC structure.
    4. Fixed a bug that prevented DmgrStopEnum from stopping a non-blocking
       enumeration that included network devices.
    5. Made various bug fixes and improvements related to non-blocking
       enumeration.
    6. Switch from dynamic linking to static linking for OpenSSL to remove the
       need to distribute shared libraries that may be in conflict with
       libraries that were already installed on the system.
    7. Add support for FTDI devices that use Digilent's USB Vendor ID.

Adept Runtime for Linux 2.22.1 (05/03/2021):
    1. Added support for encrypted network connections. Transport Layer
       Security (TLS) is now enabled by default when communicating with
       network devices that support TLS.
    2. Added support for account management by extending the DMGR API set to
       include the following functions:
       DmgrIsClientAuthenticationEnabled
       DmgrEnableDisableClientAuthentication
       DmgrAddAccount, DmgrDeleteAccount
       DmgrGetAccountAttributes
       DmgrSetAccountAttributes
       DmgrChangeAccountPassword
       DmgrGetAccountList
    3. Extended DMGR API set to include the following functions:
       DmgrGetEdvc
       DmgrEnableControlChannelTLS
       DmgrEnableDataChannelTLS
       DmgrIsControlChannelTLSEnabled
       DmgrIsDataChannelTLSEnabled
       DmgrIsControlChannelSecure
       DmgrIsDataChannelSecure

Adept Runtime for Linux 2.21.3 (03/31/2021):
    1. Updated FTDI driver to version 1.4.22.

Adept Runtime for Linux 2.21.2 (11/11/2020):
    1. Fixed a bug that may have resulted in duplicate entries being created
       for Ethernet devices in the list of enumerated devices.

Adept Runtime for Linux 2.21.1 (09/30/2020):
    1. Extended the DMGR API set to include the following functions:
       DmgrSetNetworkEnumTimeout
       DmgrGetNetworkEnumTimeout
       DmgrSetNetworkConnTimeout
       DmgrGetNetworkConnTimeout

Adept Runtime for Linux 2.21.0 (08/04/2020):
    1. Added beta support for TCPIP connected devices (dtpEthernet).
 

[JerryM]

Thanks so much @attila and @malexander! 

I have upgraded to AlmaLinux 9.2 and installed Adept Runtime 2.27.9 and Waveforms 3.20.1. This looks much better: I no longer have the error message above and was able to enable the ethernet interface as described here.

The problem now is that Waveforms is not able to find the digitizer via Ethernet (I only see the USB one on the Device Manager). I followed the instructions linked above closely. The ADP3450 uses IP 192.168.2.10, mask 255.255.255.0, and the computer I set a static IP address 192.168.2.10, mask 255.255.255.0.

Are there any actions I can take to understand this? Thank you!

[attila]

Hi @JerryM

The IP should be different, like .10 for one and .11 for the other one.

[JerryM]

Hi @attila, right, thanks! I made a copy/paste mistake, I am indeed using 192.168.2.11 on my computer. 

[attila]

Hi @JerryM

Make sure the other network interfaces are not in conflict with this, are on different subnet, it is not 192.168.2.X
Have you tried connecting the device to your local network with auto IP, DHCP ?

[JerryM]

Hi @attila, thanks! I tried a few different subnets and none work. I also tried connecting to my local network with auto IP following the instructions here, and it still doesn't appear on the device manager. This is what is shown on PuTTY after I reboot from the device manager in Standard Boot:

Running Standard Mode v03.42
PL done
QSPI: 01-60-18-FF-FF-FF
AXI-DMA Setup
Failed XAxiDma_CfgInitialize Out
Setup
MAC: 00-18-3E-03-BF-40
Running
USB Connect 512B
Start PHY autonegotiation
Waiting for PHY to complete autonegotiation.
autonegotiation complete
link speed for phy address 15: 1000
IP :       192.168.2.10
Netmask :  255.255.255.0
Gateway :  0.0.0.0

So it looks like the ethernet link is there. From my computer, I am also able to successfully "ping 192.168.2.10". But still, I can't see the ethernet connection on the device manager:

[malexander]

Hi @JerryM

Is there anything on your network that would block UDP broadcast or MDNS-SD? We use those two mechanisms to discover network devices during enumeration when the host is Linux or MAC and the ADP3450 is running Linux. Windows hosts can also support MDNS-SD but it's not enabled because we didn't build the dependencies into the installer. I don't think the ADP3450 standard mode (non-Linux) supports MDNS-SD, and in that case, discovery is performed entirely with UDP broadcast. You could try running Linux mode on the ADP3450 and see if it makes any difference - just please be sure to use the latest image, as older images may not support on features of Adept.

Thanks,
Michael

[attila]

Hi @JerryM

1. With local network, select "Obtain IP address automatically" ! or use your networks subnet and an unused IP, outside of the DHCP server reservation.

 

2. You can try Linux mode but with this you loose the deep buffering and a bit on transfer performance.