Advanced Search

Your table is missing the channel data, not sure why, but this is what I get:

IO Connections for TB1/TB2 -> 7I96_1
Pin#                  I/O   Pri. func    Sec. func        Chan     Sec. Pin func   Sec. Pin Dir

TB1-2,3                17   IOPort       StepGen          0        Step/Table1     (Out)
TB1-4,5                18   IOPort       StepGen          0        Dir/Table2        (Out)
TB1-8,9                19   IOPort       StepGen          1        Step/Table1      (Out)
TB1-10,11            20   IOPort       StepGen          1        Dir/Table2        (Out)
TB1-14,15            21   IOPort       StepGen          2        Step/Table1      (Out)
TB1-16,17            22   IOPort       StepGen          2        Dir/Table2        (Out)
TB1-20,21            23   IOPort       StepGen          3        Step/Table1      (Out)
TB1-22,23            24   IOPort       StepGen          3        Dir/Table2        (Out)
TB2-2,3                25   IOPort       StepGen          4        Step/Table1      (Out)
TB2-4,5                26   IOPort       StepGen          4        Dir/Table2        (Out)
TB2-7,8                27   IOPort       QCount            0        Quad-A            (In)
TB2-10,11            28   IOPort       QCount            0        Quad-B            (In)
TB2-13,14            29   IOPort       QCount            0        Quad-IDX         (In)
TB2-16,17            30   IOPort       SSerial             0        RXData0          (In)
TB2-18,19            31   IOPort       SSerial             0        TXData0          (Out)
Internal-TXEn       32   IOPort       SSerial             0        TXEn0             (Out)
Internal                33   IOPort       SSR                  0        AC Ref            (Out)

Default firmware on a 7I96S is 7i96s_d.bin

 

Currently they time the RX and TX data transfer overhead:

EtherRecv2Mem
        sta     SetTP0
        lda     recvfcount      ; already doing a multi frame recv,
        jmpnz   recvframe       ; so skip the prelims   

.......

recvdone
        lwi     1
        addto   recvpktcount
        lwi     MinusSix                ;adjust for CRC and 2 byte offset
        addto   recvpktsize
        sta     ClrTP0
        ret

EtherSendFromMem
        sta     SetTP1
        lda     sendpktsize             
        add     threeloc

.......

        lwi     1
        addto   sendpktcount  
        sta     ClrTP1
        ret     




 

Although, I don't understand why the pin func for the Stepgens are all "Step/Table1" and "Dir/Table2". I would have expected an index between 1 and 5 (or 0 and 4).

unknown wrote:

If not you can redirect the mesaflash output to a text file.
Don't mind me I still spend a bit of time using the command line in Linux. Just find it can be a bit quicker at times.

No need to apologize.  I've been working at Unix/Linux command line prompts since 1980.

mesaflash has provided me with the table I wanted.

There's so many different configs available, and you can even build your own firmware from source. So the manual is pretty generic.

Off track
I haven't use the 7i96, I have a 7i92/7i76 for the mill, with a couple of extra boards, I've hacked to together some FPGA dev boards to use self built 7c81/7i90 firmware. SPI & EPP is easy pcb wise, but I'm having a go at a board using ethernet based on the 7i92 schematics.
On Track

The mesa hardware & firmware is really versatile. Actually the 7i90 would be a great way to learn to program FPGAs as the I\O is 5v tolerant, most dev boards are only good for 3.3v or the smoke comes out.

If you mc (midnight commander) installed on the client or host it's real simple to transfer files.

Or some file managers let you type something like sftp://username@hostname

LinuxMint using caja, one has to have the gvfs installed. So I'm using sftp to look at my server, but as long as ssh is on the client your good, no need to have a ssh session running. Yeah the server is named after a "Happy Tree Friends" character cos I'm a 50+ yro child.

 

I find Ubuntu great for a server, much easier to add software to than Slackware, now that was dependency hell, sometime you'd spend all day installing\replacing packages from source just to install one package. Even if the packages were available you'd have to work out what else to add.

Either Mint or Debian for desktop. Used to use some of the first version of Puppy Linux, prior to it having wifi and helping to get that going.

I don't actually know what firmware I have, nor have I downloaded any. I assumed it shipped with the firmware I need.

The manual corresponds to a specific firmware, no? So the information could/should be in the manual.

Bloody oath mate.

Yourself, Cannuck ?

If you know what firmware you have on board, eg the name of the .bit file, all you need to is look in the corresponding pin file, if you've downloaded the firmware stuff.

If not you can redirect the mesaflash output to a text file.

Don't mind me I still spend a bit of time using the command line in Linux. Just find it can be a bit quicker at times.

No mate, genuinely impressed, I think I may have misjudged you and would like to extend my apologies.

All The Best
Rob

Thank you -- I haven't run my own test yet, but I see the correlations in your sample output.

If I were a python or gui programmer, I'd take a stab at adding that info to pncconf. And I suppose I'd probably discover that it's difficult, which is why it hasn't been done.

