Is this expected? It has me baffled. Initially this was noticed when trying to configure the bldc component with a pseudo-absolute encoder, but I see the same thing with my jogwheel encoder.
set the jogwheel rawcounts to 300 halmeter shows hm2_5i23.0.encoder.02.rawcounts as 300 halcmd net enc hm2_5i23.0.encoder.02.rawcounts conv_s32_float.0 halmeter shows hm2_5i23.0.encoder.02.rawcounts = 0 ???! move jogweel, halmeter shows 40 delsig enc -> halmeter goes back to 300. The actual thing I am trying to fathom is that when I load my test hal file, the encoder rawcounts shows as 11000, but if I delsig and re-net to bldc it shows 0. The example above was to check whether it was a bldc bug, and conv_s32 was something I knew would have the right pin type. This is with 2.5.0_pre -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men" ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
