Advanced Search

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. 

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...

That would be around 5 meters of belt for each motor, so 20mm belt might be still OK
If you feel like it, go for it for sure.
And to further give you hope, a friend i taught about building CNC's did build a router with 2x1 meter envelope, using 10mm GT2 belts and it works nicely once he got a hang of feeds and speeds, been in use for over a year, and yes it is CoreXY driven by Marlin and LightBurn... Yeah, don't ask
Somewhere in my process of teaching him, he went a bit sideways!

Hello everyone, I have another small problem again. My machine does not have an active feed slider for some time now. Normally, after start and homing, it is active but during a cycle run I cannot adjust the feed with the slider. What is the reason for this? I know that this has worked before and I don't know which setting has been lost.In the INI, I have MAX_FEED_OVERRIDE = 2.000000Does anyone know anything about this?
 

ChatGPT told me to add two entries in the HAL file:
net feed_override <= halui.feed-override
net motion_feed_override => motion.feed-override
I made these entries, but the machine does not start - error - halui.feed-override does not exist...

What can I do? 
Thanks for every hint!
Greets, Hanno

    

MTTI, some systems do not work on RTAI. I tried RTAI on my SO's laptop and it instantly kernel panicked each time.

Is it really too hard to state I have a xx xxxx computer ?
I don't want to go searching what ever the common name is for the HP machine your using .
Why is it people want to play 20 questions? Is it so hard just provide some simple information.
I'm really not interested whether you are the guy people go to support for or whether you can program in 27 million different languages, that information does not help with the issue at hand.
A normal person would have said I've got XYZ PC and after installing Linux I can't boot from the installation drive. Not I can't install to a USB drive and expect us to know you've tried to install to an internal SATA drive or whatever. We can't read minds, we can only work on the information provided. Surely you must understand this ?
Support is a 2 way street, you need to provide the correct and relevant information so you can be given a correct and relevant answer. So far this has not been the case, you mentioned something about running commands as the superuser but made no indication of what they were no the output.
This is not the World of Windows where you will be told to "update to the latest drivers".
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. Installation issues regarding any other OS other than the provided Linuxcnc image is beyond our scope of support, but generally we are a helpful community.
But before anything else I would run a live Linuxcnc session and do a latency as described in the docs. If this does not pass I would either reconsider the suitability of the PC in question.
Another to have a search for is for any issues in general regarding installing Linux on your model of PC.
As for Mint or Ubuntu or any other flavour of Linux their respective forums are the best place to get support with installation issues.

Also valid points timo. thank you

I am sorry that I was not more detailed about all the things I tried. But to be clear, I did try all the most obvious things first. I am new to Linux but have installed countless OS systems since the first computers came out. I have programed in over 5 languages, I am just new to Linux and I am amazed how much trouble I am having. The photos I uploaded should help identify the problem."Since you have not even mentioned the PC you are trying to install on" The my system photo should have the information about it. What info do you need that is not there? I am happy to provide what anyone may need to help me solve this problem.
"it appears the machine is attempting to connect to a boot server" I noticed that too, and I think it is related to the “UEFI: IPv4 Realtek PCIe FE family controllers” that keep coming back. I did not set up any IP connection info during the install attempts but did have a Ethernet connected for some installs for working with the "live" versions that did work. Using the sudo commands to get any bootloader\grub and other required files that may not have been in the install ISOs. I disconnected the ethernet connection during the last attempted install, But I will keep trying with other suggested ISO downloads with it disconnected.
"Linux is case sensitive as well, be sure to respect this" Thanks, I may have used some lower case letters that needed to be upper case on some script entries but mostly I copy and paste the exact scripts to be certain. I will get to trying the provided suggestions now and get back with the results. Thank you again for all the helpful suggestions.

Danke fürs Draufgucken, Jens!
Also die drei oberen Einträge kommen direkt aus dem Github mit der Probe Basic Installation, da hab ich auch nichts dran geändert. In der custom_connfig.yml stehen wohl Einstellungen für die GUI drin, aber alle relevanten stehen auf false, und da ist nichts zu sehen von feed-override. Eher Screen Angaben ob das grid gezeigt werden soll usw. Wenn ich die nicht lade geht auf dem Maschinen Bildschirm nichts.
DIe user_tabs und user_buttons hab ich mal nach feed* durchsucht, da gibts nur Einträge zum Feed Hold Button. Kein override, kein slider.
Es muss aber was Probe Basic Spezifisches sein, denn ich hatte vorher einige Zeit QTDragon installiert, da ging der Regler auch während einens Programmablaufs.

Pfeiltasten hab ich tatsächlich noch nie probiert! Würde ich auch nicht benutzen, ich hab das Handrad und die Buttons auf dem Touch Bildschirm das reicht mir. Aber gut zu wissen dass man das einschalten könnte.
- funktioniert wieder nicht - ja die Unerklärbarkeiten... ich hab da auch noch einige

Ich glaube ich wechsle mal mit dem Thema aus dem DE Bereich zum QTVCP/Probe Basic, da ist auch der Entwickler Chris unterwegs vielleicht kann der was dazu sagen. Sonst habe ich hier im DE Bereich eig. immer zielführende Antworten von den Mods und ganz Aktiven gehabt. Scheint ein seltsames Problem zu sein.
Danke Dir bis hierhin!
LG Hanno