Advanced Search

Yes the PC is in metal housing and right now it is outside the control cabinet. I am confident this is not a EMC issue.

i have bought a much older pc which i will test tommorow.

thanks so far.

is

hm2_7i80.0.pwmgen.00.enable <== j6-amp-enable

true when you expect PWM output?

Your firmware has PWMGEN 0 enabling all 7I54 PWMgens
If this is not desirable you leave the enables as GPIO
bits.

Thanks for your reply. That works fine, except I can't use the three-position switch for forward and reverse.
I've also noticed that when I press the stop button, I have to hold it down until the motor stops completely. If I release it before the motor stops, it doesn't stop and the RPMs increase again.
I'll keep this VFD (A2 8015) for a belt sander I'm building.
I bought another VFD, a Suswe SU600, for the lathe, and I'd like to do the same as with the other one: add a three-position switch for forward and reverse, and a start/stop button.

Does the pc have a metal housing (shielded), with the 6i25 inside? Or is it a motherboard mounted in a cabinet that also contains a VFD, relays, etc? If so, your motherboard will likely need additional shielding.

Find or borrow a used PC.

the pc only reboots when i try to run my configuration. i can run Sample configurations like "axis". But when i try to run the config i created using pncconf wizard the pc just reboots. i also does this if i try to Open Loop test or test / tune axis.

langdons as these are release candidates I would prefer if these are only available from the links on my github page. If you have any images with rcX in the file name on your server could you please kindly remove them.

No, not really, you will need another PC at least.
Lets clear something up first, does the PC reboot when turning ON the Mesa cards, or, when running LinuxCNC ?

@Spumco,
Thank you for reminding me, now i know why i can not recall what was going on as i am used to ignoring everything having to do with clearpath since back when they were selling stepper motors and labeling them as "revolutionary servo motors" for a lot more $, and i think they still do, but now with encoder feedback.

Fastfred wrote:

Thank You for that looks like the .hal file is correct now I am assuming I dont have correct settings in the motors thought it would fault if power/loss of com .

or am I missing a config for that? 

Thanks
 

This is why I suggested the FIRST thing was to verify/edit the motor programming using the Clearpath software.

You cannot successfully edit/adjust HAL unless you know exactly what the motor(s) HLFB output is doing under various conditions.

Power up the motors - no need to enable in LCNC - connect a Windows computer to the motors and open the Clearpath software.  Verify that all motors' HLFB output is set to 'Servo On.'

Check your LCNC input pins are working correctly.  You can enable/disable the motors using the Clearpath software (overriding LCNC's output). 

While you enable/disable the motors via Clearpath software, two things should happen:

• The Clearpath software display should show 'servo on' in the output monitor
• LCNC halshow input pins should be high/yellow when enable is true, and low/dark when the motor is not enabled

 


@tommylight - Clearpath motors have no separate drives.  The motors are supplied with DC power and all programming/control stuff is mounted internally in the motor itself.  They have three inputs (enable + A + , and a single output (HLFB) that can be programmed to do different things.

some little progress made, I managed to flash the EEPROM, the name of the device changed and I don't see the input/output anymore.
However, I m not able to pass the INIT step

OK thank you i wil ltry

Hi Tommy!
The PC only has 1 PCIE X16 so that is problematic
I can see this in terminal:

mesaflash --device --5i25
General configuration information:

BoardName : MESA5I25
FPGA Size: 9 KGates
FPGA Pins: 144
Number of IO Ports: 2
Width of one I/O port: 17
Clock Low frequency: 33.3333 MHz
Clock High frequency: 200.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256

Modules in configuration:

Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: IOPort
There are 2 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: MuxedQCount
There are 12 of MuxedQCount in configuration
Version: 3
Registers: 5
BaseAddress: 3600
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: MuxedQCountSel
There are 1 of MuxedQCountSel in configuration
Version: 0
Registers: 0
BaseAddress: 0000
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: SSerial
There are 1 of SSerial in configuration
Version: 0
Registers: 6
BaseAddress: 5B00
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes

Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 33.333 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P3
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

1 0 IOPort SSerial 0 TXEn2 (Out)
14 1 IOPort SSerial 0 TXData2 (Out)
2 2 IOPort SSerial 0 RXData2 (In)
15 3 IOPort SSerial 0 TXData1 (Out)
3 4 IOPort SSerial 0 RXData1 (In)
16 5 IOPort SSerial 0 TXData0 (Out)
4 6 IOPort SSerial 0 RXData0 (In)
17 7 IOPort MuxedQCountSel 0 MuxSel0 (Out)
5 8 IOPort MuxedQCount 0 MuxQ-A (In)
6 9 IOPort MuxedQCount 0 MuxQ-B (In)
7 10 IOPort MuxedQCount 0 MuxQ-IDX (In)
8 11 IOPort MuxedQCount 1 MuxQ-A (In)
9 12 IOPort MuxedQCount 1 MuxQ-B (In)
10 13 IOPort MuxedQCount 1 MuxQ-IDX (In)
11 14 IOPort MuxedQCount 2 MuxQ-A (In)
12 15 IOPort MuxedQCount 2 MuxQ-B (In)
13 16 IOPort MuxedQCount 2 MuxQ-IDX (In)

IO Connections for P2
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

1 17 IOPort SSerial 0 TXEn5 (Out)
14 18 IOPort SSerial 0 TXData5 (Out)
2 19 IOPort SSerial 0 RXData5 (In)
15 20 IOPort SSerial 0 TXData4 (Out)
3 21 IOPort SSerial 0 RXData4 (In)
16 22 IOPort SSerial 0 TXData3 (Out)
4 23 IOPort SSerial 0 RXData3 (In)
17 24 IOPort MuxedQCountSel 6 MuxSel0 (Out)
5 25 IOPort MuxedQCount 3 MuxQ-A (In)
6 26 IOPort MuxedQCount 3 MuxQ-B (In)
7 27 IOPort MuxedQCount 3 MuxQ-IDX (In)
8 28 IOPort MuxedQCount 4 MuxQ-A (In)
9 29 IOPort MuxedQCount 4 MuxQ-B (In)
10 30 IOPort MuxedQCount 4 MuxQ-IDX (In)
11 31 IOPort MuxedQCount 5 MuxQ-A (In)
12 32 IOPort MuxedQCount 5 MuxQ-B (In)
13 33 IOPort MuxedQCount 5 MuxQ-IDX (In)

is there anything else i can test in software / firmware / drivers?

cdamm11 wrote:

When i load the program my pc just reboots.

That is most certainly a PC issue, not Mesa/LinuxCNC issue, so the first thing to try is insert the 6i25 into another PCI-E slot, even the long 16X one will work, and so will 8X and 4X ones.

I guess it is not obvious what to do, and one needs a drive with EoE to test with as well.
I looked around a bit and it's not so common with EoE in the drive especially the cheap ones
don't have it. 
I did find an opening though, it's in the SOEM and SOES ethercat master and slave libraries I use for embedded things.
They actually support EoE both master and slave.
I have a bit extra time now when I'm waiting for the hip to grow out again and will read up on that and try to understand the steps.
Then it should be possible to adopt this to IgH and lcec. Maybe.