Advanced Search

Alright so it turns out I can use sinking outputs since all the outputs go to a relais board and I can just give the common on the coils +5V and then switch them by sinking. That means I can use the 7i97t as my "main card" with ethernet connection to the pc and the 7i84D for I/O. The 7i73 in the control cabinet could then be connected using the adaptor talla83 shows in the video, right?

I think with that I am all set.
7i97t: connection to PC, 3 analog axis outputs, encoder feedback with linear scales, spindle output, 3 handwheel mpg inputs(uses 6 inputs), 10 inputs, 6 outputs
7i84D: 32 inputs, 16 outputs

A whole 7i96 is a lot of card, for the potential expansion of a stepgen, maybe in the future. All those FPGA cards have a 25 pin expansion slot which we mostly dont use (P1 on the 7i97).
I am pretty sure you can add a stepgen onto a couple of those pins with a bit of playing around in the MesaFlash utility. It looks like you could also use that to hook in a second SS for the 7i73.

Peter (Talla83) has done some excellent videos on how to edit the bitfile for the mesa cards, such as this one (In german, but Youttube does good tranlations subtitles.


 

Hi,

I am now at the point that we have done :

- Calculate the velmax of each segment given the max curvature of that segment.
- Path Vel Optimizer: perform a forward scurve motion over the path, update vo's, ve's if valid.
- Path Vel Optimizer: perform a reverse scurve motion over the path, update vo's, ve's if valid.
- Plot 2d, 3d velocity profile.

2D velocity profile, the green verticals to z zero, indicates a segment transition.
You see i at the begin of the green curve, i added multiple colinear lines, to test the transition.
 

3D velocity profile,
 

My conclusion so far, if user gives no G64 P.. value. Then P=0. Then no fillet segments are created.
This must be avoided as fillets are ideal to get endvelocity's in line-line corners etc.
So solution is to set a very low P value if P=0 is given.
Then we set P=0.0001, this is valid and creates the fillets, and end velocity's without adding a bunch of extra sourve code.

Then i have seen when max_jerk is set at very low value, the scurve can't keep up and finishes with endvelocity > 0. This
is not ok. So when the Optimizer algo is performed, and the final velocity at the end of the path > 0, then
we must increase the jerk value until a valid output, wich is endvel=0. I have no other solution found for this so far.

I checked the motor cables for continuity with a multimeter, I didn't mix A and B.

tommylight wrote:

Stepper motor wiring is very strict, no mixing of coils, that is something most drives will not survive.
 

How will I know if a drive didn't survive? The green LED lights up continuously.

Update, my rs232 probe works now, it was just a wiring issue :
ibb.co/ZxrJnKZ

But transfer config still don't work, and probe doesn't show anything than on that image above.

Other screens :
ibb.co/jZMLThV
ibb.co/KV0D0tS

I've flashed remora-rt1052-nvem-0.2.1.bin, is that the right bin? 

I should have done the same on my last build.

Thanks ! I used the free program kicad. I have no experience with boards, but the important thing is that everything works

 

 

 

Also, for the outputs i really only need the analog signals for the drives and vfd and digital 5V outputs. Anything that is not 5V has its own little relay in the cabinet.

First of all thanks for the quick reply.

The setup with 7i97t with 7i84 would be ideal, however the 7i84 with sourcing outputs is currently out of stock everywhere I look. The spindle vfd takes a 0-10v signal and can therefore easily be controlled with one of the 6 axis outputs. I actually follow your Schaublin retrofit and that's where I got the idea for the 7i73 in my control cabinet. This can support physical keys in a matrix and also the encoders for Spindle/feed/jog so that's really good. I'm not satisfied with the cards in my electrical panel as well, but selecting from the available components this seems to work. Also, maybe in the future I'm gonna add a 4th axis to this machine and I'm not sure which type of motor I'm gonna use then, but having the 7i96 would leave the possibility of using a stepper or a servo for that.

Nice work. What did you use to design and layout the panel PCB?

Had to boot up the Co2 laser control laptop this weekend, last time I've booted this laptop was like 6~8 months ago. At boot it decided to throw "We Ran Into A Problem And Need To Restart Your Computer". It did that twice before auto-entering into "Recovery Mode".

After a few minutes, "Attempting Repairs" magically appeared on the screen and the router started flashing dwload lights crazy. Long story shorth; upon post-investigation, it was concluded that it had to install "Sec Patches and/or Updates" so to be able to boot up. Or else --NO COMPUTER FOR YOU BUDDY. 

Why I'm saying this? As a response to 'Anything Is Vulnerable'. Even Microsoft (NSA/CIA?) installs TIME BOMBS inside their OS. Law of decriminalized mobs!!

Really nice job on the control panel.

That sounds very odd, because we use the Debian 12 live installer so it is just Debian with some added elements for Linuxcnc.

Why a 7i96 and a 7i77? Can't the VFD be set up to accept an analog speed command, and therefore controlled by one of the free axis on the 7i77? These are both FPGA cards, so you end up with a lot of reduntant processing, and also a lot of unused features on the 7i96.

Are all your outputs on the same voltage? I ended up short of 24V outputs, as I had to put one rail of the 7i84 on 5V.
Good choice on a 7i73 in the user interface panel is a huge time saving in wiring reducing the wiring from the User interface down to the electrical panel to a single Cat 5E, plus one discrete for the E Stop.
Are you not using encoders for Jog/spindle/feed overides? These are slow enough to use normal pins and software encoder.

Have you considered 7i97/7i84/7i73?

Another option is the way I did it on my lathe. I split up all the functions with:
7i92 for the FPGA, plugged straight into:
7i85 interfacing the axis and spindle encoders, and providing 5 channels of RS-485 SSfor:
7i84 I/O (I might need to add a second one)
7/83 Analog servos
7/73 User control panel.
That leaves two spare RS-485 SS ports, so it will be easy to connect in the second 7i84 (once I find space for it in the electrical cabinet), and maybe a second 7i84 for jog wheels down on the apron.
 

Okay, the information that I was looking for is actually documented but it is a different one called STEPGEN. There I was able to find what steplen, stepspace, dirhold and dirsetup corraleted to, which are t3, t4, t2 and t2 respectively. Leadshine documentation is in micro seconds, it should be translated into nano seconds, which is x1000.