- Bdi4emc-help - lists.ourproject.org

RE: Bdi4emc-help Digest, Vol 11, Issue 9
by Craig Gadd 14 Dec '06

14 Dec '06

Thanks for the help! Craig *------------------------------ * *Message: 2 *Date: Tue, 12 Dec 2006 21:04:18 +0000 *From: Paul <bdi4emc(a)bulldoghome.com> *Subject: Re: [Bdi4emc-help] BDI - Motenc-Lite Issue? *To: bdi4emc-help(a)lists.ourproject.org, "abdul.rafiq(a)yahoo.com" * <arafiq1(a)yahoo.com> *Message-ID: <200612122104.18951.bdi4emc(a)bulldoghome.com> *Content-Type: text/plain; charset="iso-8859-1" * *On Sunday 10 December 2006 22:10, Craig Gadd wrote: *> I've been working on my BDI-EMC system this weekend and came across a *> problem that I think may be software related... My setup is a *> Motenc-Lite card with a 7525 IO termination board, and a 7535 IO board. *> *> I have my control system prototyped on a table and have been struggling *to *> get any motion out of the motor(s). I attributed the problem to my *wiring *> "skills" and my proof of damaged was that vsitest.c (available on the *Vital *> site) reported a "Segmentation fault" when compiled and run on BDI 4.50. * *A segfault is usually caused by a null pointer - Looking at the source, *line *79 is the culprit... * * if (dev == NULL) { * printf ("\nVendor %X Device %X\n", dev->vendor_id, dev->device_id); * printf ("PCI Motenc Card Not Found\n"); * return -1; * } * *The first printf uses dev which will always be NULL, hence the segfault... * *> Before I sent my card back, I went and down-revved BDI to version 4.38 *and *> the segmentation fault error went away. The utility seems to function *> properly allows me to communicate with the board, send voltage to the *> amplifier etc. Any thoughts? * *It looks like the the later versions of libpci require the use of *pci_fill_info() before any data can be read from the internal structures - *Without valid data, the tests for vendor & device ID were failing and *triggering the segfault.. Attached is an updated vsitest.c that runs with *the *card I have here. * *Abdul: The changes should be compatable with earlier versions of libpci, so *you may want to update the MOTENC-Lite & MOTENC-100 files.. * * *Regards, Paul. * * * *------------------------------ * *_______________________________________________ *Bdi4emc-help mailing list *Bdi4emc-help(a)lists.ourproject.org *https://lists.ourproject.org/cgi-bin/mailman/listinfo/bdi4emc-help * * *End of Bdi4emc-help Digest, Vol 11, Issue 9 ********************************************

1 0

BDI - Motenc-Lite Issue?
by Craig Gadd 12 Dec '06

12 Dec '06

Hello Paul, I've been working on my BDI-EMC system this weekend and came across a problem that I think may be software related... My setup is a Motenc-Lite card with a 7525 IO termination board, and a 7535 IO board. I have my control system prototyped on a table and have been struggling to get any motion out of the motor(s). I attributed the problem to my wiring "skills" and my proof of damaged was that vsitest.c (available on the Vital site) reported a "Segmentation fault" when compiled and run on BDI 4.50. Before I sent my card back, I went and down-revved BDI to version 4.38 and the segmentation fault error went away. The utility seems to function properly allows me to communicate with the board, send voltage to the amplifier etc. Any thoughts? Regards, Craig

2 1

configuring ini file
by alex 07 Dec '06

07 Dec '06

Hi, folks! I was able to install latest BDI with great success! I have a 4 axis machine, a punch press. All axes are linear. How do I set up an ini file, were can i find a manual for this? Can I use a sherline inch EMC - it looks great! Alex

5 23

synergy
by David Szakovits 03 Dec '06

03 Dec '06

does the version of synergy distributed with bdi have a an expiration period? does it produce g-code? if it expires, i cannot bother to learn it. djs

2 1

RE: X-Axis display problems
by Craig Gadd 02 Dec '06

02 Dec '06

Hi Paul, *On Friday 01 December 2006 15:56, Craig Gadd wrote: *> Package rtai-headers is a virtual package provided by: *> rtai-dev-2.6.16.18-rtai 3.3-4+2 *> rtai-dev-2.6.16.20-rtai 3.3-5+1 *> rtai-dev-2.6.16-rtai 1 *> rtai-dev-2.6.12.6-rtai 2 *> You should explicitly select one to install. *> *> I know I need to include some additional information in get-build *command, *> but am not sure how to include it, can you help me out? * *You need to install the rtai-dev package that corresponds to the kernel *running on your machine - `uname -r` will provide the necessary version *number, or you can use: * * apt-get install rtai-dev-`uname -r` * *This will also pull in the correct kernel-headers and compiler versions for *you.. * To recap, I managed to install the development tools, download the source code and add a -DSIMULATED_MOTORS to the RTFLAGS line in src/Makefile.inc. So last night, I did the following from /src as root: ./configure Make Sudo make modules_install (hopefully this is what you meant when you said to run make modules_install)! Everything recompiled at this point and it appeared to complete successfully. When I launched generic.run however, I still had the same problem with the x-axis display freezing when I manually spun the motor shaft. So as an experiment, I increased the max acceleration and velocity values in the generic.ini file to 100000 and that seems to have solved the problem. I felt like an idiot for not trying that before recompiling everything but at least I now know how. Thanks again for the help Paul. Craig

