MPG Pedant on 7i43
Mike_Eitel wrote: Sooner or later I want to connect a 7i73 to a 7i43u
Is that possible?
Yes, with the right firmware and interface. I think that a TTL to RS422 level shifter would also be required.
Some 50-pin daughter cards have that built in. The 7i44 is the easy way, but uses up the entire connector.
I think that this is a suitable single-channel adaptor: store.mesanet.com/index.php?route=produc...74_80&product_id=192 (but check with Mesa)
Good that you thought on the hw signal. I simply ignored until now, so I have to dig into. Somehow I was in the believe that it is normal 5 Volt ttl based. No problem as I have somewhere lot of 485/422 shifters anyhow.
Then there will stay the chalange of a special firmware.
Modified one section in my mpg.hal file like so:
Link to mpg example
# The inputs to the mux4 component
net scale1 mux4.0.sel0 <= hm2_7i43.0.encoder.00.input-a
net scale2 mux4.0.sel1 <= hm2_7i43.0.encoder.00.input-b
Found the signal names for the encoder in "showhal" in LinuxCNC.
After starting LinuxCNC i had an error.
Debug file information:
HAL: ERROR: thread 'base-thread' not found ./mpg.hal:5: addf failed 4687 PID TTY STAT TIME COMMAND Stopping realtime threads Unloading hal components
This is line 5 in the mpg.hal file
"addf encoder.update-counters base-thread"
PCW wrote: You dont need to access the encoder input pins or loadrt, addf the software encoder component, just link the 7I43s encoder count pin to motions jog count pins
Found the encoder count pin via halshow under:
Component Pins: Owner Type Dir Value Name 12 s32 OUT 0 hm2_7i43.0.encoder.00.count
But where can i find the motion jog count pins in halshow tree?
I guess in my case there are three motions jog count pins (for each xyz)?
Do i have to connect the encoder count pin to each axis, right?
Thanks so far. But i do not understand too much at the moment.