5i25 - 7i76 support testers wanted

Hi,

I have now 2.5.0-130-0728b54 from 26 July

when i press the forward or back button in the X-Axis/Y-Axis or Z-Axis configuration, the positive travel distance and home switch location
is automatically changed with multiplier 10 or 100 . My value 800 is changed after on klick back an on forward to the new value 8000.0, again back and forward the new value is 800000.0.

I tested the spindle out (TB4) with the 7i76. It works, but i don't understand the output_scale and output_max_limit with the help file.
My Spindle Drive need 0-10V, the max. rpm of the Spindle is 60000.
it works well with these parameters:
OUTPUT_SCALE = 60000.0
OUTPUT_MIN_LIMIT = 0.0
OUTPUT_MAX_LIMIT = 60000.0

in MDI S60000=10V, S30000=5V .....

The maximum value in pncconf is only 6000!, I've changed it in the ini.


david

That is the newest version.

I cannot get the distance to be multiplied each time pass the axis config page. Must be a certain combination of options.
Can you post the .pncconf file?

You figured out the scaling properly I will add an example in the help file.
Not many people have a 60 000 RPM spindle I will up the limit something higher.
is there still a problem with the output pin name ? ( The original problem you spoke of)

Chris M

Hello chris,

my new version 2.5.0.134.g2bc3ccc.

here is my pncconf File.

- the output pin name TB5/TB6 is OK. Hardware works.
- Spindle rpm 60000 in pncconf - OK , help page very well




david

here it is

I went to use the CNC today and LinuxCNC would not load. I am not sure what could have changed. I tried to run pncconf to let it 'refresh' the configuration and found that I could not test the axis, HAL would not function.

I have been allowing Update Manager to do it's thing. The last time I ran LinuxCNC was June 2. I have changed monitors (not graphics card) so I did the installing software based Open-GL drivers with sudo apt-get install libgl1-mesa-swx11. I tried reseating the Mesa card.

I don't know how to proceed.

Here is the error when I start LinuxCNC.

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/stan/linuxcnc/configs/Sweet_Mesa'
Machine configuration file is 'Sweet_Mesa.ini'
INIFILE=/home/stan/linuxcnc/configs/Sweet_Mesa/Sweet_Mesa.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...
Running HAL shutdown script
Killing task linuxcncsvr, PID=1319
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/hm2_pci.ko': -1 Invalid parameters
Sweet_Mesa.hal:9: exit value: 1
Sweet_Mesa.hal:9: insmod failed, returned -1
See the output of 'dmesg' for more information.
1319
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components

Kernel message information:
[ 468.501310] I-pipe: Domain RTAI registered.
[ 468.501320] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 468.501324] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 468.501334] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 468.501337] PIPELINE layers:
[ 468.501341] fae29e20 9ac15d93 RTAI 200
[ 468.501345] c085cb20 0 Linux 100
[ 468.551595] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 468.551729] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 468.551738] RTAI[sched]: hard timer type/freq = APIC/12468720(Hz); default timing: periodic; linear timed lists.
[ 468.551743] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 2393706000 hz.
[ 468.551746] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 468.551841] RTAI[usi]: enabled.
[ 468.663502] RTAI[math]: loaded.
[ 468.864758] hm2: loading Mesa HostMot2 driver version 0.15
[ 468.870306] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
[ 468.870350] hm2_pci 0000:02:01.0: enabling device (0000 -> 0002)
[ 468.870361] alloc irq_desc for 22 on node -1
[ 468.870365] alloc kstat_irqs on node -1
[ 468.870374] hm2_pci 0000:02:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 468.870379] hm2_pci: discovered 5i25 at 0000:02:01.0
[ 468.870505] hm2/hm2_5i25.0: invalid cookie, got 0xFFFFFFFF, expected 0x55AACAFE
[ 468.870511] hm2/hm2_5i25.0: FPGA failed to initialize, or unexpected firmware?
[ 468.870516] hm2_5i25.0: board fails HM2 registration
[ 468.870528] hm2_pci 0000:02:01.0: PCI INT A disabled
[ 468.870537] hm2_pci: probe of 0000:02:01.0 failed with error -22
[ 469.403150] hm2: unloading
[ 469.523474] RTAI[math]: unloaded.
[ 469.585612] SCHED releases registered named ALIEN RTGLBH
[ 469.600309] RTAI[malloc]: unloaded.
[ 469.700021] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[ 469.704392] I-pipe: Domain RTAI unregistered.
[ 469.704405] RTAI[hal]: unmounted.

