the trace mark erase option

[spsid13]

So the the gluing I/O for example makes a trace when the program is run.. but now I want erase the trace and run the program again.

[neoaero99]

If you disable the trace with the button in the miscellaneous menu, then the trace will be cleared.

On Jul 7, 2017 05:59, "spsid13" notifications@github.com wrote:

So the the gluing I/O for example makes a trace when the program is run.. but now I want erase the trace and run the program again.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218, or mute the thread https://github.com/notifications/unsubscribe-auth/ANdpJi-nw8Xen-1JRZlv73fpxXio0wXRks5sLgGFgaJpZM4OQvYv .

[spsid13]

No its not working..

On Fri, Jul 7, 2017 at 7:17 AM, Joshua Hooker notifications@github.com wrote:

If you disable the trace with the button in the miscellaneous menu, then the trace will be cleared.

On Jul 7, 2017 05:59, "spsid13" notifications@github.com wrote:

So the the gluing I/O for example makes a trace when the program is run.. but now I want erase the trace and run the program again.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218, or mute the thread https://github.com/notifications/unsubscribe-auth/ANdpJi-nw8Xen- 1JRZlv73fpxXio0wXRks5sLgGFgaJpZM4OQvYv .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313654970, or mute the thread https://github.com/notifications/unsubscribe-auth/AQarXQBOUEj1uPcrFsTs2qhrakx2wOCwks5sLhPdgaJpZM4OQvYv .

-- Siddharth Parmar Mechanical Engineer 248-516-9390

[vtdrusch]

I'll take a look at this and let you know when I have a new release.

On Jul 7, 2017 8:24 AM, "spsid13" notifications@github.com wrote:

No its not working..

On Fri, Jul 7, 2017 at 7:17 AM, Joshua Hooker notifications@github.com wrote:

If you disable the trace with the button in the miscellaneous menu, then the trace will be cleared.

On Jul 7, 2017 05:59, "spsid13" notifications@github.com wrote:

So the the gluing I/O for example makes a trace when the program is run.. but now I want erase the trace and run the program again.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218, or mute the thread https://github.com/notifications/unsubscribe-auth/ANdpJi-nw8Xen- 1JRZlv73fpxXio0wXRks5sLgGFgaJpZM4OQvYv .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313654970, or mute the thread https://github.com/notifications/unsubscribe-auth/ AQarXQBOUEj1uPcrFsTs2qhrakx2wOCwks5sLhPdgaJpZM4OQvYv .

-- Siddharth Parmar Mechanical Engineer 248-516-9390 <(248)%20516-9390>

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313666960, or mute the thread https://github.com/notifications/unsubscribe-auth/AHZyl6vyaXZOT8e7sko8roXjSoF_BcNaks5sLiNggaJpZM4OQvYv .

[spsid13]

Thanks Vince.

On Fri, Jul 7, 2017 at 10:02 AM, Vincent Druschke notifications@github.com wrote:

I'll take a look at this and let you know when I have a new release.

On Jul 7, 2017 8:24 AM, "spsid13" notifications@github.com wrote:

No its not working..

On Fri, Jul 7, 2017 at 7:17 AM, Joshua Hooker notifications@github.com wrote:

If you disable the trace with the button in the miscellaneous menu, then the trace will be cleared.

On Jul 7, 2017 05:59, "spsid13" notifications@github.com wrote:

So the the gluing I/O for example makes a trace when the program is run.. but now I want erase the trace and run the program again.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218, or mute the thread https://github.com/notifications/unsubscribe-auth/ANdpJi-nw8Xen- 1JRZlv73fpxXio0wXRks5sLgGFgaJpZM4OQvYv .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313654970, or mute the thread https://github.com/notifications/unsubscribe-auth/ AQarXQBOUEj1uPcrFsTs2qhrakx2wOCwks5sLhPdgaJpZM4OQvYv .

-- Siddharth Parmar Mechanical Engineer 248-516-9390 <(248)%20516-9390> <(248)%20516-9390>

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313666960, or mute the thread https://github.com/notifications/unsubscribe-auth/ AHZyl6vyaXZOT8e7sko8roXjSoF_BcNaks5sLiNggaJpZM4OQvYv

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313690993, or mute the thread https://github.com/notifications/unsubscribe-auth/AQarXZcn_OfmrdiNij4FyFpkCiUz0sviks5sLjpagaJpZM4OQvYv .

-- Siddharth Parmar Mechanical Engineer 248-516-9390

[vtdrusch]

