Advanced Search

That looks basically OK

Possible a cable issue?
 

General configuration information:

BoardName : MESA7I92
FPGA Size: 20 KGates
FPGA Pins: 256
Number of IO Ports: 2
Width of one I/O port: 17
Clock Low frequency: 100.0000 MHz
Clock High frequency: 180.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: DPLL
There are 1 of DPLL in configuration
Version: 0
Registers: 7
BaseAddress: 7000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 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: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: MuxedQCount
There are 12 of MuxedQCount in configuration
Version: 4
Registers: 5
BaseAddress: 3600
ClockFrequency: 100.000 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: 100.000 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: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes

Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P2
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

1 0 IOPort SSerial 0 TXEn2 (Out)
14 1 IOPort SSerial 0 TXData2 (Out)
2 2 IOPort SSerial 0 RXData2 (In)
15 3 IOPort SSerial 0 TXData1 (Out)
3 4 IOPort SSerial 0 RXData1 (In)
16 5 IOPort SSerial 0 TXData0 (Out)
4 6 IOPort SSerial 0 RXData0 (In)
17 7 IOPort MuxedQCountSel 0 MuxSel0 (Out)
5 8 IOPort MuxedQCount 0 MuxQ-A (In)
6 9 IOPort MuxedQCount 0 MuxQ-B (In)
7 10 IOPort MuxedQCount 0 MuxQ-IDX (In)
8 11 IOPort MuxedQCount 1 MuxQ-A (In)
9 12 IOPort MuxedQCount 1 MuxQ-B (In)
10 13 IOPort MuxedQCount 1 MuxQ-IDX (In)
11 14 IOPort MuxedQCount 2 MuxQ-A (In)
12 15 IOPort MuxedQCount 2 MuxQ-B (In)
13 16 IOPort MuxedQCount 2 MuxQ-IDX (In)

IO Connections for P1
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

1 17 IOPort SSerial 0 TXEn5 (Out)
14 18 IOPort SSerial 0 TXData5 (Out)
2 19 IOPort SSerial 0 RXData5 (In)
15 20 IOPort SSerial 0 TXData4 (Out)
3 21 IOPort SSerial 0 RXData4 (In)
16 22 IOPort SSerial 0 TXData3 (Out)
4 23 IOPort SSerial 0 RXData3 (In)
17 24 IOPort MuxedQCountSel 6 MuxSel0 (Out)
5 25 IOPort MuxedQCount 3 MuxQ-A (In)
6 26 IOPort MuxedQCount 3 MuxQ-B (In)
7 27 IOPort MuxedQCount 3 MuxQ-IDX (In)
8 28 IOPort MuxedQCount 4 MuxQ-A (In)
9 29 IOPort MuxedQCount 4 MuxQ-B (In)
10 30 IOPort MuxedQCount 4 MuxQ-IDX (In)
11 31 IOPort MuxedQCount 5 MuxQ-A (In)
12 32 IOPort MuxedQCount 5 MuxQ-B (In)
13 33 IOPort MuxedQCount 5 MuxQ-IDX (In)

   

What solution exists for mill front panel button inputs? These are non critical real time inputs
for example extra inputs for front panel buttons like cycle start/stop/pause/ +- x+-y+-z+-a/flood/mist/tool clamp/spindle cw-ccw-stop.
Can i use parallel port for these or something
from usb port like arduino or rs232 or rs485 port?

Would need the hal, ini files and to verify the firmware with mesaflash  to trouble-shoot

I have a 7i92t connected to a 7i77. All of the I/O seem to be functioning properly. The analog 0 works properly and the encoder for that axis reads properly. The problem is the remaining joints, and their encoders are not working. Is there a setting that I might be missing to get all of the axis to work? Currently I only have the X axis in linuxcnc working and I can't seem to find the problem with the remaining 5. Any suggestions on what the problem is would be appreciated. I will try to post the hal. and ini. later, but I can't right now.

Rod recommends Balena Etcher.

Victory! (of step 1, now I move on to step 2, building my HAL  )

I am using the Raspi build (forum.linuxcnc.org/9-installing-linuxcnc...erry-pi-4b-5?start=0), but after recompiling mesaflash from git it worked flawlessly!

Thank you so much for guiding me along!

What type of hardware do you have?

 

Where did you get the image from?
Is there a file or a long string of numbers/letters with something like md5sum or sha256 where you downloaded the image?
Did you check if those numbers/letters are the same?

There is no way of knowing without actually testing it.
There are probably hundreds of NUC's versions.

natholego11 wrote:

and here is a link to the probe I have.
 

I don't have a solution, but I have the same probe that I will soon be integrating into LinuxCNC, however mine is NC, not NO. I also have the toolsetter accessory that goes with an identical second probe, which comes with a slightly weaker spring, so you can set the spindle probe length with the toolsetter. There's even a magnet on the bottom.

If it helps, here is an electrical breakdown of the board on the probe. The reverse is just contacts to the pogo pins. The important part - and the point of this reply - is the pinout of the type-c port, so you can make your own cable . I will use shielded microphone cable. The solution could be that simple.

A5-CC1 & B5-CC2, are tied on the probe PCB. The little plug PCB's larger pads are +24v & gnd, and while there are passives on the little plug PCB, I don't know one way or the other if they affect the signal. It seems easy enough to remove them and bridge their pads if it comes to that.

That most likely means you don't have a very recent mesaflash installation.

The bin file header parsing was changed on more recent mesaflash versions
to accommodate longer path-names (the build path-name is embedded in
the .bin file header)

Sorry @PCW, I need to request your help once more... I tried flashing the bin file with
and I get 
Error: Wrong bitfile destination device: Trion, should be T20F256

Should I have set somewhere in Efinity the type of board used? I started simply from the 7i92t.zip, taking the 7i92t_G540x2_34 file as basis...

I download the filewhen I try to use the pi image i get this errorwhat am I doing wrong?thanks