Mesa 7I43-4 first tests but no sucess

More
15 Jul 2012 16:28 #21960 by Mike_Eitel
I need a hint where to search

I'm doing my first test with MESA 7i43

It's a 4 stepper, no other modules test.
I can see the three LED's on the board changing... Connection should be good

THX in advance for your ideas
Mike



Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/realtime-2.6.32-122-rtai/modules/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.5
LINUXCNC - 2.5.0
Machine configuration directory is '/home/cnc/linuxcnc/configs/MesaCNC'
Machine configuration file is 'MesaCNC.ini'
INIFILE=/home/cnc/linuxcnc/configs/MesaCNC/MesaCNC.ini
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Shutting down and cleaning up LinuxCNC...
Killing task linuxcncsvr, PID=1897
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Cleanup done

Debug file information:
Can not find -sec MOT -var MOT -num 1
Can not find -sec IO -var IO -num 1
Can not find -sec LINUXCNC -var NML_FILE -num 1
Can not find -sec EMC -var NML_FILE -num 1
insmod: error inserting '/usr/realtime-2.6.32-122-rtai/modules/linuxcnc/lowpass.ko': -1 Invalid parameters
MesaCNC.hal:12: exit value: 1
MesaCNC.hal:12: insmod failed, returned -1
See the output of 'dmesg' for more information.
1897
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components