Could you describe how exactly you found this bug? To test the trace function, I just made a short program and enabled tracing through the misc. menu, but I haven't been able to reproduce the problem yet on the most recent build.

[spsid13]

so turn on the I/O for gluing make the robot move and turn the I/O off.. when you run this program it will leave a trace for the robots movements. Now there isn't a way to get rid of that trace.

On Fri, Jul 7, 2017 at 3:41 PM, Vincent Druschke notifications@github.com wrote:

Could you describe how exactly you found this bug? To test the trace function, I just made a short program and enabled tracing through the misc. menu, but I haven't been able to reproduce the problem yet on the most recent build.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313774759, or mute the thread https://github.com/notifications/unsubscribe-auth/AQarXfz6kZeapHsVFqEu6Vy7oaMQtHOmks5sLonPgaJpZM4OQvYv .

-- Siddharth Parmar Mechanical Engineer 248-516-9390

[spsid13]

by turning on IO i mean write a program that says IO[4] = ON p1 p2 p3 IO[4] = Off

On Fri, Jul 7, 2017 at 3:42 PM, Siddharth Parmar syparmar@mtu.edu wrote:

so turn on the I/O for gluing make the robot move and turn the I/O off.. when you run this program it will leave a trace for the robots movements. Now there isn't a way to get rid of that trace.

On Fri, Jul 7, 2017 at 3:41 PM, Vincent Druschke <notifications@github.com

wrote:

Could you describe how exactly you found this bug? To test the trace function, I just made a short program and enabled tracing through the misc. menu, but I haven't been able to reproduce the problem yet on the most recent build.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313774759, or mute the thread https://github.com/notifications/unsubscribe-auth/AQarXfz6kZeapHsVFqEu6Vy7oaMQtHOmks5sLonPgaJpZM4OQvYv .

-- Siddharth Parmar Mechanical Engineer 248-516-9390 <(248)%20516-9390>

-- Siddharth Parmar Mechanical Engineer 248-516-9390

[vtdrusch]

I managed to clear the trace after running this program by clicking on the "Enable Trace" button in the miscellaneous menu, then pressing the same button again once the trace is enabled (it should then read "Disable Trace"). If this does not clear the trace for you, could you look in your I/O register menu and tell me if your I/O register was correctly set to OFF? Pressing the "Disable Trace" button should clear the trace, from the screen, but only if the I/O register associated with your current end effector is set to off as well (although I agree this is somewhat confusing, and I plan on adding a button to explicitly clear the trace, I just want to make sure there aren't any other problems preventing you from clearing the trace with the current version of the software).

[spsid13]

It worked with the I/O off. Also can you assign the F key for turning IO on and off in the I/O menu.

Yaa, it would be great if you could add a clear trace button that is independent of I/o being on/off. Please let me know when you update and push a build with these two changes.

On Fri, Jul 7, 2017 at 4:05 PM, Vincent Druschke notifications@github.com wrote:

I managed to clear the trace after running this program by clicking on the "Enable Trace" button in the miscellaneous menu, then pressing the same button again once the trace is enabled (it should then read "Disable Trace"). If this does not clear the trace for you, could you look in your I/O register menu and tell me if your I/O register was correctly set to OFF? Pressing the "Disable Trace" button should clear the trace, from the screen, but only if the I/O register associated with your current end effector is set to off as well (although I agree this is somewhat confusing, and I plan on adding a button to explicitly clear the trace, I just want to make sure there aren't any other problems preventing you from clearing the trace with the current version of the software).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skuhl/RobotRun/issues/218#issuecomment-313779932, or mute the thread https://github.com/notifications/unsubscribe-auth/AQarXf5zMWMXIqwWHxY1XaIcoSr4oPBIks5sLo-EgaJpZM4OQvYv .

-- Siddharth Parmar Mechanical Engineer 248-516-9390

[vtdrusch]

I've implemented these features and will be uploading a new build with these changes in about an hour.

Turning the trace function on and off no longer clears the current trace, this must now be done explicitly by pressing the "Clear Trace" button that I've included in the miscellaneous menu. Pressing CTRL+F on your keyboard will now also toggle the state of the I/O register corresponding to your currently selected end effector.

Unfortunately, while these changes should allow the user to create multiple disjoint trace lines in theory, the way that we currently store and render the trace line means that any trace segments created by repeatedly toggling the trace function on and off will still be connected. I plan to fix this in a future update, but it might take some time to implement.

[neoaero99]

I probably should have mentioned this earlier, but Ctrl+P will toggle the state of the active end effector of the active robot. It has been implemented for some time.