Mesa 5i25 and single 7i76 have wrong pins [SOLVED]

More
9 years 6 months ago #91084 by ebartel
Hello, long time listener but first time poster.

I'm setting up a new to me cnc mill and this is the first time I'm using a mesa card with linuxcnc. Previously I have used the gecko g540 directly to parport.

I have a 5i25 with a single 7i76 connected via parallel and have gone through the pncconf multiple times. The problem I'm having is the pins on the TB2 of the 7i76 do not line up with the documentation. I bought them as a kit so I thought the firmware would be right. I have also tried updating the firmware with mesaflash to 5i25_7i76x2.bit and reloaded.

To give an example, in pncconf IO Connecter 3 Num 0 is the X Axis StepGen. I would expect that when running a test for Axis X pin 3 of TB2 on the 7i76 would show the step wave. Instead it is pin 17.

I'm probably missing something simple. When I ran dmesg | grep hm2, I noticed that my pins were different then a example found here . Any ideas?
Code:
[150395.083003] hm2: loading Mesa HostMot2 driver version 0.15 [150395.084305] hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7 [150395.084331] hm2_pci: discovered 5i25 at 0000:01:0c.0 [150395.084942] hm2/hm2_5i25.0: 34 I/O Pins used: [150395.084945] hm2/hm2_5i25.0: IO Pin 000 (P3-01): IOPort [150395.084947] hm2/hm2_5i25.0: IO Pin 001 (P3-14): IOPort [150395.084949] hm2/hm2_5i25.0: IO Pin 002 (P3-02): StepGen #0, pin Direction (Output) [150395.084951] hm2/hm2_5i25.0: IO Pin 003 (P3-15): IOPort [150395.084952] hm2/hm2_5i25.0: IO Pin 004 (P3-03): StepGen #0, pin Step (Output) [150395.084954] hm2/hm2_5i25.0: IO Pin 005 (P3-16): IOPort [150395.084956] hm2/hm2_5i25.0: IO Pin 006 (P3-04): StepGen #1, pin Direction (Output) [150395.084957] hm2/hm2_5i25.0: IO Pin 007 (P3-17): IOPort [150395.084959] hm2/hm2_5i25.0: IO Pin 008 (P3-05): StepGen #1, pin Step (Output) [150395.084961] hm2/hm2_5i25.0: IO Pin 009 (P3-06): StepGen #2, pin Direction (Output) [150395.084963] hm2/hm2_5i25.0: IO Pin 010 (P3-07): StepGen #2, pin Step (Output) [150395.084965] hm2/hm2_5i25.0: IO Pin 011 (P3-08): IOPort [150395.084966] hm2/hm2_5i25.0: IO Pin 012 (P3-09): IOPort [150395.084968] hm2/hm2_5i25.0: IO Pin 013 (P3-10): Encoder #0, pin Index (Input) [150395.084970] hm2/hm2_5i25.0: IO Pin 014 (P3-11): Encoder #0, pin A (Input) [150395.084972] hm2/hm2_5i25.0: IO Pin 015 (P3-12): Encoder #0, pin B (Input) [150395.084974] hm2/hm2_5i25.0: IO Pin 016 (P3-13): IOPort [150395.084975] hm2/hm2_5i25.0: IO Pin 017 (P2-01): IOPort [150395.084977] hm2/hm2_5i25.0: IO Pin 018 (P2-14): IOPort [150395.084978] hm2/hm2_5i25.0: IO Pin 019 (P2-02): IOPort [150395.084980] hm2/hm2_5i25.0: IO Pin 020 (P2-15): IOPort [150395.084981] hm2/hm2_5i25.0: IO Pin 021 (P2-03): IOPort [150395.084983] hm2/hm2_5i25.0: IO Pin 022 (P2-16): IOPort [150395.084985] hm2/hm2_5i25.0: IO Pin 023 (P2-04): IOPort [150395.084986] hm2/hm2_5i25.0: IO Pin 024 (P2-17): IOPort [150395.084987] hm2/hm2_5i25.0: IO Pin 025 (P2-05): IOPort [150395.084989] hm2/hm2_5i25.0: IO Pin 026 (P2-06): IOPort [150395.084990] hm2/hm2_5i25.0: IO Pin 027 (P2-07): IOPort [150395.084992] hm2/hm2_5i25.0: IO Pin 028 (P2-08): IOPort [150395.084993] hm2/hm2_5i25.0: IO Pin 029 (P2-09): IOPort [150395.084995] hm2/hm2_5i25.0: IO Pin 030 (P2-10): IOPort [150395.084996] hm2/hm2_5i25.0: IO Pin 031 (P2-11): IOPort [150395.084998] hm2/hm2_5i25.0: IO Pin 032 (P2-12): IOPort [150395.084999] hm2/hm2_5i25.0: IO Pin 033 (P2-13): IOPort [150395.085018] hm2/hm2_5i25.0: registered [150395.085020] hm2_5i25.0: initialized AnyIO board at 0000:01:0c.0

Please Log in to join the conversation.

