Advanced Search

DId you modify the qtdragon ui and handler fikes is that why you copied
the original files? I don't think you told me that.
The qtdragon_handler file that I posted creates an addition to the original. But you can't do both, either you copy the whole file and modify them or you set the file to extend the original.

Let me know what you want to do.

Any daughtercard that provides a RS-422 interface will work for BISS

With your 7I76 + 7I74 configuration, the BISS interface could either be on the one RS422 interface on the 7I76 or
any of the eight RS-422 interfaces on the 7I74 depending on the firmware.

@grandixximo
Note the issues related to scurve code:
github.com/LinuxCNC/linuxcnc/issues/3719
github.com/LinuxCNC/linuxcnc/issues/3720

I'm not sure if pinging you on github works.

Update, i just received the (almost) final plan for this project.
mesa part:
  6i25 => 7i76  -> spindle   = 1 motor
                        - >field output 1 = motor on/off
                        - >field output 2 = motor on/off
                          ? -> encodeur biss-c ?
          => 7i74   ? 0 => encodeur biss-c (RAIK060 by vishay) ?
                         1 => 7i87 -> 6 temperatures captors
                                          ->  1 pressure captor
                         2 => 8i20 -> main motor
Encodeur:
- i use an encoder raik060 from vishay (doc bellow) it seem to need a clock from the master card and maybe a signal? start?? in order to operate.

Project non mesa part.
This project is not a cnc but a system to test pieces it is composed  of 2 part:
- The first part is 1 motor cyclic powered by 8i20 in team with the biss-c encoder and a pressure captor in team with the motor controlled by 7i76 spindle

- The second part is the cooling system that will work in continue.
this is 2 motor that will run full time en 4 temp captors for security

QUESTIONS:

-Concerning the signal biss i am flexible on what part to use, ether the 7i76 or the 7i74 depending on what may be possible or the easiest and i saws where was an encoder part on the 7i76U  was curious if it was possible to use that?.
-If we keep the signal biss-c on the 7i74 it is important to note that i need to have most of the 7i74 port to work normally and only the port 0 has a biss-c socket. If it is not possible i can use a second 6i25 and 7i74 dedicated to handling the signal biss.
- i still dont have any signal from or to my encoder, is their something to do in order to generate the clock signal or to make it react? I cant seem to find details about this part in the forum (i still have a lot to read so i am not loosing hope) and chatgpt or other ai keep telling me that it is impossible or to use non existing  driver like hm2_biss.

I added the doc of the encoder i am using, it is the Multi turn version, information about the signal are page 15 and 16.

Lastly is there any doc about how to configure a framework? Even if i cant do one myself, knowing what is happening would help me to know what information i need to give in order to get a bitfile adapted to my configuration.

I'm really poor in network matter....
Why my results are so dismal?
I red "60000 packets transmitted, 60000 packets received, 0% packet loss" and I was almost happy.....
BTW, the Mesa in wired to the onboard ethernet card, while the router (LAN, WEB) is wired to a PCI board (a commercial, very cheap one, this PC is intended only for CNC machining)
At the moment I don't remember the MB specification, but as soon as I can, I'll check e post it.

HI
the .xml file should look like this, I think
  

OK. Have done this and grounding each of these inputs produces no response from any of the pins a, b or index in halshow, on any of encoder channels 00, 01, or 02.

Those are fairly dismal ping results, What is the Ethernet hardware?
If Intel, make sure you disable IRQ coalescing (see hm2_eth manual page)

 

That’s a solid approach, especially starting from Clough42’s ELS project. Mounting an encoder and motor on the dividing head is a clean way to get a lot of capability without going full CNC. The DR-DRO setup makes sense too, it’s way more flexible for tropical-casino.com/ oddball indexing and manual machine tricks. Doing something similar on an MH800E with LinuxCNC sounds like a natural next step, especially since you can blend manual control with some pretty advanced automation when you need it.

First thing is that my data path isnt /usr/share anymore, instead some documentations told me to get the file seperated copyed into the machine folder, for me i got the base ui and handler there : /home/.../linuxcnc/configs/.../qtvcp/screens/qtdragon_hd/. The second thing is your talking about taking your file name it "qtdragon_hd_handler.py", if i go like that i would override the current base handler, that doesnt make sence to me. What i exactly did know is

-Rename ur .py data to vacuum_popup.py (using it as a second handler)
-Implement your 3 lines to .ini like that:
EMBED_TAB_NAME=vacuum_popup
EMBED_TAB_COMMAND=qtvcp vacuum_popup
EMBED_TAB_LOCATION=DIALOG
-/home/.../linuxcnc/configs/.../qtvcp/panels/vacuum_popup/ is the path where the ui would be

If i start then it seems like it load but it cant cant work with the class: Like you will see in the error code i attached as .txt

I feel kind of sorry but i really want to learn the things, even if the start is currently kind of hard. But your help is getting me confident i can make it.
Thanks for your help

 

I took some time to modify some BIOS settings, performed several restarts, and ran tests. This is the result I was able to achieve.

sorry for being late in my answer, but job and family demand their time too.....This is what i get : joccnc@JocCnc:~$ sudo chrt 99 ping -i.001 -c 60000 -q 10.10.10.10
[sudo] password for joccnc:
PING 10.10.10.10 (10.10.10.10): 56 data bytes
--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.246/0.395/0.733/0.032 ms

In the meantime, I was testing around with the HOME_ABSOLUTE_ENCODER = 2 setting in axis SIM. It turns out that there might be a positional accuracy issue when homing. Ive created a github Issue for it already. It seems like its reading the joint position and not the encoder position when setting the new home so on re-home, it shifts the axis location in software by your home-offset value while hardware remains the same.  

juliankoenig87 wrote:

Der Titel dieses Threads suggeriert aber, dass du eine 7i96 nutzt. Wenn dem gar nicht so ist, bin ich bei euch.

Was soll der titel sein?

will do