Advanced Search

netmask is set to 10.10.10.2/24. Any alternative netmask? 

The only thing that I see is  different is the netmask

you might try

address 10.10.10.2/24

Also ipv6 has been enabled, which is really odd

Hmm I tried both, changed priorities eno1 to 1 and auto/enp2 to 0 - no effect.
Then I changed the position of the lines in /etc/network/interfaces - no effect at all.

On what reason ever, the network definitions are faulty.

WTF is going on there?

And this is ip a with the 4 lines in /etc/network/

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 863931sec preferred_lft 863931sec
inet6 2003:ce:5f08:8600:6ae7:3d2d:fe1d:c940/64 scope global dynamic noprefixroute
valid_lft 7132sec preferred_lft 1118sec
inet6 fe80::d017:c5ae:2734:c531/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/8 brd 10.255.255.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::223:24ff:fe5b:b4ac/64 scope link
valid_lft forever preferred_lft forever

why does it change the altname to enp0s25? that is a conflict with 2. where can I change the altname manually to fix this?
Or should I change the priorities so that eno1 is launched before enp2?

This is the feedback of ip a without the suggested lines:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:0a:cd:00:00:56 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.55/24 brd 192.168.178.255 scope global dynamic noprefixroute enp2s0
valid_lft 862758sec preferred_lft 862758sec
inet6 2003:ce:5f08:8600:6ae7:3d2d:fe1d:c940/64 scope global dynamic noprefixroute
valid_lft 7101sec preferred_lft 1700sec
inet6 fe80::d017:c5ae:2734:c531/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:23:24:5b:b4:ac brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
 

I tested it a bit, it works very well.
I like it.
It could be everything even in one menu, axis button, but if it is possible to customize the content of both menus, it is very good.
How to do it in the style sheet?
In qtdragon_hd, the ref buttons are probably no longer needed? If so, I can customize the layout..

Marek

Hello PCW,
thank you for your answers! (sorry for delay, I was very busy the last days and couldn't do anything at my machine.)

I tried the lines in /etc/network/interfaces file and  after reboot my internal Intel network was disabled. Just  auto internet with RLT8111 is possible. The file is as follows:
 

Well, internet network is ok. What is the faulty setting here?
 

I do recommend not to use halui pins, but the hardware button pins to control that stuff.

See:

Right and Botton Button Hal Pin

Can't you use the gmoccapy Jog hal pin?

• gmoccapy.jog.jog-A-plus (bit IN)
• gmoccapy.jog.jog-A-minus (bit IN)
  
  Norbert

I'm kind of stuck I think there are some mistakes in my hal and ini setup.
I wonder if it would make sense to start new but its a relative complex machine an I've also done a lot to the GUI.
I attached my config files maybe some one sees what I can't see at the moment.
If not I'll restart new new

 


these two files are for gui and hand wheel

   


thanks Patrick
 

You may have the wrong forum. This forum deals with the use & installation of Linuxcnc.

I use 4 PICOs RP2040, a total of 16 ADC channels (4 ADC channels
per PICO) where the trigger signal (reference voltage) is connected to GP14. I’ve programmed the Picomite to set a trigger value for a falling edge, which means the trigger should activate when the signal reaches 0.8 V. However, I’m encountering an issue where the output voltages I’m getting are higher than expected—they should be lower or close to 0.8 V. The trigger signal frequency is set at 360 Hz, and the input voltage is a 1.2 V AC sine wave at the same frequency. Currently, the output voltages from all ADC channels are between 0.85 and 0.87 V. When I increase the frequency to 400 Hz, 450 Hz, or 500 Hz, the output voltages rise even higher, which is confusing. Could you please help me identify where I might be making a mistake?
I aim to capture the input signal precisely at the point where it crosses the trigger voltage of 0.8 V on a falling edge. To achieve this, I set the offset to zero (minimum). I connected an oscilloscope in DC coupling mode on the input side to monitor the amplitude and frequency of the input voltage. Since the trigger is set for the falling edge, which means the system should capture the signal as it transitions from rising to falling and reaches the trigger level, I expect the captured voltage to be less than 0.8 V.
Kind regardsHasham

Yuhp I found it -_- Sorry guys

Thanks mate I am an stupid

Thanks Ill have a look. hopefully this is the case I have a habit of not finding things right in front of me

Hi Scott
Thanks!
I'm stupid,
it was the classic solution that you have in front of your eyes and you don't see.

The output must be enabled, of course, and the scale must also be set, of course,
but I didn't think of it, even though I had done the same thing for the FR4000
I'm speechless....

Everything works, I'd say the driver is ok

Thanks again for your time!