Advanced Search

Mit dieser Anpassung sollte das vollständig durchlaufen

    #2 = [#2 + 1]
   #1 = 0
o101 endwhile

7I76EU firmware for 7I85 on P1, and 1 PWM on P3

 


After doing this I also had a thought that you could use a spare RS-422
output on the 7I85 for the PWM output, so you get a  buffered output
rather than a bare FPGA pin.

 
 Thats a dodecadon lol
I was planning to make rounded corners actually be radiuses in the gcode G2 G3, probably next week, unless you want to oblige, many thanks again Rüdiger!

Reply to PCW with:
"Yes, that's correct:

7i85 encoder card on P1 (first DB25 expansion connector)
PWM on P3 (second DB25 expansion connector) for laser

Or if it's easier, PWM on P1 and 7i85 on P3 - whichever works best for the firmware. i use all 5 stepper outputs. so any port or pin you think is best will do.

I'm a little unconvinced how changing to USB would have an affect on the "wiring nightmare or EMI issues".
At the end of the day one still has to make a connection from the input or output device on a control panel to the interface board.
The wiring nightmare and/or EMI issues will be a creation of the practices used by the person doing the work. In summary these issues are going to be site specific.
From memory Mesa did have a USB interface board, but is now listed as obsolete. It also supported EPP, only mentioned for completeness.

Ich versuche gerade eine while Schleife in einer while Schleife zum laufen zu bringen, die äusere Schleife wird nur ein mal ausgeführt,.

nc-code

F10000
#<radius> = 10
#<anzahlEcken> = 3
#<winkel> = [360 / [#<anzahlEcken>]]
#<verrundung> = 0.001
#<drehungUmC> = 60
#<wiederholungen> = 5

G10 L2 P1 R[#<drehungUmC>]
G64 P[#<verrundung>] Q0.0
#1 = 0
#2 = 0

o101 while [#2 LT [#<wiederholungen>]]
    o201 while [#1 LT [#<anzahlEcken> + 1]]
        g90 g1 x[COS[#1 * #<winkel>] * #<radius>] y[SIN[#1 * #<winkel>] * #<radius>]
        #1 = [#1 + 1]
    o201 endwhile
    #2 = [#2 + 1]
o101 endwhile
m2

ist es überhaupt möglich ?

Gruß
Rüdiger
 

I am working on integrating my first analog servo build. 7i97 and Anilam drives. I am following the steps here . I have the encoder scaling correct but when I go to enable the machine, there is a brief moment of runaway before I get two errors: 
"joint 1 following error"
"could not switch the machine on. is limit switch activated?"

I am only working on joint 1 at the moment. 
No limit switches are in use at the moment. 

I have tried inverting 'output scaling' and 'encoder scaling' in every possible combination on the configuration page. 

Any suggestions? 

Thanks! 

Do you mean 7I85 on P1 and PWM on P3  (on 7I76EU P1 is the first parallel expansion connector and P3 is the second)

Very interesting. A few points.
1. You don't say anywhere how to get the boards which are very well thought out. I'd love to test it.
2. New software to go into Master branch (2.10) which will be released in a few months.... This needs to be tested on this version (I'm finalizing a how to build linuxcnc video on my @MrRodW YouTube channel
3. Reformulate (or recreate) the git repo so this can be packaged as a PR to Linuxcnc. This would give you the best chance of success with your hardware project.
4. Your business model is similar to Mesa's so having an open source driver for your hardware in the Linuxcnc distro is not really controversial.

I revised the NC program and made the number of corners and the radius parameterizable.

Hi PCW,

I need custom firmware for 7i76EU with:
- 7i76 daughter card on internal SSerial (currently working)
- 7i85 encoder card on P2 (currently working)  
- PWM generator on P1 for 20kHz laser control



Can you create firmware combining all three?

Board IP: 192.168.1.121
5 axes: XYZAB vfd rs485 controls spindle direct on the mini pc with rs485 output

Thanks!

In linuxcnc 2.9.8 I genereted ethercat-conf.xml file from slaves with command:

That might be a question for Sorotec. They also offer grease guns and lubrication products, and should be able to make a recommendation:

www.sorotec.de/shop/Tools-and-utilities/...roducts/Lubrication/

HGH20CA is a Hiwin part number, although I suspect that Sorotec is selling generic clones. Hiwin has an extensive linear guide and ballscrew lubrication guide at the following link (737KB PDF). They recommend viscosity grade NGLI 2, and list specific greases (see attached table).

www.hiwin.com/wp-content/uploads/lubricating_instructions.pdf
 

Subject: Solving the USB Latency Dogma for HMI/MPG: Technical Feedback Request

Hi all,

I’d like to open a technical discussion about a project I’ve been working on, io_decoder, focusing on the software solution I've implemented to handle USB communication within LinuxCNC.

I am well aware that in the official LinuxCNC documentation and Wiki, USB is often described as 'the evil' (or, more formally, as 'not suitable for real-time control'). However, if one looks closely at the context of those warnings, they are strictly related to step generation and primary motion control, where microsecond-level jitter is fatal.

For HMI panels, MPGs, and secondary I/O, I believe this 'dogma' can be challenged if the HAL component is designed to manage the USB stack correctly. My goal is to allow users with complex retrofits (like those using Mesa 7i80/7i92) to offload all non-critical I/O to a single USB bus, freeing up high-speed pins and reducing the 'wiring nightmare' and EMI risks.

To test the limits of my custom HAL component, I’ve pushed it to handle real-time axis tracking via an encoder (not just simple buttons).

You can see the fluid response in this playlist: 
www.youtube.com/playlist?list=PL9D_TSVxg...tA9_k6njBeVTL0IYY7Ct

In other communities, the mere mention of 'USB' triggers an immediate rejection. I’m posting here because I’d like a more nuanced, engineering-focused feedback:

1. Given that a human operator has a reaction time of ~200ms, is a stable 20ms update cycle (50Hz) really a bottleneck for MPG tracking or HMI interaction, considering it's handled by a dedicated non-blocking HAL component?

2. How can I further improve the HAL component to make the communication even more robust against bus jitter?

The project is Open Source and I'm looking for peers to discuss the driver implementation rather than the hardware itself. What do you think about the responsiveness shown in the videos?

Documentation & Wiring: 
bobwolfrst.github.io/io_decoder-linuxCNC/

Best regards,
Roberto

So to use a custom panel you have made in Qt designer.
Say the panel name will be 'test.ui'
save the panel in your configuration folder in qtvcp/panels/test/ as test.ui

then in the ini under [DISPLAY]

EMBED_TAB_NAME=demo
EMBED_TAB_COMMAND=qtvcp test
EMBED_TAB_LOCATION=DIALOG

please give feedback on any problems or needs.

Chris