Is this something? http://timeguy.com/cradek-files/emc/0001-Allow-use-of-polar-coordinates-in-radius-angle-form.patch
(@radius<angle is how you say it in autocad)
EMC: 03cmorley 07master * r15a5e19e931d 10/src/emc/usr_intf/pncconf/ (pncconf.glade pncconf.py): Add external MPG jogging code / bug fixing
EMC: 03cmorley 07master * ra188791e982c 10/src/emc/usr_intf/pncconf/ (pncconf.glade pncconf.py): Add external controls page
EMC: 03cmorley 07master * r08a20e694cf1 10/src/hal/utils/meter.c: Add width request option
EMC: 03cmorley 07master * rcab0fdd3f00e 10/docs/man/man1/halmeter.1: Update man page with requested width info
EMC: 03cmorley 07master * rfce62fdcbbc2 10/src/emc/usr_intf/stepconf/stepconf.glade: Add minimum screen resolution warning to openning page
EMC: 03cmorley 07master * r5537df5e8f4d 10/src/emc/usr_intf/pncconf/pncconf-help/help-extcontrols.txt: Add help page for new external controls page
EMC: 03cmorley 07master * r2f318335f270 10/src/emc/usr_intf/pncconf/pncconf-help/ (help-basic.txt help-gui.txt help-welcome.txt): update help pages
EMC: 03cmorley 07master * r3f8b32680796 10/src/emc/usr_intf/pncconf/ (pncconf.glade pncconf.py): Fix pwm signal names, add help page, servo test work
EMC: 03cmorley 07master * r26ddd2301c17 10/src/emc/usr_intf/pncconf/pncconf.py: Remove last bit of code for tlo_along_w - its defunct
chester88: tlo_along_w isn't quite defunct since we haven't merged tlo_all_axes yet
but it's a safe bet that it will be merged, IMO
Ok it's defunct in pncconf. The option is gone. ya micges asked me to remove it
happy holidays guys
chester88: I was thinking about tlo_all_axes branch to do this fix but it's ok
oh I see- I miss understood
as to pncconf testing:
micges: do you feel like that branch is close to merging?
1. changing units on the first screen doesn't change suffixes on fields
yes . the next commits change that- actual adds another screen
cradek: but I'll let you know , I want to do some test few days
cradek: and I want you to do some test with random toolchanger
micges were you testing with actual hardware? servos ? steppers?
micges: anymore I worry more about nonrandom because I am not exercising it
pncconf don't allow me to finish creator yet ;)
micges: but of course I am happy to help you test when you are ready
micges please explain
chester88: I've grayed button on z table limit page
chester88: wait for moment I'll do test again on new master
chester88: basic machine info: spin box with base period have max of 199000 ns (strange)
mesa cards count can be only one
I will add ability of more cards when everything else works
what max should base be?
don't know max allowed but two cards are quite common
my vmc has two 5i20
it's pretty easy to need more than 3 plugs
max spindle override spin have init val 200 but have max set to 190
yes I guess I was hoping evrybody guys the larger card now :)
cradek: there is any max?
micges: motherboards only have so many pci slots
I bet very very few people have 3 cards
chester88: the same with max feed override spin
above that I bet it diminishes even faster
biggest prob I have with adding more cards is I cannot test. I only have one
chester88: I can test
you may be sorry you saif that :) lol
I don't follow the max spindle override problem . you mean it won't spin to 200?
if you have done skeleton, I have electronic change on one machine to two mesa, I can give it try for debugging stage
chester88: yes, init value is 200 but max is 190
I have not done any work for two cards. Actual haven't even though how I would do it.
so you have to set max to 200 or set init val to 190
I'm trying it and it spins up to 200? oh are you using metric?
chester88: did you locate all issues?
what are you referring to?
I mean spin boxes issues I noticed
this is undr GUI configuration, general gui defaults?
you cannot set max override to 200 percent?
yes in metric
strange I can.
with spin box buttons?
so you mean it starts at 200 but if you lower it you can not but it back to 200?
ok you metric what else xyz machine? Axis display?
so it is something with localisation
not sure how to fix that
ok this is minor
still in metric on mesa io setup page there is wrong number of GPIO (I have 48 instead of 72)
default of that page is 5i20 firmware svst8_4
suffixes should be hz instead of htz
no number should be 48. it is the number of gpio not pins
and I cannot set any pwn stepgen or encoder values other than 0
hmmm I can
if frequency it is spelled Hz, not hz or htz
as you change the number of components the GPIO number should go up and down
and on PID pages I have many float errors due to ',' sign
ahh someone else complained of this. He was from Germany. I don't know how to fix it but I think he did.
I will look in my emails...
chester88: so this is mainly why I can't end creator ;)
I would bet. It works pretty well for me. If I remember he changed something locally and the , . problem was fixed > I am still looking
I can do some more checks when you find it out
micges: what language are you using?
K I emailed the guy for more info. I can't find the email. He may have just found a way around the problem
let me know about progress
Ok Thanks for feed back!
It helps alot!
Thank you. I'm trying!
I will think about the two mesa card deal
cradek: it could be cool if we add callbacks for hal pin changes
if we had*