ricky_v8

Thanks for the replies, I will look into using a Modbus TCP I/O unit. Seems to be fairly straightforward.

Unfortunately we do not have the EtherCAT option. It is possible to get controllers upgraded by sending them to the factory, but in my experience that takes several months.

I'm in a situation that calls for expanding the I/O on a PowerBrick controller, and I'm not able to move to a Power UMAC or other controller. I need to add more outputs than the 24 available on the PowerBrick. What have you guys done to expand the I/O in the past? Demuxes, Field Bus modules? Any help is appreciated.

Thanks Steve. I was able to get it working with this method. For anyone else looking to do the same, here is an example of what I did showing only one machine and configuring just the X axis: #define MACHINE 2 // actually defined in different file #define X_AXIS_DEF_PRIMARY Motor[1].CoordSf[6] #define X_AXIS_Y_COMPONENT Motor[1].Coord[7] #define X_AXIS_Z_COMPONENT Motor[1].Coord[8] // Initial axis def with small Y/Z compensation. // If Y and Z values aren't defined here, later assignment below will have no effect #1->1000X + 0.1Y + 0.1Z #if MACHINE == 2 #define X_AXIS_X_ADJ (0.55) #define X_AXIS_Y_ADJ (-0.2) #define X_AXIS_Z_ADJ (0.175) #endif X_AXIS_DEF_PRIMARY = X_AXIS_DEF_PRIMARY + X_AXIS_X_ADJ X_AXIS_Y_COMPONENT = X_AXIS_Y_ADJ X_AXIS_Z_COMPONENT = X_AXIS_Z_ADJ What I've learned here is that although the PMAC preprocessor seems similar to the C preprocessor (CPP), it certainly does not behave the same way. In this case, macro expansion. Also, it appears you cannot parenthesize #defines if you are going to use them in conditional preprocessor statements (i.e. "#if MACHINE == 2" evaluates to false if you do #define MACHINE (2). It seems nested macro definitions are allowed in the PMAC preprocessor, but only if they are not used in conditionals like #if/#elif.

I'm trying to define axis definitions in a way that allows me to use multiple machines that would traditionally have separate axis definitions. I'd also like to use the axis definitions to calculate scale factors. Initially I tried to use #if/#elif/#endif to #define relevant components of the axis definitions based on the machine, but the preprocessor doesn't perform macro expansion the way it does in the C preprocessor. #define AXIS_BASE_COUNTS (1000) #define X_AXIS_COMPENSATION (-0.5) #1->(AXIS_BASE_COUNTS + X_AXIS_COMPENSATION)X The axis definition gives an error when trying to download. Judging from the build output, it looks like the preprocessor is not doing macro expansion. Instead just does #1->((1000) + (-0.05))X. As expected, I get an error from that axis definition. I then tried something slightly different, thinking the preprocessor might only allow a single #define in the axis definition, so #define AXIS_BASE_COUNTS (1000) #define X_AXIS_COMPENSATION (-0.5) #define X_AXIS_DEF (AXIS_BASE_COUNTS + X_AXIS_COMPENSATION) #1->(X_AXIS_DEF)X I have the same problem with this approach. Does anyone know if there is a way to conditionally or programatically do axis definitions? I can provide more and/or exact code if it helps. Thanks in advance.

I'm trying to determine if the power requirement listed in the PowerBrick Controller manual includes the current when all outputs are driving a load. It lists logic power as 24V 5A, but does not mention outputs. On the related topic, how much current are the outputs on the PowerBrick Controller capable of sourcing/sinking? I have some 100 mA loads that I would like to drive with the sourcing outputs directly, but I can't find much info in the manual. I noticed the PowerBrick uses the same beefy output FETs that are used in the ACC-65E, and that card's manual lists 0.6A per digital output, or ~300 mA if all 24 outputs are in use. This leads me to believe the PowerBrick digital outputs are also capable of this, but I'm not certain. I suspect I will need to add the current sourced by the digital outputs to the 24V 5A logic power required for the PowerBrick Controller. Can anyone confirm the digital output drive current capability, and that I will need to add this additional current requirement to the logic power?