> > I assumed all added symbols should have loadrt and a thread but this is not > > always the case. > > There are only really three options in common use. loadrt / addf to > the base thread, loadrt / addf to the servo thread and loadusr. > > One way to handle that might be to drop the functions into one of > three re-sizable panes on the screen. > > I wonder if Scilab is a better fit? I have coded real-time systems in LabVIEW.
They are not to different in an electric network a signal is driven from one source and the same apply for xcos in Scilab or Simulink. I guess all blocks could be expressed a function called at regular intervals and the lines decide from which input the arguments should come. Gschem is also to some extent suitable for cable drawings so I it might be a better choice because of this. As is now I stick with gschem because it is rather close to be useful. With the correct symbols I guess it would be possible to generate a netlist suitable for Xcos or Simulink style simulation although spice is maybe not useful. > (A large proportion of the real-time code at work is compiled directly > from Simulink models, and that that isn't is documented in Ascet > diagrams.) The real time code could quite often be expressed in the form of ordinary algebraic equations. There is input on one side and output on the other and most often in the real system this will end up in a function called at regular intervals. Some of the blocks in linuxcnc is the same as in Simulink or Scilab xcos but I think there is no hostmot driver in Simulink and it could not generate the *.hal file to connect the blocks or function calls. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
