Hello

(Third try posting this, there's something wrong with the forum server)

I'm retrofitting a Cincinnati Arrow which does not have any kind of homing or limit switches on x and y -axis. Glass scales have distance coded index marks though and I would like to use them for homing. I found one successful attempt doing so: 
forum.linuxcnc.org/12-milling/42195-retr...ing-success?start=50

Editing hm2 similarly shouldn't be too difficult but homing.c looks completely different nowadays. Should this kind of thing be done with homecomp? Any advice on that would be welcome, my coding skills are slightly limited and there is not too many examples of homecomp yet.

Thanks
Ossi

Welcome Hannes and thank you from my side for your contributions. I am fairly new here myself, and have made no "real" contributions to LinuxCNC so far.

If you read through this thread, you saw we discussed a "loops" variable. The changes you made to hal.cc should be another way of fixing that specific issue. As for the other changes, I haven't really used any of those features. And to be honest, I'm a bit confused about the modes (auto, MDI, manual, teleop, joint).


In other news, I have been slowly chipping away at making a new firmware for the dongle. As of right now, I have something that is mostly working. I will release the source code once I have it in a little bit better shape. But I don't think it will be of use to most people, as flashing a new firmware is likely a one way street, and may make the pendant unusable.

If you or somebody else wants to update the xhc-whb04b-6 component (more), there is some low hanging fruit:
The libusb_fill_bulk_transfer in:
github.com/LinuxCNC/linuxcnc/blob/master...whb04b-6/usb.cc#L457
should really be a libusb_fill_interrupt_transfer. Endpoint 1 is an interrupt endpoint after all. The dongle/pendant doesn't know the difference between bulk and interrupt, but for scheduling of traffic on the USB bus, there are some differences. It's not inconceivable that some of the disconnects could be from USB congestion and wrong transfer type, but I do think it's unlikely.

Another thing is the checksum calculation. The full formula is: In the XHC implementation, the seed is the day of month [1...31] and "random" is from a timer in the microcontroller.

Hi i have the exact same problem, even when trying to jog the motor by the display and have it disconnected from ethercat, so it's probably a parameter of the servo drive. I know that's not the point of the topic but i would like to know how you managed the problem!

Hello,

there is an example:
forum.linuxcnc.org/38-general-linuxcnc-q...indle-flagging-error
 

@Waggi : Vielen Dank für deinen Bericht.
Das mit den Reparaturen ist jetzt eher unschön. Zu den 2 beschriebenen Defekten würde mich noch folgendes interessieren:

Kannst du noch nachvollziehen, was du beim Bruch des Mittnehmers bearbeitet hast? Also Material und bei den Zustellungen eher aggressiv oder moderat.

Bist du dir sicher, dass das genannte Lager ein Spiel von 2mm hatte?
Das ist ja schon erheblich und kaum vorstellbar.
Weist du zufällig noch, was das für ein Lager war/ist?

Und noch eine letzte Frage. Wenn du von Werkzeugwechsler bei einer HF-Spindel schreibst, meinst du da ein ähnliches System wie bei der AMB oder ein Druckluftbetriebenes ATC?

Hi.
Are them already preset in project or them should be created by myself?

/eugenius

Hi,

did you manage to get the compensation working? I also have a bed wear problem on my lathe and wondering if there are any software solutions?

Temporary solution:
1. Add to your ini file line bellow in [RS274NGC] section: 2. Make and place in proper folder setspeed.ngc file: Now LinuxCNC waits at every change of spindle speed.
Tested by code bellow:

Hi,
I worked on the configuration again today, and I think I am very close to getting it working.
The first reason I did not get the 7i83 to work yesterday was that I powered it with 5V (which was wrong). Now, with 24V and plugging it into Serial 4 (pins 1 and 14), I got it to show up in HAL Show.
I then modified the HAL file. I removed all the pwmgen stuff and changed the enable and output lines for the axes and spindle to the analog channels of the 7i83.With that, I was still able to load the configuration and enter AXIS. After flashing the correct firmware to the 7i92 (7i92t_7i85x2d.bin) and changing the serial channel in the HAL file from channel 0 to 4, it still works.

So now to my remaining problem:
Serial channels 0 to 3 in the current firmware are on the pins that were PWM outputs in the firmware I used to convince PnCconf to generate a configuration.
Now, with the “correct” firmware, these four channels seem to no longer be usable.So my question is:
where are the pin definitions stored?
I think if I can manually correct these eight pins, then I would have the configuration fully working.
I hope my explanation makes sense.
In the attached pictures, I included the pin definitions of both firmwares and an error log that shows that serial channels 0 to 3 are detected as I/O and not as serial.
 

you have a mess going on there. if you were installing per the probe basic docs then it would have looked exactly as what i showed above, that is from a very simple apt installation. you seem to be making this much harder on yourself than it should be. i would remove everything and reinstall from scratch using apt only, be sure to purge all installations you may have installed per the docs on how to do that that you used to install. hat goes for both probe basic and qtpyvcp.

once done you ONLY edit while running:

editvcp probe_basic

this goes for when you edit anything including the user sidebar, the user tabs, user buttons etc. this opens probe basic in qtdesigner and qtpyvcp so all of the existing custom widgets are available.

DO NOT EDIT THE PROBE BASIC SCREEN or it will break you apt update ability.

only run it to startup qtpyvcp with full functionality.

Hello,

thank you for your response. By the time of my post, I had just started reading the  Stepperonline A6 topic. In the end i found that you posted a working configuration files for XYRYLZ. I tried to adapt your configuration files for my machine, deleting IO Periphery that I do not  have, and I almost got it working.

The problem is that for some reason the parameter or pin 'joint.0.request-cia-homing' is not found as if there is a problem with the cia402_homecomp component. I attached the report.

Let me answer your questions:
- What type of servo drives are they and are they CIA402 compatible? - WECON VD3E EtherCAT servo  VD3E Manual
- What type of network card are you using? - Standard network card on a HP ProDesk Mini PC
- Your ethercat.xml > basic Ethercat configuration - attached as a file
- Your maschinen.hal > required for loaded modules and links - attached as a file
- Your maschinen.ini > required for your machine configuration - attached as a file

Best Regards
Konstantin Kolev

sorry - did not think they attached - hit the below buttons too for inserft, will know better next time