Hello, the error that appears when I disconnect the probe cable and try to change the tool is 916 unexpected contact of the probe, and if I try to lower the z axis the 453 movement appears while the probe is detected.
Actualizacion EMCO VCM 300
Moderator: cnckeith
-
- Posts: 91
- Joined: Thu Jun 24, 2021 1:55 pm
- Acorn CNC Controller: No
- Allin1DC CNC Controller: No
- Oak CNC controller: Yes
- CNC Control System Serial Number: A901029
- DC3IOB: No
- CNC12: Yes
- CNC11: No
- CPU10 or CPU7: No
Re: Actualizacion EMCO VCM 300
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
Re: Actualizacion EMCO VCM 300
Those messages are generated internally by CNC12; not by the PLC program.
Assuming that you have Parameter 18 set correctly, then this would be a bug in CNC12, which Centroid needs to fix.
Please post a current Report, so they can test and reproduce the problem.
CNC12 should not report a probe-tripped condition, regardless of the state of the input specified by Parameter 11, if:
1) The probe is detectable (Parameter 18 is not zero), and
2) The probe is not detected (the input given with Parameter 18 shows the probe is not present).
Assuming that you have Parameter 18 set correctly, then this would be a bug in CNC12, which Centroid needs to fix.
Please post a current Report, so they can test and reproduce the problem.
CNC12 should not report a probe-tripped condition, regardless of the state of the input specified by Parameter 11, if:
1) The probe is detectable (Parameter 18 is not zero), and
2) The probe is not detected (the input given with Parameter 18 shows the probe is not present).
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
-
- Posts: 91
- Joined: Thu Jun 24, 2021 1:55 pm
- Acorn CNC Controller: No
- Allin1DC CNC Controller: No
- Oak CNC controller: Yes
- CNC Control System Serial Number: A901029
- DC3IOB: No
- CNC12: Yes
- CNC11: No
- CPU10 or CPU7: No
Re: Actualizacion EMCO VCM 300
Hello, today I have checked all the parameters and they seem correct, when I disconnect the probe cable, the trigger appears in green on the diagnostic screen and the probe detection appears in red, I don't know what is happening, here I leave the file so that if it is see somethingcncsnw wrote: ↑Mon Jul 22, 2024 2:13 pm Those messages are generated internally by CNC12; not by the PLC program.
Assuming that you have Parameter 18 set correctly, then this would be a bug in CNC12, which Centroid needs to fix.
Please post a current Report, so they can test and reproduce the problem.
CNC12 should not report a probe-tripped condition, regardless of the state of the input specified by Parameter 11, if:
1) The probe is detectable (Parameter 18 is not zero), and
2) The probe is not detected (the input given with Parameter 18 shows the probe is not present).
- Attachments
-
- report_0008DC111213-0504211128_2024-07-23_17-38-50.zip
- (5.37 MiB) Downloaded 1 time
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
-
- Posts: 91
- Joined: Thu Jun 24, 2021 1:55 pm
- Acorn CNC Controller: No
- Allin1DC CNC Controller: No
- Oak CNC controller: Yes
- CNC Control System Serial Number: A901029
- DC3IOB: No
- CNC12: Yes
- CNC11: No
- CPU10 or CPU7: No
Re: Actualizacion EMCO VCM 300
Hello, I don't know if there is any solution for this problem, I have reviewed all the wiring and parameters, it seems like a software error, what can I do, for now I have uninstalled the probe, let's see if something can be done.Oscar6 wrote: ↑Tue Jul 23, 2024 7:34 pmHello, today I have checked all the parameters and they seem correct, when I disconnect the probe cable, the trigger appears in green on the diagnostic screen and the probe detection appears in red, I don't know what is happening, here I leave the file so that if it is see somethingcncsnw wrote: ↑Mon Jul 22, 2024 2:13 pm Those messages are generated internally by CNC12; not by the PLC program.
Assuming that you have Parameter 18 set correctly, then this would be a bug in CNC12, which Centroid needs to fix.
Please post a current Report, so they can test and reproduce the problem.
CNC12 should not report a probe-tripped condition, regardless of the state of the input specified by Parameter 11, if:
1) The probe is detectable (Parameter 18 is not zero), and
2) The probe is not detected (the input given with Parameter 18 shows the probe is not present).
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
Re: Actualizacion EMCO VCM 300
First, try updating your CNC12 software from version 4.20 to version 5.10. It is possible that Centroid has already fixed this issue.
If the same 916 and 453 messages appear when the probe is disconnected, with P17 = +50771 and INP771 open (red), then report it to Centroid as a bug to be fixed.
If the same 916 and 453 messages appear when the probe is disconnected, with P17 = +50771 and INP771 open (red), then report it to Centroid as a bug to be fixed.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
-
- Posts: 91
- Joined: Thu Jun 24, 2021 1:55 pm
- Acorn CNC Controller: No
- Allin1DC CNC Controller: No
- Oak CNC controller: Yes
- CNC Control System Serial Number: A901029
- DC3IOB: No
- CNC12: Yes
- CNC11: No
- CPU10 or CPU7: No
Re: Actualizacion EMCO VCM 300
Hello again, I have looked at the manual to update to the current version, but it says that if I have a customized plc I may have problems, I am a little afraid of ruining what already exists, all this is very complicated. What would you do?cncsnw wrote: ↑Wed Jul 31, 2024 6:47 pm First, try updating your CNC12 software from version 4.20 to version 5.10. It is possible that Centroid has already fixed this issue.
If the same 916 and 453 messages appear when the probe is disconnected, with P17 = +50771 and INP771 open (red), then report it to Centroid as a bug to be fixed.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
Re: Actualizacion EMCO VCM 300
First, you should make a full backup of your c:\cncm directory and all its subdirectories, just to be sure you can revert to v4.20 any time you want to.
Then, since you have an Oak control, (not an Acorn), you can just install v5.10 as an update over the top of your existing 4.20 installation.
When the installer asks you whether you want to install a PLC program, answer "no". You already have a suitable PLC program and macros in place, and you do not want the installer to replace them.
You may find that your virtual control panel (VCP) is incomplete after the update. If so, then post a Report here and we will figure out how to get the current (v5.10) servo_mill_vcp_skin.vcp file installed in place of the old (v4.20) version. In the older software, the Reset button and feedrate override controls were provided automatically by the VCP program. In the new software, those controls need to be defined in the skin .vcp file.
Because of the VCP skin file requirement, I expect that your system will work correctly if you just install v5.10 as an update over v4.20; but if you use Restore Report to copy a report file you made with v4.20, then you will lose the bottom part of the VCP (because the old Report includes the old skin file, which lacks the Reset button and feedrate override controls).
So, install v5.10 as an update over v4.20; verify that the VCP is correct and your basic functions all work; then save a fresh report using v5.10, so that you have a backup you can use without losing the VCP.
Then, since you have an Oak control, (not an Acorn), you can just install v5.10 as an update over the top of your existing 4.20 installation.
When the installer asks you whether you want to install a PLC program, answer "no". You already have a suitable PLC program and macros in place, and you do not want the installer to replace them.
You may find that your virtual control panel (VCP) is incomplete after the update. If so, then post a Report here and we will figure out how to get the current (v5.10) servo_mill_vcp_skin.vcp file installed in place of the old (v4.20) version. In the older software, the Reset button and feedrate override controls were provided automatically by the VCP program. In the new software, those controls need to be defined in the skin .vcp file.
Because of the VCP skin file requirement, I expect that your system will work correctly if you just install v5.10 as an update over v4.20; but if you use Restore Report to copy a report file you made with v4.20, then you will lose the bottom part of the VCP (because the old Report includes the old skin file, which lacks the Reset button and feedrate override controls).
So, install v5.10 as an update over v4.20; verify that the VCP is correct and your basic functions all work; then save a fresh report using v5.10, so that you have a backup you can use without losing the VCP.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
Re: Actualizacion EMCO VCM 300
For what it's worth, the things that you worked hard to make custom for your machine are all in:
- The PLC program, a901029.src and mpu.plc
- The supporting message files, plcmsg.txt and cncxmsg.txt
- Your CNC12 configuration, parameters and WCS files, cncmcfg.xml, cncm.prm.xml and cncm.wcs
As far as I recall, you do not have a custom VCP, and you do not have any custom macros in the c:\cncm\system directory.
- The PLC program, a901029.src and mpu.plc
- The supporting message files, plcmsg.txt and cncxmsg.txt
- Your CNC12 configuration, parameters and WCS files, cncmcfg.xml, cncm.prm.xml and cncm.wcs
As far as I recall, you do not have a custom VCP, and you do not have any custom macros in the c:\cncm\system directory.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)
-
- Posts: 91
- Joined: Thu Jun 24, 2021 1:55 pm
- Acorn CNC Controller: No
- Allin1DC CNC Controller: No
- Oak CNC controller: Yes
- CNC Control System Serial Number: A901029
- DC3IOB: No
- CNC12: Yes
- CNC11: No
- CPU10 or CPU7: No
Re: Actualizacion EMCO VCM 300
Hello, today I updated the software and the panel seems to work correctly, I have not had time to test everything, but it seems to be going well, regarding the probe it seems that it has not been completely solved, now with the probe disconnected the z axis does not work. wants to move down, I can move the axes (x,y) in all directions and z only up, when I start the machine for the first time and it goes to look for the reference switches it starts going up the z but when it goes down there it stays there and doesn't It finishes referencing the axes. It seems that there is a protection in z, but I don't understand why if the probe is disconnected and centroid does not detect it.cncsnw wrote: ↑Sun Aug 04, 2024 2:55 pm First, you should make a full backup of your c:\cncm directory and all its subdirectories, just to be sure you can revert to v4.20 any time you want to.
Then, since you have an Oak control, (not an Acorn), you can just install v5.10 as an update over the top of your existing 4.20 installation.
When the installer asks you whether you want to install a PLC program, answer "no". You already have a suitable PLC program and macros in place, and you do not want the installer to replace them.
You may find that your virtual control panel (VCP) is incomplete after the update. If so, then post a Report here and we will figure out how to get the current (v5.10) servo_mill_vcp_skin.vcp file installed in place of the old (v4.20) version. In the older software, the Reset button and feedrate override controls were provided automatically by the VCP program. In the new software, those controls need to be defined in the skin .vcp file.
Because of the VCP skin file requirement, I expect that your system will work correctly if you just install v5.10 as an update over v4.20; but if you use Restore Report to copy a report file you made with v4.20, then you will lose the bottom part of the VCP (because the old Report includes the old skin file, which lacks the Reset button and feedrate override controls).
So, install v5.10 as an update over v4.20; verify that the VCP is correct and your basic functions all work; then save a fresh report using v5.10, so that you have a backup you can use without losing the VCP.
(Note: Liking will "up vote" a post in the search results helping others find good information faster)