Forums
New posts
Search forums
What's new
New posts
Latest activity
Articles
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Lab talk, the good, the bad, and the ugly
Dental-CAM
DWX50 skipping the fine milling stage
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="CoolHandLuke" data-source="post: 106829" data-attributes="member: 4850"><p>we can all concede that certain computers are certainly better than others, however "workstation computer" are not two words that really should go together, as they do not form a coherent phrase. its like saying Amphibious Frog. </p><p></p><p>anyway all that to say the best computer in the world is limited by its software; in most circumstances that software is capable of detecting computational issues such as a memory stack overflow. in this case however it is a lost cause to be going through the computer looking for computational errors; the fault of the software - it is not likely. we've discussed how even doing the simulation in the sum3d has resulted in no error, so no arithmetic is at fault here.</p><p></p><p>i suspect the actual arms of the machine itself are at fault. if memory serves, they are powered and fed data (and controlled feedback) through the old IDE drive cabling, which as we may well know are aluminum wires that are easily broken (especially after repeated bending) and are not as conductive as a braided wire (which would be much easier to short circuit and lose data).</p><p></p><p>i believe the error to be roland-side, because if this were a computer hardware or sum3d error, it might be more prevalent in each user's system. software being so needy with the hardware, and all.</p><p></p><p>i say this based on the experience of working in a past lab where the same *symptom* arose, in completely different machinery, computers, and data transmission. different G code as well. same error - a machining stage was skipped, or more commonly in that system the issue of halting Z axis.</p><p></p><p>no error messages generate in both lab's circumstances. nothing in sum3d now, and nothing in the Laserdenta proprietary nesting code either.</p><p></p><p>the machine is at fault; the question now is how to service it. nobody but glen has been able to provide anything from roland to help with this error, but i got money says he isnt the Service advisor or team lead to robotic machine design.</p></blockquote><p></p>
[QUOTE="CoolHandLuke, post: 106829, member: 4850"] we can all concede that certain computers are certainly better than others, however "workstation computer" are not two words that really should go together, as they do not form a coherent phrase. its like saying Amphibious Frog. anyway all that to say the best computer in the world is limited by its software; in most circumstances that software is capable of detecting computational issues such as a memory stack overflow. in this case however it is a lost cause to be going through the computer looking for computational errors; the fault of the software - it is not likely. we've discussed how even doing the simulation in the sum3d has resulted in no error, so no arithmetic is at fault here. i suspect the actual arms of the machine itself are at fault. if memory serves, they are powered and fed data (and controlled feedback) through the old IDE drive cabling, which as we may well know are aluminum wires that are easily broken (especially after repeated bending) and are not as conductive as a braided wire (which would be much easier to short circuit and lose data). i believe the error to be roland-side, because if this were a computer hardware or sum3d error, it might be more prevalent in each user's system. software being so needy with the hardware, and all. i say this based on the experience of working in a past lab where the same *symptom* arose, in completely different machinery, computers, and data transmission. different G code as well. same error - a machining stage was skipped, or more commonly in that system the issue of halting Z axis. no error messages generate in both lab's circumstances. nothing in sum3d now, and nothing in the Laserdenta proprietary nesting code either. the machine is at fault; the question now is how to service it. nobody but glen has been able to provide anything from roland to help with this error, but i got money says he isnt the Service advisor or team lead to robotic machine design. [/QUOTE]
Insert quotes…
Verification
Who do we work for?
Post reply
Forums
Lab talk, the good, the bad, and the ugly
Dental-CAM
DWX50 skipping the fine milling stage
Top
Bottom