ini file

It could be a hardware failure of some kind though those are pretty strange symptoms. That is, its pretty hard to find the card (which requires correctly reading two 32 bit numbers from the card), and then fail at reading another 32 bit number. And its unlikely a corrupted bitfille on board since the bitfile in the EEPROM will not load if the CRC is wrong.

I dont think LinuxCNC would be updated but if it was, others have reported that builds from July have a bug in the Hostmot2 driver

Can you try running the mesaflash utility which would verify if an independent (of LinuxCNC) program can access the card?

Mesaflash is in the 5I25 zipfile. You need to be root to run it.
running it without any command line options will print usage information
probably the easiest test is to run a verify with the correct bitfile (also in the zipfile)

No Joy. I do not know how to run Mesaflash. I changed the properties of the file to allow execution. Here is what I saw:

root@PowerEdge:~/Downloads/5i25/utils/linux# mesaflash
mesaflash: command not found
root@PowerEdge:~/Downloads/5i25/utils/linux# ls
7i76x2.bit 7i76x2.pin mesaflash source
root@PowerEdge:~/Downloads/5i25/utils/linux# mesaflash 7i76x2.bit v
mesaflash: command not found
root@PowerEdge:~/Downloads/5i25/utils/linux#

Stan

since mesaflash is not in the execute path you need to prepend
a ./ to its name

./mesaflash blah blah blah

forgot to say that since the utility needs to be run as root, you will need to type:

sudo ./mesaflash blah blah blah

Joy! Terminal log below:

root@PowerEdge:/home/stan/Downloads/5i25/utils/linux# ./mesaflash 7i76x2.bit verify
PCI device 14 at bus/device/function 02/02/0
Vendor/Device/SSVendor/SSDevice: 2718/5125/2718/5125
Region 0: MEM 65536 bytes at fcfd0000
Checking cookie... OK
Identifing EEPROM... OK
8Mb found
Checking file 7i76x2.bit... OK
File type: BIT file
Design name: TopPCITargetHostMot2.ncd;UserID=0xFFFFFFFF
Part name: 6slx9tqg144
Design date: 2012/04/12
Design time: 14:07:24
Config Length: 340604
|
Error at 0x80025 expected: 0xE5 but read: 0xF4
root@PowerEdge:/home/stan/Downloads/5i25/utils/linux# ./mesaflash
Syntax: mesaflash filename [command]
Writes config data to 5I25 EEPROM
filename - VALID FPGA configuration file.
Commands:
write - write program in 'filename' into FPGA.
verify - verify if 'filename' is properly programmed in FPGA.
info - print info about 'filename'.
root@PowerEdge:/home/stan/Downloads/5i25/utils/linux# ./mesaflash 7i76x2.bit write
PCI device 14 at bus/device/function 02/02/0
Vendor/Device/SSVendor/SSDevice: 2718/5125/2718/5125
Region 0: MEM 65536 bytes at fcfd0000
Checking cookie... OK
Identifing EEPROM... OK
8Mb found
BootSector OK
Checking file 7i76x2.bit... OK
File type: BIT file
Design name: TopPCITargetHostMot2.ncd;UserID=0xFFFFFFFF
Part name: 6slx9tqg144
Design date: 2012/04/12
Design time: 14:07:24
Config Length: 340604
Erasing EEPROM sectors starting from 0x80000...
|EEEEEE
Programming EEPROM area starting from 0x80000...
|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
Board configuration updated successfully

After this, LinuxCNC ran properly.

Thanks for the help.

Stan