Am 02.07.2013 um 16:35 schrieb John Kasunich <jmkasun...@fastmail.fm>:
> Classic Ladder (as we use it) is basically a HAL application. It uses (agree to all of above) > I'm having a harder time wrapping my mind around Michael's > larger messaging proposal(s). Non-scalar HAL types certainly > have benefits for some applications, but they introduce new > mental models. How do you troubleshoot such things? Tools > like halscope and halmeter don't apply to non-scalars, I think. There wont be additional data types at the HAL primitives level; but since messaging will be used to interface GUIs, task and interp to a HAL instance, and also used to link 'between' HAL instances, I'd think it has to go along with a HAL package this will become much clearer when I finish the examples document on how to tie messaging into HAL, and I also would think the split decision makes sense following through only after the NML migration is completed, which I'd see several months out; at least I dont see a point in spinning out a HAL package which still rests on NML, which would have severely hampered usability -m > I haven't given the whole messaging thing much thought. As > soon as I got home from Wichita I started preparing for a > hiking trip, last weekend I was in the woods far from the > internet, and this week I'm trying to catch up at work. > > > > On Tue, Jul 2, 2013, at 10:16 AM, EBo wrote: >> good point. Where should the classic ladder be grouped? In its own >> bin, with HAL, with a generic parser/PLC? >> >> On Jul 2 2013 7:43 AM, Dave wrote: >>> I would also make sure that you can still use it with Classic Ladder >>> as >>> a standalone also. That could be very useful. >>> >>> Dave Cole >>> >>> On 7/2/2013 3:24 AM, Anders Wallin wrote: >>>> Some random thoughts/discussion. >>>> >>>> To be useful a stand-alone HAL package also needs tools for building >>>> HAL >>>> networks. >>>> These include halscope, halmeter, siggen, etc. as well as any future >>>> insanely great visual HAL-netlist creation and visualization >>>> software. >>>> Hardware-drivers should also be included in the HAL-package, or >>>> perhaps >>>> packaged individually so you only need to install the ones you want. >>>> >>>> Non-conventional HAL-applications (temperature-controller, >>>> datalogger, >>>> weather-station, etc) require non-conventional hardware drivers. >>>> There's a >>>> bunch of work on DAQ cards with linux at http://www.comedi.org/ I >>>> wonder >>>> how much work is involved in using a comedi driver through HAL? >>>> >>>> I am interested in developing small embedded >>>> controllers/user-interfaces >>>> for various lab-applications such as temperature control, >>>> datalogging etc. >>>> These would also require some sort of user-interface, similar to >>>> pyvcp or >>>> gladevcp, which would work on a minimal linux-install (some embedded >>>> boards >>>> do not have gpu/cpu power to run a full X install). >>>> >>>> Anders >>>> >>>> >>>> >>>> On Mon, Jul 1, 2013 at 8:04 AM, Chris >>>> Morley<chrisinnana...@hotmail.com>wrote: >>>> >>>> >>>>> This was a tabled item from the last meeting. >>>>> The consensus seemed to be the idea had merit but discussion was >>>>> needed. >>>>> >>>>> Micheal's proposal was a 'machiekit' package that included: >>>>> >>>>> "Machinekit would be HAL+RTAPI+NML replacement (zeromq+protobuf)" >>>>> >>>>> The idea here is that HAL is a great piece of code that has a >>>>> fairly easy >>>>> boundary >>>>> to break it out of liuxcnc. >>>>> >>>>> Then other projects could use it and hopefully improve it and maybe >>>>> join >>>>> our group. >>>>> Modularity also makes it easier for people to digest the code so as >>>>> to be >>>>> able to contribute. >>>>> John K's original idea for HAL was similar (as I understand it). >>>>> >>>>> I'm for all it. >>>>> >>>>> I'm not sure of the downside other then it's work to do. >>>>> I assume others wish to discuss the NML replacement >>>>> >>>>> Chris M >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> This SF.net email is sponsored by Windows: >>>>> >>>>> Build for Windows Store. >>>>> >>>>> http://p.sf.net/sfu/windows-dev2dev >>>>> _______________________________________________ >>>>> Emc-developers mailing list >>>>> Emc-developers@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/emc-developers >>>>> >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.net email is sponsored by Windows: >>>> >>>> Build for Windows Store. >>>> >>>> http://p.sf.net/sfu/windows-dev2dev >>>> _______________________________________________ >>>> Emc-developers mailing list >>>> Emc-developers@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/emc-developers >>>> >>>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by Windows: >>> >>> Build for Windows Store. >>> >>> http://p.sf.net/sfu/windows-dev2dev >>> _______________________________________________ >>> Emc-developers mailing list >>> Emc-developers@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/emc-developers >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers > > > -- > John Kasunich > jmkasun...@fastmail.fm > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
