Remap of M6 not working correctly
- viesturs.lacis
- Offline
- Premium Member
- Posts: 108
- Thank you received: 4
Biesse.ini is my version, based on sample config of racktoolchange.iniJust noticed this, there are two ini files in that config. Are you running 'Biesse.ini' or ''racktoolchange.ini'?
Please Log in or Create an account to join the conversation.
- viesturs.lacis
- Offline
- Premium Member
- Posts: 108
- Thank you received: 4
I am using remap/racktoolchange sample config as my starting point. It did work in simulation, but I do not get any movement when I edit ini file for axis/joints sections, add glade panels and my HAL files. I do not touch [RS274NGC] and [PYTHON] sectionsThe other thing (but maybe of no importance here) is that your ini files use FEATURES in the [RS274NGC] section
# turn on all optional features except RETAIN_G43 FEATURES= 30 which has been replaced by individual entries: [attachment=65601]Features.png[/attachment]
Please Log in or Create an account to join the conversation.
I am using remap/racktoolchange sample config as my starting point. It did work in simulation, but I do not get any movement when I edit ini file for axis/joints sections, add glade panels and my HAL files.
I see. Trying to edit a sim config to run physical hardware comes with a lot of potential pitfalls.
I would very much recommend to do this the other way around. Create a config that runs your hardware and then add the M6 remap to that.
Please Log in or Create an account to join the conversation.
- viesturs.lacis
- Offline
- Premium Member
- Posts: 108
- Thank you received: 4
That was my first approach - I had a working config and I copied in all the bits of remap from a config of previous retrofit. But got all kinds of errors that ngc file not found although I could not find any mistake where subroutine folders are specified. I even copied from sample config and recreated the folders but still error. But in sample config it did work so I went the other route of merging my stuff into sample config
I am using remap/racktoolchange sample config as my starting point. It did work in simulation, but I do not get any movement when I edit ini file for axis/joints sections, add glade panels and my HAL files.
I see. Trying to edit a sim config to run physical hardware comes with a lot of potential pitfalls.
I would very much recommend to do this the other way around. Create a config that runs your hardware and then add the M6 remap to that.
Please Log in or Create an account to join the conversation.
But got all kinds of errors that ngc file not found although I could not find any mistake where subroutine folders are specified.
can you post this config and the exact errors you are getting?
Please Log in or Create an account to join the conversation.
- viesturs.lacis
- Offline
- Premium Member
- Posts: 108
- Thank you received: 4
There are no errors, everything looks as if g-code file is being executed - I can pause, resume, execute next line, stop, you name it. But nothing actually happens. Running normal g-code files is ok, I have made quite a few test parts
Should I make a video of that?
Please Log in or Create an account to join the conversation.
So if you have a tool-change (ie M6 T..) inside a gcode then the file executes all the way with the toolchange being ignored?Running normal g-code files is ok, I have made quite a few test parts
What I meant is post the first config you added the remap to and the errors you got there before you modified the sim config. The problem with the current situation is that nothing happens and there are no errors which makes troubleshooting very difficult.Config is in first post, starts with Biesse.ini
Please Log in or Create an account to join the conversation.
net tool-change iocontrol.0.tool-change iocontrol.0.tool-changed
[edit]
for troubleshooting it might also make sense to use the 'show halconfiguration' to watch the iocontrol.* pins like
iocontrol.0.tool-prepare
iocontrol.0.tool-prepared
iocontrol.0.tool-change
[edit2]
Just so we are on the same page, I presume you have tried the suggested (ie reversed M6 T..):
T.. M6
Please Log in or Create an account to join the conversation.
- viesturs.lacis
- Offline
- Premium Member
- Posts: 108
- Thank you received: 4
Now that you mention it, yes, I do not remember putting these iocontrol pins anywhere. I knew that I might be making some stupid mistake. I guess I will go to workshop to check although I just put kids to sleep.I think you might be missing this in your hal file:
net tool-change iocontrol.0.tool-change iocontrol.0.tool-changed
To be honest, no, I did not try that because on previous retrofit it worked. IMHO specifying M command and then its parameters makes sense, doing other way around feels awkward and wrong. But ok, I will try that.
[/code][/code][code]Just so we are on the same page, I presume you have tried the suggested (ie reversed M6 T..): [code]T.. M6
I am testing from MDI. I _think_ that I tried a test file once but am not sure. Ok, that is 3rd point in my list to check.
I will take a look, it is very likely that I have deleted/overwritten it. And the lack of errors is exactly what makes it difficult as I have absolutely no clue where to look. I think that lack of those iocontrol HAL pins seems to be very likely cause, on my way to check that.
Please Log in or Create an account to join the conversation.
- viesturs.lacis
- Offline
- Premium Member
- Posts: 108
- Thank you received: 4
Reversing to Tn M6 did not help.I think you might be missing this in your hal file:
[/code]net tool-change iocontrol.0.tool-change iocontrol.0.tool-changed [edit] for troubleshooting it might also make sense to use the 'show halconfiguration' to watch the iocontrol.* pins like iocontrol.0.tool-prepare iocontrol.0.tool-prepared iocontrol.0.tool-change [edit2] Just so we are on the same page, I presume you have tried the suggested (ie reversed M6 T..): [code]T.. M6
Adding
net tool-change iocontrol.0.tool-change iocontrol.0.tool-changed
net tool-prepare iocontrol.0.tool-prepare iocontrol.0.tool-prepared
net tool-change iocontrol.0.tool-change iocontrol.0.tool-changed
Please Log in or Create an account to join the conversation.