![]() Downright stupid that this was left unsecured in a position that could easily crash the model. The "spare" wire and servo plug left floating around loose (and able to get into the tail servo rod and drive ) is apparantly an external governor line from the ESC, not used. Have not as yet set up "Panic" mode, but it is now flying. Has anyone set up Panic on a early DX9 without the GYR parameter, and if so how please? I note that the 230S and 130S both use a simpler system of allocating Aux2 to Switch I, and even the 360 Fusion manual shows a simpler set up for a DX8. It does not have Gyro as a mix option, so the manual mix which makes Panic effective is not able to be set. My grey case DX9 cannot have any firmware alteration or I will lose DSM2 (Euro). What does this extra wire do, and should it be connected?Ĭan't find any explanation in manual, HH not replying to support query, anyone with one, please inform or show pic?Ģ. I have six plugs connected without anything in channel 6/this floating plug. There is also an unused "spare" socket on the FC, Channel 6.ĭid the plug fall out of socket in transport? The only picture I can find online of this close up shows six plugs connected but is not that clear where, and does nto show this "extra" plug and wire. This comes from the ESC and is a single Orange wire in the signal position, this in addition to the usual Red/White/Black from the ESC in another more usual plugged in connection to throttle. On my newly delivered 360 there is a plug floating loose. I may be forced to gradually swap out the differing content and repost my trial CAM file to see what is causing it.īoth posts contain the same section for outputting G28 in either XZ or UW, so I'm guessing something has been broken, preventing it from functioning as it originally did:įor (var i = 0 i < retractAxes.Well, my newly delivered one is causing some concern before its even switched on :-ġ. I don't see any obvious major structural / content differences, so I wonder if the loss of G28 function was due to a subtle but unintentional formatting / syntax change due to insertion or deletion of a space in a critical statement. All the previous versions are available in the Fusion post libraryĤ3462 Added the ability to specify the coolant codes as a text string.Ĥ3418 Fixed undesired expansion of tapping cycle in generic turning posts.ĭoing a file compare in VSC shows the 2 authors had different styles when it came to spaces and tabs, which accounts for most of the differences. Seems somebody may have screwed up a perfectly functional G28 feature when changing something else.īottom line is that previous version (r43417) outputs X & Z, so one simple fix is to revert back. It seems that r43470 and r43462 output U and W, while the previous version r43417 correctly outputs X and Z. I seem to have the last 3 versions reversed in my mind. Hmm, yes, that's forced me to look again. Please Log in or Create an account to join the conversation. I've checked it and it works, so I am now back to using my preferred G28. But it's worth installing the latest version if you want to use G28 instead of G53 coords at the end of your file. They don't seem to have published any release notes, so I've no idea what else they changed and I can't be bothered to diff it to find out right now. So now a G28 will set coordinates in X and Z rather than U and W. It seems to be dated September 2021, although I'm pretty certain it hadn't been released when we were posting about this back in October. Incidentally, Autodesk recently updated the LinuxCNC lathe post processor with the G28 U/W issue corrected. The lathe CAM still seems a bit buggy, so I'm being fairly cautious in how I use it. ![]() I suspect they consider the lathe CAM to be largely complete now, so don't have any / much effort planned to support it and to be fair, the milling CAM is an order of magnitude more complex and wider ranging, with a much bigger user (paying subscriber) base. ![]() I might give it a go and see what if anything transpires. ![]() Perhaps worth asking them to look into it but TBH, their response to Alkabal's query on the matter was pretty dismissive, despite him and Andy Pugh pointing out that they'd misunderstood how LinuxCNC interprets the U/W output.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |