Advanced Search

Good afternoon - 
I had a BK1120 with KL1104 fall on my desk a bit ago and was curious if anyone has been able to get a combination like this to work? (The BK1120 is Fieldbus or K-Bus so isn't as easy as an EK1100 for instance).

I was testing (and not succeeding) against my normal lab setup of LCNC on an Intel NUC, an EK1100, EL1008 and EL2008. My EtherCat setup is functional with the EK/EL baseline devices. 
My original "just plug it in" did not show anything with 'ethercat pdos' and only the EK/EL devices with 'ethercat slaves'. I read in some other posts (perhaps RodW?) that a trip through TwinCat and setting the product version to something else and writing the SII (eeprom) would get some traction, and it did (my process was to muddle my way through TwinCat as a new "solution", attach and search for the device successfully, then go down through the tree to IO->Device2 (EtherCat)->Box1 (BK1120)->select, then in the righthand properties pane, choose the EtherCat tab, change the device ID to 1001, then click Advanced Settings-> ESC Access->E2PROM->change device station alias to 1001, then click WriteToEEPROM) - after than and moving back to my test bench, the 'ethercat slaves -v' and 'ethercat pdos' sent some useful data back. I attached the text grabs of that in pdos.txt.
Using that info, I added into my ethercat-conf.xml. I attached a sample here. Note that it ALSO has my EK1100 info in it (as the units are on a test bench) so the BK1120 (the device of interest) is actually at index 3.
With my ethernet-conf.xml, I DO get pins generated by lcec_conf / lcec (I also attached my sample hal file that is run simply in a halrun terminal; the file halpins.txt shows the pins list right at the top for the BK1120).

However, although status of the devices on the EK1100 (other ethercat slave set) does change (both input and output) the BK1120 does not.
I understand that since the BK1120 is fieldbus/kbus that the layout is different since the BK1120 becomes the only slave in the stack and additional modules become syncmasters, so I probably either got config nomenclature wrong or do not have the correct registers.

Any thoughts or suggestions?

Many thanks,
Ted. 

The picture didn't post for G64 0.001, I forgot to resize it. Here it is.

scotth, thanks for explaining Axis details to me. I will look at what you found.

tommylight, may we hear your idea anyway? I'm just carving a test pattern now, there may be other issues lurking. They usually travel in packs.

OT-CNC, immense thanks. G64 at 0.001 helped a lot. I've improved the carve a fair bit during the past month, but this takes things the last (large) step. I started trying to carve a topo, it looked awful with machine marks.

First, check what others have offered above, i will wait a bit more as you might not like my answer and it might also not be what i think the issue is.

I run AXIS front end. You hit the start button as normal to run, hit the pause key (two to the right) to stop program, then use the arrow button (between the start and pause) to advance one block.

I must be lacking the right simulator. How do you run it block by block?

I don't think it is a machine problem. Running it in sim and going block by block, Z is not reaching end point and ramping across the cut. I did not find a change of M code in the area of code. It could be a DeskProto CAM problem, but this is just a guess.

What happens when you run the finish pass along the y direction?
Have you run the code with a tighter g64 like .005" or .001"?

I'm not sure I understand, the stepgen position feedback
should not be connected to anything when in spindle mode.

@Grotius,

how is everything going?  got quiet in here all of a sudden,  hope everything is alright with you!  drop a line and let us know!

Best Regards,

Chris

PCW wrote:

Then a change to velocity mode is trivial. To maintain
position reference when changing back to C mode, you likely
need to home the C axis to index. Does the spindle have an encoder?

That's correct. And I'm asking if is it possible not to take any action and just enable Spindle.
Example: spindle mode -> axis mode -> rotate to 300 degrees -> enable spindle with MDI command
How it works now: spindle mode -> axis mode -> rotate to 300 degrees ->rotate back to 0.0 -> enable spindle with MDI command

For the first mode change Spindle to Axis I'm, disabling (stepgen.position-reset = true). It mean that nothing happen with stepgen.position-fb (it be 0.0 instead of rotation count). So when I'm enabling Axis with joint.pos-fb == 0.0 everything is fine. But I can't do it twice OR I need somehow set stepgen.position-fb to zero with joint.pos-fb before enable Spindle mode.

 

Summary: For test purposes (for this problem), I'm cutting two ramps, one up, one down, in a 2" square. A lot of the resulting ramps are smoothly surfaced, but there are places where the z level is incorrect, leaving a raised area. I'm thinking it isn't hardware because the same error pattern repeats: ramp up/ramp down, moving the test pattern in Y, moving it in X, and changing the Z level (using thinner stock). The pattern repeats across all these conditions. I am at a loss. Software sounds likely, but there is no sign of the errors in simulation.

My machine: home built, open loop steppers, Gecko 540 drivers at 48V. Ball screws XY, Z is currently a fast lead screw. LinuxCNC/Axis, DeskProto CAM. I use a Bosch 1617evs router, it is cutting with a tapered ball nose bit, end diameter 1/8".

This very likely is not a LinuxCNC problem, but in my experience, this forum has some very sharp and responsive people on it. I've been working on this for a month.

Thanks,
Steve

Hallo,die Änderung hat die ersten Ergebnisse gebracht.Das kalibrieren wird ausgeführt. mit g54 gespeichert undist auch in der Werkzeugtabelle sichtbar.Ein werkzeug in z antasten, wenn man ca 2mm bis zur fläche fährt, geht auch.danke für deine unterstützung...

Hallo,beim mittelpunkt finden, wird nicht der richtige Durchmesser ausgegeben. dm 14 statt dm 17.
In der werkzeugtabelle ist der mess-durchmesser mit 6mm angegeben. Hat jemand eine lösung?
karlhe 

problem solved, custom_config.yml was outdated. thanks anyway!