From: Gregg L. <gr...@li...> - 2005-08-07 18:37:48
|
Neil Cherry wrote: > Gregg Liming wrote: > >> Neil Cherry wrote: > > >>> The second is more important and may reveal my lack of knowledge >>> of MH. How do I bring up MH without using the CM11A? >> > >> you mean to keep from getting errors? just add the following to your >> private ini: >> cm11_port= > > > I thought that might do it but wasn't sure. Thanks > > Now on to the next step, how do I a 'driver' for the cm15a to > replace the cm11a? Currently Bruce has a bunch of interface tied > into the main code loop. Is there a way to replace all that code > with some that allows the user to select the devices he has. This > would keep the main loop from growing and probably lessen the > amount of memory MH uses (not too sure of that). > What kind of a driver are you thinking? Is it a "stand-alone daemon" or something that relies on existing mh code? If the former, consider getting the daemon to be xAP BSC compliant. I hope to soon complete BSC support in mh and that would allow the daemon to run uncoupled from mh (getting the same advantages as using a mh proxy). If the latter, then consider using Lynx10PLC and corresponding common code as a model. It did not require mods to bin/mh (your reference to "the main code..."). Note that this approach may(likely will) require an update to Serial_Item. > Currently I have the CM11A doing my dirty work but I'm working on > the CM15A. In the mean time I have the Ocelot I can drop in. > |