7i77 testers wanted
11 Mar 2012 01:18 #18519
by cmorley
7i77 testers wanted was created by cmorley
I have just pushed 7i77 support to PNCconf into the 2.5 repo
I am looking for testers.
here is a zipped folder to place into /lib/firmware/hm2 ( unzip it first )
You will need sudo rights to do that ( sudo nautilus typed into a terminal will fire up a graphical sudo file broswer)
if your 5i25 was supplied with 7i77x2 firmware then PNCconf can configure it.
there is actually firmware support for 7i76x2 and prob_frx2 in that folder too if you have those firmware preloaded.
I expect there will be an odd bug as I can not actually test it, besides looking at the files it produces.
Live testing in PNCconf surely doesn't work.
Please give feedback here.
Thanks
Chris M
I am looking for testers.
here is a zipped folder to place into /lib/firmware/hm2 ( unzip it first )
You will need sudo rights to do that ( sudo nautilus typed into a terminal will fire up a graphical sudo file broswer)
if your 5i25 was supplied with 7i77x2 firmware then PNCconf can configure it.
there is actually firmware support for 7i76x2 and prob_frx2 in that folder too if you have those firmware preloaded.
I expect there will be an odd bug as I can not actually test it, besides looking at the files it produces.
Live testing in PNCconf surely doesn't work.
Please give feedback here.
Thanks
Chris M
Please Log in or Create an account to join the conversation.
- wanispissd
- Offline
- New Member
-
Less
More
- Posts: 6
- Thank you received: 0
26 Mar 2012 02:42 #18798
by wanispissd
Replied by wanispissd on topic Re:7i77 testers wanted
Hello Chris,
I attempted to run PNCconf with the 7i77 file (attached above) this weekend, and while it came up I could not do much with it. I would love to use PNCconf to setup my system, although given my limited Linux abilities, I am not sure how helpful I will be for any in-depth troubleshooting.
First, a little background on my setup. I installed LinuxCNC v2.5 pre-release onto a dedicated control PC (Intel D510MO based - specific built to avoid hardware issues). I have a Mesa 5i25 + (single) 7i77 along with a 7i69. The 7i69 breakout is connected to two Opto22 boards, and connected back to the PC thru the RS422 on the 7i77. The machine is a Sajo knee mill, which arrived to me with a dead Heidenhain TNC151 control. Its been a long term project, but now that my garage is insulated I am determined to finally figure it out. I started the project with a Vital System Motenc Lite (4 axis) card, which I was able to read/write I/O thought the Opto22 boards, but never got spindle or axis control working (limited by lack of 380v 3phase supply). It has a rotary 4th axis also, which is why I am now going the Mesa route (to get 4th axis and rigid tapping).
On the Mesa0 I/O page, I have the 7i77x2 firmware and can get past this first page. The next step gives me a number of tabs, here is where I can select a 7i69 or other daughter card and assign other I/O pins. The final tabs have selections for PWM output, which I believe should be Analog output. Once past this step, I get to the point where I can configure the X axis. The axis configuration does not go well... I am unable to test the axis, or move forward to any further selections. The ability to move forward to finalize/create an initial configuration would be helpful (or perhaps I did not get the right thing together to un-grey the selection).
While I was experimenting with the PNCconf for the 7i77, I thought of two features that would really be useful. The first is the ability to select 5i25 ports (only one 7i77, for example) on the first page, which would hide the unused tabs generated on the second step. The second feature that I thought would be useful, would be the ability to define custom I/O names (maybe load a text file on the initial page). The custom I/O names would then be imported into the selections for assigning the I/O in the subsequent step.
Anyway, If you can post an updated version that allows selection of Analog output to axis drives I would be glad to give it another shot. Thanks for all the work you've done to make setup much more accessible.
- Brian
I attempted to run PNCconf with the 7i77 file (attached above) this weekend, and while it came up I could not do much with it. I would love to use PNCconf to setup my system, although given my limited Linux abilities, I am not sure how helpful I will be for any in-depth troubleshooting.
First, a little background on my setup. I installed LinuxCNC v2.5 pre-release onto a dedicated control PC (Intel D510MO based - specific built to avoid hardware issues). I have a Mesa 5i25 + (single) 7i77 along with a 7i69. The 7i69 breakout is connected to two Opto22 boards, and connected back to the PC thru the RS422 on the 7i77. The machine is a Sajo knee mill, which arrived to me with a dead Heidenhain TNC151 control. Its been a long term project, but now that my garage is insulated I am determined to finally figure it out. I started the project with a Vital System Motenc Lite (4 axis) card, which I was able to read/write I/O thought the Opto22 boards, but never got spindle or axis control working (limited by lack of 380v 3phase supply). It has a rotary 4th axis also, which is why I am now going the Mesa route (to get 4th axis and rigid tapping).
On the Mesa0 I/O page, I have the 7i77x2 firmware and can get past this first page. The next step gives me a number of tabs, here is where I can select a 7i69 or other daughter card and assign other I/O pins. The final tabs have selections for PWM output, which I believe should be Analog output. Once past this step, I get to the point where I can configure the X axis. The axis configuration does not go well... I am unable to test the axis, or move forward to any further selections. The ability to move forward to finalize/create an initial configuration would be helpful (or perhaps I did not get the right thing together to un-grey the selection).
While I was experimenting with the PNCconf for the 7i77, I thought of two features that would really be useful. The first is the ability to select 5i25 ports (only one 7i77, for example) on the first page, which would hide the unused tabs generated on the second step. The second feature that I thought would be useful, would be the ability to define custom I/O names (maybe load a text file on the initial page). The custom I/O names would then be imported into the selections for assigning the I/O in the subsequent step.
Anyway, If you can post an updated version that allows selection of Analog output to axis drives I would be glad to give it another shot. Thanks for all the work you've done to make setup much more accessible.
- Brian
Please Log in or Create an account to join the conversation.
26 Mar 2012 03:20 #18799
by cmorley
Replied by cmorley on topic Re:7i77 testers wanted
Brian
First thanks for testing and reporting.
How long ago was your 2.5 updated. I want to make sure you have the most updated version - though I'm pretty sure you do.
First if you want to deselect the second 7i77 from the second 5i25 port :
go to the configuration page set the encoders to half (6) the number of channels to half (3) and press accept components.
do this before configuring anything. It will hide the unused tabs and free up some GPIO pins on the 5i25's second I/O port.
Yes I know it's not initiative - something to work on.
second if you can't move forward nor test then either an encoder, a pwm or the scaling of the encoder has not been selected.
If the encoder or PWM wasn't selected you should have got a warning window pop up to tell you, so did you set the scaling?
custom names are available by typing in an unique name and pressing return.
Yes having them loadable for a new config would be a nice feature.
One way around this, assuming you always use the same board type is to reload a config that has all your custom signal names then rename and edit it.
Peter (from Mesa) and Andy (driver writer) have kept me very busy trying to keep up.
PNCconf is my attempt to give back to linuxcnc and help lesson the steep learning curve.
It is easier to keep working on something if you can at least get it to move in fairly short time!
Again thanks for the feedback
Chris M
First thanks for testing and reporting.
How long ago was your 2.5 updated. I want to make sure you have the most updated version - though I'm pretty sure you do.
First if you want to deselect the second 7i77 from the second 5i25 port :
go to the configuration page set the encoders to half (6) the number of channels to half (3) and press accept components.
do this before configuring anything. It will hide the unused tabs and free up some GPIO pins on the 5i25's second I/O port.
Yes I know it's not initiative - something to work on.
second if you can't move forward nor test then either an encoder, a pwm or the scaling of the encoder has not been selected.
If the encoder or PWM wasn't selected you should have got a warning window pop up to tell you, so did you set the scaling?
custom names are available by typing in an unique name and pressing return.
Yes having them loadable for a new config would be a nice feature.
One way around this, assuming you always use the same board type is to reload a config that has all your custom signal names then rename and edit it.
Peter (from Mesa) and Andy (driver writer) have kept me very busy trying to keep up.
PNCconf is my attempt to give back to linuxcnc and help lesson the steep learning curve.
It is easier to keep working on something if you can at least get it to move in fairly short time!
Again thanks for the feedback
Chris M
Please Log in or Create an account to join the conversation.
- wanispissd
- Offline
- New Member
-
Less
More
- Posts: 6
- Thank you received: 0
27 Mar 2012 02:48 #18823
by wanispissd
Replied by wanispissd on topic Re:7i77 testers wanted
Hello Chris,
The version I have is 2.5.0-pre2, which I compiled from source on using instructions found on the wiki. I pulled the version of the 2.5 branch that was most recent on git, this past Saturday night (3/24).
I tried again tonight, and set the encoder scales. This worked and I was able to move on to the point where a configuration was generated. I encountered two issues. First, while setting up any axis in Open Loop Test, I would get the following error when enabling the amp:
I am not sure if the is expected / normal but the + / - jog would become un-greyed after this step. When I would click either, I get a similar error as above but with reference to the Jogminus or Jogplus. I did not assign any I/O to these, but did assign I/O (on the 7i69 card) for amplifier enable.
My next issue is that once the configuration is created and a shortcut is on the desktop, emc will simply not start. I get a splash screen here, but axis will not come up. I do have axis coming up while loading the 5i25 + 7i77 configuration that Big John T has put up in the Mesa FAQ section of the forum. This is where my lack of experience shows, as I do not have the slightest clue how to begin to diagnose.
I agree that seeing motion is a great start - tonight I was able to move my X, Y, and Z axis servos using the AAA battery trick. My Y axis servo drive seems to be messed up, but thats another issue. It will only turn one direction, and resist motion in one direction - it can be spun by hand in the other. I swapped the Y motor to the X axis, and it worked fine using the X axis drive/cables (both directions). I verified cables, but have not yet tested the X axis motor with the Y (suspect) drive. Suggestions are welcome here, although its quite off topic.
Tomorrow night I will try to get motion on the X axis from EMC, hopefully with the Mesa setup.
I do like the PNCconf setup!
- Brian
The version I have is 2.5.0-pre2, which I compiled from source on using instructions found on the wiki. I pulled the version of the 2.5 branch that was most recent on git, this past Saturday night (3/24).
I tried again tonight, and set the encoder scales. This worked and I was able to move on to the point where a configuration was generated. I encountered two issues. First, while setting up any axis in Open Loop Test, I would get the following error when enabling the amp:
PNCconf encountered an error. The following information may be useful in troubleshooting:
Traceback (most recent call last):
File "/home/varnamo/emc2-dev/bin/pncconf", line 9106, in on_enableamp_toggled
self.update_axis_params()
File "/home/varnamo/emc2-dev/bin/pncconf", line 9076, in update_axis_params
halrun.flush()
IOError: [Errno 32] Broken pipeI am not sure if the is expected / normal but the + / - jog would become un-greyed after this step. When I would click either, I get a similar error as above but with reference to the Jogminus or Jogplus. I did not assign any I/O to these, but did assign I/O (on the 7i69 card) for amplifier enable.
My next issue is that once the configuration is created and a shortcut is on the desktop, emc will simply not start. I get a splash screen here, but axis will not come up. I do have axis coming up while loading the 5i25 + 7i77 configuration that Big John T has put up in the Mesa FAQ section of the forum. This is where my lack of experience shows, as I do not have the slightest clue how to begin to diagnose.
I agree that seeing motion is a great start - tonight I was able to move my X, Y, and Z axis servos using the AAA battery trick. My Y axis servo drive seems to be messed up, but thats another issue. It will only turn one direction, and resist motion in one direction - it can be spun by hand in the other. I swapped the Y motor to the X axis, and it worked fine using the X axis drive/cables (both directions). I verified cables, but have not yet tested the X axis motor with the Y (suspect) drive. Suggestions are welcome here, although its quite off topic.
Tomorrow night I will try to get motion on the X axis from EMC, hopefully with the Mesa setup.
I do like the PNCconf setup!
- Brian
Please Log in or Create an account to join the conversation.
27 Mar 2012 03:11 #18824
by cmorley
Replied by cmorley on topic Re:7i77 testers wanted
Hi Brian.
Ok I am assuming that you have an installed version of linuxcnc and a git version. Is this true? What is the installed version if yes.
open a terminal cd to the folder you compiled the git version.
type :
. scripts/rip-evironment
after that you can run pncconf by typing it's name or start linuxcnc by typing its name.
this is the preferred way to run these when debugging because some messages are printed to the terminal that you usually can't see.
for instance the "broken pipe" error is most likely an actual HAL error - the message would be printed to the terminal.
maybe a misspelled pinname.
try running the pncconf config from the terminal instead of the shortcut. The shortcut works well on an installed version - often not so good on compiled versions. this is because the shortcut always runs the installed version. if the installed and compiled are different then that can cause problems.
Chris m
Ok I am assuming that you have an installed version of linuxcnc and a git version. Is this true? What is the installed version if yes.
open a terminal cd to the folder you compiled the git version.
type :
. scripts/rip-evironment
after that you can run pncconf by typing it's name or start linuxcnc by typing its name.
this is the preferred way to run these when debugging because some messages are printed to the terminal that you usually can't see.
for instance the "broken pipe" error is most likely an actual HAL error - the message would be printed to the terminal.
maybe a misspelled pinname.
try running the pncconf config from the terminal instead of the shortcut. The shortcut works well on an installed version - often not so good on compiled versions. this is because the shortcut always runs the installed version. if the installed and compiled are different then that can cause problems.
Chris m
Please Log in or Create an account to join the conversation.
17 Apr 2012 02:12 #19260
by maxvdh
Replied by maxvdh on topic Re:7i77 testers wanted
Hi Chris,
I'm not sure how helpful I'll be but since there don't seem to be too many replies on this thread I'll give this a shot. I'm new to LinuxCNC, Mesa cards, and linux, so getting this running is a bit of a challenge for me. I've set up a computer with a 5i25 and 7i77 with my machine and installed LinuxCNC 2.5 using the buildbot. I haven't connected all of my I/O yet; I was thinking I'd start with one axis (4th - C axis), see if that works, and then add everything else on from there. I know that axis can't really do any damage if something goes wrong. I've connected the encoder to the encoder 3 pins (TB4:1-8). I copied the xml files onto my machine as directed and ran PnCConf. I basically ignored everything but the encoder assignments where I set
Encoder 0 - X axis
Encoder 1 - Y axis
Encoder 2 - Z axis
Encoder 3 - A axis (I'll have to change this to C at some point but for testing purposes I imagine this works)
Encoder 4 - Spindle Encoder
Encoder 5 - multiaxis handwheel
This is the way I was intending to connect everything finally. I set the W2 jumper on the 5i25 to supply logic power to the 7i77 and I see yellow LEDs on it but I did not apply any field power - I wouldn't think it was needed just to look at an encoder.
I was able to go through all the dialogs and start EMC2, selecting the configuration I had generated. I tried using HAL Scope to look at the encoder 3 signals (all of them) while I ran the 4th axis manually and I saw no activity. However I attached a scope to the input pins and saw +5V/0V square waves coming in from the encoder. Please pardon my ignorance - can you tell me what I'm missing? Thank you,
Max
I'm not sure how helpful I'll be but since there don't seem to be too many replies on this thread I'll give this a shot. I'm new to LinuxCNC, Mesa cards, and linux, so getting this running is a bit of a challenge for me. I've set up a computer with a 5i25 and 7i77 with my machine and installed LinuxCNC 2.5 using the buildbot. I haven't connected all of my I/O yet; I was thinking I'd start with one axis (4th - C axis), see if that works, and then add everything else on from there. I know that axis can't really do any damage if something goes wrong. I've connected the encoder to the encoder 3 pins (TB4:1-8). I copied the xml files onto my machine as directed and ran PnCConf. I basically ignored everything but the encoder assignments where I set
Encoder 0 - X axis
Encoder 1 - Y axis
Encoder 2 - Z axis
Encoder 3 - A axis (I'll have to change this to C at some point but for testing purposes I imagine this works)
Encoder 4 - Spindle Encoder
Encoder 5 - multiaxis handwheel
This is the way I was intending to connect everything finally. I set the W2 jumper on the 5i25 to supply logic power to the 7i77 and I see yellow LEDs on it but I did not apply any field power - I wouldn't think it was needed just to look at an encoder.
I was able to go through all the dialogs and start EMC2, selecting the configuration I had generated. I tried using HAL Scope to look at the encoder 3 signals (all of them) while I ran the 4th axis manually and I saw no activity. However I attached a scope to the input pins and saw +5V/0V square waves coming in from the encoder. Please pardon my ignorance - can you tell me what I'm missing? Thank you,
Max
Please Log in or Create an account to join the conversation.
17 Apr 2012 02:22 #19261
by cmorley
Replied by cmorley on topic Re:7i77 testers wanted
can you go back to PNCconf and try the openloop test feature?
Can you use halmeter to check all the encoders to see if it is working but using the wrong encoder?
You could do this with the regular config too if you like.
The openloop test should be used to confirm encoder count direction and output polarity.
If these don't match a servo runaway will happen - it also helps to confirm things are working.
Can you use halmeter to check all the encoders to see if it is working but using the wrong encoder?
You could do this with the regular config too if you like.
The openloop test should be used to confirm encoder count direction and output polarity.
If these don't match a servo runaway will happen - it also helps to confirm things are working.
Please Log in or Create an account to join the conversation.
17 Apr 2012 02:59 #19262
by maxvdh
Replied by maxvdh on topic Re:7i77 testers wanted
For some reason I wasn't able to get pncconf to load the config file I made the first time so I had to make a new one. I wasn't offered any tabs for configuring the 4th axis as I was with the X, Y, and Z axes and thus there was no opportunity to use the open-loop test. I'm not sure what you mean about the "regular config". Anyway, I tried loading the new config file with emc2 and got a list of errors which I cant decipher -
Print file information:
RUN_IN_PLACE=no
EMC2_DIR=
EMC2_BIN_DIR=/usr/bin
EMC2_TCL_DIR=/usr/lib/tcltk/emc2
EMC2_SCRIPT_DIR=
EMC2_RTLIB_DIR=/usr/realtime-2.6.32-122-rtai/modules/emc2
EMC2_CONFIG_DIR=
EMC2_LANG_DIR=/usr/share/emc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
EMC2_EMCSH=/usr/bin/wish8.5
EMC2 - 2.5.0-pre2-626-g402b6cd
Machine configuration directory is '/home/maxvdh/emc2/configs/my_EMC_machine'
Machine configuration file is 'my_EMC_machine.ini'
INIFILE=/home/maxvdh/emc2/configs/my_EMC_machine/my_EMC_machine.ini
PARAMETER_FILE=emc.var
EMCMOT=motmod
EMCIO=io
TASK=milltask
HALUI=halui
DISPLAY=axis
NML_FILE=
Starting EMC2...
Starting EMC2 server program: emcsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting EMC2 IO program: io
Starting HAL User Interface program: halui
Shutting down and cleaning up EMC2...
Running HAL shutdown script
Killing task emcsvr, PID=2879
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Cleanup done
Debug file information:
my_EMC_machine.hal:25: addf requires at least 2 arguments, 1 given
2879
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
Kernel message information:
[ 9381.101640] I-pipe: Domain RTAI registered.
[ 9381.101658] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 9381.101665] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 9381.101719] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 9381.101726] PIPELINE layers:
[ 9381.101733] fce9de20 9ac15d93 RTAI 200
[ 9381.101740] c085cb20 0 Linux 100
[ 9381.166707] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 9381.168462] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 9381.168479] RTAI[sched]: hard timer type/freq = APIC/12487409(Hz); default timing: periodic; linear timed lists.
[ 9381.168488] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 1800183000 hz.
[ 9381.168496] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 9381.168668] RTAI[usi]: enabled.
[ 9381.314945] RTAI[math]: loaded.
[ 9381.635362] hm2: loading Mesa HostMot2 driver version 0.15
[ 9381.644754] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
[ 9381.644827] hm2_pci 0000:05:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 9381.644838] hm2_pci: discovered 5i25 at 0000:05:00.0
[ 9381.647290] hm2/hm2_5i25.0: Smart Serial Firmware Version 31
[ 9381.770415] hm2/hm2_5i25.0: 34 I/O Pins used:
[ 9381.770430] hm2/hm2_5i25.0: IO Pin 000 (P3-01): IOPort
[ 9381.770439] hm2/hm2_5i25.0: IO Pin 001 (P3-14): IOPort
[ 9381.770448] hm2/hm2_5i25.0: IO Pin 002 (P3-02): IOPort
[ 9381.770459] hm2/hm2_5i25.0: IO Pin 003 (P3-15): Smart Serial Interface #0, pin TxData1 (Output)
[ 9381.770471] hm2/hm2_5i25.0: IO Pin 004 (P3-03): Smart Serial Interface #0, pin RxData1 (Input)
[ 9381.770480] hm2/hm2_5i25.0: IO Pin 005 (P3-16): IOPort
[ 9381.770489] hm2/hm2_5i25.0: IO Pin 006 (P3-04): IOPort
[ 9381.770499] hm2/hm2_5i25.0: IO Pin 007 (P3-17): Muxed Encoder Select #0, pin Mux Select 0 (Output)
[ 9381.770513] hm2/hm2_5i25.0: IO Pin 008 (P3-05): Muxed Encoder #0, pin Muxed A (Input)
[ 9381.770522] hm2/hm2_5i25.0: IO Pin 009 (P3-06): Muxed Encoder #0, pin Muxed B (Input)
[ 9381.770532] hm2/hm2_5i25.0: IO Pin 010 (P3-07): Muxed Encoder #0, pin Muxed Index (Input)
[ 9381.770542] hm2/hm2_5i25.0: IO Pin 011 (P3-08): Muxed Encoder #1, pin Muxed A (Input)
[ 9381.770552] hm2/hm2_5i25.0: IO Pin 012 (P3-09): Muxed Encoder #1, pin Muxed B (Input)
[ 9381.770562] hm2/hm2_5i25.0: IO Pin 013 (P3-10): Muxed Encoder #1, pin Muxed Index (Input)
[ 9381.770572] hm2/hm2_5i25.0: IO Pin 014 (P3-11): Muxed Encoder #2, pin Muxed A (Input)
[ 9381.770582] hm2/hm2_5i25.0: IO Pin 015 (P3-12): Muxed Encoder #2, pin Muxed B (Input)
[ 9381.770592] hm2/hm2_5i25.0: IO Pin 016 (P3-13): Muxed Encoder #2, pin Muxed Index (Input)
[ 9381.770601] hm2/hm2_5i25.0: IO Pin 017 (P2-01): IOPort
[ 9381.770609] hm2/hm2_5i25.0: IO Pin 018 (P2-14): IOPort
[ 9381.770617] hm2/hm2_5i25.0: IO Pin 019 (P2-02): IOPort
[ 9381.770625] hm2/hm2_5i25.0: IO Pin 020 (P2-15): IOPort
[ 9381.770632] hm2/hm2_5i25.0: IO Pin 021 (P2-03): IOPort
[ 9381.770640] hm2/hm2_5i25.0: IO Pin 022 (P2-16): IOPort
[ 9381.770648] hm2/hm2_5i25.0: IO Pin 023 (P2-04): IOPort
[ 9381.770657] hm2/hm2_5i25.0: IO Pin 024 (P2-17): Muxed Encoder Select #3, pin Mux Select 0 (Output)
[ 9381.770667] hm2/hm2_5i25.0: IO Pin 025 (P2-05): IOPort
[ 9381.770676] hm2/hm2_5i25.0: IO Pin 026 (P2-06): IOPort
[ 9381.770685] hm2/hm2_5i25.0: IO Pin 027 (P2-07): IOPort
[ 9381.770694] hm2/hm2_5i25.0: IO Pin 028 (P2-08): IOPort
[ 9381.770703] hm2/hm2_5i25.0: IO Pin 029 (P2-09): IOPort
[ 9381.770712] hm2/hm2_5i25.0: IO Pin 030 (P2-10): IOPort
[ 9381.770721] hm2/hm2_5i25.0: IO Pin 031 (P2-11): IOPort
[ 9381.770730] hm2/hm2_5i25.0: IO Pin 032 (P2-12): IOPort
[ 9381.770738] hm2/hm2_5i25.0: IO Pin 033 (P2-13): IOPort
[ 9381.770948] hm2/hm2_5i25.0: registered
[ 9381.770957] hm2_5i25.0: initialized AnyIO board at 0000:05:00.0
[ 9383.154885] hm2_5i25.0: dropping AnyIO board at 0000:05:00.0
[ 9383.154895] hm2/hm2_5i25.0: unregistered
[ 9383.154938] hm2_pci 0000:05:00.0: PCI INT A disabled
[ 9383.154994] hm2_pci: driver unloaded
[ 9383.180932] hm2: unloading
[ 9383.580118] RTAI[math]: unloaded.
[ 9383.723065] SCHED releases registered named ALIEN RTGLBH
[ 9383.756589] RTAI[malloc]: unloaded.
[ 9383.860053] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[ 9383.892775] I-pipe: Domain RTAI unregistered.
[ 9383.892842] RTAI[hal]: unmounted.
Again, sorry for the incompetence. Not sure what I did differently this time but I'll go back through and try to get it right and do the HAL meter test you suggested. Thanks
Print file information:
RUN_IN_PLACE=no
EMC2_DIR=
EMC2_BIN_DIR=/usr/bin
EMC2_TCL_DIR=/usr/lib/tcltk/emc2
EMC2_SCRIPT_DIR=
EMC2_RTLIB_DIR=/usr/realtime-2.6.32-122-rtai/modules/emc2
EMC2_CONFIG_DIR=
EMC2_LANG_DIR=/usr/share/emc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
EMC2_EMCSH=/usr/bin/wish8.5
EMC2 - 2.5.0-pre2-626-g402b6cd
Machine configuration directory is '/home/maxvdh/emc2/configs/my_EMC_machine'
Machine configuration file is 'my_EMC_machine.ini'
INIFILE=/home/maxvdh/emc2/configs/my_EMC_machine/my_EMC_machine.ini
PARAMETER_FILE=emc.var
EMCMOT=motmod
EMCIO=io
TASK=milltask
HALUI=halui
DISPLAY=axis
NML_FILE=
Starting EMC2...
Starting EMC2 server program: emcsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting EMC2 IO program: io
Starting HAL User Interface program: halui
Shutting down and cleaning up EMC2...
Running HAL shutdown script
Killing task emcsvr, PID=2879
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Cleanup done
Debug file information:
my_EMC_machine.hal:25: addf requires at least 2 arguments, 1 given
2879
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components
Kernel message information:
[ 9381.101640] I-pipe: Domain RTAI registered.
[ 9381.101658] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 9381.101665] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 9381.101719] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 9381.101726] PIPELINE layers:
[ 9381.101733] fce9de20 9ac15d93 RTAI 200
[ 9381.101740] c085cb20 0 Linux 100
[ 9381.166707] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 9381.168462] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 9381.168479] RTAI[sched]: hard timer type/freq = APIC/12487409(Hz); default timing: periodic; linear timed lists.
[ 9381.168488] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 1800183000 hz.
[ 9381.168496] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 9381.168668] RTAI[usi]: enabled.
[ 9381.314945] RTAI[math]: loaded.
[ 9381.635362] hm2: loading Mesa HostMot2 driver version 0.15
[ 9381.644754] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
[ 9381.644827] hm2_pci 0000:05:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 9381.644838] hm2_pci: discovered 5i25 at 0000:05:00.0
[ 9381.647290] hm2/hm2_5i25.0: Smart Serial Firmware Version 31
[ 9381.770415] hm2/hm2_5i25.0: 34 I/O Pins used:
[ 9381.770430] hm2/hm2_5i25.0: IO Pin 000 (P3-01): IOPort
[ 9381.770439] hm2/hm2_5i25.0: IO Pin 001 (P3-14): IOPort
[ 9381.770448] hm2/hm2_5i25.0: IO Pin 002 (P3-02): IOPort
[ 9381.770459] hm2/hm2_5i25.0: IO Pin 003 (P3-15): Smart Serial Interface #0, pin TxData1 (Output)
[ 9381.770471] hm2/hm2_5i25.0: IO Pin 004 (P3-03): Smart Serial Interface #0, pin RxData1 (Input)
[ 9381.770480] hm2/hm2_5i25.0: IO Pin 005 (P3-16): IOPort
[ 9381.770489] hm2/hm2_5i25.0: IO Pin 006 (P3-04): IOPort
[ 9381.770499] hm2/hm2_5i25.0: IO Pin 007 (P3-17): Muxed Encoder Select #0, pin Mux Select 0 (Output)
[ 9381.770513] hm2/hm2_5i25.0: IO Pin 008 (P3-05): Muxed Encoder #0, pin Muxed A (Input)
[ 9381.770522] hm2/hm2_5i25.0: IO Pin 009 (P3-06): Muxed Encoder #0, pin Muxed B (Input)
[ 9381.770532] hm2/hm2_5i25.0: IO Pin 010 (P3-07): Muxed Encoder #0, pin Muxed Index (Input)
[ 9381.770542] hm2/hm2_5i25.0: IO Pin 011 (P3-08): Muxed Encoder #1, pin Muxed A (Input)
[ 9381.770552] hm2/hm2_5i25.0: IO Pin 012 (P3-09): Muxed Encoder #1, pin Muxed B (Input)
[ 9381.770562] hm2/hm2_5i25.0: IO Pin 013 (P3-10): Muxed Encoder #1, pin Muxed Index (Input)
[ 9381.770572] hm2/hm2_5i25.0: IO Pin 014 (P3-11): Muxed Encoder #2, pin Muxed A (Input)
[ 9381.770582] hm2/hm2_5i25.0: IO Pin 015 (P3-12): Muxed Encoder #2, pin Muxed B (Input)
[ 9381.770592] hm2/hm2_5i25.0: IO Pin 016 (P3-13): Muxed Encoder #2, pin Muxed Index (Input)
[ 9381.770601] hm2/hm2_5i25.0: IO Pin 017 (P2-01): IOPort
[ 9381.770609] hm2/hm2_5i25.0: IO Pin 018 (P2-14): IOPort
[ 9381.770617] hm2/hm2_5i25.0: IO Pin 019 (P2-02): IOPort
[ 9381.770625] hm2/hm2_5i25.0: IO Pin 020 (P2-15): IOPort
[ 9381.770632] hm2/hm2_5i25.0: IO Pin 021 (P2-03): IOPort
[ 9381.770640] hm2/hm2_5i25.0: IO Pin 022 (P2-16): IOPort
[ 9381.770648] hm2/hm2_5i25.0: IO Pin 023 (P2-04): IOPort
[ 9381.770657] hm2/hm2_5i25.0: IO Pin 024 (P2-17): Muxed Encoder Select #3, pin Mux Select 0 (Output)
[ 9381.770667] hm2/hm2_5i25.0: IO Pin 025 (P2-05): IOPort
[ 9381.770676] hm2/hm2_5i25.0: IO Pin 026 (P2-06): IOPort
[ 9381.770685] hm2/hm2_5i25.0: IO Pin 027 (P2-07): IOPort
[ 9381.770694] hm2/hm2_5i25.0: IO Pin 028 (P2-08): IOPort
[ 9381.770703] hm2/hm2_5i25.0: IO Pin 029 (P2-09): IOPort
[ 9381.770712] hm2/hm2_5i25.0: IO Pin 030 (P2-10): IOPort
[ 9381.770721] hm2/hm2_5i25.0: IO Pin 031 (P2-11): IOPort
[ 9381.770730] hm2/hm2_5i25.0: IO Pin 032 (P2-12): IOPort
[ 9381.770738] hm2/hm2_5i25.0: IO Pin 033 (P2-13): IOPort
[ 9381.770948] hm2/hm2_5i25.0: registered
[ 9381.770957] hm2_5i25.0: initialized AnyIO board at 0000:05:00.0
[ 9383.154885] hm2_5i25.0: dropping AnyIO board at 0000:05:00.0
[ 9383.154895] hm2/hm2_5i25.0: unregistered
[ 9383.154938] hm2_pci 0000:05:00.0: PCI INT A disabled
[ 9383.154994] hm2_pci: driver unloaded
[ 9383.180932] hm2: unloading
[ 9383.580118] RTAI[math]: unloaded.
[ 9383.723065] SCHED releases registered named ALIEN RTGLBH
[ 9383.756589] RTAI[malloc]: unloaded.
[ 9383.860053] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[ 9383.892775] I-pipe: Domain RTAI unregistered.
[ 9383.892842] RTAI[hal]: unmounted.
Again, sorry for the incompetence. Not sure what I did differently this time but I'll go back through and try to get it right and do the HAL meter test you suggested. Thanks
Please Log in or Create an account to join the conversation.
17 Apr 2012 03:05 #19263
by cmorley
Replied by cmorley on topic Re:7i77 testers wanted
no problem.
I bet you tried to load the old program gave up the continued to make a new one without reloading pncconf again.
I have seen this problem from time to time.
reload pncconf and make a new one without trying to load one.
did it give an error message when you tried to reload the original config?
by 'regular config' I meant the configuration that you built the first time. i meant you could use halmeter to check encoders by loading it in the regular configuration or by using pncconf's openloop test.
I bet you tried to load the old program gave up the continued to make a new one without reloading pncconf again.
I have seen this problem from time to time.
reload pncconf and make a new one without trying to load one.
did it give an error message when you tried to reload the original config?
by 'regular config' I meant the configuration that you built the first time. i meant you could use halmeter to check encoders by loading it in the regular configuration or by using pncconf's openloop test.
Please Log in or Create an account to join the conversation.
17 Apr 2012 03:07 #19264
by maxvdh
Replied by maxvdh on topic Re:7i77 testers wanted
oops. I think I forgot to set it to XYZA and 7i77x2. I now get the option to configure the A axis but I have to set a PWM output for it and I'm not quite sure how to do that properly but I'll figure it out here. The thing thats confusing me is that I dont want PWM, I want an analog output for a servo amplifier.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.106 seconds