Advanced Search

the same thing happens with a restart, as soon as I want to insert any axis or anything on the 7i96s (specifically the A axis) the fields for angular are blurred...also if I don't do that and export the configuration for the 7i77, an error appears about 0.analogen...and 0.spinnen which I have to comment on. it is very possible that it is due to the new version of mesact, which requires a newer mesaflash, and I need to see how to update the older one and then try, because there is no previously flashed 7i96s-7i77.bin in the tab ``firmware''

Maybe im missing something, is this just installed into a standard debian OS?

I see the install guide commands to "install" everything, but im attempting to install in debian13 and getting alot of errors.

At last the Spindle is back under control, the new VFD works well, and the rigid tapping cycle executes, so therefore spindle orientation must work....
M19 R120 Q5 simply times out.
Linuxcnc ORIENT Man  explains I need to setup the orientation pins etc.
loadrt orient names=orient
loadrt pid names=orient-pid
net orient-angle spindle.N.orient-angle orient.angle
net orient-mode spindle.N.orient-mode orient.mode
net orient-enable spindle.N.orient orient.enable orient-pid.enable
net spindle-in-pos orient.is-oriented spindle.N.is-oriented
net spindle-pos encoder.position orient.position orient-pid.feedback
net orient-command orient.command orient-pid.command

all good, except for the enigmatic statement at the start:-
"On spindle.N.orient disconnect the spindle control and connect to the orient-pid loop:"

This I cannot quite get into my hal without error. 

Current error is:-
./Hurco_7i92.hal:347: Pin 'encoder.position' does not exist

Also having failed to get spindle.0.orient to connect, I have reverted to the original enable connection.

I'd appreciate some guidance please.
Thanks

DemonClaW wrote:

Better like that?

Yes, thank you.

Try Modbus. hy_vfd isn't Modbus.

Another question, about the python module. How can i get path and name of the current loaded file, in the python module. I need to read and find some specific content. I couldnt find the answer myself.

Same as the previous one. Same wiring. Same usb adapter.

The manual www.huanyangvfd.com/wp-content/uploads/2.../FC01-Series-VFD.pdf says it uses Modbus, did you try that?

Hi guys, previously I've been using hy inverter which worked well with hy_vfd via modbus. After it failed I've bought huanyang FC01 and connected the same way. Unfortunately with the same configuration it didn't work straight out of the box as I expected. Did anyone succeed with FC01 model? 

Only way to know is to have the xml and hal files, the error messages and some lines around them, and the last say 30 lines of the syslog.

need for v2.8.4
I created a program file and embedded debug messages into it. It was established that the error was triggered directly during execution of the g38.5 command

===========
            (LOG,стр 65 )
        #5070=1
        (LOG,X#5061 Y#5062 Z#5063)
        #5070=1
             (LOG,стр 68)
        #5070=1
        G38.5 F[#<_скорость_отскока>]  Z[#<_z> + #<_отскок>] 
             (LOG,стр 70)
===========
there is an entry in the log "стр 68", the machine was stopped by mistake and the state of the sensor - it drove away and in the "no contact" state #5070=0

seems like the lcec file in the hal fie has an invalid path. or XML has an invalid path.

I certainly could but would we want to make the python vtk module a runtime dependency?

Better like that?

You are making good progress. Once you have it all running, I will have to use your HAL and Ini to upgrade my machine to 2.9