Advanced Search

MTTI wrote:

Thanks for this answer.

I would like to install RTAI due to the jitter in my setup, which is around 70k.
I'm using 4 stepper motors with encoders (closed loop) and a USC board from PICO.

Sometimes, though not very often, I get an "Unexpected realtime delay" message.
Do you think this could be related to the jitter amount?

I've tried every optimization I could find in the BIOS...
 

Just having a look at the PICO config, is the base thread used ? From a quick look nothing appears to attach to the base thread. Which would lead me to think that a simple RT_PREEMPT kernel would be suffice. The PICO board would seem to operate in a simialr way to a mesa 7i90 using the EPP protocol. IE using the parallel port to send timing info to a FPGA.

I think that there are issues with https on the wiki, try http:
wiki.linuxcnc.org/uploads/hobbing.zip
 

Rodw, you said "Be sure to select Mate or XFCE desktop" The defaults in your suggested ISO / Debian 13"are "Debian desktop environment", then "Gnome" and "standard system utilities". All preselected. Not selected are "Mate and Xfce" among others. Do you feel going with the preselected defaults will cause the "can not find a bootable drive" error problem? or should I just go with the defaults? If I don't select some of the unchecked software options on this install page, will it cause my system to not install or just not find the bootable OS on reboot? It does say "the core of the system is installed"

Debian 13 is still in testing. Debian 12 is the current stable version. So no Debian 13 (Trixie) is not more stable than Debian 12 (Bookworm). Honestly I would stay away from Trixie based on your Linux experience. Stay with the version that actually has been released rather than a version that is still in testing.

I would also look for any HP forums that discuss your particular machine as it maybe a "HP issue" with some input from Microsoft that is causing the issue, not a "Linux issue".

But have you followed my advice regarding testing the latency of the computer ? If the latency is not suitable I wouldn't bother trying to install Linuxcnc on that machine.

You keep mentioning "sudo commands" but give no indication to what these areor what they are supposed to do, do you see this is another issue where you are not supplying information, do you need this information beaten out of you (this does not mean an actual beating, but this how frustrating you are being). Would these be related to HP's buggy uefi and having to rename some boot files.

I have a HP computer 110-210, The system info is in the first photo provided “Mysystem.jpg” I will send a photo of the label on the side of the box if you like, but it has less info than the detailed system info. Sorry to provide to much background info on me, but is was suggested that I did not try the obvious things first like using the default settings or installing to my main internal drive first.

"unknown" said “The reason for my troll comment was because you seemed to not want to give a lot of info, or it would seem directly reply to any suggestions.” I though with all the photos like “my detailed system info” I was providing too much info. If there is something missing from all the info and photos provided, I am happy to provide it.

I saw the latency test while in live mode. It asked to do things like stress my system that I could not do yet like running motors I think. But it did not seem like it would prevent my “successful installs” from being found on ether hard drive” Do you think they are related? Now that you have seen my system info, do you feel that my system is not capable of recognizing a successful install on ether of my hard drives?

Update… I thought trying installs without the Ethernet connected may help avoid the “UEFI: IPv4 Realtek PCIe FE family controller” coming back and interfering with something, but the install made it clear it wants to be connected to get all needed files. So I am starting over with it reconnected. I am currently trying “rodw” suggestion to see if this ISO “debian-trixie-DI-alpha1-amd64-netinst.iso” will be found after a successful install I hope. I did see it said Debian13, so maybe it is more stable than the others I have tried. Unless the problem is something else. I will post the results of this install attempt using the suggestions like “Be sure to select Mate or XFCE desktop “ but the sudo commands would need to be in a live mode terminal if the install fails.

NO = normally open switch
NC = normally closed switch

Are you hitting 70K microseconds on RTAI or PREEMPT_RT?

Just in case, here are the options I've found to help:

github.com/NTULINUX/RTAI/blob/master/README.BIOS

Sorry, I'm a bit stupid today, but when you say "you must use
the plain inputs pins for NO contacts and the -not pins for NC contacts."

On the 7i96S there are only input pins with a common, not listed particularly as NO (normal pins ref:inputs) or NC (i.e. -not pins).

Do you mean that the NO are set as normal with Common Ground, and when set to NC then the Inversion sets the logical pin "type" to -NOT?

I know I am being a bit anal, but just want to be clear.

Thanks.

Good evening, I tried to follow this tutorial, but I couldn't find the stlink bin file, the DAPLink file no longer exists, I couldn't find it anywhere

I apologize, I forgot to translate, as the website is already automatically translated I didn't notice, I translate everything on Google, I don't speak English

I got my motors and drivers and was able to get them setup thanks to dschultz's configuration files. My next goal is to get sensorless homing working, using homing method -2. My understanding is that I will need a custom homing component to use the external homing on the servo drive. I noticed that rodw was working on a github repository for just that . I gave the instructions a shot, and was able to build and install the component; however, it does not seem to work. I can see the additional pins that it creates in LCNC (e.g. joint.n.request_custom_homing, joint.n.is_custom_homing, and joint.n.custom_homing_finished), but starting homing does not set joint.0.request_custom_homing and setting it manually does not seem to do anything. I feel like I must be missing something in my hal file.
Something else that is unclear to me is how the homing method is set. In the manual, PDO 6098h sets the homing method. Would I need to set that in my hal file using setp? Attached are my configuration files. Any help is greatly appreciated!

     

This may be a purely academic question, but nonetheless:

G49 seems to be 'modal' whenever a G43 Hn is not in effect (also, the 'n' tool must have a non-zero offset in order to 'turn off' G49 and 'turn on' G43 in the 'active g-codes display').

I say the previous because whether or not I specify G49 in the RS274NGC_STARTUP_CODE , my machine shows G49 under 'active g-codes' after every restart. (I'm using QtDragon, and this is right under the last axis in the DRO).

I guess my questions are:
Is there any reason the G49 needs to be specified in RS274NGC_STARTUP_CODE ?
It appears that tool offsets are not persistent across re-starts: but is there any case outside of custom programming that would make them persistent across re-starts? (I guess this might be an answer to my first question.)

Thanks!

 

For the UI you do not need that, it's coded and the only setting is the ini. You may have a conflict if using an external source besides the screen sliders. I would remove any external source and check if functionality on screen returns.

Also try the sim to verify it still has functioning override sliders.

Hoping for some advice, things to check.
I have In rv901t board running,  correct firmware,  i disabled most os the mdb2hal stuff in hal to get it to run. I have modded the board as posted on this post, the j601 port works for outputs and tests well. However the j600 port isn't working as input. If i mod my hal file so one of the inputs (on the j600 port) is an output it works as one. ( setp ***** is_output true.  - or something like that) shouldn't the firmware be setting it as input?
edit # found the problem,  page 8 note that the bit file on github is not suited to a modded board. So use your own created bitfile or the page 8 one.