Advanced Search

I just updated to newest version from wheezy. Looks like now the active gcodes has been moved out of the mdi tab view  , but now contributing to top pane height increase? The result is axis hangs below the bottom of the screen.

 

Could someone give me a hint as to what command would let me reduce the height of the top pane?
I am able to increase its height using the .axisrc file by usingbut it seems something inside stops its height from being reduced any further and this has no effect
For now I am going to scale my resolution until I have more time to look through the code.

the 429 builds, but doesnt run. i copied stuff from grblhal, but they have an open issue about it, you know the one, so we both have the same issue. im gonna try and copy it from marlin instead

github.com/cakeslob/Remora-STM32F4xx-W55...M32F429VGTX_FLASH.ld

but the pio config for the 429 i havent setup, and some of the pins are hard coded, so the one you compiled will go somewhere inconvenient. but if you are still gonna play with it, dont do it with hardware attached.

github.com/cakeslob/Remora-STM32F4xx-W55...2/platformio.ini#L88

this needs to be configured a bit better for the spi,

github.com/cakeslob/Remora-STM32F4xx-W55...b/bp2/Src/spi.c#L168
the spi pins

github.com/cakeslob/Remora-STM32F4xx-W55.../Inc/w5x00_spi.h#L18

this is where the cs pin is hardcoded


but im going to strongly recommend you just keep using the Rpi one, if you want to get your machine working. the ethernet one, you will probably need to lower your pru_freq, and there is no encoder or estop module, so you will need to use IO for that.

stonebite wrote:

i have a basic question - are my questions incomprehensible, inappropriate, not detailed enough, written way too much, boring to answer ...?

No, no, no, no and no !
The only reason i started helping here was to get better at asking and answering questions, i was bad at both.

stonebite wrote:

i am an absolute beginner in the field of LinuxCNC and the interfaces it creates. i am happy to receive advice and have no problem admitting my own mistakes.

We were all beginners at one point in time.

stonebite wrote:

As already mentioned, I am and was very grateful for any help.

And you are welcomed to ask for help always, you are also welcomed to try to help others with stuff you are good at, many topics on this forum, so we keep an eye on "recent topics" most of the time.

stonebite wrote:

I have the uneasiness with your answer that my concern is not understood or does not want to be understood.
I think it's a pity that a topic can drag on for such a long time as the one on the previous pages of this thread. I would like to avoid this and don't want to waste your time unnecessarily and receive answers that frankly don't get me anywhere.

This is a bit harder to explain, but i know for sure there is no need for concern, it is just that all we who try to help here have a life, and that life takes it's time, so the very little spare time we have we try to help others here.
There are times that i can not reply to anything for weeks, but at least i check and remove spam, and there are times when i post here 10 times a day despite working all the time.
We are all volunteers, we were all young and had to go through rough times when we had no one to help us (no internet back then)
And yes, sometimes answers here might seem absolutely weird, but with a bit of digging you always find out those are good answers.
You asked : To enable this via the 7i76 I have to assign the correct property from the pull-down menu, which is the correct property?
You got the answer : For a general enable output, "Control" --> "Machine Is Enabled"
is a good choice
That is the exact answer to that question, on the output pins pull down menu, choose "control" and select "machine is enabled".
That is the pin that will enable the machine when F2 is pressed on the keyboard or screen/GUI.
That is also the pin that will disable the drives in case of joint errors or pressing E-stop.
For more info about PncConf or anything related to LinuxCNC, start by using you Linux menu, in the CNC section together with LinuxCNC, there are also links to documentation, there is way to much there, so try just finding what you need at any moment in time, it is easier to absorb.

no, its cool. i like when other people are interested.

the hal pin that shows up, "encoder.0" isnt the same halpin as regular linuxcnc encoder. so it doesnt have the same options like encoder.N.counts. The remora PRUencoder is mainly for positional feedback from closed loop stepper motors

can you post your newest hal file? i cannot get the encoder through the float-s32 to work. I hooked up an mpg wheel so i can test with you, but i cant get it connected.
Are you trying to get it to count 1 pulse instead of 4? i dont know how we can do that yet in hal.


The remora estop is all in hardware, but triggers a controller estop so there must be some kind of pin. i will need to investigate, there are a few pins that seem to be connected to remoras estop signal to see if its status is estop. i think remora.SPI-enable/reset.status are linked to the estop status

"Why LinuxCNC is so much over complecated? I am still struggling to build a fully working cnc."

linuxcnc is hard, but you chose the hardest way to do it. a mesa card/paraport, this would be completed in much less time and struggle. because you are using remora, you are probably the first guy to do this configuration. i am learning new things a long with you, so it will be easier for the next person