1 0

RE: X-Axis Display Problem
by Craig Gadd 01 Dec '06

01 Dec '06

Hello Paul, *On Sunday 26 November 2006 16:37, elnerdo(a)cox.net wrote: *> 20,000 counts per revolution is in fact pretty high for an encoder. The *> "latest thing" however is the new sin/cos encoders which output counts in *> the millions. * *The sin/cos encoder referred to in the article only has 1024 "periods" per *rev. The sine waves are then interpolated to produce the 4M discrete counts *with the aid of a dedicated DSP - Presumably, correction tables are *programmed in to reduce cyclic errors and phase variations. * *> I originally thought the video card might be the problem source so I *> replaced it last week (and lowered the period to .0001) but the problem *> still remains. * *Unlikely unless it shares system RAM and/or uses proprietory closed source *drivers * *> My next step is to make an attempt at recompiling without the debounce *> code. I have *some programming experience but a duffer's guide on this *> would be great! Really, any instructions or recommended reading you *could *> suggest would be appreciated. * *First stage is to install the tools and libraries using the command: * * apt-get build-dep emc When I enter this command I get the following message: Package rtai-headers is a virtual package provided by: rtai-dev-2.6.16.18-rtai 3.3-4+2 rtai-dev-2.6.16.20-rtai 3.3-5+1 rtai-dev-2.6.16-rtai 1 rtai-dev-2.6.12.6-rtai 2 You should explicitly select one to install. I know I need to include some additional information in get-build command, but am not sure how to include it, can you help me out? *Then "apt-get source emc" will download and extract the sources to the *current *directory. Run configure in src/ and add -DSIMULATED_MOTORS to the RTFLAGS *line in src/Makefile.inc - A `make modules_install` as root will compile *the *low level module where the "position debounce" takes place - We don't need *to *worry about recompiling & installing any of the user space parts.. * * Thanks, Craig

2 1

RE:X-Axis Display Problems
by elnerdo＠cox.net 27 Nov '06

27 Nov '06

