Advanced Search

SOLVED !

Codes available.
Thxs

Hi evryone,
My buttons jog xyz +- in the custom panel are working ! Yéhhhhhhhh
Home button as well.
Slider for speed control as well.
Last problem is the speed max in this pannel.
Very slow @ max more slow @50%

 Can someone tell me where and in whitch files I can increase the max speed in pyVCP.

Thanks

Marco


 

Qtvcp does not know about multitouch.
I don't have a multitouch to test with and QtPy5 had very little examples the last time I looked.

If you would like to try...
Somewhere around here is where you would add the code:
github.com/LinuxCNC/linuxcnc/blob/master...mlin/qt5_graphics.py

After nearly 3 Month i have to thank all of you.
Last November I startet these upgrade with linear encoders on all axis and after view days with try and error i just solved the problems and i can`t tell what a gamechanger this upgrade was to my mill.

Before this upgrade I allways had the problem, that on long programs with many moves i often had some losses of steps and the result never was perfect. (mostly on my 2m long X-axle) After the upgrade to the encoder its a dream to work. No more losses of steps and i can work on a level i never dreamd of.

Next project will be an upgrade to an ATC Spindle with a cabinet.
So i think th next thead is coming soon ...

Thanks a lot at all
Jens

RotarySMP wrote:

On my older MH400E, with Indramat drives, I made the mistake of adding a relay to give LinuxCNC co-control over the vertical axis brake. The original Maho design is that the Indramat axis driver solely controlled that brake. I had the opposite behaviour to you, where instead of dropping, the drive fought the brake during the period I had my finger on the machine start button.
Once I removed the 19K2 relay I added (second schematic in this post) the behavior worked correctly.
forum.linuxcnc.org/12-milling/33035-retr...0e?start=1740#340651

From the schematics you shared it I don't see the brake control circuit.Could it be that your brake control should be left to the axis driver alone?
Cheers,
Mark
 

Thanks for the feedback.
I haven't attempted to do anything like that. I'm not sure it is even possible for the brake control to be left to the axis driver itself. From what I see (on my untouched original DMU 50M too) the brake/release is nothing but an output signal from the controller to the drive. I don't think the drive itself is capable of handling such logic, or at least that wasn't the original machine manufacturer's intention. I will look into it, though.

Oh, also, my braking/release signal is a single one for all 3 XYZ drives. Is it possible to try and separate them electrically? Most likely. I'm not sure that's a good idea, though.

freemoore wrote:

I just had a very similar issue with a Yaskawa servopack drive on the Z axis of a Morbidelli. I tried adding `z-brake release delays via hal and had no luck. What eventually worked was finding a parameter in the servo drive that had the same purpose, something about keeping the control loop active so many milliseconds after the servo-ON signal or brake-ON signal was received. Perhaps your drive has similar? good luck!
 

Honestly, this sounds very reasonable and I've been trying to track such a parameter down for a while now. But my Simodrive is so old, it isn't supported by Simocom. I have to chug through manuals in the hopes of finding the correct one and the correct parameter. Been trying, but it's often conflicting information that I find, since Siemens don't publish specific manuals for a specific model, but general manuals for the entire product lineup... I will definitely keep searching, though.

It is probably worth noting that before we took out the original TNC 310 there was no such issue. So I would assume no parameters are corrupted or something of the sort.

radom wrote:

I release z axis brake 0.2s after motion.motion-enabled and it works with my simodrive,
when does this servo power on signal becomes true? are you sure you are not releasing the brake before pid is working?
 

I don't think this is the issue. I checked just now to make sure. With me pressing F2 (which is also linked to the CNC ready signal going from the Mesa to the drive), I can clearly see the PID enabled and also motion.motion-enabled.

My AC power on button and circuit is separate from the Mesa entirely in an attempt not to have to reverse engineer the emergency stop, which is on the same board originally.

So my startup procedure is essentially:
LinuxCNC startup, LinuxCNC power on (F2), manually pushing the servo AC power on button, a signal returns to the Mesa board from the drive when AC power on is successful, that signal is linked in HAL to the brake release after a short timedelay.

In many cases, this works just fine. In many, Z falls through. Sometimes after a slight delay, so just when you think it's started up properly and the servo is holding the motor, it still falls through 10 seconds later.

Thanks for the suggestion, though!
How exactly is your servo AC power on handled? My Simodrive is sort of old, as you may see — the servos are 6SN1118-0AD11-0AA1 and the control board is 6SN1121-0BA11-0AA1. 

Thank you for testing. The output indicate that the program was working as expected. The firmware is not exactly the same as mine, but it looks similar. How big differences/similarities there are would require disassembly comparing those. I can see that at least memory addresses are a bit different. Here is the output from mine (not the real dongle, I put the factory firmware on another device which has bootloader version 2.40):The addresses and sizes are close to each other, but not exactly the same.

Because you have bootloader version 2.40, I believe we would be able to read out the firmware through the bootloader. But it requires creating a similar program for that as the one we just used. And to get to bootloader mode, a 10k resistor needs to be added to the pendant. So maybe better to wait until I have tested the new firmware a bit more. And then you could read out the firmware and flash the new one at the same time, if you are still interested at that point.

I release z axis brake 0.2s after motion.motion-enabled and it works with my simodrive,
when does this servo power on signal becomes true? are you sure you are not releasing the brake before pid is working?

Thanks a lot !
It's working fine but the jog speed is vert low.
Jog slider @max
Can you tell me where to change this value ?
Thanks
Marco

In your XML file, you have opened the root tagtwice.

Hello,
I would appreciate a second thought on an issue I experience with the 7i92TM. The board is connected to a G540. After installing linuxcnc 2.9 and some rearrangement of hardware, I only have two axis left functioning (z and y) and switches (connected to the G540) are not recognized anymore either. 
Swapping the wiring to other axis transferred the functioning axis over to the new config. 
I was suspecting the G540 to be at fault and swapped it against a chinese parport BOB I still had around.
After flashing the 7i92 with the correct file (5abobx2), the new setup shows the same behavior as before which pretty much rules out the G540. 

I am running out of ideas and hence considering the 7i92TM being the problem. 
I measured the voltage of Step+ to ground and Dir+ to  ground with Linuxcnc running directly at the BOB. Results as shown below. 

Xstep: 5V
Xdir: 0V
Ystep: 5V
Ydir: 5V
Zstep: 5V
Zdir: 5V
Y2step: 0V
Y2dir: 0V

Is my assumption correct that, since z and y axis do have 5V on step and dir an the others don't, that these are outputs are physically damaged?

Thanks for your help. 


 

I just had a very similar issue with a Yaskawa servopack drive on the Z axis of a Morbidelli. I tried adding `z-brake release delays via hal and had no luck. What eventually worked was finding a parameter in the servo drive that had the same purpose, something about keeping the control loop active so many milliseconds after the servo-ON signal or brake-ON signal was received. Perhaps your drive has similar? good luck!

Hi This is a linuxcnc report after changing codes in custom panel files.Can someone help me ?

On my older MH400E, with Indramat drives, I made the mistake of adding a relay to give LinuxCNC co-control over the vertical axis brake. The original Maho design is that the Indramat axis driver solely controlled that brake. I had the opposite behaviour to you, where instead of dropping, the drive fought the brake during the period I had my finger on the machine start button.
Once I removed the 19K2 relay I added (second schematic in this post) the behavior worked correctly.
forum.linuxcnc.org/12-milling/33035-retr...0e?start=1740#340651

From the schematics you shared it I don't see the brake control circuit.Could it be that your brake control should be left to the axis driver alone?
Cheers,
Mark