- About stephenOtis
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About stephenOtis
since
08-09-2021
3 weeks ago
stephenOtis
Member
6
Posts
1
Likes
0
Solutions
3 weeks ago
Hello, I'm trying to configure an oscilloscope in the Oscilloscope app to view position data from my Indradrive I have connected. I can see the data in the motion tree under NRT data, but I need RT data in order to see anything meaningful. However, when I look in the NodeRT tree and check the Motion tree and the Fieldbus tree, I don't see any data options to select for the scope. All the boxes are greyed out and when I expand them, they don't show me any options. If I look in the Data Layer under the Fieldbus tree, I can see the realtime data I am looking for. Why can't I assign that to my oscilloscope as well.
... View more
08-04-2022
05:15 AM
1 Like
Hello, I haven't seen any update to this. I see 1.16 was just released, but I don't see anything in the release notes for the Motion app saying this issue was resolved with MPE Indradrives and the CtrlX Core functioning. Can anyone confirm if this is resolved in 1.16 or is still an open issue? Is there a solution to get MPE drives to work with CtrlX?
... View more
06-02-2022
07:06 PM
Hello, Thanks for checking on this issue. It is very strange and I hope to find a resolution. Attached is the new system log with axisprofile trace enabled before I trigger the fault. Please let me know if you find anything.
... View more
05-26-2022
06:52 PM
Hello, Is there any update on this? Can anyone duplicate what I am seeing here with my MPE drives on RM22.03? At the moment I am looking to try and get replacement MPB drives to swap into this project in order to keep moving forward, but if there is another solution that would be simpler.
... View more
05-19-2022
07:28 PM
Thanks for the help, but I'm still having an issue. I went ahead and tested downgrading to 1.12 and back to 1.14. I then tested 1.14 with a different 2 axis demo which uses MPB and MPC firmware drives with MSK motors. With those drives connected, I'm able to create the axis profiles in teh motion app and go into running mode with no issue. I then went back to the system I'm testing which has 3 MPE firmware drives with MSM motors, and I still have the issue where I'm getting an Axis Profile error when I try to switch the motion app to running. If I downrev to 1.12 on this particular system, I can get it to work. So it appears that the issue is tied to this combination of hardware somehow. What's strange is that I don't even have to have the axis profiles tied to an axis on the system, it just has to exist and have the ethercat data links and I get the axis profile errors. System log is attached below as well. Any help is appreciated. EDIT: I was able to test an MPB drive with MSM motor on my Motion v1.14, and that was working with the Axis Profile. So I think the issue is specifically with the MPE drive variation and not the MSM motors.
... View more
Latest Tags
No tags yet
