Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RPC Communication Error: VarType 8192 is not supported when using blackbox licenses to retrieve get_magnetic_graph() data #420

Open
2 tasks done
EmilCallerfjord opened this issue Oct 30, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@EmilCallerfjord
Copy link

🔍 Before submitting the issue

  • I have searched among the existing issues
  • I am using a Python virtual environment

🐞 Description of the bug

Hello,

I am using the blackbox licenses for parametric sweep in MotorCAD through the pymotorcad API. I am getting the error "RPC Communication Error: VarType 8192 is not supported" when trying to get graph data through the function get_magnetic_graph().

When I am not using the multiprocessing package but still using a blackbox, I do not recieve this error and the data is retrieved without any errors.

📝 Steps to reproduce

  1. Follow the "Running_Parallel_Sessions_Scripting" Python_Tutorial2
  2. Add get_magnetic_graph("PhaseCurrent1") or any other magnetic graph.

💻 Which operating system are you using?

Windows

📀 Which ANSYS version are you using?

MotorCad 2024R2.3

🐍 Which Python version are you using?

3.10

📦 Installed packages

aiohappyeyeballs==2.4.3
aiohttp==3.10.10
aiosignal==1.3.1
annotated-types==0.7.0
ansys-motorcad-core==0.5.0
ansys-pythonnet==3.1.0rc3
appdirs==1.4.4
async-timeout==4.0.3
attrs==24.2.0
bezier==2023.7.28
biopython==1.79
certifi==2024.6.2
cffi==1.17.1
charset-normalizer==3.3.2
clr-loader==0.2.6
contourpy==1.2.1
cycler==0.12.1
defusedxml==0.7.1
et-xmlfile==1.1.0
fonttools==4.53.0
fpdf2==2.7.9
frozenlist==1.4.1
gtfparse==2.0.1
idna==3.7
importlib_metadata==7.1.0
jsonschema==4.23.0
jsonschema-specifications==2023.12.1
kiwisolver==1.4.5
matplotlib==3.9.0
multidict==6.1.0
numpy==1.26.4
openpyxl==3.1.5
packaging==24.1
pandas==2.2.2
pillow==10.3.0
plumbum==1.8.3
polars==0.16.18
propcache==0.2.0
psutil==5.9.8
pyaedt==0.10.2
pyarrow==16.1.0
pycparser==2.22
pydantic==2.9.2
pydantic_core==2.23.4
pyedb==0.28.0
pyfaidx==0.8.1.1
pyparsing==3.1.2
pypxl==0.2.3
pypxlib==2.5
python-dateutil==2.9.0.post0
pytomlpp==1.0.13
pytz==2024.1
pyvariant==2.2.4
pywin32==306
PyYAML==6.0.2
referencing==0.35.1
requests==2.32.3
rpds-py==0.20.0
rpyc==6.0.1
Rtree==1.3.0
scikit-rf==1.3.0
scipy==1.14.0rc2
scipyx==0.0.18
six==1.16.0
toml==0.10.2
typing_extensions==4.12.2
tzdata==2024.1
urllib3==2.2.1
yarl==1.16.0
zipp==3.19.2

@EmilCallerfjord EmilCallerfjord added the bug Something isn't working label Oct 30, 2024
@jgsdavies
Copy link
Collaborator

jgsdavies commented Dec 13, 2024

Hi @EmilCallerfjord. Is this maybe a problem with the script trying to access results too early? Do you have a minimal reproducible example I can use to test this locally?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants