Advanced Search

Try
0x0100

Any and all info is definitely very helpful. Thank you, I really appreciate it! And thanks for the encouragement.

Hopefully now I can figure out how to actually hook this thing up properly. I found the switches here . They are inductive proximity sensor switches. It says 6-36V DC so I'm not sure how these will work on the Mesa board or how I'll even mount them or even how to get wires run all the way from then through the things he has. So looks like I have some more research and tinkering to do. I think first I have to figure out how to test them to make sure they actually will work before going through all the trouble.

 

Hello everyone,

My name is Philipp and i started a new project a couple of weeks ago:Retrofitting a Weiler 160 Cnc to be servoconventional (like a E35).I want to keep the original DC spindle motor and replace the X and Y servos with 750W Ac ones.(got all the parts already).

I use probe basic lathe with a touchscreen and a Mesa 7i76e and a 7i85, which works already. Now to the problem:The "pendant" for the conventional part makes some trouble:

Schematic: 
first page is the "pendant" that goes on the machine saddle, second one is the control cabinet with touchscreen.

I have printed this mockup:  

The problem is the "Vorschubsrichtung/ SVH NA 4022", its a latching joystick.
I want it to feed in the selected direction, but with a defined feed per revolution. So the feed scales with the RPM of the spindle.
I have looked through all possible articles, but could not find anythig matching.
Maybe someone here has an idea on how to do that?

Regards,
Philipp

Did you home the machine? It won't let you run a file till the machine is homed.

While it might not seem like it to you..... You almost got it!

Put that home switch on z.
Your sequence is correct.

For those clear path servos. Save the tune you have that works ok. Playing around with it shouldn't break things. I'm not familiar with how those tune but have worked on a few machines with them. Most of them have the problem you describe.
Two things you can do about it.
1. Mess around with your pid tune. Typically if it's jittery only when stopped your "I" part of the tune is having issues. It's either oscillating when I is too high (you should be able to see this) or not moving but on when I is too low. This can happen when your mechanics are sticky, the gantry is out of alignment, etc. basically the servo is trying to gently get to a position and hold it without overshooting.... But can't make cause something is holding it back. The motors either needs more power (higher I) or fix your mechanics.
2. Increase the deadband. If the mechanics are good and playing with I doesn't seem to help ( or you don't want to mess with it) try increasing the deadband. Servos are very accurate and often try to get to an insane level of precision (some have millions of encoder counts per revolution) so you may be telling it to go to encoder position 1,000,000 and it goes to 999,999,364 instead but tried to get to 1mil. Hence the jittery. But you don't care as after dividing that error by the pitch of your ball screw is going to result in some tiny tiny tiny linear distance. So increasing the deadband tells the servo.....ya you are close enough don't worry about it.

Option 3
Don't worry about it. If the motors are cool to the touch after jittering for an hour or so it's not a big deal. If they are too hot to much for more than a sec it should be fixed to extend motor life. Anything in-between is up to you. Personally I'd fix it cause it's annoying. If it's hot mess with the "I" tune, if it's cool mess with the deadband.




Hope that helps

I would check the output voltage, they might be 5V out or open collector.
The may also be open collector with a pullup resistor to their power supply
(you can test for a resistive pullup by supplying a small load on the output,
say 1K Ohm. and seeing if the voltage output drops significant;y when loaded

How to handle the interface depends on what kind of outputs the encoder has.

 

It's fine to customize the created hal file, just don't go and change it in pncconf again.

Yes Thanks a lot. That was the problem
and also after correcting that, "mv: cannot stat 'dev/ttyFIQ0'" doesn't show up anymore too.
Thank u

Hi folks.

I have used Pncconf to create the initial hal- and ini-files for my machine, just to get a starting point for configuring my machine.

I am now working on finetuning and also adding additional functions to my machine-configuration.

I have made these changes/additions in the hal-file created by Pncconf and not in the custom.hal file, even though I have read several places that any additions to the machine config should be placed in the custom.hal file.

Are there any drawbacks to making all of my machine-configurations in the hal-file created by Pncconf?
Is this advice only recommended in case I need to go back to Pncconf to make changes from there?

I currently have a 7i97t board, and I would like to connect a pin encoder to my board.

my encoder must be powered in 10-30V dc (i don't know the encoder output voltage), it's single-ended wiring.

i've seen that the 7i97t board can handle input voltages of 12V single-ended.

is it too risky to cable my encoder on my board with 10V voltages or should I cable it with a voltage divider?

My encoder is currently connected like this:

VCC - A - B - /Z - Ground

should I keep it as is (no importance) or should I change the wiring of the /z to z index?

Thanks for helping mate.

So went into the .HAL file and the port matches what I have in lspci -v exactly
gone through and tired 0x3048
0x3040
0x3000
even tried 0x3028 all yield no response.

Your hal file in missing the lines that load the base & servo thread. And few other bits & pieces.
At the start of your hal file you'll need something like this

And you need to sort out the issue withThis could be the file not existing or you don't have the correct permissions to access the file. Unfortunately as the whole error log isn't there, just a screenshot or a small part, I can't comment any further.

 Now I'm wondering if I need to edit the .HAL file for the built in parport tester as mine isn't at 0x278 or 0x378? How would I even do that if thats what I need to do?

I'm not overly familiar with parallel port setups but I would think that you would need to edit your hal to the new port.

[ 3.711658] parport0: PC-style at 0x3028, irq 16 [PCSPP]

So have a look in your .hal file and see if you can find something like this (i think):

loadrt hal_parport cfg= ....

and change the port to reflect the newly installed one.
If in doubt please post your hal and ini files.
 

also not sure if relevant, the parport is connect to my bob and when I power cycle the pc the onboard bob relay is clicking. so some communication is happening via parport atleast.

i have a problem with mesact, when i try to create my configuration, i get this error message.

when i look in the folder where it created the files, i only get an ini file.