1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • xaxexa
  • xaxexa's Avatar
10 Oct 2024 08:35
Replied by xaxexa on topic Remora - ethernet NVEM / EC300 / EC500 cnc board

Remora - ethernet NVEM / EC300 / EC500 cnc board

Category: Computers and Hardware

Should actually be the right firmware for the board. Flashing worked, ping worked, uploading the configuration worked. Only the connection board to RPI does not work yet. Guess I need another cable for the direct connection.

I didn't understand correctly, yes you have an NXP board, and this is the firmware that you need, and yes, that's right, if you connect the RP to the NVEM directly you need a crossover cable, or use router.
 
  • cnctrucker
  • cnctrucker's Avatar
10 Oct 2024 08:04
Replied by cnctrucker on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

ISSUE SOLVED NOW -- PROBING WORKS JUST AS IT SHOULD.
  • cnctrucker
  • cnctrucker's Avatar
10 Oct 2024 08:01
Replied by cnctrucker on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

Try changing the line below this in your hal file:
# ---JOINT ASSOCIATED WITH THE Z AXIS---

from:

[code]net plasmac:axis-position joint.2.pos-fb => plasmac.axis-z-position


to:
[code]net plasmac:axis-position joint.3.pos-fb => plasmac.axis-z-position
[/code][/code]
 


I couldn't wait -- I went out to the shop & made the change tonight.

Problem solved -- it ran the whole G-Code program just like it should (no plasma though).  I'll try the actual cut tomorrow, but I'm confident that the issue is solved now.

Again, many thanks!!!
  • Ritterchen
  • Ritterchen
10 Oct 2024 07:29
Replied by Ritterchen on topic Protocol to Error Message Output

Protocol to Error Message Output

Category: Advanced Configuration

I created a quick draft about how I imagine an error I-O component would work.
If anyone has feedback about the intended function I would love to hear and adjust if necessary.

It sounds a bit complex to write myself, so I am looking also for help. If anyone is up to the job I would like to hire someone for it.


General:
Currently there is no error management implemented in LinuxCNC. I would like to have a component that simplifies that and makes it easy to react on a number of error signals from modern drives.

Example of the general function:
A servo drives sends out the error integer "2" via Modbus = Current overload. The components reads this error message in error stream 4 (One device= One Stream). Integer 2 is available as an error and will be processed in the component and therefore there is an output pin: ES4.2 (this output pin can trigger a message of the GUI e.g. "Drive A current overload").
Furthermore this error under this error stream is connected to a reaction pin e.g. "machine stop"
The reaction pins can be shared for various errors all connected via or.

One input is the number of error streams e.g. 0-32
One input is the range of each error stream e.g. 0-1000
One input should mask the available errors e.g. 1,2,3,10,111 (from the range above 0-1000), these numbers will be available as output pins (of the same number)
One input should define the number of "reaction-outputs" e.g. 0-2 (machine stop, motion-inhibit, pause)
One input should assign the errors (1,2,3,10,111) a "reaction-output" e.g. 2,1,1,1,0

Would love to hear feedback on that or PM me if you are interested in the job.
  • Aciera
  • Aciera's Avatar
10 Oct 2024 07:16
Replied by Aciera on topic linuxcnc trajectory planner

linuxcnc trajectory planner

Category: General LinuxCNC Questions

Now i think a good strategy is to change a few tiny things to the current linuxcnc motion command flow:


sounds like a good starting point.
  • cnctrucker
  • cnctrucker's Avatar
10 Oct 2024 07:12
Replied by cnctrucker on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

My guess is it might be the lack of debouncing on critical inputs.

The dbounce components are loaded but the raw parallel port signals
are routed to Plasmac and the dbounce component inputs, but the signal
paths should be:

parallel port pin --> dbouncex.in --> dbouncex.out --> Plasmac

That is you have for example:

net plasmac:float-switch <= parport.0.pin-12-in-not
net plasmac:float-switch   => db_float.in

when it should be something like:

net raw-float-switch <= parport.0.pin-12-in-not
net raw-float-switch   => db_float.in
net plasmac:float-switch   => db_float.out

or the equivalent:

net raw-float-switch <= parport.0.pin-12-in-not => db_float.in
net plasmac:float-switch   => db_float.out

also the debounce times were not set (so would default to 5 servo-thread periods so 5 ms)
 


I'm using proximity switches, so there is no appreciable bounce.  With the exception of the line you pointed out, this is the same HAL code I have used in several iterations of this machine -- and I've never had a problem with a lack of debouncing before.
I'm sure that the wrong joint assignment is the problem -- I'll know in the morning for sure, but the previous iteration of the machine worked just fine before I added the THCAD-2 to the machine.
  • nartburg
  • nartburg
10 Oct 2024 07:03
Replied by nartburg on topic Mesa 7i96s --pktUART

Mesa 7i96s --pktUART

Category: Driver Boards

Ok--- reloaded 7i96sd_pktv2.bin unhooked everything except for power, ethernet, and the oszi.

Got what we expected !! a nice signal equivalent to what you got!!

wrote a .mod for the SKI780 VFD hooked it up and was able to control spindle direction and speed while reading the vfd's potentiometer.

Great Mission accomplished!

Big cheer for PCW!!

Then it stopped --
File Attachment:
  no contact no signal

back to trouble shooting.

 
  • cnctrucker
  • cnctrucker's Avatar
10 Oct 2024 06:58 - 10 Oct 2024 07:04
Replied by cnctrucker on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

Try changing the line below this in your hal file:
# ---JOINT ASSOCIATED WITH THE Z AXIS---

from:

[code]net plasmac:axis-position joint.2.pos-fb => plasmac.axis-z-position

