Remora - ethernet NVEM / EC300 / EC500 cnc board

Some great news to share. Configuring the NVEM with a custom config file is now possible! I have updated the firmware and the example configuration.

github.com/scottalford75/Remora-NVEM/tre...json_config/Firmware
github.com/scottalford75/Remora/tree/fea...gSamples/remora-nvem

The config.txt file in the config sample enables all features on the board including the NVMPG. To customise, simply remove the unused step generators, IO, spindle or NVMPG as required. You can also change the IO mapping and naming just like the SPI version of Remora.

I've done limited testing but it all seams to be working ok.

To upload a new config file to the board use the python script from within the config directory. The config file can be a text file called anything.

pi@remora:~/linuxcnc/configs/remora-nvem $ python3 upload_config.py config.txt

The file will only be uploaded if it is a correctly formatted JSON file, the NVEM board will check the CRC-32 and if ok will move the uploaded config file into the storage location and reboot the board by forcing a watch dog timeout.

pi @ remora: ~ / linuxcnc / configs / remora-nvem $ python3 upload_config.py config.txt
The file or directory does not exist
which means : The file will only be uploaded if it is a correctly formatted JSON file ?
bash: /: is a directory

@scotta Here is my config. Probably not ideal, however it does work fine with the lpt port.

btw I think the link in your post should be [url] github.com/scottalford75/Remora-NVEM/tre...json_config/Firmware [/url]

Domi wrote:

pi @ remora: ~ / linuxcnc / configs / remora-nvem $ python3 upload_config.py config.txt
The file or directory does not exist
which means : The file will only be uploaded if it is a correctly formatted JSON file ?
bash: /: is a directory
 

Open Terminal [/code][/code] [/code][/code] [/code][/code]

Uploading doesn't work I'm getting time-outs and now after a single movement I'm getting a following error:

Valid JSON config file, uploading to NVEM board
Config file length (words) = 1652
Config file length (bytes) = 6607
Remainder = 3
Padding added =  [0]
Config file length with padding (bytes) = 6608
CRC-32 = 0xc1997785
Timeout waiting for traffic, retrying...
Timed-out waiting for traffic
resending last packet
Resending packet WRQ packet: filename = config mode = octet on sessions <tftpy.TftpStates.TftpStateSentWRQ object at 0x7f931391c6a0>
Timeout waiting for traffic, retrying...
Timed-out waiting for traffic
resending last packet
Resending packet WRQ packet: filename = config mode = octet on sessions <tftpy.TftpStates.TftpStateSentWRQ object at 0x7f931391c6a0>
Timeout waiting for traffic, retrying...
Timed-out waiting for traffic
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/tftpy/TftpContexts.py", line 171, in cycle
    (buffer, (raddress, rport)) = self.sock.recvfrom(MAX_BLKSIZE)
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "upload_config.py", line 72, in <module>
    client.upload("config", "/tmp/config.txt", timeout=60)
  File "/usr/local/lib/python3.7/dist-packages/tftpy/TftpClient.py", line 101, in upload
    self.context.start()
  File "/usr/local/lib/python3.7/dist-packages/tftpy/TftpContexts.py", line 325, in start
    self.cycle()
  File "/usr/local/lib/python3.7/dist-packages/tftpy/TftpContexts.py", line 174, in cycle
    raise TftpTimeout("Timed-out waiting for traffic")
tftpy.TftpShared.TftpTimeout: Timed-out waiting for traffic

 

I downloaded it in windows. He then put it in Linuxcnc and then edited config.txt
python3: cannot open file 'upload_config.py': [Errno 2] No such file or directory