Advanced Search

Hallo zusammen, könnt ihr mir bei folgendem Problem helfen?

Board: NVEM V5 (i.MX RT1052)
Getestete Firmware-Versionen: remora-rt1052-NVEM-0.2.1.bin, remora-rt1052-0.0.1.bin, remora-rt1052.bin — alle zeigen identisches Verhalten
Ping auf 10.10.10.10 funktioniert einwandfrei
upload_config.py sendet korrekt eine WRQ-Anfrage auf Port 69 (bestätigt per tcpdump), erhält aber nie eine Antwort vom Board
Keine Firewall aktiv (iptables ACCEPT), direkte Verbindung ohne Router

Gibt es eine spezielle Prozedur, um den TFTP-Config-Upload auf diesem Board zu aktivieren (Pin kurzschließen, erst einen Befehl senden, o. ä.)?

Vielen Dank schon mal im Voraus!

Hello everyone, could you please help me with the following problem?

Board: NVEM V5 (i.MX RT1052)
Tested firmware versions: remora-rt1052-NVEM-0.2.1.bin, remora-rt1052-0.0.1.bin, remora-rt1052.bin — all show identical behaviour
Ping to 10.10.10.10 works fine
upload_config.py sends a WRQ request on port 69 correctly (confirmed via tcpdump), but never receives a response from the board
No firewall active (iptables ACCEPT), direct connection without a router

Is there a special procedure needed to enable TFTP config upload on this board (short a pin, send a command first, etc.)?

Thanks a lot in advance!

Feed per revolution too high ?

Hi!
Nice to see NativeCAM alive again.
I have a new clean installed Trixie and NativeCAM 2.0b all looks fine but i get a error
Negative F-WORD at Line near 101
Does anyone have any ideas?

 

Tks for the info But I stick to GIVE THE USER THE CHOICE right off the bat....! an force me to "DIG" for that info to have to disable. at a later date

I under stand with the internet the way it is.? "BUT" give me the "choice"

I understand this will never HAPPEN but had to get my 2 cents worth in.!

the old timer

It is possible to set up a linux system with no passwords, but it isn't completely simple or recommended (especially on systems with any internet exposure.)

First you can do away with a root password, by leaving that blank when installing. The user password is required while installing, but you can configure Linux to boot directly to the user interface by enabling automatic login, and the system will start without needing to input a password.

If you configured the system without a root password, the installer will have given sudo privileges to the user, and will promp for a password when a sudo command is input at the terminal.

With automatic login and sudo privileges for the user, you would only need to enter your password to perform administrative tasks that probably should be password protected. Otherwise you shouldn't normally need to user your password.

There are ways to even remove the requirement for a password for sudo tasks, but I've never tried and would have to google instructions how to do it. (not to mention that it's generally probably not a good idea.)

I installed linuxcnc 2.9.4
and problem solved,
lol

Sorry about Pxxx/Moning about passwords I am leaving M.S. because of how they handle the passwords. I have been building boxes since Aug of 1977 (Almost 50 years) and over 100 boxes's
why cant they just have a check box do you need a password yes / no and leave it at that
1 frustrated old man
Ken (5280)

Thank you for the reply (link to the Debian 13 install link after building a USB boot install flash drive and doing the install on the (older Dell laptop 8 gig memory)thee install goes fine till the password section which i have tried any number of password from 4 letters to 20 letters / numbers .? nothing get me past the enter login on the reboot . Every thing looks fine on the setup "but" ? I guess I am not to have this I have never understand why since I am the only person "WHY " I need a password" and the only person who will use this people have gotten crazy with the requiring passwords

Thanks for the help

Thanks to everyone for their comments. The overall take away from this is that you want a solution with minimal hassle, go with Mesa and pay accordingly.

Let me ask a related, more targetted question: what is the most solid Remora implementation both in terms of solid operation once configured *and* using HW that is solid and has a reasonable support expectancy. Novusun (sounds iffy), esp32 based? RP2040 (sounds experimental), some kind of 3D printer driver board? Other?

forum.linuxcnc.org/18-computer/38838-har...ency-tests-used-pc-s

forum.linuxcnc.org/18-computer/39371-res...ith-linuxcnc?start=0

Ok, I got this searching the forums and internet. So would be needed to test it to see eventually how that latency would be affecting it. Another question is if there is an better suitable industrial PC to buy ?

I mean do you have any recommendations on what motherboard and chipset is preferable for use with LinuxCNC ? I understand that this would be any motherboard
that Debian or linux kernel supports, but is there a some preferred hardware list or suggestions for a good LinuxCNC industrial PC ?

Tommy thanks. So Yaskawa would be preferred correct ? What kind of latency issues are there with EtherCAT ? Is it on the LinuxCNC side or due to network ?

1) yes

2) If you have a simple switch probe you simply connect a wire from the input on your board to one side of the probe, and run the other wire to the ground on that board. There are some basic instructions here for the Hal programming.
wiki.linuxcnc.org/cgi-bin/wiki.pl?Touch_Probe

There is not any real programming needed in Linuxcnc, it is ready to go once the Hal lines for the probe are added to your configuration. You might want to make some G-code probing routines to automate your probing process.

3) Most any probe will work. If you have access to a 3d printer you can even make your own probe like this one.
www.thingiverse.com/thing:4672365
Obviously the better the probe quality, the better your results can be.

Depends on budget, good ones are from Yaskawa and Delta, all the way down to cheap china ones that do work, but getting there might be very hard as usually they are not tested or tuned to the motor you get.
I am still skipping EtherCAT due to feedback latency issues.