7i73 custom firmware?

I'm brainstorming a custom control panel and the 7i73 is obviously the easiest thing to use. I glanced at the manual and the stock configuration isn't quite what I want to do. Not quite sure how the IO works if using different keypad setups since some of the key inputs become outputs if the jumpers are set.

What I'm thinking I want to do is have 2} 3x4 matrix keypads and have enough outputs to light LEDs on the 24 keys, also one MPG and whatever random IO is left for a few buttons/switches. Is this possible?

If you want custom with 96 gpios (48 inputs & 48 outputs) I recommend a 5A-75E. Only 6 (six) buffers needs replacing on the board, an hour job max, no need for magnification.

Stepgens, encoders, pwms, in/out signals custom via a JSON and compiled using Litex/oss-cad.

github.com/Peter-van-Tol/LiteX-CNC

What I'll probably do if the 7i73 doesn't work out is use ArduinoConnector . I'll likely have to whip up a panelPCB anyway, I could either slap a 7i73 or an Arduino Mega on it. Being an Arduino based project I could probably just omit the Mega and use basically any MCU that can be programmed with Arduino if I feel like going that route.

If you use a 7I73 with a 4x8 matrix kb you have 18 outputs available
so it would  be pretty easy do do simple 2x muxing to get 32 LED drives
(18 outputs used for 2 column drive and 16 row drive)

When I did my mill panel I wound up with a 4x8 matrix of keys and 14 outputs for LED's on the 7i73.  Plus other inputs for encoder(s) and selector switches.

The 7i73 doesn't have a lot of current available for super-bright LEDs.  Think indoor-visible indicator and not a gaming keyboard.

If you want more outputs for LED's you'll probably want to go the Arduino route.

EDIT - as usual, PCW has the better answer.

PCW wrote:

If you use a 7I73 with a 4x8 matrix kb you have 18 outputs available
so it would  be pretty easy do do simple 2x muxing to get 32 LED drives
(18 outputs used for 2 column drive and 16 row drive)
 

Not sure I follow you if using standard firmware. I suppose the matrix keyboard layout isn't special as long as it fits within 32 keys.

Not sure how muxing the outputs would work. Electrically I could use a couple of 74HC4051s but I'm not sure how that would work in HAL without a firmware setup.

Not sure how muxing the outputs would work. Electrically I could use a couple of 74HC4051s but I'm not sure how that would work in HAL without a firmware setup.

Using a periodic polling loop stat.poll() and sending over a bit mask to your mux hardware... 

Mecanix wrote:

Not sure how muxing the outputs would work. Electrically I could use a couple of 74HC4051s but I'm not sure how that would work in HAL without a firmware setup.

Using a periodic polling loop stat.poll() and sending over a bit mask to your mux hardware... 

I doubt that's what PCW was referring to.

blazini36 wrote:

 Not sure how muxing the outputs would work.

Me either.  A diagram would probably help.

I just bodged mine up (non-muxed) after some consulting with PCW about current-limiting resistor values.  My hand-wiring looks like a rats-nest - not my finest work.

I hacked (actually some low level modding of the code for one of the softcores) some 7i90 smart serial remote firmware that can used on a RV901-T board (similar hardware to the above mentioned board but with the same FPGA used by Mesa before the shortage ). Currently it has 56 bits I\0 & 4 MPGS (for jogging, not encoder use). Completely compatiable with Mesa smart serial infrastructure (no extra drivers required), just needs a RS-422 converter board and it will plug into a smart serial interface on any Mesa board.

I've tested with a custom board I'm working on with 2 Smart Serial interfaces with a 7i73 connected to first port and the RV901T board on the second port.
I could almost do it for almost any Spartan 6 based dev board.

May not make a lot of sense but here's a link to a thread where PCW was helping.
forum.linuxcnc.org/27-driver-boards/4995...ccess?start=0#282432