haha (chris morley's message)
jepler: after applying your sane period patch joint velocity are precise close to 0.00001 mm/min, before there was about 0.5 mm/min
before: F500, fb_vel = 500,5
now F500 fb_vel = 500.0000
EMC: 03cmorley 07TRUNK * 10emc2/src/emc/usr_intf/stepconf/ (stepconf.py stepconf.glade): (log message trimmed)
EMC: work to improve loading of selected ladder program, copying of ladder program to
EMC: user directory. added widgets to select base address and direction type of two
EMC: more parallel ports. Stepconf only connects signal names to the pins. for now
EMC: it's up to the user to connect to the signals in the custom hal file. added text
EMC: to README so user can can lookup examples of these names. Hope nobody is upset
EMC: about the parport mods...still need to add dialog to warn about overwiting of
hmmm gs2_vfd still causes a Communications Warning: Illegal data value - The data value received in the command message is not available for the AC drive.
gs2_vfd.spindle-speed and spindle-on do not do anything but spindle-fwd works fine...
but it might only be spindle-on when testing the hz is not displayed until your running
all the items from the drive seem to show up in HAL configuration watch window fine
EMC: 03bigjohnt 07TRUNK * 10emc2/src/hal/user_comps/gs2_vfd.c:
EMC: fixed parameter and pin having the same name which caused hal configuration show window to show the
EMC: value for the parameter instead of the pin
ok, I got spindle-on working but speed-command does not get to the drive... perhaps that is the root of the error
ok got speed-command to work but a value of 30 is 2.0 on the drive...
ok 30 is rpm not hz...
heh - sounds like you are having fun :)
yep, about to get it figured out so I can write the manual :)
ok, now the error message is gone
again - you are doing great work!! Thanks again.
weeee it works... now to make a working config :)
what does anything think of adding the ability to specify [HAL]ERRORS=continue in an emc2 inifile? this would arrange to pass the "-k" option to halcmd, and might ease testing
I'm not sure it should be apermanent thing like an ini option
but it sounds like a good idea otherwise (maybe an emc script option)
yeah, that makes a bit more sense
jepler: are you going to apply the period patch?
jmkasunich: no, I still haven't tried to do it "the right way"
I wish "de-legacying" wasn't so hard
EMC: 03jepler 07TRUNK * 10emc2/scripts/emc.in:
EMC: fix(?) problem reported by Les Newell about realtime not unloading
EMC: new flag 'emc -k' to help users incrementally develop their hal files
EMC: 03jepler 07TRUNK * 10emc2/src/emc/motion/motion.c: it's not useful anymore to run motion not as a hal realtime component
why is motion.spindle-speed-out a negative number when I issue a S200 M4 from the MDI?
M4 means "go backwards"
so -200 = 200 backwards
I thought spindle-reverse means "go backwards"
yes, that's true too
but you can't have a negative speed...
only a speed...
well, that's true too ;)
btw, the gs2 is running now except for the speed issue
I saw the pin name change, thanks
or param ;)
so is it a mistake for the speed to be negative for M4 or does some other thing use it that way?
I don't think it's a mistake, but it still could be dumb
I don't recall what eventually fixed your gs2 problem - what was it?
ok, you must configure the gs2 to use the commands from the modbus or you get an error if you try and take control from the machine :)
now I remember having to change modes at the keypad whenever there was an error I had to reset
and then switch back for more testing
now if I load the gs2 driver in the custom.hal I have to do any net pin things in custom postgui.hal or I get an error that the pin does not exist
are you loading with loadusr, or loadusr -Wn?
one of the wait options should make it possible to load and connect in the same hal file
oh, have you been using the command-line options for the serial port parameters?
no I just used the default
I'm pretty sure those are working, but it might be good to check
you can also set a different name with -n
is it -Wn or -W and a number?
you can also set a different name with -n, like "spindle"
the letter n
wait for this component name to become ready
so something like loadusr -Wn spindle gs2_vfd -n spindle -d /dev/ttyS1
will give you spindle.motor-RPM ... names
rather than gss2_vfd
you can also leave out the n and -n options: loadusr -W gs2_vfd
ok loadusr -W gs2_vfd works
yep. if you decide to change the name, or add more VFDs or anything, you'll need the -Wn gs2_vfd -n name form
the name form looks like a good idea to keep things clear
is the -Wn for a name form?
yeah, I figured there's a possibility of having a machine with a lathe and mill spindle, so you'd need different names
-Wn means "wait for a component with the following name"
otherwise the component name is the module name
(gs2_vfd in this case)
but when you have things like pyvcp which can have different names depending on what you're doing, you need to tell halcmd that it should wait for something with a different name
so it's loadusr -Wn name (or loadusr, wait for this named component), then gs2_vfd -n name, to make the VFD have that same name
I gotta get this info in the manual... I just did a quick search and came up empy on "-Wn"
man halcmd has it
as does halcmd -h loadusr
I tried man loadusr :(
* BigJohnT finally gets logged in to sourceforge
SWPadnos: that driver is sweet!
hmmm. did I default the cycle time to 0.1 second?
I think so
* BigJohnT heads upstairs to cook Crawfish Cardinal