Integration between PyWorkbench and PyAEDT without reading a third script

[ManuelMDVR]

Hello!
I am new to this, so I am facing some problems. My goal is to generate a script using pyworkbench and pyaedt, in which I'll read a Discovery geometry and its parameters, to then perform several a parametric study in Maxwell3D and connect the results to Mechanical, hence the initial idea of connecting through Workbench. However, from what I have seen, apparently there is no "connect_to_mechanical" equivalent for AEDT? And, even if there was, apparently connecting to Mechanical with "connect_to_mechanical" doesn't allow you to setup the Mechanical simulation directly, but makes you read a script in which the Mechanical simulation is defined, is that correct?
I have managed to launch a Workbench session in which I setup the Geometry and Maxwell3D components and connect them, but that has been through the run_script_file method. I would have expected to be able to do that through pyWorkbench directly, instead of reading a recorded journal?
Surely I'm missing something, I'd appreciate it if someone could provide some insight on this.

Thanks!!

[MeenaBytes]

@ManuelMDVR There isn't any function for connecting to PyAEDT in PyWorkbench. And you are right now mechanical, connect_to_mechanical is allowing users to use remotable pymechanical where you send string of mechanical script commands to mechanical for your automation.

For AEDT, if Workbench allows using RunScript or SendCommand, I would recommend you use that.

[franknli]

We had plan to integrate PyAEDT with PyWorkbench and identified the technical requirement, which is for AEDT team to switch to grpc based connection for its Workbench addin. @ManuelMDVR Please advocate this integration.

[ManuelMDVR]

[like] Manuel Delvalle reacted to your message:

…

________________________________ From: Frank Li ***@***.***> Sent: Sunday, September 14, 2025 4:07:16 AM To: ansys/pyworkbench ***@***.***> Cc: Manuel Delvalle ***@***.***>; Mention ***@***.***> Subject: Re: [ansys/pyworkbench] Integration between PyWorkbench and PyAEDT without reading a third script (Discussion #203) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Warning This email comes from outside of Hitachi Energy. Make sure you verify the sender before clicking any links or downloading/opening attachments. If this email looks suspicious, report it by clicking 'Report Phishing' button in Outlook. See the SecureWay group in Yammer for more security information. We had plan to integrate PyAEDT with PyWorkbench and identified the technical requirement, which is for AEDT team to switch to grpc based connection for its Workbench addin. @ManuelMDVR<https://github.com/ManuelMDVR> Please advocate this integration. — Reply to this email directly, view it on GitHub<#203 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BQOQ7RMNUOS4FQUIVWEYAP33STSXJAVCNFSM6AAAAABZAJQWWCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZZGQ2DAMI>. You are receiving this because you were mentioned.Message ID: ***@***.***>