Advanced Search

@ ihavenofish
Did you already put the bounty up for the jerk control?

The lspci report indicates the the board is accessible (as a 5I25)

Make sure that you leave the 6I25 jumpered for 5I25 mode or you will have access issues.

@ abs32

can you share a screenshot after running on your system

latency-histogram

for a few minutes with a few glxgears running?

From your lspciThat is the 5i25.

I have similar problem; tried 2 PCs. On both 6i25 is disabled in UEFI and enabled in legacy mode. Tried switching between 5i25 and 6i25 modes.
But mesaflash reports that no boards are found.
Attached output of dmesg and lspci commands.
I am using latest Debian version from LinuxCNC website.

Hi niiice christmas light From the person that wrote on your youtube page

Sorry, I tried uploading pictures of my BOB several times, but it wouldn't do it. I think I got it to work finally.

NWE, even though I have the BOB right next to the contactor and 12v/24v power supplies, I have never had any issues from those. I have consistently been able to run programs without issue with everything except the VFD on. The contactor is part of my Estop circuit, and it only gets turned on before I run a program or off if I hit the Estop. I have only ever experienced issues when the VFD is on.

I experimented yesterday and learned some. I tried connecting it to earth ground, but that did nothing. I tried disconnecting everything from the BOB except for the 24v coming in and the parallel port and USB from the PC (I switched the VFD to manual control). LinuxCNC ran the program with out any trips even though the VFD was running, so the BOB itself can't be the issue. I tried reconnecting one of the stepper driver pulse/direction signal wires (the steppers were completely off) and ran the program again, and it did trip, even though that wire is shielded and grounded.

I will disconnect the second shielding grounding at the motor. I will also try adding ferrites on the VFD wires first. I think we have a couple lying around that we also pulled from other things.

i am here just for subscribe and learn something more about PLL ... 

take a look at default resolution SDO .. it has to be something like 20 or 16 ... it is user resolution per revolution ... maybe it has some weird setup from factory ... you have maybe swapped bytes or something or wrong data type .... 

you dont share anything ... maybe share more details for focused reply 

Never seen a several km long axis so I am out of clues, sorry.

I can only take credit for rediscovering the PLL code and write some lines of documentation.
Sasha Ittner made the PLL code back in 2018 and it hasn't changed since then. 

Will be interesting to see what you come up with.

My problem. Is in PDO mapping, i was able to configure how to switch the IO module to OP state by using sdoconfig in XML to set some SDO to be able to switch to OP state, now my problem is with PDO mapping section, the manual says PDO 6000 is for inputs and PDO 7000 for outputs, when i ran sudo ethercat -p 5 pdos, i couldn’t find these PDOS

Hello, i have R3EC leadshine io + DI + DO
Are you having same io system , if so could you please help me in writing the xml, i am stuck in the PDO mapping section

Really nice work thank you.

I’ve modified the interface so that the scanned surface can be visualized with a button press. The next step is to make the probing settings persistent across LinuxCNC sessions. These settings are stored in the .var file, but I’m not sure how to load them at startup and update the Qt widgets accordingly.

 

jjdege wrote:

Hi,
try changing the value in the .hal file

setp cia402.0.pos-scale 1000

 
[code]Hi. Pardon for offtop. Please could you try to explain what will do linunxCNC when you using this scale, and reach the calculating maximum of +2^31, and momentary jump to -2^31. On my case system stops and there an error of following..

[/code]