Advanced Search

Yes, if you use 7i96s_7i77d.bin firmware on the 7I96S, 
you have all the capabilities  of the 7I96S + 7I77.

The only changes are that the 7I96S encoder is moved to
encoder 07 and the 7I96S sserial port is moved to channel 3

This was done to make the encoder and sserial channels
more compatible with standard 7I77 configurations.


 

tommylight wrote:

Looks awesome, as usual !
The box seems a bit to heavy to be mounted on the gantry, but if he insisted...

Yes, it was how the machine was designed previously and there wasn't really a space it could be mounted elsewhere even if it was a stand alone cabinet. Here it was all packed up for shipping, (Plasma in a box)  The control box weighs  28 kg
 

snowgoer540 wrote:

Reading how much you like being on the "bleeding edge", I'm a drop curious why you didn't use the master branch? It does have a few more features that are not present in 2.9. It's also noteworthy to mention that at this point, 2.9 is considered "end of life" from a development standpoint (to include bug fixes).

Thanks. I actually asked  here which version to use for production and 2.9 was recommended.
forum.linuxcnc.org/plasmac/53044-best-qtplasmac-version-to-use
I also built the 2.9.x ISOs on the Linuxcnc downloads page soi maybe I am biased. For a production setting on a machine 1800 km (over 1000 miles) away for a user, using a production version  made a lot of sense.

Its not that the buildbot is broken but V2.9 is frozen following a release. Release debs for  2.9.3 are in the Linuxcnc repository which can be installed on any linux distro by running the bash script mentioned here 
linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel
(or by using the ISO)

Checking the release version of QTplasmac in Linuxcnc 2.9.3 , I see it is 2.9-238.314. It seems your last release for 2.9 was not included. It will probably get in there if ever a 2.9.4 is released.

I might write a script to convert from using the Linuxcnc repos to the 2.10 repos at buildbot2.highlab.com/

Anyway off topic for long enough, The main issue for us is the breakaway. It really makes no sense that it will not work when all the pins are set correctly as inputs into plasmac.comp. I will look at the state of the plasmac.comp output pins to halui as it might not be a qtplasmac issue. All of these features were working years ago so its odd they have broken.
 

 

my friend just repaired the 7i77 that I had and broke it with a short circuit (he says it's a dc-dc converter), in case it's successful, I'll try to connect it with the 7i96s...my question is, in that case, can I use the spindle output and encoder from  7i96s plus mpg and I/o, and with the 7i77 also use the I/O plus analog signals for the drivers (siemens amplifiers)?

bertoldo wrote:

Good morning!

I am using the image from the link that started the forum about ethercat.
 

sorry,
it's not clear to me which image file you're talking about

are we talking about this one?

 

Those drives have more-or-less infinitely adjustable microstepping.

HIGHLY recommend adjusting the following alarm setpoint.  I have similar drives (Nema34's) from Stepperonline, and the following alarm was set to 4000 counts from the factory.  They've got 1000-line (4000ppr) encoders, which means from the factory they won't alarm for a full turn.

Once set to a reasonable level, you can see if they are actually losing a few steps.  I'm also wondering if your g-code is output with lots of line segments instead of arcs and you need to adjust your G64 P-value (or turn it on).

BTW, the "M61..." is from one of the GUI screen buttons (UNLOAD SPINDLE BUTTON)

Looking back at the old thread I linked, it's pretty clear I - and the PB Dev who was responding - thought #5210 was for setting/clearing G52/92 offsets.

I don't know why the author would want to clear the offsets during a spindle unload.  The original subroutines had a bunch of numbered parameters added by the authors - this may have been a mistake and they overlooked the fact that #5210 was already in use.

And yes, I, too, am convinced this is a mistake.  I'll raise an issue on PB-GH tonight.

Thanks for kicking this around with me.

Building from source should still work, and it is quite easy, and you can build the debs so if you need to install on another pc or reinstal, just use the debs.

Forgot, these closed loop steppers, i have no idea how the position geedback is setup, so if you can:
-set the drive to x1 or x2
-lock the shaft so it can not turn
-in linuxcnc jog in the smallest possible increments
How many steps before a fault?
-
Geckodrive servos had a 128 step fault tolerance, and that is ok for high ppr encoders, but not ok for say 100ppr encoder as that is more than 90 degree of deviation before fault.

Impressive Andre! I have a the bigger brother of your MV-Junior; a MV 35/40 school machine and a SL25-B that i am planning to retrofit. Do you have even more information/pictures of your build?
I see you are Norwegian as well, please hit me up on FB or IG if interested in sharing experiences
 

As a general rule with microstepping, use only powers of 2, and as low as possible with some acceptable vibrations.
So x4 or x8 (800 or 1600 steps), rarely 3200 (x16). X32 should be the absolute max.
Microstepping is never precision, it is usefull only to lower vibrations, as steppers can be easily positioned between 2 poles but not easily betwen 16 divisions of those 2 poles, and any microstepping lowers the torque.

@DPFlex ... from 2.8 I'm unable to use halcompile .... AndyPugh suggest to use a rip install ..... you download on Lcnc_292_wharehouse ..... search on these new folder scarakins.c and change it with modify version .... than run process for make .... when obtain compilation file on rtai folder inside Lcnc_292_wharehouse folder of rip install, use sudo command for root permission, search for original one scarakins.c of your installation (if not use a rip install) and cancel these, copy with root permission your scarakins.c compiled from Lcnc_292_wharehouse  folder to system folder. Reboot ... all done.

Use these tryk for all modifications. Or learn you about customkins.c (never looses these time really) .....

If you have a rip istall .... use the same trick, but change modify scarakins.c from your "compiled Lcnc_292_wharehouse  folder" to your preferred rip install .... reboot and voilà.

regards

To be absolutely honest I don't really understand why they are setting #5210 = 0 in the first place.

What does unloading the spindle have to do with g92/g52?

Also here:
M61 Q#3991 G43 H#3991 #5210 = 0

Why the need to set #5210 = 0?

[edit]
The more I look at it the more this looks like a mistake to me. It just simply does not seem to make any sense at all.

and in witch SO?

tommylight wrote:

No easy way to install LinuxCNC on Linux Mint 22, yet.

no easy way like first installation on mint19.2? Because was quite easy in my opinion .... easy not equal "write 2 row of command" .... in my case use 2 row of command give me more and more problem than use a long list of command where I can see what happens ....