Advanced Search

Yes, I have read about and I have installed a braking resistor that matches specs.

Additionally, I changed the ACC/DEC times from 10 secs to 12 secs.

The resistance of the cables in not important, the issue is most likely
EMI from the VFD. This may be improved with a common mode choke
(large ferrite bead) on the three wires going to the VFD. It also may be
that your voltmeter cannot read DC voltages accurately  in the presence
of large amounts of EMI

A USB/MODBUS adapter will likely also be susceptible to EMI so standard
EMI control measures may be needed in either case. These measures include line
filters on the incoming AC line power, common mode chokes on the interface
wiring and common mode chokes on the UVW motor wiring.

I tested my setup with cables as short as possible. Everything worked as expected. So the long cables are probably the culprit. Maybe capacity of the cables? or Resistence (0.2ohm)?

I ordered usb to modbus converters, hopefully they are more stable

you don't need a cross over cable.

Look at this, it may help.


P01.12 Acceleration Time 1 ♦R/W 010C 40269
P01.13 Deceleration Time 1 ♦R/W 010D 40270
P01.14 Acceleration Time 2 ♦R/W 010E 40271
P01.15 Deceleration Time 2 ♦R/W 010F 40272
P01.16 Acceleration Time 3 ♦R/W 0110 40273
P01.17 Deceleration Time 3 ♦R/W 0111 40274
P01.18 Acceleration Time 4 ♦R/W 0112 40275
P01.19 Deceleration Time 4 ♦R/W 0113 40276
P01.20 JOG Acceleration Time ♦R/W 0114 40277
P01.21 JOG Deceleration Time ♦R/W 0115 40278
Range/Units (Format: 16-bit unsigned) Default
P0145 = 0: 000–60000 sec
P0145 = 1: 00–60000 sec
1000 / 100
The acceleration time determines the time required for the AC motor drive to ramp from 0.00 Hz to
the maximum operation frequency (P01.00). The deceleration time determines the time required
for the AC motor drive to decelerate from the maximum operation frequency (P01.00) down to
0.00 Hz.
•
The acceleration and deceleration time are invalid when using P0144 Auto-acceleration and
Auto-deceleration Setting
•
Select the Acceleration/Deceleration Time 1, 2, 3, 4 with the multi-function input terminal settings
The defaults are Acceleration Time 1 and Deceleration Time 1
•
With the enabled torque limits and stall prevention functions, the actual acceleration and
deceleration time are longer than the above action time
•
Note that setting the acceleration and deceleration time too short may trigger the drive’s
protection function (P0603 Over-current Stall Prevention during Acceleration or P0601
Over-voltage Stall Prevention), and the actual acceleration and deceleration time are longer than
this setting
•
Note that setting the acceleration time too short may cause motor damage or trigger drive
protection due to over-current during the drive’s acceleration
•
Note that setting the deceleration time too short may cause motor damage or trigger drive
protection due to over-current during the drive’s deceleration or over-voltage
•
Use suitable braking resistors (refer to Appendix A: Accessories) to decelerate in a short time and
prevent over-voltage
•
When you enable P0124–P0127 (S-curve acceleration and deceleration begin and arrival time),
the actual acceleration and deceleration time are longer than the setting

Elo1 over voltage is normally caused by too fast of a decel ramp or lack of a breaking resistor.

Hi,

When I run pncconfig I get all the encoders pin types grayed out and read Muxed Enc 0, Muxed Enc 1, etc..
I cannot change it to Quad Enc A - Quad Enc B for each of the axis encoders I have.   The same is true for the StepGen which is also grayed on the pin type.  By the way I am using LinuxCNC 2.9.2.  Am I doing something wrong?  I have a 7i76e with a 7i85 card connected and used the discovery option in pncconfig and it picked up the card.  Also I chose 7i76 Mode2 I/O Card in the TB2/TB3 option.

Is there a jumper on the 7i85 card that needs to be in place to choose the type of encoders?
Thanks,
AC

If you get 1.2V on the spindle output  without LinuxCNC even running,
There either a wiring error or the 7I76E spindle output has been damaged
(most likely the OP-AMP U26)

gardenweazel wrote:

My spindle runs in reverse when the Durapulse VFD indicates Forward.

Change ONLY two of the motor wires.
Do unplug the VFD before doing this.

Hi,I have two boxes for my self-built CNC. One contains the Mesa card, stepper drivers, and 24V/36V power supplies, while the other contains the VFD. Both boxes are connected with a ~2m cable. I believe it is connected correctly. Spindle+ to 10V, Spindle Out to V11, and Spindle- to GND.Just by powering everything up, the spindle out reads roughly 1.2V, and if I start the spindle, it reads 8.1V. Also, the VFD shows ~20-40Hz in the off state and ~350-370Hz in the on state. That is obviously not what I want.

I tried setting 03.06 to 150 and 03.07 to 800, but that didn't help
 Did I miss something? Is the cable simply too long?

I am still not clear on this issue.

My spindle runs in reverse when the Durapulse VFD indicates Forward.

And I am getting an error Elo1 over voltage, likely caused by the above.

 

If the green user LEDS on the 7I76E count up, the 7I76E is receiving packets
What error do you get from ping?

Rodw
Thank You for Your video, I saw him and one more with configuration network, but in this distribution isnt grafical network manager. Tomorrow I try again start with fresh system, but I need suggestion, what i wrong do.
In Your movie, after powered card, all the time four green leds flashing. In my card after powered green leds dont flashing.

Tommylight
I havn't idea, why i was thinking, that i need "crossover" cable. If problem is in "straight" cable, that isnt problem
I set mesa to 10.10.10.10, and rpi to 10.10.10.1, 10.10.10.2, 10.10.10.11, 10.10.10.100, many times, but I dont tried change cable for "straigth", ehhh..

I cant wait check it tomorrow,

Bartek
 

First cable is "cross" so not sure if it works, allthough it should with all new-ish PC as they all have automatic settings.
The second cable is useless for networking as it is not a standard pinout/wiring.
Try using a normal "straight" cable.
Also, when Mesa is set at default 192.168.1.121 your settings should work. But if you change Mesa to 10.10.10.10 you also have to set the RPI to 10.10.10.11 for it to work.
And as a general rule, do not mess with systcl, edit only the interface file.

I think you are chasing the wrong thing. ip6 has nothing to do with it
In this video about 16 minutes in, I explain networking and how to set this up with a mesa card