EMC: 03cmorley 07TRUNK * 10emc2/src/emc/usr_intf/stepconf/stepconf.py: Fix for 'all limit' signals
yay, halscope is fixed?
I think so
then we can branch :-)
any week now
seriously, this cleared my personal backlog of "stuff that needs to be fixed before branch", so we can do it anytime unless somebody says otherwise
can I add the G540.stepconf file?
oh. I guess I should see if it loads with 2.3 stepconf :)
that'd be a nice test
even better if you can test it working
um. yeah, I can, but not tonight
by (the end of) this weekend though
I was hoping to make beta2 before the end of the weekend, but that's life
you can put it on the branch, though, as long as you test the installation and all that
it's just a stepconf file - sort of compact, and peiople can't run it unless they step through the config
I figure that's safer (marginally)
stepconf doesn't hand-hold people choosing files from /usr/share/emc2, or whatever the file would have to go
jepler: I'm similarly clear
yeah, I don't know where it should go
it'll be on the gecko site for sure, we can have it on the wiki, and otherwise - uh
jepler, I get this:
Traceback (most recent call last):
File "/usr/bin/stepconf", line 1380, in on_pport_prepare
ValueError: list.index(x): x not in list
going from the basic machine information page to the port/pin mapping page
and all pins are unused
should I build from cvs to see if this is fixed? (this is from 2.3~betawhatever)
SWPLinux: yes, I fixed it on TRUNK today
ok, it loaded with a fresh build
I didn't actually test the hardware though, since I've disconnected some things (like the power supply)
added a little more validation and arrow keys which broke some stuff, that i then fixed (i think) http://filebin.ca/gbjbo/tooledit.tcl
Anyone awake in here?
Goodie! In this line: "net spindle-speed-cmd motion.spindle-speed-out => pwmgen.0.value" what is the first 'spindle-speed-cmd' good for? I know that net ties these things together but wouldn't it suffice with the latter two?
its the name of that signal
when you create signal with net command then if you want use that signal later in hal to connect to something more, you can only access it by name
ok, and motion.spindle-speed-out is the pin? so why do we need to tie the signal to the pin? Don't understand this yet.
Now I see
Were you in here yesterday when we discussed my laser-issues?
ah lasers :)
Tottish: whats the problem ?
Have you heard any of the discussions yesterday and before that about solving a problem with turning a laser on/off while moving at constant speed in X/Y?
writting in hal is the only resolution for now
better: I must write such module soon so you could chatch sources of simmilar one
Oh really? Yesterday I was to understand from SWPadnos that I would have to change the sourcecode
Tottish: to be sure: I don't have time now to dig logs, can you shortly describe what you want to do and problems do you have up to now
I'm at work now :)
Hmmm, I guess it's pretty complicated but the problem seemed to be that I wanted to stream values from a textfile. Then, they said, I have to use something called halstreamer and userspece and for that I had to change the sourcecode. Can't say I understood the half of it and it seems like a lot of work to me so the reason I asked you if you knew about my problems was that I wanted to try a new idea.
One which I would think is possible to solve without digging deeper from HAL.
Are you up for a little Idea-Bouncing? Really, It's ok if you have to work... =P
OK, one quick question, then: Is there a pin or something containing the current velocity of an axis?
never mind, found it!
micges_emc: Tottish wants to do laser engraving/burning
but doing it with raster scanning
moving the laser left-right on a line, then advance to the next line, etc
the issue is to turn the laser on at the exact time during the raster scan
do you have time for a little chat alex?
alex_joni: funny but I'm designing same machine here :D
Tottish: yup, I have at the moment
micges_emc: I suggested a possible solution, which I'm sure you can implement ;)
but it will be about month to write that module :)
I don't think so
it should be a day or so
especially since you can compile emc2 for simulator and debug it
err I can start write it in may ;)
Nice, So I'm thinking about speedcompensating. What about putting the value from motion.current-vel in the the pwm-value for a pwmgen and use a digital-out to enable the PWMgen. Invert the pin and you should have a decent inverted value of the speed to the power of the laser. You shuld probably put a SCALE in between but a testrun would do without it. What do you think?
update in servothread and makepulse in base thread
should give a nice responsetime
Tottish: I have that module
it's working nicely
Tottish: I must work, remember me soon
alex:why do you figure he needs this new module if the old one workes fine?
I'm not sure what module micges has
but probably the one for pwmgen
Sounds like it, but why would a full-line rasterscan be preferrable? If this new idea is working it sounds like a better way to me...
new for me, that is... =)
er.. I don't understand
please try to be more explicit when talking about things than "this new idea"
What I wrote in the long post about 10 posts up...
there have been at least half a dozen new ideas lately, and my psychic skills are pretty low atm
thats 'the new idea
speedcompensated pwm ?
then write that.. not that hard :)
I have my doubts (just gut feelings) you'll get much better results
I will try, hav never done HAL before. I was just wondering if you had a clue about why a rasterscan would be preferable. ==)
Yeah, may be so. I'll give it a shot. Wish me luck!
good luck :)
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/hal/images/halscope-11.png: add images
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/hal/tutorial.lyx: finished updating this one afaik
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/hal/tutorial.lyx: minor edits
Hey, Can I tie a float from a parameter to a signal? I want to use the motion.current-vel in the pwmgen.0.value... It seems the net-command only tie pins and signals?
if it is RW I think you can
Then maybe it's not because I get an error "pin 'motion.current-vel' does not exist" But I kind of already knew that since it's a parameter... =)
ok I missed the parameter part
OK, but this must be doable, right?
you can't connect parameters to anything
except using halscope to see them
there is a component which watches parameters and outputs the same value on a pin, but that is not realtime, and won't help you
bah, then how will I get the Velocity into the PWM?.... grrrr...
otoh, look at the sim config, there is another way to get the velocity
using ddt blocks
hmmm, ok, I'll be honest: I have no idea what that means. =) Does it mean I will have to (re)compile the source in the end? Were should I start looking?
Tottish: you do know what a configuration is.. right?
and that there are sample-configs we distribute
and along those there is a folder called sim/
and inside there are some "sim" configs
composed from .hal + .ini + ...
if you look in the hal files you'll see a current vel
OK, I created my configs with stepconfwizard is there a velocity component in one of those?
I'm quite sure there isn't
[12:00:50] <alex_joni> http://cvs.linuxcnc.org/cgi-bin/cvsweb.cgi/emc2/configs/common/core_sim.hal?rev=1.15
there is a hal file which contains the ddt part you'll want to use
Thanks alot, I'm sorry I'm such a noob here. Thanks alot for having patience with me...
but if you want to make this work, I would rather try to learn what a full configuration looks like, how thins work, and how they interact .. instead of using stepconf
stepconf is nice & easy, but at one point it's limited, and more of a problem than a help
yeah I suppose thats what I'm doing now... but I use the stepconf generated files as a base...
I've read the Integrator manual and most of the HAL tutorial so I'm starting to get the picture...
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/hal/ (hal-examples.lyx tutorial.lyx): add file
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ (Master_Integrator.lyx Submakefile docs.xml index.tmpl): add hal-examples to integrator and html
It seems I succeeded in making the speedcompensating HAL-script! I have yet to try it out on the machine, though. In any case it's a small victory to me. Thanks alot for the help alex!
Tottish: what did you end up doing?
Speedcompensating, with the XY-velocity input into the PWM for the laser. And ON/OFF on a M64-Digital output thingy. I'll probably test later today to see how even the result gets. I figure I migh be able to SCALE the value to match my lasers output/dutycycle-curve but this is a good start!
Jippie! It seems to work nicely.. still needs more testing though...
EMC: 03tissf 07TRUNK * 10emc2/docs/src/hal/tutorial_fr.lyx: french translation update
EMC: 03tissf 07TRUNK * 10emc2/docs/src/ (6 files): french translation update - to follow John
EMC: 03tissf 07TRUNK * 10emc2/docs/src/hal/ (hal-examples_fr.lyx tools_fr.lyx tutorial_fr.lyx): french translation update - to follow John
Guest374 is now known as skunkkworks