Error on startup

I think that "ini.z.maxlimit does not exist" is probably the real problem.

At a guess a HAL file is referencing those pins before the module that creates them is loaded. I am not sure which module creates them, though. I would have guessed motion, but they are not in the manpage

andypugh wrote: I think that "ini.z.maxlimit does not exist" is probably the real problem.

At a guess a HAL file is referencing those pins before the module that creates them is loaded. I am not sure which module creates them, though. I would have guessed motion, but they are not in the manpage

I think that's a fairly accurate guess. the maxlimit errors mostly shows up in SIM, but I have seen it once or twice on a live table. It always felt like a timing thing, so maybe we need to delve a little deeper into the order the modules are loaded.

I have not seen that error before.

ini.z.max_limit is netted by the handler file as the fourth command of the initialized function. Quick testing has shown that there is no difference whether it is the first or last command.

If I rename it to the wrong pin number then I get the following: but I dont see these messages which are in the first post. or further down:

A bit more testing:

In the ini file, if I change: to a non existing path: I get this error in terminal: plus this error from qtvcp: so I don't think it is a qtvcp error, just qtvcp's reaction to not being able to load correctly because of some other pre-existing issue.

Pins like ini.z.max_limit,ini.z.min_limit are created by
task (typ: [EMCTASK]TASK=milltask)


Ref: linuxcnc.org/docs/2.8/html/man/man1/milltask.1.html

snowgoer540 wrote: I've only seen it in SIM not in a live table, so it could be a timing thing.

I would have expected the opposite.

In your real table you are using the pmx485 userspace component and in you sim you wouldn't be. I was just thinking that the USRMOT error could be from the pmx485 component.