Advanced Search

Ja Anleitungen habe ich einige im Netz gefunden, aber leider keine wirklich verständliche. leider eher für die Mesa 7i76e
Update: zum Totlachen, am FU gibt es 2 Klemmen GND und XGND, XGND verwendet und es funktioniert. Mache gerade noch eine Doku und hänge sie dann hier an. 

Hello.  This question is most likely for Mr. Wallace, I assume.   

Having connected my 7i89 board to my 7i76e board using an (apparently) miswired DB25M to IDC26 cable, I seem to have blown the top off what I believe is a hex inverter:


 


I intend to try to fix it.

I can't find an ON Semiconductor record for a chip exactly identified as "ACT04G."  Perhaps this 74ACT04SCX is a close enough match?:

74AC04, 74ACT04 Data Sheet

Lastly, I think my mistake was in assuming I understood the pin numbering on the 7i76e's expansion connectors.  Which of these (or neither) is correct?:

 

Thanks in advance!

I'd think that a one-shot information message right after:

"Failed to execute SDO download"

something like:

"Are any of your EtherCAT devices powered off? Did you add/remove a device w/out editing your XML?

I suspect LinuxCNC isn't happy if an ethernet attached Mesa 7i76e is powered off either.

A simple hint could reassure the user that nothing may be broken, just forgot to power something up.