Once again I need help from the LinuxCNC experts, I got to the point of changing the Grub file, I have an Intel so I use the 3 for my printout.
I don't know how to make the change in the Grub file, I looked on line and on YouTube no help for this dummy, so please explain (simply for me).
Back space and retype don't get me there 
 

Made this a sticky so it remains at the top for now, let me know if that is OK.
Thank you and your team for all the hard work.

Run the latency histogram with this
latency-histogram --nobase --sbinsize 1000 --show
Post a screenshot.
That is if you do not use the parallel port, there is no need for base period.

Thank you, couldn't see the simple solution in front of me. Solved it as follows:

net car-ccw            motion.digital-out-05      or2.2.in0
net car-cw              motion.digital-out-04      or2.1.in0
net tool-index-btn        or2.1.in1             [HMOT](CARD0).7i76.0.3.input-05
net CarIndex        or2.1.out      or2.2.in1 [HMOT](CARD0).7i76.0.3.output-13
net CarIndexRev         or2.2.out               [HMOT](CARD0).7i76.0.3.output-14

Another or gate or so can do this...

That's a big improvement already indeed, if it won't show big latency on the servo thread like this with "latency-histogram --nobase" it should be good for use with Mesa.
After such a big latency you can check "cat /proc/interrupts" to see if there is a device causing a latency on the isolated CPU.

Max c-state should be 0 indeed which means fully active, already set as kernel parameter, but might help if you still set it already in the BIOS.

If you don't trust the kernel I compiled, it's pretty easy to compile it yourself. Look for the newest rt patch, download that release of Linux and apply the patch and compile (after setting it at full realtime). You can find a tutorial easily online.

We checked and no PDO are shown in the ethercat master.The debug info shows warnings for SM2 and SM3 are not found and error that the FFMU doesn't have a sync manager configured.

[  487.220742] EtherCAT WARNING 0-0: PDOs configured for SM2, but slave does not provide the sync manager information!
[  487.220744] EtherCAT WARNING 0-0: PDOs configured for SM3, but slave does not provide the sync manager information!
[  487.220745] EtherCAT ERROR 0-0: Failed to determine PDO sync manager for FMMU!

( github.com/West-Coast-R-C-Works/linuxcnc...2.log#L701C1-L703C82 )

I'm working on getting my ATC to index, and the way the original was wired was output 13 rotated the carousel counterclockwise.  Output 13 AND 14 at the same time rotated it clockwise.  On top of that, I have a physical button to rotate it as well.  What I'm looking to do is use an OR2 with or2.1.in0 as the button, and or2.1.in1 as the logic input with or2.1.out to rotate the carousel (preferrably clockwise, so setting both output 13 and 14 true).  Then I need another input that can set just output 13 true so that the carousel can rotate CCW as well.  My problem is that only 1 signal can be assigned to an output pin, so if I set or2.1.out to outputs 13 and 14, I cannot set car-ccw to output 13.

Thanks. Finally succed to implement EL8 internal homing. For future reference here is how I did.

Cloned Marco's git: github.com/marcoreps/linuxcnc_leadshine_EL8
in el8_homecomp.comp modified the link to homing.c file, what I get from
github.com/LinuxCNC/linuxcnc/blob/master.../emc/motion/homing.c
with homing.h and motion.h files.

After I run
homecomp --install el8_homecomp.comp
and
homecomp --install cia402.comp

from marcos git repo.

Modified the ini, added to EMCMOT:
HOMEMOD=el8_homecomp

After restarting lcnc and set the servo drive 6098x02 to -6 the internal homing working.

Question first, how do I set the "Go To Sensor location" to include the Z-Axis to get within 5mm? I see the X and Y axis location but, not a Z-Axis textbox. Meaning that I want to machine to first move to X and Y sensor location and then move to within 5mm of the sensor top.

Then the issue from compiling the most recent code from GIT.Once I get the Z-Axis to within 5mm I get the error in the following screenshot. 



[QTvcp][CRITICAL]  Retry from Error Dialog
 Qtvcp encountered an error.  The following information may be useful in troubleshooting:
LinuxCNC Version  : 2.10.0~pre0

Traceback (most recent call last):
  File "/home/andy/linuxcnc-dev/share/qtvcp/screens/qtdragon_hd/qtdragon_hd_handler.py", line 891, in btn_touchoff_clicked
    info = "{} {}{} {}".format(txt1, self.w.lineEdit_max_probe.text(), unit, tx2)
                                                                             ^^^
NameError: name 'tx2' is not defined

 (qtvcp:519)
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 46018, resource id: 8653658, major code: 40 (TranslateCoords), minor code: 0


This was not happening yesterday, just started after compiling today.Is there a possibility that I have incorrect sensor heights set based on my tool sensor pad base being very low verses my table top? 

 

As always thanks in advance.

Development and stable versions are now up and live! please provide your feedback and questions here!

Thanks,

Chris