pncconf update

I'm sorry the transition has been so difficult - it usually isn't.
Sounds like a real problem as dmesg should always report all the pins of all the headers.

dmesg is not giving much info as to the problem either....

i wonder if this has something to do with renaming - I see alot of references to emc2 and most were changed to linuxcnc.

I'm sorry I am not sure what to recommend.
I have heard of no problems with buildnot linuxcnc.
Hopefully someone else will shed some light.

Chris,

Thanks for your time and effort, all your time and effort.

For the time being I shall revert to 2.4.7.

I need to get the machine up and running for the morning.
We are fabricating printed circuitboards and are now suppoerting a local R&D facility fabricating boards with 3D rf structures including cavities within a multilayer structure.

Have been down for a few weeks with servo problems so now really need to get the gear up and running

just to confirm the buildbot version you are running is fine i use it here ,
but .... their are changes to be made in the hal file for older configurations to run .
make a new config and then copy across from your older version any extra parts needed is the easy way

make sure you run the newer pncconf program if you have more than one version on the machine
this can cause problems .

Thanks for Your cabove comments.

And now Happy news.

I am back with 2.4.7.

Machine is up and running.
Need to get a clarification on PDM numbers.
In one spot I think I saw maximum PDM clock at 2 MHz. Optimum 5i20 / 7i33 PDMclock 1MHz.

PNCCONF pushes out sub two hundred KHz setting.

In another posting I saw 6 MHz as being optimal for above combo.

Is there a definitive statement on this?

6 MHz using PDM mode ( you need to select pulse density as the pintype on the mesa signal selection page)

yes the default numbers are badly choose in pncconf 2.4.x

Chris M

Chriss,

Thank You.

The axes are up and runing.
Machine is based on a 5I20 / 7I33 controls with AMC BE12A6 servo amps and Anaheim Automation 180W BLDC motors.

Measurement system is Renishaw 5 micron linear scales with CUI Inc. AMT rotary shaft encoders for servo amp tacho feedback.

HALSCOPE was used to monitor following error and judicious application of P, D, FF0, FF1 and FF2 components produced an outcome of almost zero following error at speeds in the order of 600 mm /min

A great outcome beyond my reach without the forum's support..

I'm glad to hear of your success !!
And I'm glad you found Pncconf and any of my comments helpful.

Post a pic of your machine some time.

Chris