Advanced Search

If it helps, this is what's displayed when starting in recovery mode.

(I know this problem isn't really about LCNC, but this forum is full of clever people who know way more about linux and computers than I do.)

Final testing of my ATC (rev2) and getting an error when I try to run M6 Tn via g-code.  M6 Tn works fine via MDI.

Error message was something about remap, pointed to emccannon.CHANGE_TOOL() not matching c++?  Cryptic, backstage code stuff I didn't understand.

Poked around a bit and discovered stdglue.py has been updated since I last updated LCNC, so tried running apt update/upgrade.  Failed due to some broken dependency.

Restart computer and now none of my USB ports work once the desktop has started.  Keyboard works at first boot - can select a kernel or recovery mode - but once the desktop starts I've got no way to do anything.  No mouse, no keyboard.  Unplugging/replugging doesn't fix.

Any ideas?  Even if I have to re-install everything I still need to get my latest config off the drive... it's got all the INI and HAL tweaks I've done in the past week for the ATC.

[Debian 12, 6.6.15-rt-amd, Xfce]

Can you check on the offsets tab if there is any rotational offset?

The issue is the source method installs its files in a different folder that the deb install does

andypugh wrote:

I feel that making this as an EtherCAT slave might open something of a licensing can of worms. But it already has Ethernet port for command input, and I would expect the STM32 to have the CPU horesepower to handle the protocol.
 

I don't think this will be a problem because the ethercat license is paid for in the price of the lan9252 chip.
If you were to manufacture these for commercial sale, you would need to be a company and register for free membership of the ETG to be compliant.
Its only linuxcnc who has a lcensing issue because we do not have any legal business structure.

Moved to "milling machines" so ... is this a mill?

After a quick run through i could not find any mention of induction or permanent magnet type.... Fanuc, that is really not nice.
Disconnect the motor from VFD, connect any two motor wires together and turn the shaft by hand, can you feel detent's and does it require more force to turn than when wires are not connected together?
If there are detents, it is a permanent magnet motor so it does not work with VFD, use a servo drive.
If it turns out to be an induction type, you can try settings on the VFD, there are several types of "drive modes" there, like Vector, triangle, sinusoidal, etc. These are just what i recall, been several years since i last set up a VFD.
Also, limit the current on the drive, you are using a 200V motor with a 380V VFD.

Got it. I ran up a new config with pncconf and indeed the ini file was missing
in the ini file. It must have been deleted along the way.

More useful than ethercat is 600vdc because opens the door
to more powerful from 2kw range servos like spindle servos and big cnc servos.
Except other igbt module to handle 600vdc better isolation better connectors
what other needs?
The modifications will be in power stage.. driving stage needs modification?
To all stmbl owners are you happy from stmbl ? Works like commercial servos?

Just finalising an implementation of qtplasmac on a retrofit and we don't seem to have the breakaway and float switch connected
I know these should be connected to plasmac.float-switch and plasmac.breakaway
These seem to be connected in qtplasmac_comp.hal but I can't see this hal file is being loaded anywhere in our config so maybe we broke something. If that is the case, there are a lot of other signals unconnected.

Can someody set me straight here?






 

Hi All,

I have finally reached the point in my Kitamura CNC retrofit that i can get the spindle turning.
I got a Delta 3.7KW C2000+ (3PH 380v) VFD + PG-01H encoder card. But I'm having some interesting issues....

So My Spindle motor is an old FANUC 2S 2.2 / 3.7KW 200V 4P 1500/8000rpm spindle motor:

Datasheet link:  s3.amazonaws.com/Icarus/DOCUMENTS/Fanuc_Manuals_1791.pdf So what I tried is to first figure out if this is an AC induction motor or an PM motor. From what I can find (or not find in this case) anything in the datasheet so that made me think it is an AC motor as i feel no "dents" when i turn the motor by hand.
So I connected it all including the OEM Fanuc encoder signals the the VFD.
And then I went through the setup wizard, (immediately went for the complicated method) of including the encoder feedback etc.
When i tried to do a test run it just immediately jumps in OL3 error. I tried some of the advisement in the datasheet such as changing accel time or carrier frequency but that did not help.

So i went back to the basics and just put it in V/F mode. Max output voltage 200V , poles: 4 , max freq 267Hz , base freq 50hz (1500rpm) .
Now when i pressed run it turned, but it did not sound good. The current was around 17A's when it runs with no load on like 500rpm. I tried to set it to higher RPM but the high load pretty much states around. After a bit the VFD throws and overload as it is pulling too much current.

And now... I'm quite lost, any idea what I'm doing wrong? I have worked quite a bit with vfd's and never had such troubles so I'm thinking there is something fundamentally wrong. (this servo spindle worked well with the FANUC drive it had before).

No, 7i95t_5abobd.bin should work.

Well that worked. No more dither error.
Thanks.

I don’t know where mesact expects the files either. I searched for the files in the file system with that name and replaced them. I know nothing about Linux so I’m sure made a mistake.
But if I ever need to flash again, I’ll know to use the command line in the directory with the file.

Sorry i could not help, i am sure it is something wrong with the "desktop explorer", that is the normal file explorer that does the desktop part, had this happen on Mate DE twice, it just requires deleting a hidden folder, but i do not know what folder is that on XFCE.

Yeah, that's the old file. not sure where mesact expects the files but you can program the new file with:

mesaflash --device 7i97t --addr 10.10.10.10 --write 7i97t_5abobd.bin --reload

run in the directory where the new file has been placed