Advanced Search

Hi, everyone. In the LinuxCNC source code, there should be a directive like IniFile->Find(, “SERVO_PERIOD”, ) to initialize SERVO_PERIOD, but why can't I find it? Also, I found in the motion.c file that SERVO_PERIOD_SEC is given by the system and this value does not change based on the ini file.

Maybe have a look at the simulation configurations using limit3 in the folder 'configs/sim/axis/extrajoints'

cncwhacko wrote:

I connected stlink to my nvmpg to get a dump of the running firmware, it would be interesting to get a copy from someone that has a working to see if there's major difference? Scott, would you be able to take my .bin from my nvmpg and see if it differed from yours? I dont have the skills to reverse engineer things like you did up front but happy to poke about and learn more!

Great, yes please send me your bin file from the NVPMG and I can compare to the one from mine that was use to reverse engineer the payload. It will be interesting to see if they have made some changes.

disneysw wrote:

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

The default config within the firmware has only three step generators configured. You will need to upload a config, but strange you are getting timeouts..

Hi all!

I've tried installing linuxcnc to an N100 mini-pc (Alder Lake N100, 16GB RAM, 512GB ROM).
      mfg specs : S1 vertical mini pc with 12th generation Intel Alder Lake-N100 processor (up to 3.4GHz, 6MB L3 cache), 20W TDP.
Connected to a MESA 7i96s card with new tested 30cm long CAT6 FTP/S cable. (and also tried unshielded during troubleshooting)

All was easy with the install- the latest linuxcnc debian amd64 iso was used, setup with pnfconf, and the newly installed linuxcnc OS runs (albeit with some timing/latency warnings).

Tried the HAL monitor, but couldn't see responses to any limit or estop button press. (Electrically the voltage swing is 24v to 0v, and the MESA board LEDs blink from bright-on to fully-off as each button is pressed - confident not a wiring issue). 

So next I installed MESACT.Tried the PC/Servo Thread Test, and maybe a clue....

the "Get CPU Speed" button returns only 792 MHz.

Whereas the N100 should be running much faster. In BIOS I believe I had set "Max turbo mode". (images attached).

At this stage I am thinking of three routes to investigate...
1. Is a BIOS setting preventing the mini-PC from reporting it's correct speed to linuxcnc ?
2. Is a missing driver in linuxcnc preventing the OS "seeing" the correct cpu speed ?
3. Something else...

I've attached a complete set of photos of the mesact test, the actual PC and all of the BIOS windows.

I have the C- States set disabled (as in photo IMG_529), but also took a photo of that setting enabled (IMG_0517) just to show the sub-options available.

To prove the cnc machine hardware, I've repeated the install on an old pentium PC, connected to the same MESA card and CNC machine, and can successfully read the CPU speed, get an acceptable latency result, HAL monitor detects all switches correctly, and the machine jogs, homes and runs a small test peck drill task correctly.

So the mini-PC is the issue it seems. I'm hoping a setting or missing driver as all that needed for such things?

Would anyone have experience with running linuxcnc on an N100?  - does it even work for anyone?
    - (according to numerous threads here that I've collected advice from, seems it should!)

Figure I'm missing something obvious!

All photos: drive.google.com/drive/folders/1YG3q0ehZ...ZtYmPWzBao1RR8ckq3ZM 

Could you post your user command file and I will try to come up with something tomorrow afternoon. 

At the beginning all of them were set to 2A current to match steppers. Then I set Y axis driver to 2.5A and that's what you can see on the video.Regarding microstepping I've set it up to 8. 

Working on understanding the exact mesaflash/pncconf steps for setting up the firmware/linuxcnc associations for the
7i92T right now...

I got a copy of the "7i92t_7i85sx2d" zip file from mesanet on hand

Also, already went into pncconf to get an idea how THAT interface is handling this setup. It appears the discovery option
does identify the 7i92T (so that should mean the TRION fpga 7i92 is properly handled?), but once I get to the 7i85S an
"unsupported device" error is generated. Perhaps some sort of ini help file or other redirection method would be the solution
at this step. Maybe a one card at a time approach is also part of the method, still figuring out the specifics for this.

Considering the firmware may be handled at this stage, I am cautious of editing anything yet, but I suspect this shouldn't
be too difficult to accomplish, its just a matter of identifying what exactly needs modification and where...

Didn't even realize this was coming. Only bummer on the base model is the omission of the 2nd ethernet port. Could do without the rest of the stuff for a machine build, but it might still be worthwhile to use the H4 base and attach a Netcard and have 5 ethernet ports

I'm guessing they use an Intel NIC on the H4 because they redesigned the Netcard to use Intel NICs and Hardkernel generally likes to source the same components for multiple devices. FYI the NetCard is a 4port ethernet card that plugs into the M.2 slot and a BIOS flash changes it from NVME x4 PCIE to 4 straight x1 PCIE. There's no PCIE bridge or anything like that so each Netcard NIC should have no more latency than an onboard NIC

Hello,

Using Terminal when staring linuxCNC I can read logs. I have solved some INI errors (missing parameters). LCNC  works properly but I still have some errors that I don't know how to solve.

System info :

Im in contact with Delta support. The main issue is missing Digital output PDO 60FEh.
I also described issue with sii changes wanishing after reboot and the reply was:

Which data do you need to write? I'm asking because you can't write all EEPROM in B3 servo drives, only the essential ODs. The design of the servo drive does not allow you to have the same data after rebooting, except for the write-allowed ones. So, you may see it like that. 

I'm afraid I may have given you an uncompatiple file. I based it on my 2.9 branch witch has other changes.
If it gives unrelated errors then bill have to find thecdoec8fic 2.9.2 version and fix it.

Not enough sleep makes mistakes!

Hello Chris,

Thank you for the Info.
Of course, I’m happy to test that. However, it will take another day since I’m not at home this weekend. I’ll provide you with feedback as soon as I’ve tried it.

Klaus

fsabbatini wrote:

Hi! Just to show the thing I am working on 
 

Nice panel Franco!

Using Ethercat to connect like you showed on previous panels?

How're the $iemens-ish GUI and LCNC modifications coming along?

This worked half way. I added a USER_COMMAND_FILE = qtplasmac_custom_post.py with the python code to set the range:

self.w.safe_height.setRange(0.125, int(self.maxHeight))

I can start QtPlasmaC and interactively set and save a Safe Height value as low as 0.125". However, if I save any value less that 0.75", when I reload QtPlasmaC the value is reset to 2" (my maxHeight).

I think this is happening because the load_plasma_parameters method that loads the value from the prefs file into memory (github.com/LinuxCNC/linuxcnc/blob/56e137...py#L2901C16-L2901C27) happens after set_spinbox_parameters which sets the defaults but before the USER_COMMAND_FILE (I'm not yet sure how that file gets invoked with QtPlasmaC to be honest).

This leaves me at a bit of a loss as to how to customize this. I could just write a sed script to change the python code for now, but that seems like a bit of a hack. Anyone have other thoughts as to how this might be achieved?

Thanks!

Scott