Advanced Search

Hi, I saw your post about the SL2-100 interpreter — I'm an FPGA engineer working on decoding the same protocol and finding solid documentation is really tough. Would you mind sharing how far you got, or any pointers on the frame structure / encoding you figured out? Totally understand if it's not shareable. Wishing you smooth progress on the project either way!

Just re-read this topic ... twice, i am confused on many levels...
If you want just to test use the live version, do not install it.
And that never asks you for a "password" ... that is a thing since the inception of personal computers.

Okay, sorry

F-WORD = F = feed rate, it can not have a negative value as far as i know, although there might have been talks about that for EDM probably, but i do not recall the end result.

@CNC_Manni
This is the third post with the same subject, although one is in German, abd this one has more info, so do not do multiple posts, that makes a mess for us and for whoever tries to help you.

This is a duplicate of this topic but in German language.
forum.linuxcnc.org/42-deutsch/59075-nvem-v5-rt1052#348502

PCW wrote:

Here is 5I25/6I25 firmware for a 7I76U with the PKTUART

 

File Attachment:

File Name: 5i25_7i76x1pktd.zip
File Size:124 KB

I can try to help more later, but note there is another user trying to get a Omron MX2
working with a Mesa card and having issues. I suspect I may have to acquire a MX2
to try and get this going.

The 7I76U manual has the RS-485 wiring information (and you must use RS-485 mode with the 7I76U
so you lose on estep/dir output)

 

Sorry that was the wrong firmware for a 5I25/6I25  --> 7I76U using RS-485 mode
The correct firmware is this:


 


 

7I92 and 7I92T firmware for 7I76U with PKTUART/RS-485:

   

Ok I reinstall the debian system iso file and it still will not let me past the login screen I tried the blank password name and password but still it will not let me past the login screen with or with out the login.

now at a stand still.?

Ken

BigDo wrote:

Negative F-WORD at Line near 101
Does anyone have any ideas?
 

This is conflict with lathemacro.

Perfect. I always thought I had to cascade them, which seems to multiply the tuning time and effort.
@cmorley I printed that and am hanging it on my wall for future reference 

Hi,

Thanks for sharing your experience - I'm running into a very similar issue and hoping you might have found a solution since posting this.

I'm using an NVEM V5 board (RT1052 chip). I successfully flashed the firmware via pyOCD (tried multiple firmware versions: remora-rt1052-NVEM-0.2.1.bin, remora-rt1052-0.0.1.bin, remora-rt1052.bin - all flashed without errors). Ping to 10.10.10.10 works perfectly and consistently.

However, unlike your case, I'm getting a timeout on my very first config upload attempt - not after a successful first upload. I've tried:
- My own custom config file
- The unmodified official example configs (both nvem-rt1052.txt and remora-rt1052-basic/ec500-rt1052.txt)
- Uploading with the SWD/ST-Link connection both attached and disconnected during the upload
- Confirmed via tcpdump that the WRQ packet is sent correctly on port 69, but no response ever comes back from the board
- No firewall involved (iptables set to ACCEPT), direct point-to-point Ethernet connection, no router

The script always confirms "Valid JSON config file" and calculates the CRC correctly, so it gets stuck at exactly the same point you describe - after everything on the PC side looks fine.

Did you ever find out what caused the board to stop responding to TFTP? Was it possibly related to the eStop/enable state getting stuck, as you mentioned the LED stayed permanently lit? Any insight into how you (or anyone else) resolved this would be hugely appreciated - trying to avoid unnecessary re-flashing if there's a known cause.

Thanks in advance!

Feed 75,00
i used this settings long before.

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!