Advanced Search

hello friends i have problem to configure spindle  pwm dynamically that relate to speed of x,y,xy axies speed please help to edit the hal and ini file to achieve.first in setpconf wizard i setup pwm and the spindel works but at fixed rate i can add or reduce speed but is manual. 

Thank your for your suggestions. Doesn´t using Ethernet compromise system performance? If have read that using PCIE offers the higher performance advantage, or is it neglible? An ethernet card would be easier during setup, but my goal is to have everything inside the original spacious cabinet anyways.

royka wrote:

When you activate too many overlays they can interfere with each other, because some pins have multiple functions. Some can also cause extra interrupts, so remove everything that you don't need and isolcpus should be placed after extraargs:

verbosity=1
bootlogo=true
console=both
fdtfile=rockchip/rk3399-orangepi-4-lts.dtb
rootdev=UUID=a703d82e-8d61-4266-8b54-c10361d608ca
rootfstype=ext4
extraargs=isolcpus=2-5
overlay_prefix=rockchip
overlays=rk3399-opp-2ghz rk3399-spi-spidev rk3399-uhs
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

The spi it's not found yet. I've enabled it in armbina-config menu but still there's no spidev in /boot/ directory.
just to be clear, here is my /boot/ directory:
root@orangepi4-lts:~# ls /dev/
autofs           gpiochip2    log           mmcblk0boot1  snd     tty20  tty37  tty53   ttyS1    vcs5   vcsu7
block            gpiochip3    loop0         mmcblk0p1     stderr  tty21  tty38  tty54   ttyS2    vcs6   vga_arbiter
btrfs-control    gpiochip4    loop1         mmcblk0rpmb   stdin   tty22  tty39  tty55   ttyS3    vcs7   vhci
bus              hidraw0      loop2         mqueue        stdout  tty23  tty4   tty56   ttyS4    vcsa   vhost-net
cec0             hidraw1      loop3         net           tty     tty24  tty40  tty57   ttyS5    vcsa1  video0
char             hidraw2      loop4         null          tty0    tty25  tty41  tty58   ttyS6    vcsa2  video1
console          hidraw3      loop5         port          tty1    tty26  tty42  tty59   ttyS7    vcsa3  video2
cpu_dma_latency  hugepages    loop6         ppp           tty10   tty27  tty43  tty6    uhid     vcsa4  video3
cuse             i2c-0        loop7         psaux         tty11   tty28  tty44  tty60   uinput   vcsa5  video-dec0
disk             i2c-1        loop-control  ptmx          tty12   tty29  tty45  tty61   uleds    vcsa6  video-dec2
dri              i2c-3        mapper        pts           tty13   tty3   tty46  tty62   urandom  vcsa7  watchdog
ecryptfs         i2c-4        media0        random        tty14   tty30  tty47  tty63   usb      vcsu   watchdog0
fb0              i2c-7        media1        rfkill        tty15   tty31  tty48  tty7    v4l      vcsu1  wcn_op
fd               iio:device0  media-dec0    rtc           tty16   tty32  tty49  tty8    vcs      vcsu2  zero
full             initctl      media-dec1    rtc0          tty17   tty33  tty5   tty9    vcs1     vcsu3
fuse             input        mem           shm           tty18   tty34  tty50  ttyBT0  vcs2     vcsu4
gpiochip0        kmsg         mmcblk0       slog_wcn0     tty19   tty35  tty51  ttyBT1  vcs3     vcsu5
gpiochip1        kvm          mmcblk0boot0  slog_wcn1     tty2    tty36  tty52  ttyS0   vcs4     vcsu6

and as you said, this is the content of my armbianEnv.txt:
verbosity=1
bootlogo=true
console=both
fdtfile=rockchip/rk3399-orangepi-4-lts.dtb
rootdev=UUID=a703d82e-8d61-4266-8b54-c10361d608ca
rootfstype=ext4
extraargs=isolcpus=2-5
overlay_prefix=rockchip
overlays=rk3399-opp-2ghz rk3399-spi-spidev rk3399-uhs
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u


btw, during latency test and glxgears, the board has many lags and works so slow. is it normal? 
 

It seems a lot of effort to program any meaningful thing from the start.
It is quite expensive to "rent" a ready programmed solution.

Boils down to the question is it worth it? Pay someone to program it, or (provided one is able to) spend all the time to do it.

Nevermind! I found the correct bin file in the 7I94T manual, 7i94t_ssd.bin. 

Just an FYI when i run pncconf with the Mesa Card 1 option I get an ValueError: Invalid literal for int() with base 10: 'EXPANSION+SERIAL'.

I will try and add the card info to the hal file, should be good practice. 

PCW,

Okay, I do not have the board in front of me right now so I can't say for sure, but I have not modified anything on my board so if the jumpers came installed stock then that is how they are now.  Btw, I assume that "jumpers" are just connectors connecting two different points on the board and are used to control the logic, yes? 

And okay, I see what you are saying.  I will plan on testing with the ALRT pined directly into the input (on pin 29).  If I have any issue reading the signal I will revisit this.  

Thank you. 

Now I am going to start trying to put the code together so I can test as soon as I am home. 

Best,
-Dylan

That took care of it!
 removed the existing mesaflash folder since git couldn't clone with an existing folder of the same name, did the sudo make install and was able to right away get the info from the board with mesaflash --device ethernet -addr 192.168.1.121.
Ran the mesaflash --device 7I94T --addr 192.168.1.121 --set ip=10.10.10.11 and I can ping both the 7I96S and the 7I94T through a switch.

Do I need to flash a particular .bin file for the 7I94T and the 7I84s?

Thanks!

I have 2 simple classic cast iron rectangle precision levels 0.02mm/m (one new made in china and one old made in germany ) the problem is that they lost calibration and are very difficult to use them succesfully in practice.
I have tried the communicating vessels approach and was much easier in practice
cheaper and does not need calibration .

I should also mention that some of the MainWindow translation will get overwritten by the HandlerClass so the translations will need to be done in both. CYCLE START is an example.

I copied your two files to share/qtvcp/screens/qtplasmac/languages and ran QtPlasmaC on master branch with the standard screen size and it works here:


What version of LinuxCNC are you using and what QtPlasmaC screen?

I would replace with the latest
(sudo make install will do this)

I get this error when I try and and read the device with mesaflash --addr 192.168.1.121 --device=ETHER --readhmid:
unsupported ethernet device 7i94t at 192.168.1.121 no ether board found

From what I've read is it could be that I need to update the mesaflash version, I currently have 3.4.9. Is there a clean way to update Mesaflash or should I remove it and install the latest version?

Try setting the latch direction to opposite.

www.linuxcnc.org/iso/ubuntu-10.04-linuxcnc3-i386.iso

用英語問你的問題會有幫助