to:
[code]net plasmac:axis-position joint.3.pos-fb => plasmac.axis-z-position
[/code][/code]



 

Ahhh... I never noticed that, but it makes sense.

When I created that machine config in StepConf, it did not insert a [JOINT_2] block in the [AXIS_Y] block -- I had to manually copy & paste the [JOINT_1] block to add a [JOINT_2] block. I didn't notice that it had linked the Z axis to [JOINT_2] over in the .HAL file.

I'll give that a try in the morning, but that's probably the problem.  Thanks a bunch!!
  • Aciera
  • Aciera's Avatar
10 Oct 2024 06:47
Replied by Aciera on topic linuxcnc trajectory planner

linuxcnc trajectory planner

Category: General LinuxCNC Questions

Disregard the above. I was not aware that I needed to go through the usual linuxcnc build process before running the cmake build:
You now need to run 'sudo make setuid' in order to run in place with access to hardware.
user@user-iMac:~/linuxcnc_trajectory_planner/src$ cd ..
user@user-iMac:~/linuxcnc_trajectory_planner$ cd cmake/build/
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$ make
Consolidate compiler generated dependencies of target motmod
[  5%] Linking C shared library motmod.so
[ 50%] Built target motmod
Consolidate compiler generated dependencies of target tpmod
[ 55%] Building C object planner/CMakeFiles/tpmod.dir/tpmod.c.o
[ 60%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/tc.c.o
[ 65%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/tcq.c.o
[ 70%] Building C object planner/CMakeFiles/tpmod.dir/tp.c.o
[ 75%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/spherical_arc.c.o
[ 80%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/tp/blendmath.c.o
[ 85%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/nml_intf/emcpose.c.o
[ 90%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/libnml/posemath/_posemath.c.o
[ 95%] Building C object planner/CMakeFiles/tpmod.dir/home/user/linuxcnc_trajectory_planner/src/libnml/posemath/sincos.c.o
[100%] Linking C shared library tpmod.so
[100%] Built target tpmod
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$
  • Aciera
  • Aciera's Avatar
10 Oct 2024 06:34
Replied by Aciera on topic linuxcnc trajectory planner

linuxcnc trajectory planner

Category: General LinuxCNC Questions

Does not seem to work for me (missing 'config.h'):
user@user-iMac:~$ cd linuxcnc_trajectory_planner/
user@user-iMac:~/linuxcnc_trajectory_planner$ cd cmake/
user@user-iMac:~/linuxcnc_trajectory_planner/cmake$ cd build/
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$ cmake ..
-- The CXX compiler identification is GNU 11.4.0
-- The C compiler identification is GNU 11.4.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/user/linuxcnc_trajectory_planner/cmake/build
user@user-iMac:~/linuxcnc_trajectory_planner/cmake/build$ make
Consolidate compiler generated dependencies of target motmod
[  5%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/kinematics/cubic.c.o
[ 10%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/axis.c.o
[ 15%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/motion.c.o
[ 20%] Building C object motion/CMakeFiles/motmod.dir/command.c.o
[ 25%] Building C object motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/control.c.o
/home/user/linuxcnc_trajectory_planner/src/emc/motion/control.c:31:10: fatal error: config.h: No such file or directory
   31 | #include "config.h"
      |          ^~~~~~~~~~
compilation terminated.
make[2]: *** [motion/CMakeFiles/motmod.dir/build.make:132: motion/CMakeFiles/motmod.dir/home/user/linuxcnc_trajectory_planner/src/emc/motion/control.c.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:116: motion/CMakeFiles/motmod.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
  • meister
  • meister
10 Oct 2024 06:08
Replied by meister on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)

Category: Computers and Hardware

fixed, but this error comes only if you do not add .json suffix to your filename.

Thanks for reporting !
  • OttoDidact
  • OttoDidact's Avatar
10 Oct 2024 06:04
Replied by OttoDidact on topic My Cable Robot CNC Foam Cutter is running!

My Cable Robot CNC Foam Cutter is running!

Category: Show Your Stuff

Very cool.
  • Aciera
  • Aciera's Avatar
10 Oct 2024 04:27
Replied by Aciera on topic Slider (scale) to change stepper acceleration

Slider (scale) to change stepper acceleration

Category: pyVCP

INI hal pin values can be changed in gcode during execution but require a queuebuster command (eg M66 E0 L0) to be updated.
  • phillc54
  • phillc54's Avatar
10 Oct 2024 04:09 - 10 Oct 2024 04:10
Replied by phillc54 on topic -- SOLVED -- Inconsistent Probe Performance...

-- SOLVED -- Inconsistent Probe Performance...

Category: Plasma & Laser

Try changing the line below this in your hal file:
# ---JOINT ASSOCIATED WITH THE Z AXIS---

from:
net plasmac:axis-position joint.2.pos-fb => plasmac.axis-z-position


to:
net plasmac:axis-position joint.3.pos-fb => plasmac.axis-z-position
  • dreBird
  • dreBird
10 Oct 2024 04:07
Replied by dreBird on topic Joint homing offset and following error - HELP

Joint homing offset and following error - HELP

Category: General LinuxCNC Questions

OK thank you everyone! I ran a live session with the Linux installation disk and changed the thread period back to 1000000 (it was saved at 10000). I then tried 700000 and I got a weird A axis burn out, where the axis rotated very quickly and erratically during the homing sequence. So its back at 1000000.

I ran the latency test and didn't see much difference in Max Jitter (ns), around 20100 at each thread rate tested above. (I could not run LCNC and the latency test at the same time due to conflict with the real time processor).

Mesa 5i25 is connected to the 7i77
Displaying 22066 - 22080 out of 23341 results.
  1. Forum
  3. Search
Time to create page: 0.932 seconds
Powered by Kunena Forum