Advanced Search

If the keyboard is not working, its a Linux (or hardware) issue. The Linuxcnc ISO does not install any sticlky keys app but it might be a default Debian thing.
Its nothing to do with linuxCNC, trying to reinstall may resolve things.

Does it show up in Linux with lsusb?

I have read the full thread, wiki and looked at git hub and there are a number of things I am still confused about due to conflicting information.

I am using a standard LinuxCNC distro on an i5 PC. I have erased and programmed an NVEM V5 board (RT1052) using pyocd and the remora-rt1052-NVEM-0.2.1.bin and the board responds to pings at 10.10.10.10.

I cannot upload a config to the remora board due to time outs, but I understand this is to be expected as the firmware has a full config built-in - is this correct or is this the root cause of my issues?

The board outputs the following via the debug port on boot:

        Initializing PHY...

         ## Entering SETUP state


         ## Entering START state

          Starting the threads

         ## Entering IDLE state

I have installed the remora components (remora-eth, remora-nv, remora-nvmpg) into LinuxCNC and I copied various remora configs to my config directory.

Satrting LinuxCNC and using the remova-nv config I can get the x & y steppers to sort of move but I cannot see any inputs change state (I have tried all of them). In the HAL viewer I can see the Remora status as OK and both the servo-thread.time /remora.update-frq.time are updating.

Ultimately I want to set this up for a lathe with x,y and spindle control but for now it is sitting on my desk with two steppers and some switches wired up to the inputs.


So my questions are:

1: have I flashed the correct firmware?
2: do I need to upload a config file to the NVEM - if so why would I get a timeout (this is mentioned by someone else in an earlier post)?
3: If the above is OK why can I not see any input changes?
4: Do anyone have a Lathe config as a starting point?

Thanks in advance

This is a regular sized desktop PC with internal power supply.

This is a knee mill and everything is grounded properly.

Resurrection of the keyboard after rebooting the PC makes me suspect something on the software side but who knows?

Moving the keyboard to another USB port while it's non functional does not help, so it seems unlikely to be hardware,

Is Stickykeys part of the 2.92 ISO? I can't recall installing this but I might have and I want to rule it out as a possible problem, I do get intermittent pop up messages about sticky keys.

Is there some sort of LinuxCNC diagnostic that I can run or examine when the keyboard stops working? Obviously I would have to access it via mouse clicks.

Ok.
let me try.

It was the latest ISO of 2.9.2..

I believe I'm not microstepping, though you make me doubt and maybe I confused the ON and OFF position on the driver because I have no vibration or rougness, I will have to verify. Either way, I have either no microstep at all, or 6400 microsteps (both position where all the pins are aligned, all ON or all OFF).

If I do the same calculation with 6400 microsteps :
-10 turns of the motors gives 64 000 microsteps.
-10 turns of the motor makes one turn of the pignon, which got a perimeter of 100.531 mm

So 64 000/100.531 = 636.62step/mm

I've tried to empirically find the STEP_SCALE which would give me a 600mm/min advance (the new setting I have set for "default linear velocity) and it's around 2348...

The thing is I can't really be sure of what I'm doing. I need confirmation than when you jog the machine manually, it moves at the "default linear velocity" I have set up during the configuration. From this point it will be easier to understand what's wrong.

Ja unter win 11 wird er erkannt

Hello,My setup for a re-retrofit (from Mach3 to LinuxCNC) of an old EMCO Compact 5 CNC lathe is as follows:

• RPI 5 with Linuxcnc 2.9.2 on Debian bookworm
• Mesa 7i96s
• 2x 200W AC servos with A5 drives from Lichuan, for X and Z. Encoders are 17bit incremental type (why on earth did I not get the absolute ones when they were like 20 dollars more....)
• 1x 1000W AC servo with A5 drive from Lichuan, for spindle. Same encoder as for the 200W motors.
  
  As far as I've understood, normal lathe use would indicate that i run the axis drives in position mode with step/dir inputs, and the spindle drive in speed mode, with -10- 10V analog input.
  
  I believe that is what will be relevant info for the questions in this thread?  
  
  1. In the axis section of the pncconf wizard I am faced with some settings I have never encountered before, namely "step-on time", "space", "direction hold" and "direction setup". I have tried to read up on what they mean and how it relates to the information I am given in the servo drive manual. Among the numerous settings and points of information for the servo drives, I cannot find anything which is called the same or remotely the same as those parameters. Can I assume that my step high/low and pulse high/low times are identical, and that I can simply use the drives' maximum step frequency as a base for step-on time and space? It is stated as 1MHz in the manual. What about direction hold and direction setup, could someone please explain what they are? I am anxious of doing something bad to my new precious drivers and motors, so in case any wrong settings can hurt my drives, i just want to be on the safe side...
  2. Is there anything else I need to pay special attention to when using AC servos with step/dir inputs, instead of stepper motors? I see there are some unseleactable/uneditable tuning parameters (PID info) on the left; I thought I would be tuning the servos internally on the drives?
     
     Link to servo motor with drive (200W version): 
     www.aliexpress.com/item/1005005440028771...ain.5.76c81802WfkwiM
     
     
     
      
     
     
     
     

@cornholio not a single one here that had to mess with their ubootloader.
To build a rt kernel is also pretty easy or just download and install. Mainline Linux support is getting there too, it's already usable.

@vre There isn't a SPI driver like on the Raspberry Pi indeed but a /dev/spidev like cornholio said. If I can test the speed with a microcontroller or something I'd like to test it.
@cornholio Is there a reason that this can't work fast enough or just a guess?

Mesa over Ethernet might be the most safe option. An Opi5-plus has dual Ethernet too.

Beyond that you have to manually copy/paste and modify the hal and ini files.

Not sure any configuration utility currently  works fully for the 7I97/7I97T

The 7i97t_7i85d firmware does support all 7I97T on card and 7I85 features,
but you would likely have to start with a sample 7I97T configuration and add
the additional I/O for the 7I70 and 7I71.

Edit: Have you tried pncconfs discovery feature? I think it will fail at
discovering the 7I97T local inputs but should work at setting up the
7I70 and 7I71 I/O, possibly creating a donor file to cut/paste bits
into the basic 7I97 sample file.
 

I am sorry for all the trouble - there is another bug.
I think I have it fixed - maybe you could test for me.

Put this file in YOUR_CONFIGURATION_FOLDER/qtvcp/screen/qtdragon_hd/
name the file qtdragon_hd_handler.py

If there is a problem your can remove the file and qtdragon_hd will load the default screen again.

Please stick with it - we will get this working.

Chris

Has anyone tried odroid h4/h4+ ?
www.hardkernel.com/shop/odroid-h4
www.hardkernel.com/shop/odroid-h4-plus

latency-histogram ?
 

This seems very good for use with mesa ethernet card + extra ethernet for internet
www.hardkernel.com/shop/odroid-h4-plus/