weird - someone just sent me a change he made to truetype-tracer because he thinks the license (GPL2 or later) requires that he send any changes to me.
ries_ is now known as ries
ries_ is now known as ries
I just want to note while I remember: in master docs there is no info about halui.joint.unhome pins and there is no info about VOLATILE_HOME in homing ini configs section
both functionality are in 2.4 too
what does VOLATILE_HOME do? and what section is that in?
as for VOLATILE_HOME option everything is ok
only unhome pins
VOLATILE_HOME is option to used with stepgen joints, if you disable machine, those joints are automatically unhomed
so you must home machine again to continue program
and you not loose accuracy
micges: I'm trying to connect a feed override knob that puts out a binary 0-12 to indicate the feed override position.
have you done this?
phisically no but I emulate such thing connected to halui, it works fine
I can get it to work somewhat by using ladder to "press" the halui.feed-override.increase and decrease pins but it misses sometimes
I tried using hal comp to make the compare between the input and halui.feed-override.value but that does not work
don't react for pin change? how fast are you clicking?
yes if I turn the knob too fast it does not react to the pin change
not very fast
it needs to work as fast as I can move the knob with my hand
I've noticed that while making many pin changes, not everything is processed
if things don't look right I would turn the knob as fast as possible to 0 or 10% position and watch or abort
looks like halui have not enought time
I would think that if the knob was suddenly at 0 that the code would keep moving till feed override was at 0 but it does not for some reason
I wonder if a comp would be better for this task?
I would try with knob => halui (phisically) and see if it works properly
if not then I would think on another soulution
but halui only takes and increase and decrease pin not a number that I know of
just looking at the man pages for 2.4 and 2.5 I don't see info about halui.joint.unhome pins
EMC: 03micges 07master * r893b9628d5e4 10/docs/src/gcode/main.lyx: remove words from quick reference table
EMC: 03micges 07master * r1904aa313f17 10/docs/src/ (common/User_Concepts.lyx gcode/coordinates.lyx): add a bit more on coordinate systems
EMC: 03micges 07master * r47b13f912192 10/src/emc/usr_intf/pncconf/pncconf.py: Fix description of 7i43 firmware in pncconf
EMC: 03micges 07master * r67944f4933b7 10/src/emc/task/emctaskmain.cc: Unhome VOLATILE_HOME joints also after external estop
EMC: 03micges 07master * r06b93f6f250d 10/ (13 files in 13 dirs): Revert "make sure that canon path control mode is equal motion path control mode"
EMC: 03micges 07master * rd55f52d8c486 10/ (18 files in 17 dirs): Merge branch 'v2.4_branch'
halui.joint.unhome is in the manual but not in the man page
hmmm looks like the man page is a manual troff document
I'm glad Slavko K found both those bugs before we released 2.4
I didn't looked for estop latch bug yet
I have never even understood how that component is supposed to work
(so I use ladder for that)
* micges goes for a ride
[19:26:21] <alex_joni> http://imagebin.ca/view/kx47Xv.html
mach clones anyone?
[19:27:30] <alex_joni> http://imagebin.ca/view/W2N4Oio.html
is it working?
micges: he's working on skins now
the rest of it is working afaik
but it's pre-beta
good night all