Post Go back to editing

How to remotely connect to ACE IPC server?

Category: Software
Software Version: 1.30.3323.1470

I have the ACE software and IPC server up and running on a local machine. Now I want to controll it remotely for measurement automatization. From my remote machine I see the server on the network on port 2357, as configured in ACE, but I am not able to make a successful connection. When sending any kind of data with telnet or the like the connection gets closed by the remote host immediately. The local console started from within ACE works fine, though. I am not able to find any documentation for this so could someone point me in the right direction?

TIA

  • Hi  ,

    One thing that might affect this is that in the remoting client you need to specify the host machine when opening the connection if you are connecting to a different machine. From the ACE Remoting Help docs:

    Connecting the Remoting Console to a Remote ACE Application Host

    If the ACE host is running on a different machine, you will need to specify the host when you open the connection:

    > open lab-bench-43:2357
     Note

    You must be able to open a TCP/IP connection on the remote host in order to connect to it. To successfully connect, the host's attached network must be accessible from the client and firewalls cannot be blocking the port.

    You can access this documentation by clicking the Help button in the bottom left corner of your ACE window, then opening the Application Resources dropdown and clicking the Remote Control Interface Documentation, which will open in a separate window.
    Hopefully this helps to address your issue, but if not let me know and we can debug further.

    Thanks,
    Eoin
  • Yes, but I want to connect from a custom application since I need to do some test and measurement automation and ACE can only run in a virtual machine with no access to the local network since it requires Windows.

  • I'm not sure I understand the requirements fully here, or why you cannot access the local network from the virtual machine running ACE. Could you provide some more details on the environment?
    It sounds like the issue here may be related to the networking configuration between your host machine and the virtual machine, or the remoting server may be blocked by a firewall.

    It's difficult to diagnose without more details, I'm not sure I'll be able to provide much support on virtual machine configurations unfortunately.


    Thanks

    Eoin

  • Alright, I'm sorry, I try to elaborate. So I have the ADMV1013-EVAL connected to my linux workstation via USB and the device forwarded to a virtual machine running Windows and ACE to control the dev board. Now I need to run some Python scripts on my machine to control our custom hardware and the board.

    I can see the IPC server from my workstation but the connection gets closed by the IPC server whenever I send some data. The example code

    from AnalogDevices.Csa.Remoting.Clients import ClientManager

    refers to a package which comes bundled with ACE and is not available for Linux as far as I can tell so I'm a bit at loss how to solve my issue.

    Thanks

  • Hi  ,

    Thank you for the explanation, I understand the issue now.
    Unfortunately, the remoting client and associated packages only run on Windows, and the ClientManager is required for interacting with the remoting client. This is why the connection is being closed, connections must be created through the ClientManager, which cannot load on Linux.

    Unfortunately, there is no simple solution for this issue as ACE and it's packages only target Windows machines.

    The only solutions I can think of are to use a Windows workstation or for you to create another Python script locally on the Windows VM which would communicate with the Linux Python script and then execute the client commands on the Windows machine.

    Apologies that we cannot provide more support on this, Linux is unfortunately just not supported by ACE.


    Thanks,
    Eoin

  • Hey Eoin, thanks for you efforts! I was contemplating your proposal already but it's too much effort for a very sketchy solution so I decided to modify the hardware.

    It would be really great, though, if the dev boards could either

    - be controlled via iio

    - the source code for the PIC controller would be open source to be easily adaptable

    - the communication protocol for the dev board would be documented

    - have a connector (and some jumpers) for external SPI

  • Hi  ,


    Glad you found an alternative, looks pretty inventive, kudos to you!

    Your suggestions are very valid and noted, the exact things you suggest are actually present on other evaluation boards for other Analog Devices parts, I can't say for sure why they're not available on the board for this part as I'm on the software side, but it may be worth posting this feedback on the RF and Microwave forum to ensure that it gets back to the product team:  RF and Microwave

    If you have any more issues with ACE or remoting, please let me know and I'll try to help if I can,

    Thanks,
    Eoin