Advanced Search

Hello PCW, thank you for your reply
Here is my ini file regarding spindle:

[SPINDLE_0]
P = 1
I = 0.01
D = 0
FF0 = 1
FF1 = 0
FF2 = 0
BIAS = 0
DEADBAND = 0
MAX_OUTPUT = 2500

When i just run the MDI command M3 S500, everything is fine
But when I run a gcdoe file with the same command, I get this issue

Oops. I've edited the table to a more convenient/compact format, and I had already edited that column out of mine, because I didn't think "Channel" was interesting (to me, at least). I hadn't realized what it represents.

Thanks.

thank you . I will try that next

What are the spindle P terms (in the ini file)

In general for spindle setup, I would get open loop operation
running correctly first before trying to close the loop.

Basically if you have a spindle PID loop, this means setting
FF0 to 1  and all other PID gains to 0
 

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.

unknown wrote:

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.

Not easier over SSH.

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.