Centroid Community CNC Support Forum

Is there documentation somewhere that tells the canned actions or logic scenario behind the Output Assignments?

For example, "NoFaultOut" toggles on after successful boot sequence. Do any of the others have action or logic behind them?

Thanks, GC

Gary Campbell wrote: ↑Thu Jan 18, 2018 9:38 am Is there documentation somewhere that tells the canned actions or logic scenario behind the Output Assignments?

For example, "NoFaultOut" toggles on after successful boot sequence. Do any of the others have action or logic behind them?

Thanks, GC

Looking for this as well.
Clay

Is there a document that explains what turns on these outputs? I assume it's part of the PLC, but not sure where to look.

I possibly want some custom functionality, but need to see how everything works.

Thanks,

Clay

frijoli wrote: ↑Thu Jan 18, 2018 10:31 am Is there a document that explains what turns on these outputs? I assume it's part of the PLC, but not sure where to look.

I possibly want some custom functionality, but need to see how everything works.

Thanks,

Clay

Can you explain in a systemic sequence what you want to occur exactly? That should be nailed down first. PLC can be modified.
I think Keith posted the PLC manual before. Here is a link:
http://www.centroidcnc.com/downloads/CN ... Manual.pdf
I'm not that gutsy right now.
I learned recently on a PLC mod how things are some functions are "intertwined" so you really need to know as you say, how everything works and understand when you touch one thing, you may affect the operation of another function....with uninteneded consequences.

Marty

martyscncgarage wrote: ↑Fri Jan 19, 2018 12:52 am

frijoli wrote: ↑Thu Jan 18, 2018 10:31 am Is there a document that explains what turns on these outputs? I assume it's part of the PLC, but not sure where to look.

I possibly want some custom functionality, but need to see how everything works.

Thanks,

Clay

Can you explain in a systemic sequence what you want to occur exactly? That should be nailed down first. PLC can be modified.
I think Keith posted the PLC manual before. Here is a link:
http://www.centroidcnc.com/downloads/CN ... Manual.pdf
I'm not that gutsy right now.
I learned recently on a PLC mod how things are some functions are "intertwined" so you really need to know as you say, how everything works and understand when you touch one thing, you may affect the operation of another function....with uninteneded consequences.

Marty

At this point in the game, I'm not going to change anything. I just want to understand what does what. This all ties back to my spindle control.
The wizard is great for setting up standard systems, but I've never been a wizard kind of guy...

Clay

Marty, et al...
I too have interest in this info, asked here: viewtopic.php?f=60&t=1401

When you say: "some functions are "intertwined" so you really need to know as you say, how everything works and understand when you touch one thing, you may affect the operation of another function....with unintended consequences." Is the exact reason that I seek the knowledge. Being a "routerhead" I have no idea how or why a machinist would want or use the majority of the functions on the button names, let alone the terminology listed in the drop box in the Wizard for outputs.

That said, there is a lot in common between mills and router tables and I am sure that if there was a little info those same "behind the scene" actions are similar or usable to add feature to router tables that are being upgraded to Acorn.

The function of NoFaultOut is what it's name indicates it is. It means the control is not in a Fault/Reset condition. Typically it is used in the Estop loop so if the control or a peripheral reports a fault, the output turns off dropping the coil voltage to the Estop contactor. In a properly wired system, a NoFaultOut output should be included in every system.

The boot sequence in and of itself has nothing to do with the state of NoFaultOut. If NoFaultOut is on when the software starts, it simply means that there are no faults detected. Keep in mind that, if you close the Acorn software and restart the software without power cycling the Acorn, you WILL be in a fault condition when the software starts. This is because the Acorn hardware and the software send keep alive packets to monitor the hardware and software status. When you close the software, the Acorn hardware can no longer communicate with the software so it puts the hardware in a fault condition. When this happens, simply cycle estop and/or the VCP reset to clear

Most I/O have comments included in the source code. For instance, this is the section that handles flood coolant:

;--Flood coolant on/off
;
; Toggle on/off or off/on if:
; In manual mode and a toggle key was pressed
; Turn on if:
; In auto mode and have M8
; Turn off if:
; Any fault or error
; In auto mode and don't have M8
; Doing tool check (?)
IF CoolFloodKey || KbFloodOnOff_M || SkinCoolFlood_M THEN (CoolantFloodPD)
IF ((Flood ^ (!CoolAutoModeLED && CoolantFloodPD))
|| CoolAutoModeLED && M8)
&& !(SV_STOP ||
CoolAutoModeLED && !M8 ||
ErrorFlag_M ||
DoToolCheck)
THEN (Flood), (CoolFloodLED), (SelectCoolantFlood)

Most I/O have comments in the source code that explains how they work.

For flood coolant:

;--Flood coolant on/off
;
; Toggle on/off or off/on if:
; In manual mode and a toggle key was pressed
; Turn on if:
; In auto mode and have M8
; Turn off if:
; Any fault or error
; In auto mode and don't have M8
; Doing tool check (?)
IF CoolFloodKey || KbFloodOnOff_M || SkinCoolFlood_M THEN (CoolantFloodPD)
IF ((Flood ^ (!CoolAutoModeLED && CoolantFloodPD))
|| CoolAutoModeLED && M8)
&& !(SV_STOP ||
CoolAutoModeLED && !M8 ||
ErrorFlag_M ||
DoToolCheck)
THEN (Flood), (CoolFloodLED), (SelectCoolantFlood)

Where is this data located? Is it a single program or many subroutines?