Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Wall-E

Pages: [1] 2 3 4
Support / Enhancement wishes for the "Analysis" window
« on: January 28, 2020, 09:14:28 AM »
I attached a "mock-up" of a possible evolution of the "Analysis" window.

First and foremeost, I think that priority should be given to respect the execution speed (or percentage of execution speed selected by the user), and that the framerate should always adapt.
In other words, the framerate should always be as high as possible for a given simulation speed , and that for two reasons :
-Who would set a crappy framerate on purpose anyways ?
-Who would want the simulation to not reflect the intended speed ?

If, despite a slower framerate, the simulation can not reflect the desired speed, then there should be a WARNING ! sign because it is not accurate, and accuracy is a desired attribute of a simulation.

Then I added a regular slider to make a "rough" positionning, and would use the white dotted line to make more accurate positionning.

The traditionnal buttons would be used to  "Play" and "Stop" of course, but also "go to start" and "go to end", which is not easy to do with the present interface.


Support / Animation stops randomly
« on: January 27, 2020, 07:51:23 PM »
As can be seen in this video :

The animation stops randomly, and it needs to be prodded by the "dotted slider line" to resume.

I think it would be nice to have an option  for not displaying the path which lies before the current animation frame (the one that has already been traveled trhough).
That would probably speed the animation as less and less path has to be drawn, and in some cases make things clearer.

What do you think ?

Support / Jump to a line number ?
« on: January 15, 2020, 05:36:53 PM »
Sorry for this question not directly related to KUKA|prc, but : once a program is selected, how can I jump to a certain line ?
The "Escalator" slider is super slow in a program with over 25 000 lines...

General Discussion / (Another) Fusion 360 NC import wish
« on: October 16, 2018, 02:41:07 PM »
I have set a specific value for the "Rapid" input in the "Fusion" component, but I can see that value defined nowhere in the .SRC file
I wish that there was an input to over-ride whatever process speed is defined in the .xml file exported from fusion, and that the "Rapid" input actually affects the speed of travel in the "hops" between actual milling.

General Discussion / WISH : Analysis - Null Axis values if out of range
« on: September 19, 2018, 06:04:00 PM »
I wish that the Analysis output for Angles were null for each axis which is out of range.
This would allow to make custom axis value displays as in the attached, but with a specific warning for the relevant axis.

General Discussion / WISH : "Official" enhanced "Tool axis offset" component
« on: September 17, 2018, 07:28:07 PM »
Hi Johannes,

You remember I asked for an enhancement of the "Tool axis offset" component which would allow to control independently the speeds of the various phases of travel :
-"Flyover" speed (typically high to avoid losing time between operations
-"Dive" speed (Typically a bit lower)
-"Process" speed -> Here, I actually wish there was no input since the speed is set upstream ; this component should only be relevant to the offset movements and the "Flyover".
-"Retract" speed

Thoughts ?

General Discussion / Fusion 360 NC import wish
« on: August 18, 2018, 07:12:56 PM »
I wish it was possible to apply a transform to the paths defined by a "Fusion 360 NC import" component.
I feel that it would be more natural and easy than to mess with the Base coordinates.

General Discussion / Carthesian offset writes no values
« on: August 09, 2018, 05:08:50 PM »
Carthesian offset writes no values in this case ...

General Discussion / "Wait" component writes no time value
« on: August 09, 2018, 05:05:19 PM »
"Wait" component writes no time value .
How does the controller know how long to wait then ?

The new "Tool offset" component turns "PTP" commands into "LIN" commands.
Why ?

General Discussion / Bug with custom tool
« on: August 09, 2018, 02:14:58 PM »
When I opened my definition today, the custom tool mesh had disappeared, and the tool effector point was on the robot flange.
I plugged in a new "Custom tool" component, and everything went back to normal.
Bug ?

Hi Johannes,

I started reading the KRL documentation after three years of owning Wall-E :)
I realize that the .src generated by KUKA|prc uses a "E6POS" data type to define the trajectories, and this includes 4 values for external axis.
Since I have no external axis, it would make the files much smaller if I could toggle an option to use just a "POS" data type with no external axis values.
Specially for milling, this would allow me to generate longer tool paths...

Would you consider including such an option in the main component ?


Support / More evolved "Play/Pause" component please
« on: March 11, 2018, 06:43:32 PM »
I think that the "Play-Pause" component should have a more evolved UI which would include :
-A slider
-The Analysis graph
-A "speed" option to accelerate or display the kinematics in slow motion

Support / Suggestion for the robot list
« on: March 11, 2018, 06:23:50 PM »
I think that the robot list would be better hidden in a component's specific UI instead of all the tiny icons.
This would free the "02|Virtual Robot" toolbar , and the dialog box that would pop-up when clicking the "Robot choice" component would display for example high-resolution thumbnails of the various robots, with a few data points.
This occured to me because I often find myself fumbling around in the robot icons to find my specific model. Moreover, there are multiple robots called KR6, and the tiny icons really don't help much in picking the right one.
This tool could even include the "Custom robot", and allow to adjust the angle parameters in an existing robot, without having to fully define a custom robot.
For example, I'd be able to tweak the Axis 3 angles of my KR6-arc for which the range seems slightly more narrow than the preset values, and programs often fail because of this : "Axis 3 angle exceeded !".

Pages: [1] 2 3 4