Advanced Search

PCW wrote:

I'll try to get to this sometime this week
 

So, did you create firmware for this setup? I am using this BoB´s in several machines, I would like to switch to driving them by 7i92, but cant find proper pinout in 7i92 firmwares file downloaded from your pages. Or whats the name of file with this pin setup?

______________________________
ParPortPin Function
1 Enable
2 xstep
3 ydir
4 (-I dont need-) SpindlePWMout (creating a 0-5V signal for the VFD with a buffer and low pass filter from this pin)
5 adir
6 astep
7 zstep
8 zdir
9 (-I dont need-)
10 max-home-z
11 min-home-x-and-y
12 (-I dont need-) SpindleSensorIn (RPM sensor, 4 pulse per revolution)
13 probe-in
14 xdir
16 ystep
17 CoolantEnable

Did you take a look at userspace python hal components? Using that you can create hal pins within a python program. As far as I know, you can easily import time and use it. It will just not be running in the realtime kernel. For a central lubrication system I doubt that would be a problem.

希望没有任何误会。我确信这个论坛欢迎中文话题，就像欢迎其他语言一样。

你们从我们这里得到的回复比较少，原因是我们不懂中文，而使用翻译工具需要额外的时间。

我认为按照这个论坛的运作方式，“其他语言（Other Languages）”是开始发布新的中文话题的最佳地方，就像我现在所做的一样。

如果由一些懂中文的人来负责中文话题会更好，因为我们如果不借助翻译是无法阅读的，那样会占用我们太多时间。

如果有人行为不当，最主要的做法是先警告对方。如果在多次警告后仍然继续不当行为，请使用“Report This（举报）”按钮，通知版主介入并协助处理。

“Report This（举报）”按钮也用于举报有害的垃圾信息，这样版主就可以将其删除。

Chinese translation provided by ChatGPT 5.2
I hope there is no misunderstanding, I am sure Chinese topics on this forum are welcome, just like the other languages.

The reason you get very little response from us is we do not understand Chinese and translators take extra time.

I think the way this forum works, the "Other Languages" is the best place to start your new Chinese topics. Just like I did now.

It will be best if some of you who know Chinese are in charge of the Chinese topics, because we can not read it without translation, it would take too much of our time.

The main thing to do if someone is misbehaving, you warn the person. If they continue misbehaving after several warnings, use the "Report This" button to notify the moderators to step in and help you with the misbehaving person.

The "Report This" button is also for reporting harmful spam so the moderators can delete it.

I received the Suswe SU-600 VFD today. I started by getting the motor to rotate. I configured it in Advanced Vector Control with the parameters from the motor's nameplate, but it's not producing any torque. What parameters would I need to configure to get good torque at low RPMs? The motor is rated at 0.86 kW, 380 V, 2.1 A, and 1000 RPM.

I am sticking with LCNC 2.7, as it will be a risk to update to 2.9, given the switch to joints, and the gearbox comp I have working. 

I really just want simpescreenrecorder. I use this on both my lathes. I just have little clue of how to get the repository working.

I also tried this method, but it also failed.

 

Well you could try upgrading to Trixie which has linuxcnc 2.95 and simplescreen recorder as standards. 2.97 is included in testing so you can use APT pinning to get 2.9.7 

packages.debian.org/search?keywords=simp...e=trixie§ion=all

zippoffs wrote:

I think I got it! 

• Use ferrites/EMI filters on the lines coming in and out of the VFD - this solved my problem!

I'm happy to hear of your success! 
I want to add a clarification to that one bullet point: EMI filters are very good for the input side of VFDs, but don't try them on the output side unless they are listed for such use. The output side of a VFD produces such a high level of harmonics, a common emi filter will smoke. Ferrites are fine for input and output side.

i did notice you use machine zero as the G54 offset. try setting it off that and run the test.

I think I got it! 
I tried moving the AC lines by the BOB, but that didn't work, probably because I didn't move them far enough. Last night I added a ferrite on the AC lines, and I was able to run the program without failing. This morning I removed the earth ground because it was temporarily through my window, and ran the program again. It did fail. 
When I started building it I had installed an EMI filter on the main power coming in, before the breaker box. I now realize that anything coming in is negligible compared to what the VFD produces. So I moved the filter to the VFD 220v lines. I think that fixed it! I have now run the program three times without fail! (see pic)

Thank you everyone for your help!

For those looking at this later, here is what I learned:

• Interference is a BIG ISSUE
• Separate AC and DC lines as much as possible
• Use shielding on low voltage signal lines (maybe fine without if 24v)
• Use a shielded spindle cable and keep it short! 
• Ground all shielding, but only at one end
• Avoid ground loops - only have one ground connection for each component
• Use ferrites/EMI filters on the lines coming in and out of the VFD - this solved my problem!
• Ferrites may help stop interference - try putting them if other things don't work

Do these things from the beginning! It will save you a huge headache.

github.com/linuxcnc-ethercat/linuxcnc-et...631ab668516b649fcaaf

Posted the PR
Will be happy to get some feedback, thanks

Okay,I did a dumb haha. I got a little too hung up on pncconf not picking up the 7i73. So I started linuxcnc and ran halcmd show pin | grep 7i73 and they're all there. I'm just going to set my pins in my hal file and it should be good to go

Thanks for the quick response. I ran mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --sserial and seems like it's communicating with the 7i73! I'm still not sure why pncconf isn't showing it? Is there some extra hal configuration that I need to do?

Here's the truncated output from the mesaflash command, just to show it is there
...
SSLBP port 0:
SSLBP Version: 1.43
SSLBP Channels: 2
SSLBP Baud Rate: 2500000
sserial device at channel 1: 7I73 (unit 0x130001F9)
SwRevision = 14
HwRevision = 1
NVBaudRate = 2.5Mb
NVUnitNumber = 0x130001F9
NVWatchDogTimeout = 50ms
.....

I could but that is a pretty huge overhead on a old pc. 

No idea, but you can always use OBS-Studio
sudo apt install obs-studio

2.9.4 is based on Debian 12 so might have better luck asking on Debian forums.