Re:pncconf - feature requests

If you're still taking feature requests in this thread, here is one: If the custom messages component ( thread.gmane.org/gmane.linux.distributions.emc.user/29167 ) makes it into 2.5, it would be great to have a page for configuring custom messages (message, signal, etc.).

Thanks,

Scott

hmmm I'm not sure how that would work.
what would control the messages?
Do you mean you want to connect physical pins to messages?
What kind of messages are you thinking of?

shasse wrote:

If you're still taking feature requests in this thread, here is one: If the custom messages component ( thread.gmane.org/gmane.linux.distributions.emc.user/29167 ) makes it into 2.5, it would be great to have a page for configuring custom messages (message, signal, etc.).

even if that does make it in, I think it is perhaps a bit too specialised to be part of pncconf. (It is also not specific to Mesa hardware)

Fair enough. My use case is for additional messages such as "spindle VFD faulted" that would (in that case, for instance) be hooked to custom named input pins. In my ideal vision, I would be able to generate the config via pncconf, but seems that is not the general goal, which is fine. I can always add in the extra handling in a custom postgui hal sourced file.

Scott

It has become a bit more complicated due to the differences between LGPL and GPL.

You can, if you want, install the comp yourself, without recompiling EMC2. You would need to save the code to a file called "message.comp" then comp --install message.comp.
That ought to work on an installed system, even without the sources.

well you can somewhat do what you wish with pncconf now.
pncconf can load extra components if you add the commands ( hal component page)
pncconf can have custom signal names just write them in the combo box. (mesa or parport page)
then you just need to add HAL glue code in the custom_hal file.

While your message idea is interesting, I have enough work just keeping up to EMC and mesa changes

Chris M