Advanced Search

Hi

I am currently setting up my 3D Probe. I declared the probe as T99 in the table. In addition to that, I set Variable 4012 in my *.var to 99.
However, when I command the Tool to be picked from the Toolrack, I  get the message "T99 not found in carousel". All the others (I actually tested only Tool 1-7) are working. Is there something I am missing?

One additional question. After inserting the Tool manually, I am using the Angle function. It works so far and I get an angle reported. However, I assume that, when clicking "Set rotation WCO", that the rotation is saved in my WCO. However, looking at the Offsets Screen, it looks like it's still 0 (I assume that would be R?).  Is this correct?

Here's a thread of someone else doing a similar retrofit:

www.cnczone.com/forums/uncategorised-met...253-engineering.html

The existing drives are 2 phase, unipolar, and 8A 
(Unipolar is why they have 6 motor wires because each winding has a center tap)

I think the forum suggestion is good: Replace the drives with standard bipolar
stepper drives but since the windings  are wired in series for a bipolar connection,
use the highest voltage capable drive you can get.

(this assumes you want to keep the motors)
 

Hi,

Indeed links are not working.

Maybe this helps you :
link

Hi,

Modbus should work.
wiki.linuxcnc.org/cgi-bin/wiki.pl?VFD_Modbus

If you have any problems with programming etc. Let us know.


 

I would probably choose a 7I96S setup as it's closer hardware wise to the 7C80.
Then the main changes would be to change the driver name and card name
and all "inm" to "inmux"

Unfortunately the locale bug is a known pncconf issue and the only known work-around
is to set the locale to  english.

If you launch pncconf from a terminal, it may be sufficient to type 

LANG=C

before launching pncconf

Hi Vre,

This for info. I hope you can use it.

The linuxcnc scurve planner has now tangential knife output value to hal.
The hal rotational output value could be coupled to a axis motor or device for rotation.

Within the the planner you can also benefit from the clothoid fillets, where the path
tends to be g3 continu, ideal for a drag knife application.

May also be useful:

www.ass-services.ch/file/img/Ersatzteile...anditI&IIaktuell.pdf

Might be the service comnpany listed on the board!

These things seem to be fairly common actually.

You can't find any schematics cuz they are proprietary.

(actually, you can find schematics for any other drivers either)

Great work

You need to use menuconfig to setup your locale.
If you go to this thread it is an index to a lot of info.
forum.linuxcnc.org/38-general-linuxcnc-q...l-images-only/unread

i now tried to extend the homing workflow to better align to the Linuxcnc usual homing.

my home states are :

PK_PEAxisState_axREADY   -> before homing
when Homing is triggered the pokeys internal Homingprocedure does the following states
 - PK_PEAxisState_axHOMINGSTART 
 - PK_PEAxisState_axHOMINGSEARCH 
 - PK_PEAxisState_axHOMINGBACK 
- PK_PEAxisState_axHOMING_RESETTING
- PK_PEAxisState_axHOMING_BACKING_OFF
 - (  PK_PEAxisState_axHOME ) that status of pulse engine is suppresed and 

after that i have to finalize the pokeys homing procedure by a "PK_PEv2_HomingFinish" command in order to operate that joint again for tho upcoming steps there fore i added two additional steps: 
    PEAxisState_axReadyToFinalizeHoming  -  used as a indicator from pokeys.comp to pokeys_homecomp that the homing finalize command can be triggered

    PK_PEAxisState_axReadyToArmEncoder  in this step that index search part should take place, in that step my intention was to reset the position feedback to ZERO_POSITION, to prevent problems on pokeys due to the (softlimits on the device side).

on the Joint for Z i have the problem that the difference to zero position is quite high as the position change might be 100 mm

so here i'm at a point  where i don't figure out what to do, and either where to find out or whom to ask for help.

what i currently try to do is 
Joint_num].index_enable = index_search_active;  at the PK_PEAxisState_axReadyToArmEncoder status


and at the follwoing status
PK_PEAxisState_axHOMINGARMENCODER  i basically reuse the actions as were done in homing.c at "HOME_INDEX_SEARCH_WAIT"

                if (H[joint_num].index_enable == index_search_armed) {
                    /* yes, stop motion */
                    joint->free_tp.enable = 0;

                    // joint->free_tp.pos_cmd = joint->free_tp.curr_pos; // set to zero
                    joint->free_tp.pos_cmd = 0; // set to zero

                    /* Pokeys resets encoder position to zeros */
                    H[joint_num].index_enable = index_search_armed;

                    H[joint_num].homing = 1;
                    H[joint_num].home_state = HOME_SET_INDEX_POSITION;
                }


but it always stops at about that step and some part triggers "do_cancel_homing"
the only message that i could see on my last version was 
"emc/task/taskintf.cc 976: Error on joint 3, command number 139"

(until now a similar message was together with a FOLLOWING_ERROR for that joint)

Is there someone who could tell me where to check, or whom to ask. I'm not sure if this thread is the right place to ask about that topic.

BR
Dominik

www.radwell.ca/Buy/ALLEN%20BRADLEY/SUMMIT/214-072-01

Is there a good source on how to set this card up?

PnCconfig doesn't have the 7C80 and i am not very good with the HAL files yet.
I tried to use PnCconfig and chose the 7I76 instead, but then at the end PnC got an error saying "unsupported locale setting".
screenshot of error

Hi all,

Today we added another feature to the scurve planner : tangential knife

The planner outputs a hal float value in degrees.
This rotational value can be used by tangential knife machines to direct the knife in
the vector direction of the trajectory.

 

Those are step motor drives, 8A max
No idea how they are interfaced but
maybe worth a bit more searching with 
the drive PN:

214 072 01d

Remember to remove the short once you have updated the firmware.

Sorry for the problem

(luckily there are  no bad firmware files out there other than what was
installed on cards)