Hello,
I am using RoboDK v5.4.3 released 2022-07-24. Robot: Mecademic Meca500-r3 is running firmware v8.4 if that matters. I am trying to connect to and do basic movements on our Mecademic Meca 500 r3 over it's ethernet, but there are some errors connecting to hardware. The m500's web interface works fine, so I deduce the hardware is good, the connection is probably good (at least at the physical layer), and I have let anything requesting a hole in Windows Firewall that access. The Ping function in RoboDK works.
I did note some issues during install such as this:
That looks like something failed, but was not fully captured or traced.
The Ping works, yet when connecting I get these errors in the log window:
It looks like the Pythonpath is not working right, so I re-installed. Same issue. So then I re-ran some setup.py's manually to try and resolve dependencies, which seemed to help, but did not fully resolve the issue.
It looks similar, but still missing something. The files are there, I'm not sure why it "can't find them". I started poking around with some python tools, but was limited by not wanting to touch the RoboDK python environment, and too new to want to perhaps induce other issues by pointing RoboDK to a conda virtual environment I control and attempt to resolve RoboDK's dependencies within. But I did install RoboDK with Python, here is its configuration pointing to that environment:
Any ideas? Not being able to connect is quite a show-stopper for both application and futher development, but maybe we can leverage simulation more while this is being resolved.
Ideally, I'd run my own python environment in a conda venv, but to start, I can say I let it install its own Python and dependencies in it's preferred folder, and is using bone stock Python 3.7 from the installation, as best I can tell. This should be fine since I think it explicitly calls this python.exe and associates with that environment/folder (but can't seem to find the installed files).
Here are some seemingly related forum posts, but they are different:
//www.sinclairbody.com/forum/Thread-Meca500-...obot-issue
//www.sinclairbody.com/forum/Thread-RoboDk-c...er-problem
>> Very similar to my issues and steps attempted, but I am not using a custom driver. It is the stock driver.
//www.sinclairbody.com/forum/Thread-Can-t-connect-to-robot
Ah, this is why my post was too long and pictures added a ton of characters. They are being base64 encoded and quickly exceed the post character limit. Argh. see here for how to post images on RoboDK forum://www.sinclairbody.com/forum/Thread-READ-THI...GUIDELINES
I am using RoboDK v5.4.3 released 2022-07-24. Robot: Mecademic Meca500-r3 is running firmware v8.4 if that matters. I am trying to connect to and do basic movements on our Mecademic Meca 500 r3 over it's ethernet, but there are some errors connecting to hardware. The m500's web interface works fine, so I deduce the hardware is good, the connection is probably good (at least at the physical layer), and I have let anything requesting a hole in Windows Firewall that access. The Ping function in RoboDK works.
I did note some issues during install such as this:
That looks like something failed, but was not fully captured or traced.
The Ping works, yet when connecting I get these errors in the log window:
It looks like the Pythonpath is not working right, so I re-installed. Same issue. So then I re-ran some setup.py's manually to try and resolve dependencies, which seemed to help, but did not fully resolve the issue.
It looks similar, but still missing something. The files are there, I'm not sure why it "can't find them". I started poking around with some python tools, but was limited by not wanting to touch the RoboDK python environment, and too new to want to perhaps induce other issues by pointing RoboDK to a conda virtual environment I control and attempt to resolve RoboDK's dependencies within. But I did install RoboDK with Python, here is its configuration pointing to that environment:
Any ideas? Not being able to connect is quite a show-stopper for both application and futher development, but maybe we can leverage simulation more while this is being resolved.
Ideally, I'd run my own python environment in a conda venv, but to start, I can say I let it install its own Python and dependencies in it's preferred folder, and is using bone stock Python 3.7 from the installation, as best I can tell. This should be fine since I think it explicitly calls this python.exe and associates with that environment/folder (but can't seem to find the installed files).
Here are some seemingly related forum posts, but they are different:
//www.sinclairbody.com/forum/Thread-Meca500-...obot-issue
//www.sinclairbody.com/forum/Thread-RoboDk-c...er-problem
>> Very similar to my issues and steps attempted, but I am not using a custom driver. It is the stock driver.
//www.sinclairbody.com/forum/Thread-Can-t-connect-to-robot
Ah, this is why my post was too long and pictures added a ton of characters. They are being base64 encoded and quickly exceed the post character limit. Argh. see here for how to post images on RoboDK forum://www.sinclairbody.com/forum/Thread-READ-THI...GUIDELINES
