Hi *, I changed my native-C rasPI-driver into a HAL-component.
It builds 16 IN- and 16 OUT-Pins for the Raspberry. The receiving parts (for rasPI- an and PC-side) are also working but not published now. I will make further tests at first. It would be fine, if a linuxCNC-developer an take a look at this: http://erste.de/raspi.comp and give me some feedback. I'm not sure: should I include -INV/-NOT-pins into this component or should those inversion be done by the rasPI- or by the PC-communication task? or by the linuxCNC-in/hal-config? I think, it depends on the number of pins, which need inversions.... ? or what do you think? regards wicki _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
