Advanced Search

Think of it as a buck converter...

First, it's still not clear whether you have a 7I92 or 7I92T(x)

The support software zip file that has all the sources and project files
needed to build firmware files is downloadable from Mesa's webstore
(in the specification tab for the appropriate card)

First, make sure what 7i92 you have, there is 7i92/7i92M/etc, then there is 7i92T/7i92TM/etc, meaning with T and without T, they have the same functionality, but use different FPGA so flashing the wrong firmware is not good.
They always have a sticker on the back with the model written.

Young??? I am 55!
And the dog got banned from the shop for a while as i got tired of monitoring her so she does not pee at everything!

The cutting machines and the many, many other things are great! Who is this young gentleman with the pretty white hair, and where is the dog? Thanks and have a good time!

Hi I found a 7I92_7I76x1dpl.bit which would be good.According to its description, it also has 2 PWM outputs onP2 7-8 I/O.Unfortunately, the description and reality are not the same.It doesn't have a PWM output.
The card has 2 IDC 26 connectors.
1 connector standard LPT assignment 1-25. 26 pins +5V
2 connectors 1-17 pin input 18-25 GND 26 pin +5V

Where can I get the 7I92_xxx.vhd files?

I assume you have a 7I92T{x}, the 7I92 uses a Xilinx tool chain, not Efinix

Can you post the pinout of your expansion card?

Note that pinouts are more flexible than you may think
because of the ability to trade off GPIO with specific pin functions,
so its likely that if you expansion card has a parallel port like pinout
that an existing configuration will work.

In the source, the files that determine the configuration pinout
are all named PIN_xxxxxx.vhd. taking an existing one of these files,
copying it to new file, the editing the new file to suit is the normal
procedure to create a new configuration. In addition to creating new
pinout file, the new pinout file needs to be added to the project
and included in the top level source.
 

Guess it's more prudent to look at the entire signal.

It should link two pins like this:

 

of course the second pin wont be qtplasmac.cut_feed_rate-f  It will be whatever the plasmac equivalent was (should be similar)

Was hoping for a 0 feed rate as that's the easiest thing.

You could have them use Halshow to "SHOW" the plasmac.cut-feed-rate pin.  It should look something like this:

 

If it looks like this, then the pin has been unlinked (or is not being linked) for some reason:

 

If it looks like the first picture you could have them add it to the WATCH section and change materials and see if the pin ever shows anything other than 0.  

If it looks like the second picture then you need to investigate why it's not being linked.  

You could have them temporarily link it with the following command in the HAL command: section of Halshow:

It should work after that (for that session)

Hallo,
EOE ist im igh ethercat driver nicht funktionstüchtig( driver < 1.7 ?) und sollte beim kompilieren deaktiviert werden.

Gruß
Rüdiger

I *could* put my stepper drivers in PV mode. So I am making a modification to the cia402 component to (hopefully) make a stepper motor work as a spindle (how useful). Servo drives also. 
Check back in few hours. 
 

Eyecandy is proving to be as issue, especially plymouth.

When image is initially created plymouth splash dispalys.

Using plymouth-set-default -R pix causes the boot splash to disappear. pix s the default so shouldn't be an issue.

So until this can be resolved it's KISS.

I had them send me a copy of the config and it appears that all the material feed rates are correctly set. They tell me this issue happens on all gcode files they try to load and run.