Thanks for the help, guys. 20,000 counts per revolution is in fact pretty high for an encoder. The "latest thing" however is the new sin/cos encoders which output counts in the millions. http://www.engineeringtalk.com/news/enc/enc109.html I originally thought the video card might be the problem source so I replaced it last week (and lowered the period to .0001) but the problem still remains. My next step is to make an attempt at recompiling without the debounce code. I have *some programming experience but a duffer's guide on this would be great! Really, any instructions or recommended reading you could suggest would be appreciated. Regards, Craig *-----Original Message----- *From: bdi4emc-help-bounces(a)lists.ourproject.org [mailto:bdi4emc-help- *bounces(a)lists.ourproject.org] On Behalf Of bdi4emc-help- *request(a)lists.ourproject.org *Sent: Friday, November 24, 2006 3:00 AM *To: bdi4emc-help(a)lists.ourproject.org *Subject: Bdi4emc-help Digest, Vol 10, Issue 4 * *Send Bdi4emc-help mailing list submissions to * bdi4emc-help(a)lists.ourproject.org * *To subscribe or unsubscribe via the World Wide Web, visit * https://lists.ourproject.org/cgi-bin/mailman/listinfo/bdi4emc-help *or, via email, send a message with subject or body 'help' to * bdi4emc-help-request(a)lists.ourproject.org * *You can reach the person managing the list at * bdi4emc-help-owner(a)lists.ourproject.org * *When replying, please edit your Subject line so it is more specific *than "Re: Contents of Bdi4emc-help digest..." * * *Today's Topics: * * 1. Re: X-Axis Display Problem (David Szakovits) * 2. Re: X-Axis Display Problem (Paul) * * *---------------------------------------------------------------------- * *Message: 1 *Date: Thu, 23 Nov 2006 11:43:13 -0500 *From: David Szakovits <dszakovits(a)cfl.rr.com> *Subject: Re: [Bdi4emc-help] X-Axis Display Problem *To: "Help and advice for BDI-4 users." * <bdi4emc-help(a)lists.ourproject.org> *Message-ID: <4565CFA1.8070607(a)cfl.rr.com> *Content-Type: text/plain; charset=ISO-8859-1; format=flowed * *i am not sure that i am not seeing the same sort of thing. i definitely *get some freezing. i have been warned about the on board video that i *have and i am going to buy an AGP card to see if that might fix the *symptom but being a emc-novice, i do not know what to expect or if it *will fix the problem or if at all related. *djs * *Craig Gadd wrote: * *>Hello Paul, *> *>I'm having a problem with my BDI setup and was hoping that you might have *>some advice on a problem I have. I'm running BDI 4.51 with a Motenc Lite *>Card installed. The card is connected through a 50 pin ribbon cable to a *>Vital Systems breakout board which in turn has been wired to a single *>encoder which has 20,000 quad/cts per revolution). *> *>When I launch the generic.run, or emc.run things seem to behave normally *>with the units showing for the axis which has the encoder on it. The *units *>will update if I turn the motor slowly, and everything seems to work. *When *>I spin the motor quickly however, the unit display of the axis seems to *>"freeze" and will not recover. The rest of the interface continues to *>function properly though. Any ideas on what might cause this and how I *>might fix it? I've tried Tkemc,Xemc, and mini but they all seem to behave *>the same. *> *>Thanks, *> *>Craig *> *> *> *>_______________________________________________ *>Bdi4emc-help mailing list *>Bdi4emc-help(a)lists.ourproject.org *>https://lists.ourproject.org/cgi-bin/mailman/listinfo/bdi4emc-help *> *> *> * * * *------------------------------ * *Message: 2 *Date: Thu, 23 Nov 2006 17:51:41 +0000 *From: Paul <bdi4emc(a)bulldoghome.com> *Subject: Re: [Bdi4emc-help] X-Axis Display Problem *To: bdi4emc-help(a)lists.ourproject.org *Message-ID: <200611231751.41344.bdi4emc(a)bulldoghome.com> *Content-Type: text/plain; charset="iso-8859-1" * * *Hi Craig * *On Thursday 23 November 2006 06:52, Craig Gadd wrote: *> The card is connected through a 50 pin ribbon cable to a *> Vital Systems breakout board which in turn has been wired to a single *> encoder which has 20,000 quad/cts per revolution). * *That is a pretty high resolution encoder ! * *> When I launch the generic.run, or emc.run things seem to behave normally *> with the units showing for the axis which has the encoder on it. The *units *> will update if I turn the motor slowly, and everything seems to work. *When *> I spin the motor quickly however, the unit display of the axis seems to *> "freeze" and will not recover. The rest of the interface continues to *> function properly though. Any ideas on what might cause this and how I *> might fix it? * *Many years ago, Fred Proctor (as I recall) was having problems with erratic *encoder counts and added a routine to "debounce" the input - This is hard *coded with an arbitrary limit of 10 times the max velocity. When the rate *of *change per servo cycle ecceeds this limit, any further input is ignored and *a *following error *should be triggered. * *With a 20,000 count/rev encoder and a moderate max velocity, I would *imagine *it would be quite easy to trigger the debounce routine - When you come to *connect the servo amps up and tune the system, as long as you don't go over *the top on the acceleration settings, you shouldn't experience any *problems.. *If you do, we can disable the debounce routine easily enough by *adding -DSIMULATED_MOTORS to the RTFLAGS of src/Makefile.inc.in and *recompiling vitalmod.ko * *If you need a step by step duffer's guide to setting up a build environment *and recompiling the kernel modules, just ask. * * *BTW With any servo system there is nothing to be gained by setting the *BASE_PERIOD parameter anywhere near what you might use with a stepper *system. *0.00005 or 0.0001 should be fine. * * *Regards, Paul. * * * *------------------------------ * *_______________________________________________ *Bdi4emc-help mailing list *Bdi4emc-help(a)lists.ourproject.org *https://lists.ourproject.org/cgi-bin/mailman/listinfo/bdi4emc-help * * *End of Bdi4emc-help Digest, Vol 10, Issue 4 ********************************************

3 2

apt
by David Szakovits 26 Nov '06

26 Nov '06

sorry for the basic questions, but i've been digging around and not figuring this out. my emc2/ubuntu has gcalctool version 5.6.34 but bdi lists 4.4.20 as the current release, i am spoiled by a couple features of the newer version. can i change the repositories for bdi so i get later versions for some of these things. also synergy-cad upgrades each and every time i do apt-get upgrade, can i correct this? thanks djs

3 2

X-Axis Display Problem
by Craig Gadd 23 Nov '06

23 Nov '06

Hello Paul, I'm having a problem with my BDI setup and was hoping that you might have some advice on a problem I have. I'm running BDI 4.51 with a Motenc Lite Card installed. The card is connected through a 50 pin ribbon cable to a Vital Systems breakout board which in turn has been wired to a single encoder which has 20,000 quad/cts per revolution). When I launch the generic.run, or emc.run things seem to behave normally with the units showing for the axis which has the encoder on it. The units will update if I turn the motor slowly, and everything seems to work. When I spin the motor quickly however, the unit display of the axis seems to "freeze" and will not recover. The rest of the interface continues to function properly though. Any ideas on what might cause this and how I might fix it? I've tried Tkemc,Xemc, and mini but they all seem to behave the same. Thanks, Craig

3 2

bdi 4.51
by David Szakovits 16 Nov '06

16 Nov '06

the /usr/local/emc/README file says that emc/doc/emcsoft.html describes how to modify the .ini file. sorry if i am a little slow, but where do i find this file. thanks in advance. djs

2 4