5i25 & 7i85 new install
28 Feb 2022 22:42 #236049
by KcChris
5i25 & 7i85 new install was created by KcChris
I had an old setup using a simple stepper board and wanted to upgrade to a Mesa card setup. I got a 5i25 / 7i25 bundle from Mesa but struggling to understand the install. Do I just use the Pconfig tool and get a basic setup and then edit the Hal file? I don't see a 7i85 in the list. Or did I make a mistake and get the wrong card bundle?
Please Log in or Create an account to join the conversation.
28 Feb 2022 22:47 #236051
by PCW
Replied by PCW on topic 5i25 & 7i85 new install
A more common and supported card set would be a 5I25+7I76
Typically a 7I85 is added where encoder feedback to LinuxCNC is desired
Do you have a 7I85 or 7I85S?
(the plain 7I85 has no step/dir outputs)
Typically a 7I85 is added where encoder feedback to LinuxCNC is desired
Do you have a 7I85 or 7I85S?
(the plain 7I85 has no step/dir outputs)
Please Log in or Create an account to join the conversation.
01 Mar 2022 23:18 - 01 Mar 2022 23:21 #236142
by KcChris
Replied by KcChris on topic 5i25 & 7i85 new install
It is the 7i85S, I got the cards about 6 months ago and just now getting around to getting it setup. I wish I would of got the 7i76 bundle as there is much more information about its setup. Being able to add encoders would be great but not a have too at this point.
Last edit: 01 Mar 2022 23:21 by KcChris.
Please Log in or Create an account to join the conversation.
02 Mar 2022 00:28 #236148
by andypugh
Replied by andypugh on topic 5i25 & 7i85 new install
First get a list of all the pins and parameters that your setup creates.
At the command line:
Now you can create a config, but maybe lying about the card if pncconf doesn't know about the 7i85. A 7i76 config should be close.
I think that Pncconf uses INI substitution for the card name, so you probably mainly have to change the [HOSTMOT2]CARD in the INI to 7i85.
Then try loading the config, look at the error message, work out what the missing pin is really called, and iterate through the HAL file.
It's not exactly fun, but it is more tedious than difficult.
At the command line:
halrun
loadrt hostmot2
loadrt hm2_pci
show pin
show param
{Then copy and paste all that into a text file)
exit
Now you can create a config, but maybe lying about the card if pncconf doesn't know about the 7i85. A 7i76 config should be close.
I think that Pncconf uses INI substitution for the card name, so you probably mainly have to change the [HOSTMOT2]CARD in the INI to 7i85.
Then try loading the config, look at the error message, work out what the missing pin is really called, and iterate through the HAL file.
It's not exactly fun, but it is more tedious than difficult.
Please Log in or Create an account to join the conversation.
02 Mar 2022 00:35 #236149
by PCW
Replied by PCW on topic 5i25 & 7i85 new install
The card name would still be would still be "5i25"
I suspect choosing a simpler breakout with pncconf
(say a probrfx2) would make a file set that pretty close
I suspect choosing a simpler breakout with pncconf
(say a probrfx2) would make a file set that pretty close
Please Log in or Create an account to join the conversation.
02 Mar 2022 20:11 #236212
by KcChris
Replied by KcChris on topic 5i25 & 7i85 new install
I'm a bit overwhelmed, So let me see if I'm on the right track and/or understanding correctly. Also if this is documented somewhere. I'm happy to do some reading before asking newbie questions.
My brain is locked up on the following.
-Where do I put the wired into the 7i85s for step gen and dir for example
-In the hal file I think I ses where to map functions to a pins (not sure that is the correct term)
net estop-out => parport.0.pin-01-out
net xstep => parport.0.pin-02-out
I found another post about this setup.
mill@DESKTOP-MILL:~$ sudo mesaflash --device 5i25 --readhmid
Configuration Name: HOSTMOT2
General configuration information:
BoardName : MESA5I25
FPGA Size: 9 KGates
FPGA Pins: 144
Number of IO Ports: 2
Width of one I/O port: 17
Clock Low frequency: 33.3333 MHz
Clock High frequency: 200.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256
Modules in configuration:
Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: IOPort
There are 2 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: MuxedQCount
There are 8 of MuxedQCount in configuration
Version: 3
Registers: 5
BaseAddress: 3600
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: MuxedQCountSel
There are 1 of MuxedQCountSel in configuration
Version: 0
Registers: 0
BaseAddress: 0000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: SSerial
There are 1 of SSerial in configuration
Version: 0
Registers: 6
BaseAddress: 5B00
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes
Module: StepGen
There are 8 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Configuration pin-out:
IO Connections for P3
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir
1 0 IOPort SSerial 0 RXData0 (In)
14 1 IOPort SSerial 0 TXData0 (Out)
2 2 IOPort StepGen 3 Step/Table1 (Out)
15 3 IOPort StepGen 3 Dir/Table2 (Out)
3 4 IOPort StepGen 2 Step/Table1 (Out)
16 5 IOPort StepGen 2 Dir/Table2 (Out)
4 6 IOPort StepGen 1 Step/Table1 (Out)
17 7 IOPort StepGen 1 Dir/Table2 (Out)
5 8 IOPort StepGen 0 Step/Table1 (Out)
6 9 IOPort StepGen 0 Dir/Table2 (Out)
7 10 IOPort MuxedQCountSel 0 MuxSel0 (Out)
8 11 IOPort MuxedQCount 0 MuxQ-A (In)
9 12 IOPort MuxedQCount 0 MuxQ-B (In)
10 13 IOPort MuxedQCount 0 MuxQ-IDX (In)
11 14 IOPort MuxedQCount 1 MuxQ-A (In)
12 15 IOPort MuxedQCount 1 MuxQ-B (In)
13 16 IOPort MuxedQCount 1 MuxQ-IDX (In)
IO Connections for P2
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir
1 17 IOPort SSerial 0 RXData1 (In)
14 18 IOPort SSerial 0 TXData1 (Out)
2 19 IOPort StepGen 7 Step/Table1 (Out)
15 20 IOPort StepGen 7 Dir/Table2 (Out)
3 21 IOPort StepGen 6 Step/Table1 (Out)
16 22 IOPort StepGen 6 Dir/Table2 (Out)
4 23 IOPort StepGen 5 Step/Table1 (Out)
17 24 IOPort StepGen 5 Dir/Table2 (Out)
5 25 IOPort StepGen 4 Step/Table1 (Out)
6 26 IOPort StepGen 4 Dir/Table2 (Out)
7 27 IOPort MuxedQCountSel 4 MuxSel0 (Out)
8 28 IOPort MuxedQCount 2 MuxQ-A (In)
9 29 IOPort MuxedQCount 2 MuxQ-B (In)
10 30 IOPort MuxedQCount 2 MuxQ-IDX (In)
11 31 IOPort MuxedQCount 3 MuxQ-A (In)
12 32 IOPort MuxedQCount 3 MuxQ-B (In)
13 33 IOPort MuxedQCount 3 MuxQ-IDX (In)
My brain is locked up on the following.
-Where do I put the wired into the 7i85s for step gen and dir for example
-In the hal file I think I ses where to map functions to a pins (not sure that is the correct term)
net estop-out => parport.0.pin-01-out
net xstep => parport.0.pin-02-out
I found another post about this setup.
mill@DESKTOP-MILL:~$ sudo mesaflash --device 5i25 --readhmid
Configuration Name: HOSTMOT2
General configuration information:
BoardName : MESA5I25
FPGA Size: 9 KGates
FPGA Pins: 144
Number of IO Ports: 2
Width of one I/O port: 17
Clock Low frequency: 33.3333 MHz
Clock High frequency: 200.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256
Modules in configuration:
Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: IOPort
There are 2 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: MuxedQCount
There are 8 of MuxedQCount in configuration
Version: 3
Registers: 5
BaseAddress: 3600
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: MuxedQCountSel
There are 1 of MuxedQCountSel in configuration
Version: 0
Registers: 0
BaseAddress: 0000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: SSerial
There are 1 of SSerial in configuration
Version: 0
Registers: 6
BaseAddress: 5B00
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes
Module: StepGen
There are 8 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Configuration pin-out:
IO Connections for P3
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir
1 0 IOPort SSerial 0 RXData0 (In)
14 1 IOPort SSerial 0 TXData0 (Out)
2 2 IOPort StepGen 3 Step/Table1 (Out)
15 3 IOPort StepGen 3 Dir/Table2 (Out)
3 4 IOPort StepGen 2 Step/Table1 (Out)
16 5 IOPort StepGen 2 Dir/Table2 (Out)
4 6 IOPort StepGen 1 Step/Table1 (Out)
17 7 IOPort StepGen 1 Dir/Table2 (Out)
5 8 IOPort StepGen 0 Step/Table1 (Out)
6 9 IOPort StepGen 0 Dir/Table2 (Out)
7 10 IOPort MuxedQCountSel 0 MuxSel0 (Out)
8 11 IOPort MuxedQCount 0 MuxQ-A (In)
9 12 IOPort MuxedQCount 0 MuxQ-B (In)
10 13 IOPort MuxedQCount 0 MuxQ-IDX (In)
11 14 IOPort MuxedQCount 1 MuxQ-A (In)
12 15 IOPort MuxedQCount 1 MuxQ-B (In)
13 16 IOPort MuxedQCount 1 MuxQ-IDX (In)
IO Connections for P2
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir
1 17 IOPort SSerial 0 RXData1 (In)
14 18 IOPort SSerial 0 TXData1 (Out)
2 19 IOPort StepGen 7 Step/Table1 (Out)
15 20 IOPort StepGen 7 Dir/Table2 (Out)
3 21 IOPort StepGen 6 Step/Table1 (Out)
16 22 IOPort StepGen 6 Dir/Table2 (Out)
4 23 IOPort StepGen 5 Step/Table1 (Out)
17 24 IOPort StepGen 5 Dir/Table2 (Out)
5 25 IOPort StepGen 4 Step/Table1 (Out)
6 26 IOPort StepGen 4 Dir/Table2 (Out)
7 27 IOPort MuxedQCountSel 4 MuxSel0 (Out)
8 28 IOPort MuxedQCount 2 MuxQ-A (In)
9 29 IOPort MuxedQCount 2 MuxQ-B (In)
10 30 IOPort MuxedQCount 2 MuxQ-IDX (In)
11 31 IOPort MuxedQCount 3 MuxQ-A (In)
12 32 IOPort MuxedQCount 3 MuxQ-B (In)
13 33 IOPort MuxedQCount 3 MuxQ-IDX (In)
Please Log in or Create an account to join the conversation.
02 Mar 2022 20:27 #236213
by PCW
Replied by PCW on topic 5i25 & 7i85 new install
The standard 7I85Sx2 firmware will wire the 7I85S
so that step0 is TX0, Dir0 is TX1, Step1 is TX2,
Dir1 is TX3 etc
Also the encoders are in the 7I85S orders
Is that your mesaflash listing?
(that is what it should look like)
so that step0 is TX0, Dir0 is TX1, Step1 is TX2,
Dir1 is TX3 etc
Also the encoders are in the 7I85S orders
Is that your mesaflash listing?
(that is what it should look like)
Please Log in or Create an account to join the conversation.
02 Mar 2022 20:56 #236215
by KcChris
Replied by KcChris on topic 5i25 & 7i85 new install
Yes, that was the output from the "sudo mesaflash --device 5i25 --readhmid"
Ok so in the 7i85 manual I see TB2 pin11 = TX0
-What does /TX0 mean? (+Dir vs -Dir ?)
So just to confirm linuxcnc to 5i25 , that is the pins I config in the Hal file?
The firmware on the 7i85S then outputs to the pinout in the manual?
Ok so in the 7i85 manual I see TB2 pin11 = TX0
-What does /TX0 mean? (+Dir vs -Dir ?)
So just to confirm linuxcnc to 5i25 , that is the pins I config in the Hal file?
The firmware on the 7i85S then outputs to the pinout in the manual?
Please Log in or Create an account to join the conversation.
02 Mar 2022 21:40 #236217
by PCW
Replied by PCW on topic 5i25 & 7i85 new install
Yes /TX0 in the inverted copy of TX0.
This is used for differential wiring
(especially for servos with MHz step rates)
For step.dir and encoder interfaces, you only deal with
stepgen and encoder numbers, not pins
This is used for differential wiring
(especially for servos with MHz step rates)
For step.dir and encoder interfaces, you only deal with
stepgen and encoder numbers, not pins
Please Log in or Create an account to join the conversation.
03 Mar 2022 00:07 #236234
by KcChris
Replied by KcChris on topic 5i25 & 7i85 new install
Ok I think I'm getting my head around it.
on the 5i25 side -> hm2_5i25.0.stepgen.00.dirsetup
is then assigned to this linuxcnc function -> [JOINT_0]DIRSETUP
then the 5i25 card takes care of the pass to the 7i85s card and the pins there.
So in the 7i85s manual, I see a pin assigned to TX0 and etc.
-on the 7i85S
So TX are always step gens?
and the QA and QB pins encoders?
What about IO for like a probe or charge pump?
Is there a gap in standard signal lango or something I can read up on?
I'm not able to download the support software for 7i85s, is there where some of this information is?
I do greatly welcome the help and a huge thank you so far.
on the 5i25 side -> hm2_5i25.0.stepgen.00.dirsetup
is then assigned to this linuxcnc function -> [JOINT_0]DIRSETUP
then the 5i25 card takes care of the pass to the 7i85s card and the pins there.
So in the 7i85s manual, I see a pin assigned to TX0 and etc.
-on the 7i85S
So TX are always step gens?
and the QA and QB pins encoders?
What about IO for like a probe or charge pump?
Is there a gap in standard signal lango or something I can read up on?
I'm not able to download the support software for 7i85s, is there where some of this information is?
I do greatly welcome the help and a huge thank you so far.
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.185 seconds