Advanced Search

Hello, hope you are doing well!
I have a new Schneider PLC to sell, almost for free cause I bought it and I did not use it once because I abort the project, so I can sell cheap. 
If someone want it, we can talk in WhatsApp. 
If this goes against policy of this forum, pls delete the topic. 
Thank you 
​​​​​​
 

Probe_postgui.hal:11: parameter or pin 'dbounce_probe.delay' not found

In deiner ini Datei unter [HAL]:

ist:
soll:

Hallo,

Habe ich entfernt, leider immer noch eine Fehlermeldung siehe report...


karlhe

Hmmmm... is the loop being closed in the drive or LinuxCNC?
If in the drive, first thing to check is the encoder wiring (if it is not factory sealed), then change motor wires to change the direction.

fat238sg wrote:

i made it work already, somehow it could see 10 stepgens and after modification of the hal file to read stepgen 05 and 06 instead of 00 and 01 previous, now the axis servos can run, but i am still unable to get the outputs to work.

Anyone able to let me know in a 7i96s + 7i76 config, what hal label will output 0 on the 7i76 be on linuxcnc?
 

It will be on sserial channel 1

You can check the I/O pin mapping by running:

mesaflash --device 7I96S --addr [card_ip_address] -dbname3 7i76 --readhmid

 

Invalid tab configuration

Lösche doch mal das hier aus deiner ini:

The problem with the .pin file in the distribution zip file is that it was made assuming
you had a 7I85 so it lists 7I85 pins not P1 pins. To make a pin file that lists P1 pins:


mesaflash --device 7I97t --addr [card_ip_address] --readhmid > 7i97t.pin


Also in case there is a question, 26 pin header physical pin arrangement is:

1  2
3  4
5  6
 etc etc

Pin 1 is marked with a square pad
This means than a flat cable has wires in numerical sequence
(with the red wire being pin 1 if made correctly)
 

What error is the driver showing?

Hallo, danke für die info, häckchen entfernt...neuer fehler report, neues geändertes maschinen verzeichnis..Grüße karlhe

Closed loop in LinuxCNC must be tuned in LinuxCNC, for stepper systems mainly just the P and FF1 values.
For P as high as it can go without vibrations at standstill, then just back a bit to be on the safe side.
For FF1 there is a corelation that i can not recall and can not check as i am on the phone, but try some rough values like 0.4 or 0.5 or 0.6 and see how it works then some finer value changes after you get it to jog, untill you can jog at full speed without error.

check the custom config yaml file for the changes made. always compare your sim config files first that is 99% of the time where your error originates from. if the sim launches and runs without issue.

you could make a custom ui file, i believe there is some discussion on this on the discord chat.

sure, just submit a pull request maybe and we can put the options in the sim config

Thanks

Sometimes what I think is clear to myself doesn’t end being that way for others.

Any file ending in “bit” is the programming file for the card.
Any file ending in “pin” is a plain text file that describes the pin functions and which connector and pin it is on.
The best resource for location of connectors for you board is the Manual for the board.