More
9 years 6 months ago #91086 by PCW
Hmm that's a Tormach pinout

I would rerun mesaflash

sudo mesaflash --device 5i25 --write 5i25_7i76x2.bit
sudo mesaflash --device 5i25 --reload
sudo mesaflash --device 5i25 --readhmid >config.txt

and post config.txt here

Please Log in to join the conversation.

More
9 years 6 months ago #91092 by ebartel
Here is the terminal output:
Code:
ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ sudo mesaflash --device 5i25 --write 5i25_7i76x2.bit [sudo] password for ebartel: Checking file... OK File type: BIT file Design name: TopPCIHostMot2b.ncd;UserID=0xFFFFFFFF Part name: 6slx9tqg144 Design date: 2015/12/21 Design time: 16:46:04 Config Length: 340604 Boot sector OK EEPROM sectors to write: 6, max sectors in area: 16 Erasing EEPROM sectors starting from 0x100000... |EEEEEE Programming EEPROM sectors starting from 0x100000... |WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW Board configuration updated successfully. You must power cycle board to load updated firmware. ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ sudo mesaflash --device 5i25 --reload ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ sudo mesaflash --device 5i25 --readhmid > ~/config.txt

and here is the output.

Attachment not found



It says I need to power cycle. Do i need to restart the computer or is the reload sufficient?

Please Log in to join the conversation.

More
9 years 6 months ago #91093 by PCW
I would power cycle, there's something funny about the mesaflash messages
(mesaflash should say you need to reload _or_ power cycle)
perhaps you have an old version of mesaflash

Also what OS and LinuxCNC version are you using?

Please Log in to join the conversation.

More
9 years 6 months ago #91096 by ebartel
I powered cycled the host and no change. Do i need to set a jumper or something before writing the firmware?
Code:
ebartel@prototrak:~$ uname -a Linux prototrak 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686 GNU/Linux

LinuxCNC is version 2.6.4

Please Log in to join the conversation.

More
9 years 6 months ago #91102 by PCW
No jumpers are involved so this is rather mysterious (unless you are running PathPilot which re-writes the 5I25
with Tormach firmware)

can you run

md5sum 5i25_7i76x2.bit

and post the results, and also run

sudo mesaflash --device 5i25 --write 5i25_7i76x2.bit
sudo mesaflash --device 5i25 --verify 5i25_7i76x2.bit

and post the results

Please Log in to join the conversation.

More
9 years 6 months ago #91216 by ebartel
Sorry for the delay, I didn't have time to work on it last night.

Still same results. Here is the output.
Code:
ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ pwd /home/ebartel/Downloads/5i25/configs/hostmot2 ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ md5sum 5i25_7i76x2 5i25_7i76x2.bit 5i25_7i76x2r.bit 5i25_7i76x2r.xml 5i25_7i76x2.pin 5i25_7i76x2r.pin 5i25_7i76x2.xml ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ md5sum 5i25_7i76x2 5i25_7i76x2.bit 5i25_7i76x2r.bit 5i25_7i76x2r.xml 5i25_7i76x2.pin 5i25_7i76x2r.pin 5i25_7i76x2.xml ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ md5sum 5i25_7i76x2.bit cfe35f4106871ef627e6f0ad38cfa78e 5i25_7i76x2.bit ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ sudo mesaflash --device 5i25 --write 5i25_7i76x2.bit [sudo] password for ebartel: Sorry, try again. [sudo] password for ebartel: Checking file... OK File type: BIT file Design name: TopPCIHostMot2b.ncd;UserID=0xFFFFFFFF Part name: 6slx9tqg144 Design date: 2015/12/21 Design time: 16:46:04 Config Length: 340604 Boot sector OK EEPROM sectors to write: 6, max sectors in area: 16 Erasing EEPROM sectors starting from 0x100000... |EEEEEE Programming EEPROM sectors starting from 0x100000... |WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW Board configuration updated successfully. You must power cycle board to load updated firmware. ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ sudo mesaflash --device 5i25 --verify 5i25_7i76x2.bit Checking file... OK File type: BIT file Design name: TopPCIHostMot2b.ncd;UserID=0xFFFFFFFF Part name: 6slx9tqg144 Design date: 2015/12/21 Design time: 16:46:04 Config Length: 340604 Boot sector OK Verifying EEPROM sectors starting from 0x100000... |VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV Board configuration verified successfully ebartel@prototrak:~/Downloads/5i25/configs/hostmot2$ sudo mesaflash --device 5i25 --reload

Please Log in to join the conversation.

More
9 years 6 months ago #91220 by PCW
Did you do a full power cycle of the machine? (reboot will not do)

Also what OS are you running (uname -a) (sorry already asked that)

I am assuming you are _not_ running pathpilot

Please Log in to join the conversation.

More
9 years 6 months ago #91243 by ebartel
As expected, it was a simple issue. I was rebooting the host and did not power off/on. I appreciate the help on this.

Please Log in to join the conversation.

Time to create page: 0.218 seconds
Powered by Kunena Forum