Kernel message information:
[ 1156.318191] I-pipe: Domain RTAI registered.
[ 1156.318213] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 1156.318217] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 1156.318228] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 1156.318232] PIPELINE layers:
[ 1156.318237] f941ae20 9ac15d93 RTAI 200
[ 1156.318240] c085cb20 0 Linux 100
[ 1156.358656] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 1156.359017] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 1156.359024] RTAI[sched]: hard timer type/freq = APIC/16686897(Hz); default timing: periodic; linear timed lists.
[ 1156.359030] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 1468681000 hz.
[ 1156.359034] RTAI[sched]: timer setup = 999 ns, resched latency = 2944 ns.
[ 1156.359277] RTAI[usi]: enabled.
[ 1156.531322] RTAI[math]: loaded.
[ 1156.671144] probe_parport 00:0a: activated
[ 1156.691069] hm2: loading Mesa HostMot2 driver version 0.15
[ 1156.700792] hm2_7i43: loading HostMot2 Mesa 7i43 driver version 0.3
[ 1156.706104] hm2_7i43.0: firmware: requesting hm2/7i43-4/SVST4_4.BIT
[ 1157.060054] hm2/hm2_7i43.0: 48 I/O Pins used:
[ 1157.060068] hm2/hm2_7i43.0: IO Pin 000 (P4-01): IOPort
[ 1157.060072] hm2/hm2_7i43.0: IO Pin 001 (P4-03): IOPort
[ 1157.060077] hm2/hm2_7i43.0: IO Pin 002 (P4-05): IOPort
[ 1157.060081] hm2/hm2_7i43.0: IO Pin 003 (P4-07): IOPort
[ 1157.060085] hm2/hm2_7i43.0: IO Pin 004 (P4-09): IOPort
[ 1157.060089] hm2/hm2_7i43.0: IO Pin 005 (P4-11): IOPort
[ 1157.060093] hm2/hm2_7i43.0: IO Pin 006 (P4-13): IOPort
[ 1157.060097] hm2/hm2_7i43.0: IO Pin 007 (P4-15): IOPort
[ 1157.060101] hm2/hm2_7i43.0: IO Pin 008 (P4-17): IOPort
[ 1157.060106] hm2/hm2_7i43.0: IO Pin 009 (P4-19): IOPort
[ 1157.060110] hm2/hm2_7i43.0: IO Pin 010 (P4-21): IOPort
[ 1157.060114] hm2/hm2_7i43.0: IO Pin 011 (P4-23): IOPort
[ 1157.060118] hm2/hm2_7i43.0: IO Pin 012 (P4-25): IOPort
[ 1157.060122] hm2/hm2_7i43.0: IO Pin 013 (P4-27): IOPort
[ 1157.060126] hm2/hm2_7i43.0: IO Pin 014 (P4-29): IOPort
[ 1157.060131] hm2/hm2_7i43.0: IO Pin 015 (P4-31): IOPort
[ 1157.060135] hm2/hm2_7i43.0: IO Pin 016 (P4-33): IOPort
[ 1157.060139] hm2/hm2_7i43.0: IO Pin 017 (P4-35): IOPort
[ 1157.060164] hm2/hm2_7i43.0: IO Pin 018 (P4-37): IOPort
[ 1157.060169] hm2/hm2_7i43.0: IO Pin 019 (P4-39): IOPort
[ 1157.060173] hm2/hm2_7i43.0: IO Pin 020 (P4-41): IOPort
[ 1157.060178] hm2/hm2_7i43.0: IO Pin 021 (P4-43): IOPort
[ 1157.060182] hm2/hm2_7i43.0: IO Pin 022 (P4-45): IOPort
[ 1157.060186] hm2/hm2_7i43.0: IO Pin 023 (P4-47): IOPort
[ 1157.060192] hm2/hm2_7i43.0: IO Pin 024 (P3-01): StepGen #0, pin Step (Output)
[ 1157.060197] hm2/hm2_7i43.0: IO Pin 025 (P3-03): StepGen #0, pin Direction (Output)
[ 1157.060202] hm2/hm2_7i43.0: IO Pin 026 (P3-05): IOPort
[ 1157.060206] hm2/hm2_7i43.0: IO Pin 027 (P3-07): IOPort
[ 1157.060210] hm2/hm2_7i43.0: IO Pin 028 (P3-09): IOPort
[ 1157.060214] hm2/hm2_7i43.0: IO Pin 029 (P3-11): IOPort
[ 1157.060219] hm2/hm2_7i43.0: IO Pin 030 (P3-13): StepGen #1, pin Step (Output)
[ 1157.060224] hm2/hm2_7i43.0: IO Pin 031 (P3-15): StepGen #1, pin Direction (Output)
[ 1157.060229] hm2/hm2_7i43.0: IO Pin 032 (P3-17): IOPort
[ 1157.060233] hm2/hm2_7i43.0: IO Pin 033 (P3-19): IOPort
[ 1157.060237] hm2/hm2_7i43.0: IO Pin 034 (P3-21): IOPort
[ 1157.060241] hm2/hm2_7i43.0: IO Pin 035 (P3-23): IOPort
[ 1157.060246] hm2/hm2_7i43.0: IO Pin 036 (P3-25): StepGen #2, pin Step (Output)
[ 1157.060252] hm2/hm2_7i43.0: IO Pin 037 (P3-27): StepGen #2, pin Direction (Output)
[ 1157.060256] hm2/hm2_7i43.0: IO Pin 038 (P3-29): IOPort
[ 1157.060260] hm2/hm2_7i43.0: IO Pin 039 (P3-31): IOPort
[ 1157.060264] hm2/hm2_7i43.0: IO Pin 040 (P3-33): IOPort
[ 1157.060269] hm2/hm2_7i43.0: IO Pin 041 (P3-35): IOPort
[ 1157.060273] hm2/hm2_7i43.0: IO Pin 042 (P3-37): StepGen #3, pin Step (Output)
[ 1157.060279] hm2/hm2_7i43.0: IO Pin 043 (P3-39): StepGen #3, pin Direction (Output)
[ 1157.060283] hm2/hm2_7i43.0: IO Pin 044 (P3-41): IOPort
[ 1157.060288] hm2/hm2_7i43.0: IO Pin 045 (P3-43): IOPort
[ 1157.060292] hm2/hm2_7i43.0: IO Pin 046 (P3-45): IOPort
[ 1157.060296] hm2/hm2_7i43.0: IO Pin 047 (P3-47): IOPort
[ 1157.060351] hm2/hm2_7i43.0: registered
[ 1157.060357] hm2_7i43.0: board at (ioaddr=0x0378, ioaddr_hi=0x0778, epp_wide ON) found
[ 1157.080249] HAL: ERROR: duplicate variable '.in'
[ 1157.603942] hm2_7i43.0: releasing board
[ 1157.603977] hm2/hm2_7i43.0: unregistered
[ 1157.604212] hm2_7i43: driver unloaded
[ 1157.611672] hm2: unloading
[ 1157.619303] probe_parport 00:0a: disabled
[ 1157.718517] RTAI[math]: unloaded.
[ 1157.847834] SCHED releases registered named ALIEN RTGLBH
[ 1157.862194] RTAI[malloc]: unloaded.
[ 1157.960356] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[ 1157.968292] I-pipe: Domain RTAI unregistered.
[ 1157.968309] RTAI[hal]: unmounted.

