New ethercat / probe basic control for minimonster

Dangit, I cant find a reference to this anymore could have sworn i asked about it here.

When I originally set up ethercat I had an issue where the drives would cycle op mode rapidly and show b2. I figured out what it was and fixed it and all was well.

Machine has been off for some weeks and now suddenly its doing that again, and I cant remember the reason or find where I solved it. I only remember it had something to do with the order of startup. Also have no idea what changed, I made no edits.

Any ideas?

Ah, it is in here. it was a modbus conflict. but that makes no sense why it would come back. unless im using the wrong config, or my modbus dongle is misbehaving? (seems fine).

grr

I'm stupid. was using a messed up config somehow.

*nevermind!*

edit: technically I'm not stupid. this is weird. if I start from the menu, its the wrong config somehow. and if I start from the icon on the desktop its fine. even though they both point to the same config. Weeeird.

So, I have 4 distinct problems that have come up switching and already working control to probe basic. Hoping some people can help.


1: i cant move the axes before homing. i need to be able to move them into postion and then home. i assume there must be a toggle somewhere for this.

2: the install process wiper out my ethercat driver somehow, and now it wont start on boot. i need to go and do it manually. It seems probe basic installed or updated other things along with itself. I need to un-update them.

3: when i shut off the machine (power button in linuxcnc) i get a lot of limit and joint errors. these were not in the axis setup. I feel like this is related to issue 1.

4: i have a 1680x1050 screen. i and scaling the output to force fit probe basic. this worked ONCE. and then after rebooting probe basic has scaled itself off to the right side and reports a resolution of 2077x1080.

Any help on any of these would be appreciated, thanks!

1. Somewhere in your ini settings kinstype=both lets you jog before homing unless you have 2 motors on an axis
2. Refer to my Ethercat install sticky for the rules to start the ethercat service on startup
3. No idea
4. It may have changed but probe basic requires a 1080p monitor so I could never used it. QT dragon is the same. I had to upgrade to a 1080p monitor.

I'm at a loss to understand what any machine needs moving before homing. Are your home switches set up so they stay triggered to end of travel?

rodw wrote:

1. Somewhere in your ini settings kinstype=both lets you jog before homing unless you have 2 motors on an axis
2. Refer to my Ethercat install sticky for the rules to start the ethercat service on startup
3. No idea
4. It may have changed but probe basic requires a 1080p monitor so I could never used it. QT dragon is the same. I had to upgrade to a 1080p monitor.

I'm at a loss to understand what any machine needs moving before homing. Are your home switches set up so they stay triggered to end of travel?

Thanks

Progress so far:

1: that interesting, its not in my ini right now. ill see if it changes anything. not that axis and qtdragon both work as expected.
2: i reinstalled the whole system, were back on 2.9.8 and everything is so far fine.
3: this is actually the drives reporting zero for one frame when resetting. i remove my filter which was filtering that bad value. it is curious, and i think only the omrons do it. its not important, but perhaps there is a setting or pdo that manages this. Or i can just re-enable the filter but only to trigger on controlword changes. (this is the same basic "bug" with the drives that cause the random joint and home errors).
4: in fact probebasic requires 2077x1080 for reason unknown, i set my res to that and its fine. Lcvette has some thoughts, but after running through them nothing has changed so far. My undestanding is after their server migration something is borked. Fonts are also wrong, too larger, which i assume is related. We will revisit it another day, it is fine for now.

So really we are just needing to fix the jog. I will try what you just said and report back.
Thanks
 

rodw wrote:

1. Somewhere in your ini settings kinstype=both lets you jog before homing unless you have 2 motors on an axis

 

This explicitely returns an error telling me i need to be homed first.... sooo. no.