You would need to add an additional RS-485 interface.
(either an existing daughtercard (7I74,7I78,7I85S,7I85,7I88,7I89
or a simple adapter with a a single RS-485 chip like a SP491 (like a mesa 485x1))

HI
Is it possible to get a second serial interface on the MESA 7i76e board? I need to interface a Mitsubishi VFD via RS485 and I have a 7i73 pendent board connected to the serial interface on TB3.


 

Thanks for the help we got the MPG to fully work after changing the mode to 20 and reconnecting some loose wires.

Lately, the machine always triggers itself to have cycle start, please see attached some photo. It uses 7i76e card, can anybody help? Also, what are the alert message meaning, they always comes out. I use LinuxCNC 3 years now, previously, I used Mach3 (more than ten years). In my feeling, It is difficult to use it than Mach3 !

You would need mode 2 on the 7I76Es I/O section to enable the MPGs:

sserial_port_0=20xxxx

These are the loadrt lines that show up in the main Hal file.
We haven't fully configured the spindle encoder yet, because we were trying to figure out how to move the axis' with the MPG, is it possible that the encoder needs to be fully functional before we can use the MPG for the axis'?

Thanks in advance

loadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS
loadrt hostmot2
loadrt hm2_eth board_ip="192.168.1.121" config="num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=00xxxx"
setp hm2_7i76e.0.watchdog.timeout_ns 5000000
loadrt pid names=pid.x,pid.y,pid.z,pid.s

I see on the screen some values X,Y,Z,A,C I think they are not the right values. Also several values available under HAL configuration and I am watching them now under WATCH, for example
hm2_7i76e.0.stepgen.00.counts
hm2_7i76e.0.stepgen.01.counts
hm2_7i76e.0.stepgen.02.counts
hm2_7i76e.0.stepgen.03.counts
hm2_7i76e.0.stepgen.04.counts
I think they are the step values you mentioned

In the main hal file, the loadrt line, does it set the board to mode 1 or mode 2?
Same line, does it have number of encoders at anything but 0?
Normally encoder 0 would be the spindle encoder, are you using that for MPG?

Hi, I'm having a similar error code when trying to run LinuxCNC

Note: Using POSIX realtime
".custom.hal:81: Pin 'hm2_7i76e.0.7i76.0.0.enc0.count' does not exist"
3999

(The 3999 number changes everytime we try to start up the program)
This only happens when we use a specific code in our custom.hal to control the axis' with a MPG controller.
We've already checked the field power TB1 (pin 5 +24V pin 8 GND) and when we measure P3 there is a 5V available.
The Custom.Hal we used is below.

loadrt mux4 count=1
loadrt mux8 count=1
loadrt select8 count=1
loadrt conv_float_s32 count=1
addf mux4.0 servo-thread
addf mux8.0 servo-thread
addf select8.0 servo-thread
addf conv-float-s32.0 servo-thread


# For velocity mode, set to 1
# In velocity mode the axis stops when the dial is stopped
# even if that means the commanded motion is not completed,
# For position mode (the default), set to 0
# In position mode the axis will move exactly jog-scale
# units for each count, regardless of how long that might take,

setp axis.x.jog-vel-mode 0
setp axis.y.jog-vel-mode 0
setp axis.z.jog-vel-mode 0

# This sets the scale that will be used based on the input to the mux4

setp mux4.0.in1 0.001
setp mux4.0.in2 0.01
setp mux4.0.in3 0.1

# This selects axis (off=0, x=1, y=2, ...)

setp mux8.0.in0 0
setp mux8.0.in1 1
setp mux8.0.in2 2
setp mux8.0.in3 3
setp mux8.0.in4 4
setp mux8.0.in5 5
setp mux8.0.in6 6
setp mux8.0.in7 7

# The inputs to the mux4 component

net scale1 mux4.0.sel0 <= hm2_7i76e.0.7i76.0.0.input-20
net scale2 mux4.0.sel1 <= hm2_7i76e.0.7i76.0.0.input-21

# The inputs to the mux8 component

net mux8-sel0 <= hm2_7i76e.0.7i76.0.0.input-22
net mux8-sel1 <= hm2_7i76e.0.7i76.0.0.input-23
net mux8-sel2 <= hm2_7i76e.0.7i76.0.0.input-24
net mux8-sel0 => mux8.0.sel0
net mux8-sel1 => mux8.0.sel1
net mux8-sel2 => mux8.0.sel2

net mux-float conv-float-s32.0.in <= mux8.0.out

net mux-s32 <= conv-float-s32.0.out
net mux-s32 => select8.0.sel
net axis-select-x <= select8.0.out1
net axis-select-y <= select8.0.out2
net axis-select-z <= select8.0.out3
net axis-select-4 <= select8.0.out4
net axis-select-5 <= select8.0.out5
net axis-select-6 <= select8.0.out6

net axis-select-x => axis.x.jog-enable
net axis-select-y => axis.y.jog-enable
net axis-select-z => axis.z.jog-enable

# The output from the mux4 is sent to each axis jog scale

net mpg-scale <= mux4.0.out
net mpg-scale => axis.x.jog-scale
net mpg-scale => axis.y.jog-scale
net mpg-scale => axis.z.jog-scale

# The encoder output counts to the axis. Only the selected axis will move.

net encoder-counts <= hm2_7i76e.0.7i76.0.0.enc0.count
net encoder-counts => axis.x.jog-counts
net encoder-counts => axis.y.jog-counts
net encoder-counts => axis.z.jog-counts

Rod, why do you mention Odroids in every one of my posts like I've never heard of them when I'm the one who got you to buy your first H2? I guarantee you I have more machines with H2/H3s in them than anyone else.....in fact I'm the grand daddy of LinuxCNC on Odroids. BTW, none of my H3s have FPGAs on-board and they're all bigger than a Rpi especially when I attach a Mesa card so I have no Idea why you even brought that up.

You reply to most of my posts so I'm sure you're aware that I'm usually not messing with a plasma, or a mill, or a lathe. and I'm usually not just sticking a vanilla Mesa card in it. I have those machines, I don't post about them because there's nothing to post....it's been done a million times over. There's nothing special as far as RT resources that a "Fully configured Plasma, 7i76e...." is doing in HAL. Addressing some hardware stepgens and some IO isn't taxing. I'm not gonna get too far off on a tangent about what I'm doing but trust me, I'm running alot more soft RT on this project than ever will on that plasma. I'll reiterate the actual question I have since I don't want it to get burried like it tends to in almost everything I post......

Just as there exists an "addf" command in halcmd to add a function to a thread, there is a "delf" command to remove it. I've never tried it but it doesn't make much sense to use such a command outside of runtime. So I guess the question is, is there any resources to be saved by adding and removing functions from hal during runtime? I know there's logistical issues with broken nets but they can be dealt with.

 

That is not very good, so try this
forum.linuxcnc.org/27-driver-boards/5122...inuxcnc-2-9-1#289803
forum.linuxcnc.org/27-driver-boards/5124...i76e?start=10#289973

The testing I did was with a Fully configured Plasma  control box and a Mesa 7i76e with no spare IO ports and 5 stepper controllers so it was not a trivial environment.

To a large extent the use case for minimal hardware has diminished since MK was forked and seems to have died a slow death.

Why would you pay USD $225 for your E10-Nano when you can buy a Odroid H3+ for $165? Its a full blown Celeron PC  that  gives you a full blown PC in a similar footprint?