Please Log in or Create an account to join the conversation.

More
15 Jul 2012 17:52 - 15 Jul 2012 18:01 #21961 by PCW
Looks like a error in the HAL file, so posting that here may help.

Also, can you launch LinuxCNC from the command line to see what it prints?
That is sometimes more helpful when it comes finding to HAL errors.
Last edit: 15 Jul 2012 18:01 by PCW. Reason: sp

Please Log in or Create an account to join the conversation.

More
15 Jul 2012 18:47 #21962 by cmorley
posting the HAL fine would help me too.
What version of linuxcnc are you using?

Thanks

Please Log in or Create an account to join the conversation.

More
15 Jul 2012 19:53 #21965 by Mike_Eitel
THX for the fast reaction.

1. I use 2.5, just upgraded,
2. and directory user dir renamed to linuxcnc,
3. Made a brand new confguration via pncconfig

I have all compressed to zip and attached


THX
Mike

P.S.
I'm very curious to see that mesa running, bought it a longer time agoo and finaly found the time to test.

File Attachment:

File Name: MesaCNC.zip
File Size:24 KB
Attachments:

Please Log in or Create an account to join the conversation.

More
15 Jul 2012 20:12 - 15 Jul 2012 20:13 #21966 by cmorley
looks to me something got messed up with the pyvcp option.

load your config in pncconf again. On the gui configuration page under virtual control panels:
open the pyvcp details. select spindle speed display (include HAL commands should already be checked)
then push next.
A warning will show about overwriting the pyvcp panel click ok.
click through the rest of the pages and save the config again. That should fix it.

I will have to figure out the sequence of events that led to the problem.
Hope that helps.

Chris M
Last edit: 15 Jul 2012 20:13 by cmorley. Reason: spelling

Please Log in or Create an account to join the conversation.

More
15 Jul 2012 22:08 #21971 by Mike_Eitel
THX Chris

Yes that was the right idea. I see axis now...

Now I can go go that path the next days.... If I find som time..

Good night
Bye
Mike

Please Log in or Create an account to join the conversation.

More
21 Jul 2012 11:23 #22264 by Mike_Eitel
Hi

Maybe a silly question:
I think there is a file that includes the configuration for the Mesa card itself.....
I wonder if I can edit those parameters..



What I want to do is using PnCConf for a general Mesa configuration in a "general" config directory.
My real config I want to do in another directory where I do everihing by hand.

My impression was that the card is "pre-CONFIGURED" by a file I did not find that config until now ?
I understand that there is a part done in the HAL, I think it is mostly choosing the number of pal modules
I'm missing some cross-table for each pin....

Mike

Please Log in or Create an account to join the conversation.

More
21 Jul 2012 15:23 #22271 by PCW
The low level configuration of the hardware is done with the FPGA configuration file (bitfile)
this is selected to match your FPGA and daughterboard types and hardware modules
required.

For example, you are using hm2/7i43-4/SVST4_4.BIT.
This is a configuration with 4 PWMGens, 4 stepgens and 4 encoder counters

Your initial error was something wrong in the HAL file unrelated to the 7I43:

[ 1157.080249] HAL: ERROR: duplicate variable '.in'

Normally all the machine connections are in the .hal file and initial setup parameters are in the .ini file
there are no Mesa specific files that control machine configuration other than these 2 files,

The only really Mesa specific file used by LinuxCNC is the FPGA bitfile

Please Log in or Create an account to join the conversation.

More
21 Jul 2012 17:35 #22283 by Mike_Eitel
THX PCW

I wonder hor pin in7oupt direction is configured and also there must e in my opinion somewhere definded of you wan't to use pull-up resistor function.

(I never did PAL programming but quite a lot of AVRmocroprocessor programming,
And as fare as I know you must do similar for a fpga)

THX

Please Log in or Create an account to join the conversation.

More
21 Jul 2012 18:00 #22286 by PCW
First you will want to look at the HostMot 2 manual:

man hostmot2

(in a terminal window)

This has information on how I/O pins are setup

Al I/O pins have pullups by default and this is basically hardware
so external devices need to be designed with this in mind

Practically this means that all outputs should be active low
(this is true of our daughtercards)

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.174 seconds
Powered by Kunena Forum