Advanced Search

thank you for your reply but this does not work for me as even if I removed the time.sleep the motor moving with the same speed

The 7I76EU (and 7I76U) have 3 new parameters and the 7I84U has 2 new parameters

The main 2 added parameters are 7i76.[port].[chan].output_source and 7i76.[port].[chan].output_sink. or
7i84.[port].[chan].output_source and 7I84.[port].[chan].output_sink. These are 16 bit masks
that control the field output mode. Each xxxx.output_source  bit controls the source attribute
of the corresponding output bit and each xxxx.output_sink bit controls the sink attribute. The
default setting is for all source mode (xxxx.output_source = 65535 or 0xFFFF, xxxx.output_sink
= 0 or 0x0000) which means a 7I76EU, 7I76U or 7I84U behave like a 7I76E,7I76 or 7I84.

So for example:

xxxx.output_sink = 0 = 0x0000
xxxx.output_source = 65535 =0xFFFF
 = normal all sourcing mode (like 7I76E, 7I76,7I84, this is the default)

xxxx.output_sink = 65536 =0xFFFF
xxxx.output_source = 0 = 0x0000
 =  all sinking mode  (like 7I76ED,7I76D,7I84D)

xxxx.output_sink = 65280 =0xFF00
xxxx.output_source = 255 = 0x00FF
= outputs 0..7 are sourcing mode, outputs 8..15 are sinking mode

xxxx.output_sink = 65535 =0xFFFF
xxxx.output_source = 65535 = 0xFFFF
= all outputs are in push-pull mode

Note that each of the 16 output bits can be individually setup for
sourcing, sinking, or push-pull mode.

The 7I76EU and 7I76U also have a spinmode parameter to set the spindle output
bit mode when this is 0 (default) the isolated spindle output bits are ENA and DIR as before.
If the spindle mode bit is set to 1 , the isolated spindle output bits now function
as FWD and REV.


 

I see what you mean.
I'll look at the numbers again, especially as I've only recently realised the INI stores velocities as mm/sec, and the GUI is in mm/min.

Vielen Dank
funktioniert wunderbar.
Wieder was gelernt
Auch vielen Dank für den Link:
linuxcnc.org/docs/html/gcode/overview.ht...:overview-parameters
Da sollte ich doch öfters mal reinschauen.
Wofür brauch ich das?
Ich möchte eine Pitch-Error-Datei bzw. Leadscrew-comp-Datei halbautomatisch erstellen lassen.
Das Programm funktioniert schon.
Gruß Peter

In the  top plot, it looks to me like you have the maximum velocity faster the the drive can go
(so the following error rapidly increases when you reach the limit)

Normally you will need to set LinuxCNCs velocity limit to 80-90% of the machine velocity at 10V

Not working, one problem after another. I can imagine that you might think i am a complete idiot.
Machine freezes still, but now, after the 4. fresh install and installing debian-12.9.0-amd64-netinst and installing the debs, of course with some missing things messages while installing them, after boot the machine does not even want to move past the motherboard screen. (press del to... press tab to... screen)
Its the 3 full day i am trying to solve the latency problem, but instead i am only getting more problems.
If i would knew i can get samba to work without spending a couple of days "trying" to get it to work, then i would give up with debian 12 and linuxcnc 2.9.x. Unfortunately i know that when i install again wheezy, i will encounter 1000 things that dont work, starting with the clock, then the internet browser that is not anymore supported and of course samba that also needs some special attention by a Linux specialist, that i am not unfortunately.EDIT: after doing 1-2 changes in bios i can enter linux and also do the latency test, but the latency is about 31000 and also freezes sometimes.

In fact there is nothing much wrong with the hal and ini entries,
HOME_OFFSET = 25.4
HOME = 0
I understand these better now, and to have the machine Home position at 0.0 25.4mm away from the limit switch after the encoder index has registered was my intention.
But even after I have tuned the axis I cannot get a successful home.
It has however stopped parking on the limit switch, but but can generate a big joint following error. The Rapid Halscope image, is at 6350mm/min and to me from what I've learned from the tutorial is pretty good.
I've set the HAlscope f-error at 5/DIV to match the tutorials, but wonder if that's correct for a metric setup
The Home image is the follower error up to the shutdown, which shows a massive figure that I cannot reproduced with the jog buttons even at max table speed. 
Not quite making sense to me yet.
I'd appreciate some comments.

tried this numerous times.
i get so far and then mouse won't work after a reboot. curser won't move and no light on bottom of mouse.
tried a powered usb hub.
any other suggestions?
hugh

folder posted