Re: [Machinekit] Machinekit Advanced HAL Tutorial

[schoone...@gmail.com]

Also, params are deprecated and have been done away with in some cases and eventually all. They originate from a time when it was not possible to set pins to a default value in code for components. Therefore params were used and set after the component was instantiated but before attaching it to a thread and starting it. They are still retained in some components, so there is a bit of a mix currently. Pins can either be set and read, or just read depending upon the requirement and type. If you run these lines, you will see the component and a signal, but you have to create it first $ DEBUG=5 realtime restart $ halcmd loadrt siggen $ halcmd net mysig siggen.0.sawtooth $ halcmd show all $ halrun -U Obviously you need to create a thread, attach siggen and start the thread before you see any meaningful values in the pins or signal regards On 15/12/18 06:53, Bas de Bruijn wrote: Hi Scott, On 15 Dec 2018, at 02:09, Scott Nortman <scott.nort...@gmail.com> wrote: Hi, Just installed Machinekit to a rpi3b+ via apt-get and I am running through the tutorial here: http://www.machinekit.io/docs/hal/tutorial/#introduction-a-id-sec-tutorial-intro-a The strange issue: When I instantiate the siggen component, all of the pins, signals, and parameters for the component appear as 'Pins'.  For example, after instantiation, when I type halcmd: show pin Component Pins:   Comp   Inst Type  Dir         Value  Name                                            Epsilon Flags  linked to:     78        float IN              5  siggen.0.amplitude                      0.000010 --l-     78        bit   OUT          TRUE  siggen.0.clock                          --l-     78        float OUT     0.8441676  siggen.0.cosine                          0.000010 --l-     78        float IN              1  siggen.0.frequency                      0.000010 --l-     78        float IN              0  siggen.0.offset                          0.000010 --l-     78        float OUT          2.78  siggen.0.sawtooth                        0.000010 --l-     78        float OUT     -4.922822  siggen.0.sine                            0.000010 --l-     78        float OUT             5  siggen.0.square                          0.000010 --l-     78        float OUT          0.56  siggen.0.triangle                        0.000010 --l-     78        s32   OUT          5261  siggen.0.update.time                    ----     78        s32   I/O         65155  siggen.0.update.tmax                    ----     78        bit   OUT         FALSE  siggen.0.update.tmax-inc                ----     66        s32   OUT        999411  test-thread.curr-period                  ----     66        s32   OUT          5261  test-thread.time                        ----     66        s32   I/O         65155  test-thread.tmax                        ---- halcmd:  And when I attempt to see the parameters, nothing shows up: halcmd: show param Parameters:  Comp    Inst Type   Dir         Value  Name halcmd:  Also, when I run the halmeter, all items show up under the 'Pins' tab and no items show up under the Signals or Parameters tab (see image) Any thoughts? This has to do with the fact that that component has no parameters, nor are there signals in your setup. The term Signal refers to a type which connects 2 pins. Although you think your siggen component creates signals (sine, cosine, square, saw, triangle) these are not the hal types we call “signal” Bas Thanks and best regards, Scott -- 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+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. <halmeter.png> -- 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+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.