Configuration 7i92 and 7i77 - get error

aleksamc wrote: I have also problem with connecting MPG to 7i77.
I used example
I connected MPG to encoder.03.count and I have change of this imput.

Code:

joint.0.jog-scale is not zero joint.0.jog-enable is TRUE axis.0.jog-counts is changing sucsesfully

But axis i not moving.
I use PyQtvcp interface.
What problem could be in?

That would be expected if the system was not homed, you would have change
the joint.0.jog-counts before homing and axis.0.jog-counts after homing.
(jogging before homing is a bit dangerous since no soft limits have been established)

Thanks PCW, you've solved both my problems.
Before your answer I made thought about difference between jog and axis. But I work now in so noizy conditions, that I tried axis.a instead axis.x)))

I'm alsmost everything configured in hal.
But yesterday I gor comunication error 2 times.
Second time was at the end of the day when machine was stopped (not moved but turned off).
I have
setp "hm2_7i92.0.watchdog.timeout_ns 2000000"
Errors are
"smart Serial Card ... Local Error ... Timeout"
I must say that I use very short Ethernet cable, less then 0,5m.
Also this cable is shielded to machine GND that is Neutral.
Possibly, it's better to shield to 0V of DC current?
But I don't think that problem could be in this. 4 years ago I used 7i92m board to make comunication with PC on 25m length of Cable and there is no Problem with communication. But there watchdog is set to 5 000 000.

That looks like more of a real time issue than a sserial issue
What was the first error?

Starting LinuxCNC from the command line would probably help
when debugging since all the errors will be logged there and can be copy-pasted
here

PCW wrote: That looks like more of a real time issue than a sserial issue
What was the first error?

Starting LinuxCNC from the command line would probably help
when debugging since all the errors will be logged there and can be copy-pasted
here

Today I've got such error one more time. I attach copy of terminal output in the file.

I increased watchdog parameter to 5000000. I have default SERVO_PERIOD = 1000000
But I got today another trouble. My one servo drive turns off and doesn't give any sign of life.

It's CACR-SR10BE12G-E yaskawa. I found that on back side is apcent cooling fan. I hope it doesn't overheet. It seems that some fuse in control circuits blowup. I took it home in will look tomorrow what inside.
I make refit of old CNC it's on configuration state. It worked 5-10 minutes.

If you get a watchdog bit error like that, it means you have lost communication
for many cycles.

I would take a look at the tmax parameters after an hour or so of operation

halcmd show param *.tmax