Advanced Search

No I dont use them.
But some time ago I add to my config probe screen and now found in psng.hal this...

# Ensure all toolchange pins are free to use
unlinkp iocontrol.0.tool-number
unlinkp iocontrol.0.tool-prep-number
unlinkp iocontrol.0.tool-change
unlinkp iocontrol.0.tool-changed
unlinkp iocontrol.0.tool-prepare
unlinkp iocontrol.0.tool-prepared

net tool-change            probe.toolchange-change      <=   iocontrol.0.tool-change
net tool-changed           probe.toolchange-changed     =>   iocontrol.0.tool-changed
net tool-number            probe.toolchange-number      <=   iocontrol.0.tool-number
net tool-prep-number       probe.toolchange-prep-number <=   iocontrol.0.tool-prep-number
net tool-prep-loopback     iocontrol.0.tool-prepare     <=   iocontrol.0.tool-prepared

But still after change the tool popup screen to confirm like in manual change...
Any help with popup screen??

are you maybe still using the manualtoolchange component?

What is the Z motion range for 0 to 10V out from your sensor?

Response:
ranger 10364.831 hm2_7i96s.00.enconder.00.velocity
ranger 621866.8 hm2_7i96s.00.velocity-rpm
I am testing with jump 64 on the THCAD2 board.

Simulations with other jumpers:

advanced hydraulic cylinder THCAD2 jump128

1416.431 hm2_7i96s.00.enconder.00.velocity
84985.84 hm2_7i96s.00.velocity-rpm

 

recessed hydraulic cylinder THCAD2 jump128

6616.257 hm2_7i96s.00.enconder.00.velocity
396875.4 hm2_7i96s.00.velocity-rpm

 

advanced hydraulic cylinder THCAD2 jump64

2868.069 hm2_7i96s.00.enconder.00.velocity
172084.1 hm2_7i96s.00.velocity-rpm

 

recessed hydraulic cylinder THCAD2 jump64

13232.51 hm2_7i96s.00.enconder.00.velocity
793950.9 hm2_7i96s.00.velocity-rpm

 

advanced hydraulic cylinder THCAD2 jump32

5671.078 hm2_7i96s.00.enconder.00.velocity
340264.7 hm2_7i96s.00.velocity-rpm

 

recessed hydraulic cylinder THCAD2 jump32

26449.64 hm2_7i96s.00.enconder.00.velocity
1586979 hm2_7i96s.00.velocity-rpm

 

I put the value 800 in the scale encoder, but it continues to display a calculation error message on the axis, but the axis moves a little, below is the video showing the result



Regarding another question, sorry for my lack of knowledge, do you have any example of how to: feed the encoder velocity signal through LinuxCNCs
offset component to remove the offset at 0V ?





















 

Thanks a lot for your two links and the tip with the StepConf. After changing the coordinate system to the near left side, I only had to invert one axis in the StepConf. Now everything works fine

Hm, interesting. It might be worth considering an issue that usually only pops up once the machine is finished which is: How are you going to create gcode for this?

Hello everyone, I'm very new to everything Linux related but frustrations with my current machinery has led me down a rabbit hole. Here we are.

I saw people asking for feedback on running the 2.9.2 package on a raspberry pi. I have a Raspberry Pi 4B 8G model that I have attempted to boot the 2.9.2 image to with very little success. I used the XZ file on the downloads page and put it into the Raspberry Pi imager, the board was booted with a small touchscreen plugged into it's display port via ribbon cable. ACT/power lights appeared promising until I got a peculiar message showing up on screen with some skulls. I have attached it here.  

After the skull message, power light turns off and the ACT light switches to a faint, consistent flicker while the display continues rotating through solid colors. 

It's entirely possible that since this is the second time ever using one of these that I have royally screwed up somewhere. I have also read some negative reviews as far as the compatibility of the 8G model goes so it could have something to do with that. Any and all info you guys could provide would be greatly appreciated. Thank you!

[Edit], the XZ file taken off the homepage for version 2.9.2 failed to flash using BalenaEtcher 

The solution was so easy...
In toolchange.ngc file I copied that lines

M68 E0 Q#<selected_pocket> ;set the carousel to move to the right pocket