Seems like there should be an easier way, than by powering up the board you're trying to configure!

paul

I'm impressed mate

Yeah I know you're giving your time, much appreciated, but text files are so much easier to search through. especially for something as long winded as dmesg. Anyway it's so much easier than cutting & pasting.....and millions of times better than a photo of a screen.

Cheers
Rob

Regarding Ubuntu, off topic a little, but did you hear that a lot of the core utilities they are rewriting as Rust and dropping the old stable C coded ones (I think a lot of origins from Unix days). I reckon Linux might be in for a few rough years.

rodw wrote:

The mesa manual for your card outlines it all.
the physical pins are generally numbered from 1 but the pin numbers start with 0
 

No, I don't think it does.  It does have that info for the P1 expansion connector, but not for TB1 and TB2.  
www.mesanet.com/pdf/parallel/7i96man.pdf
 

Hello,

I built my HAL file with bits taken from the forum and for sure sometimes I don't understand everything.
THis results in the current situation where when I run my Gcode, for example M3 S500, the spindle is going faster and faster and never stops
Signal spindle-at-speed is true before running gcode, then it goes false and never go back to true.
My encoder is working properly with the correct number of pulse.
Maybe the near part is wrong but I have no clue if it's the case, and if yes, why ?

Thank you for your help


Here is the spinde part of my HAL file
#*******************
#  SPINDLE
#*******************

setp   pid.s.Pgain     [SPINDLE_0]P
setp   pid.s.Igain     [SPINDLE_0]I
setp   pid.s.Dgain     [SPINDLE_0]D
setp   pid.s.bias      [SPINDLE_0]BIAS
setp   pid.s.FF0       [SPINDLE_0]FF0
setp   pid.s.FF1       [SPINDLE_0]FF1
setp   pid.s.FF2       [SPINDLE_0]FF2
setp   pid.s.deadband  [SPINDLE_0]DEADBAND
setp   pid.s.maxoutput [SPINDLE_0]MAX_OUTPUT
setp   pid.s.error-previous-target true
 
net spindle-index-enable  <=> pid.s.index-enable
net spindle-enable        =>  pid.s.enable
net spindle-vel-cmd-rpm-abs     => pid.s.command
net spindle-vel-fb-rpm-abs-filtered      => pid.s.feedback
net spindle-output        <=  pid.s.output
    
net spindle-revs             <=   hm2_7i96s.0.encoder.00.position
net spindle-vel-fb-rps       <=   hm2_7i96s.0.encoder.00.velocity
net spindle-vel-fb-rpm       <=   hm2_7i96s.0.encoder.00.velocity-rpm
net spindle-index-enable     <=>  hm2_7i96s.0.encoder.00.index-enable
    
# ---setup spindle control signals---
# setp hm2_7i96s.0.pwmgen.00.scale 2500
setp   hm2_7i96s.0.pwmgen.00.scale [SPINDLE_0]MAX_OUTPUT
# setp hm2_7i96s.0.pwmgen.00.output_type 1
#net spindle-vel-cmd-rpm     => hm2_7i96s.0.pwmgen.00.value
net spindle-vel-cmd-rps        <=  spindle.0.speed-out-rps
net spindle-vel-cmd-rps-abs    <=  spindle.0.speed-out-rps-abs
net spindle-vel-cmd-rpm        <=  spindle.0.speed-out
net spindle-vel-cmd-rpm-abs    <=  spindle.0.speed-out-abs
net spindle-enable             <=  spindle.0.on
net spindle-enable             =>  hm2_7i96s.0.pwmgen.00.enable
net spindle-cw                 <=  spindle.0.forward
net spindle-cw                    => hm2_7i96s.0.ssr.00.out-01
net spindle-ccw                <=  spindle.0.reverse
net spindle-ccw                    => hm2_7i96s.0.ssr.00.out-02
net spindle-brake              <=  spindle.0.brake
net spindle-revs               =>  spindle.0.revs
net spindle-at-speed           =>  spindle.0.at-speed
net spindle-vel-fb-rps         =>  spindle.0.speed-in
net spindle-index-enable      <=>  spindle.0.index-enable

# ---Setup spindle at speed signals---

sets spindle-at-speed true

net spindle-vel-cmd-rps    =>  near.0.in1
net spindle-vel-fb-rps         =>  near.0.in2
net spindle-at-speed       <=  near.0.out
setp near.0.scale 1.000000
setp near.0.difference 1.666667
 
setp lowpass.spindle.gain 1.000000
net spindle-vel-fb-rpm => abs.spindle.in
net spindle-vel-fb-rpm-abs abs.spindle.out => lowpass.spindle.in
net spindle-vel-fb-rpm-abs-filtered lowpass.spindle.out
net spindle-output => hm2_7i96s.0.pwmgen.00.value

# ---Setup spindle encoder---
setp hm2_7i96s.0.encoder.00.scale 4000