You need to contact the author.
The support in Machinekit is for the standard pendant.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Hi
$ halrun
msgd:0 stopped
rtapi:0 stopped
halcmd: loadusr ../bin/xhc-whb04b-6 -Hup
On 23/02/2018 01:12, Aurelien wrote:
The most common mistake that gives this error, is calling hal_malloc() when realtime is not started.this message is sended by the driver i have found the output text error in source code
xhc.hal = (xhc_hal_t *)hal_malloc(sizeof(xhc_hal_t));if (xhc.hal == NULL) {fprintf(stderr, "%s: ERROR: unable to allocate HAL shared memory\n", modname);exit(1);
Does not look to be the case.
I have no familiarity with this code and only have a standard xhc pendant, but will look later.
I think the author only opened the issue and not do the job for standard xhc because( i think), rubienr have only new model and report issue founded when developping new model, so i hope the issue is not related for this new unit. (for sure not sure at all^^)Thanks a lot for DEBUG=5 info
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to a topic in the Google Groups "Machinekit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/machinekit/jwvEEPT-HMg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to machinekit+...@googlegroups.com.