M64 P0 ; start carousel
;G4 P2
M66 P0 L3 Q60 ; wait for carousel finished
O210 if [#5399 LT 0]
(abort, failed to align carousel)
O210 endif
M65 P0 ; stop carousel

And inserted them to after that line

O100 IF [#<tool_in_spindle> GT 0]

Now I can turn carousel to any position for changing tools. And after that making M6T. carousel back to pocket from before loaded the tool and unload them in right pocket..
But still after change the tool popup screen to confirm like in manual change...
Any help with popup screen??

 

 

Hello guys,
I'm looking for an advice to buy the right VFD for the spindle with the following specs :

P = 2 KW
L = 4.5 A
2 poles
380 three phase
Hz 267 @ 16000 rpm
HZ 667 @ 40000 rpm

here are the specs of the ms300 VFD11AMS21AFSAA i'm thinking to buy :

2.2 KW
Input 220 single phase (so I don't require 380 three phases at all)
600 hz
Output current 11A
Built in EMC filter

Here are the CMM-EC02 ethercat expansion board features

► Supports EthernetCAT protocol
► Supports standard CiA402 speed mode
► Supports SDO (Service Data Objects) function: Drive status reading and parameters editing
► Auto shutdown function for interruptions during data transmission
► Supports remote I/O function


I'm not experienced to choose a right one without asking, this model should fits? It caps at 599hs so I should reach appox 36000 rpm? (old one seems 480hz).

Here is the delta ms300 catalog  filecenter.deltaww.com/Products/download...00_C_EN_20210714.pdf

www.farnell.com/datasheets/3171459.pdf 

 
 

I have an old kappa-goniostat (crystallography) that should be disposed and it's breaking my heart. It has 3 rotational axis for the sample in middle of the goniometer and an additional rotation+translation axis where originally detector was mounted.
I had this crazy idea that one could use it to work on spheric shapes in the wood (think about Escher's "Angels and Devils").

Two main problems:
1) I'm newbie to linuxCNC
2) goniometer has a strange geometry. I've attached image how it works.
The object rotates in center of system with three axis omega, kappa and phi. The kappa-angle is 50° to base (or 130°).
I tried to read examples about 5-axis geometry but all of them describe systems with orthogonal axis.

Any suggestions on how I should start this project? I have no idea how to tackle kinematics.
And before I spend hours reverse engineering encoders on DC motors, I need to know whether it is actually possible with LinuxCNC.

all best, Kris

was ist das für ein Schaltungs Müll !!!
Mal den N und mal den L zu schalten ist absoluter Müll man schaltet nur den den L !

What kind of circuit garbage is this !!!

To switch the N and sometimes the L, 

Juegen

That's odd, I have run up to 4 hm2 cards from one switch
I will try and duplicate this.

I cannot duplicate this error, here's a screenshot of LinuxCNC running with two 7I92T's,
one at 10.10.10.10 and the other at 10.10.10.11, both running from a single Ethernet
port going to a switch:


 


and here are the hal and ini files for the test setup:


 

The problem is that M66 is a 'queuebuster' command that halts the interpreter until gcode execution has caught up which makes it impossible to blend moves before it with moves that come after.

The only other possibility to influence axis position during gcode execution is external offsets:
linuxcnc.org/docs/html/motion/external-offsets.html

One thing I see is that the Z encoder scale is off by orders of magnitude.
If you are using the ~100 to 900 KHz range of the THCAD2, I would expect
and encoder scale to be roughly 800,000 / Z_motion_range.

What is the Z motion range for 0 to 10V out from your sensor?

It addition the scale may need to be negative. This is the first thing to get setup correctly

Also as I mentioned, you may need to feed the encoder velocity signal through LinuxCNCs
offset component to remove the offset at 0V
 

Another thread not a post.

Yes, you first write firmware to the FPGA RAM which gives you Ethernet access to the card.

Then you write the user and fallback firmware to the user and fallback areas of the EEPROM
with mesaflash.

(Your example shows the same file written to both, this will not work, you must write a fallback
file to the fallback area and a user file to the user area)

The init95t script in the .tgz file does all this but you can remove all the MAC/Netmask/IP address
writing stuff as these have already been done and are not affected by what you write to the flash memory.