bkspeedo

iTrader: (5)

Being motor timing is over the entire RPM range of the motor, for shorter tracks (Ex 90' x 50') 0 motor timing and higher boost is better. For larger tracks where there's not as many tight turns and is more open flowing than 10-20deg on the motor with 20-30 on the ESC. When dealing with timing your going to have to test different scenarios as every track is different, but these are decent starting points. The goal is to try and reach 30-40deg total timing.

Also, remember to gear 5-7 teeth (64pitch) less then people running non-timing capable ESC's (ex. Novak GTB)

pakk

iTrader: (80)

What FDR are you guys running at speedworld with a 17.5? I think I'm going to play around there sunday if the weather is good.

--pakk

STLNLST

iTrader: (32)

I believe racers are running 3.9-4.2 I'll double check and post back later. They are racing on Saturday and there will be more help at the track if you can make it then, but if you just want more track time then Sunday is the day to go.

RC MARKET

iTrader: (12)

Hk peoples used RS Pro in stock motor ( 10.5,11.5,13.5,17.5T... )had faster than LRP ESC,
because can change timming

higbo

And at modified?????

RC MARKET

iTrader: (12)

MOD motor not have big different !

Cpt.America

iTrader: (52)

I concur completely. The interface design is just horrible... For one thing, I cannot read the text over the buttons on the right. It looks like black text over dark red/black background. I also have issues moving the sliders... They don't slide from top to bottom with one swipe... you have to sorta move it some of the way, then re-click to move it some more.. re-click to move it some more.. over and over until you get it to the top. Sometimes it will slide all the way to like 95% then stop.

I have another suggestion... when the program is installed, it would be nice to have the version listed right along side the name of the program in the add/remove programs list.

JimmyMac

iTrader: (2)

I agree as well. I mean, the Hotwire interface is cool and fancy, but gets in the way of function. Is there a way to turn off the skin and get a regular window?

bkspeedo

iTrader: (5)

+3 on the interface, need something better without all the graphics.

Besercoe

iTrader: (9)

Try using the interface on an EPC, it doesnt even fit on the screen properly

mangoman

iTrader: (11)

+5

But still luv the RS

over gear

iTrader: (18)

+6 on the interface

Randy_Pike

iTrader: (6)

Ok guys we get it. We're looking into "alternatives." We think that having a different interface for each unit sets them apart. I personally like knowing what esc I'm plugged into by seeing the graphic.

I do understand that some "uses" may require a different size to fit the screen.

As always: You talk, we listen.

Cpt.America

iTrader: (52)

Could be as simple as text in the upper corner displaying what esc you're plugged into, software version, and firmware version. I wouldn't mind this interface at all, if it worked properly... The sliders are broken, and the text is unreadable. The cool design itself isn't bad at all...


Thanks for listening Randy.. we greatly appreciate it. I can't speak for everybody, but it feels REALLY REALLY good buying a product like my new RS and RS pro (yes, i have two), knowing there are guys like you right here on the forums ready to help us out with anything we encounter. For that reason alone, you won't see me running anything else. And when it comes to track days.. that kind of helpful information spreads fast

New kid: "Say... why do you run the tekin?"
Cpt. America "bla bla its the best... bla bla personal help from the guys at Tekin directly on the forums helping out in an incredibly quick fashion..."

It really is invaluable.

Another bug I have, is the text "Descriptions", dont completely show so you almost cannot even read what you are choosing. For example, when you right click the slider that changes it from fw/rv/break, forward / break / no reverse.. it only shows like the first 9 or 10 characters (dont recall exactly, would have to go look), and the rest are just cutoff. I can only assume the one I chose was forward and break only, no reverse.

cosmo1974

iTrader: (3)

Hi All,

(1) The comments appearing on this thread are starting to reflect my own thoughts on the user interface. It does appears as though the Tekin software developers have never programed in a Windows environment before. All very clunky.

(2) I suggest that the software developers follow the Windows programming style guide. The look and feel of the Tekin interface will then fit in with the expected windows experience. If nothing else, Mr Microsoft has brought consistency & practicality to our user interface experience. The use of standard sliders, tick boxes, radio buttons, menu bar, pull down menus, dragable windows, minimisable windows, etc, is what everyone expects. Its a mature user interface and should be used. Yes, there is a learning curve for the software developers but that is for the benefit of the end customer.

(3) There is nothing stopping the inclusion of a graphic in an area of the window which uniquely represents each Tekin product.

(3) I partically dislike the red colour scheme. The human eye has a certain focusing depth of field, and red is right up one end of the colour spectrum. When used with other colours towards the other end of the spectrum, the eye has to continuously refocus on the colours. You are not consciously aware of this, except for annoying eye strain, and later headaches. Once again, the Tekin window should inherit the colour palette selected by the user (colour palette should be the user's preference, not the software developers preference).

(4) I have had young software engineers develop prototype graphical user interfaces for engineering based windows applications. Using one of the many Microsoft development environments, it would take a morning to setup all of the graphical user interface functionality required (in the current hotwire). The development environment then translates the GUI into code, and a set of stubs for the back end software. The back end software can then be added and take whatever software development paradigm you see fit.

(5) If you are planning to add extra functionality, you can put placeholders in the user interface and ghost it out (as you see fit). Every type of user input has been done before, so there are plenty of practical examples around.

Hope this helps future graphical user interface development.
Cheers