Tekin RSX Thread
#1261
Tech Apprentice
Joined: Oct 2011
Posts: 55
From: Canada
That number is a value we use to determine the throttle calibration point. Your model maybe a little different between the two. For example if you calibrate at 100% on your epa's vs 140 or 150% on some radios will show a different value in the data log.
As long as you're getting WOT or wide open throttle which you can verify with your ESC's LED tree showing all LED's ramping up and flashing you're good to go.
As long as you're getting WOT or wide open throttle which you can verify with your ESC's LED tree showing all LED's ramping up and flashing you're good to go.
On the ESC it does show the lights ramp up on throttle and does show full blinky at full.
I was thinking the datalogging was showing that the throttle was very slightly flickering from 100% to like 99%. I've set the endpoints on the esc to the radio several times with the same result.
#1264
Joined: Mar 2008
Posts: 5,719
From: At dirt tracks in Michigan!
Unless they have Low ESR capacitors, I wouldn't get any from there. If they do, then look for one rated for 16 to 20 volts with a microfarad (mF) rating of 330 or greater.
#1265
Tech Adept
Joined: Mar 2017
Posts: 101
Hey all... I'm pretty new to rc cars, and recently got a RSX for my Tekin Gen 3 8.5t motor. Running it in a Losi SCT22 3.0.
The track I'm running at is really small and very slick surface and I've found that I need a lot of brakes. I ran another guy's car and I was able to hit the brakes at times to kick the rear end around. Now, I know in most cases, it's probably better to steer around corners, but on this given track, having the ability to "lock up" the rear end provides really beneficial.
I've been using the Hotwire to program via my laptop but I just can't seem to get it right. What I'm hoping to achieve is if I'm applying throttle, and rapidly push forward (reverse) on the trigger, the brakes apply and stop the wheels. I've got it tuned now so it slows the car in a pretty short distance, but still not quite aggressive enough. Would anyone be willing to point me in the right direction for this?
Any help is greatly appreciated.
The track I'm running at is really small and very slick surface and I've found that I need a lot of brakes. I ran another guy's car and I was able to hit the brakes at times to kick the rear end around. Now, I know in most cases, it's probably better to steer around corners, but on this given track, having the ability to "lock up" the rear end provides really beneficial.
I've been using the Hotwire to program via my laptop but I just can't seem to get it right. What I'm hoping to achieve is if I'm applying throttle, and rapidly push forward (reverse) on the trigger, the brakes apply and stop the wheels. I've got it tuned now so it slows the car in a pretty short distance, but still not quite aggressive enough. Would anyone be willing to point me in the right direction for this?
Any help is greatly appreciated.
#1266
Joined: Mar 2008
Posts: 5,719
From: At dirt tracks in Michigan!
Hey all... I'm pretty new to rc cars, and recently got a RSX for my Tekin Gen 3 8.5t motor. Running it in a Losi SCT22 3.0.
The track I'm running at is really small and very slick surface and I've found that I need a lot of brakes. I ran another guy's car and I was able to hit the brakes at times to kick the rear end around. Now, I know in most cases, it's probably better to steer around corners, but on this given track, having the ability to "lock up" the rear end provides really beneficial.
I've been using the Hotwire to program via my laptop but I just can't seem to get it right. What I'm hoping to achieve is if I'm applying throttle, and rapidly push forward (reverse) on the trigger, the brakes apply and stop the wheels. I've got it tuned now so it slows the car in a pretty short distance, but still not quite aggressive enough. Would anyone be willing to point me in the right direction for this?
Any help is greatly appreciated.
The track I'm running at is really small and very slick surface and I've found that I need a lot of brakes. I ran another guy's car and I was able to hit the brakes at times to kick the rear end around. Now, I know in most cases, it's probably better to steer around corners, but on this given track, having the ability to "lock up" the rear end provides really beneficial.
I've been using the Hotwire to program via my laptop but I just can't seem to get it right. What I'm hoping to achieve is if I'm applying throttle, and rapidly push forward (reverse) on the trigger, the brakes apply and stop the wheels. I've got it tuned now so it slows the car in a pretty short distance, but still not quite aggressive enough. Would anyone be willing to point me in the right direction for this?
Any help is greatly appreciated.
Once that is confirmed, check your Brake strength setting and increase it to 100. This can be done directly on the speed control without hotwire. After that, you can go into the active brakes setting in hotwire. This feature is kind of a panic brake that will apply the brakes very aggressively if you quickly apply the brakes as opposed to easing onto them. Increase the number to make the panic brake setting more prevalent.
If this still doesn't get you the strength you need, then it might be more mechanical then electrical. What pinion and spur are you using? Going to a lower gear ratio (larger spur or smaller pinion) will give the motor more leverage on the drivetrain and multiply the strength of the brakes. If you don't need any more top speed, then going to a smaller pinion will get you more brakes. You could also switch to a larger diameter rotor for more brakes as well. I believe the stock rotor is 12.5mm, so you could pick up a 13mm High Torque rotor and you will have more braking power as well.
Another factor to consider is that your friend was using a different motor that has more natural drag built into it or was using a 4 pole motor that can generate more braking strength.
#1267
Some issues I'm experiencing with 258:
When you save a profile/program, the firmware version is wrong in the profile log, it's mistyped as Version "2" (in stead of "258"), so now it gives you the incorrect firmware error when you try to reload that profile, and worse, won't actually load any profile settings at all, just leaves you with the default settings again.
Secondly, since the "hold brakes to erase datalog" isn't turned on by default (?), and the setting gets reset during the firmware update, you have to do a run, go back in, and then make the selection. However, when you do this, at least on mine, it then does a complete factory reset, and you have to start over from the beginning. At this point, I am not able to activate the hold brakes to clear feature because of this.
Unfortunately I didn't discover either of these errors until after I updated and reprogrammed all 9 of my RSX's, so that's 2hrs the first time, then almost another 2hrs to redo them all...
I was the guy that had the problem with 255 where they would reset to factory settings after the 255 update and calibration. Sent in the profile data files, etc. that you asked I send, never got any response.
I finally determined that it was because I had used my previous 250 profiles to reload my settings into 255, and something was off in the checksum's in the compiler so it was resetting itself to factory defaults. So entering all of my settings manually was the final work-around. Wasn't a problem this time, lol, as the 258 profile saving error appears to render them completely useless from the beginning.
Aside from the above problems, in future, clearly indicating if previous profiles are, or are not, compatible with the new firmware would be very helpful.
It's hard to post problems without it coming off as negative, and certainly this was a frustrating half day spent just to update firmware, but please don't read it as anything but a little frustration. I like the RSX, and appreciate the new and exciting features you continue to bring out for the existing platform. It's drivability has continued to improve, especially the drive and brake frequencies! I'm looking forward to IOS Hotwire 3, and hope there's some way to save and reload profiles cleanly and quickly and so greatly reduce this firmware update time. I also understand most don't have 9 of these they have to go through. First world problems! Keep up the good work, just maybe a little more beta testing before release, these are some pretty basic features that got missed in this update (unless it's completely some issue on my end, which is always possible).
When you save a profile/program, the firmware version is wrong in the profile log, it's mistyped as Version "2" (in stead of "258"), so now it gives you the incorrect firmware error when you try to reload that profile, and worse, won't actually load any profile settings at all, just leaves you with the default settings again.
Secondly, since the "hold brakes to erase datalog" isn't turned on by default (?), and the setting gets reset during the firmware update, you have to do a run, go back in, and then make the selection. However, when you do this, at least on mine, it then does a complete factory reset, and you have to start over from the beginning. At this point, I am not able to activate the hold brakes to clear feature because of this.
Unfortunately I didn't discover either of these errors until after I updated and reprogrammed all 9 of my RSX's, so that's 2hrs the first time, then almost another 2hrs to redo them all...
I was the guy that had the problem with 255 where they would reset to factory settings after the 255 update and calibration. Sent in the profile data files, etc. that you asked I send, never got any response.
I finally determined that it was because I had used my previous 250 profiles to reload my settings into 255, and something was off in the checksum's in the compiler so it was resetting itself to factory defaults. So entering all of my settings manually was the final work-around. Wasn't a problem this time, lol, as the 258 profile saving error appears to render them completely useless from the beginning.
Aside from the above problems, in future, clearly indicating if previous profiles are, or are not, compatible with the new firmware would be very helpful.
It's hard to post problems without it coming off as negative, and certainly this was a frustrating half day spent just to update firmware, but please don't read it as anything but a little frustration. I like the RSX, and appreciate the new and exciting features you continue to bring out for the existing platform. It's drivability has continued to improve, especially the drive and brake frequencies! I'm looking forward to IOS Hotwire 3, and hope there's some way to save and reload profiles cleanly and quickly and so greatly reduce this firmware update time. I also understand most don't have 9 of these they have to go through. First world problems! Keep up the good work, just maybe a little more beta testing before release, these are some pretty basic features that got missed in this update (unless it's completely some issue on my end, which is always possible).
Last edited by IronRing Racing; 04-03-2017 at 09:08 AM.
#1268
Some issues I'm experiencing with 258:
When you save a profile/program, the firmware version is wrong in the profile log, it's mistyped as Version "2" (in stead of "258"), so now it gives you the incorrect firmware error when you try to reload that profile, and worse, won't actually load any profile settings at all, just leaves you with the default settings again.
Secondly, since the "hold brakes to erase datalog" isn't turned on by default (?), and the setting gets reset during the firmware update, you have to do a run, go back in, and then make the selection. However, when you do this, at least on mine, it then does a complete factory reset, and you have to start over from the beginning. At this point, I am not able to activate the hold brakes to clear feature because of this.
Unfortunately I didn't discover either of these errors until after I updated and reprogrammed all 9 of my RSX's, so that's 2hrs the first time, then almost another 2hrs to redo them all...
I was the guy that had the problem with 255 where they would reset to factory settings after the 255 update and calibration. Sent in the profile data files, etc. that you asked I send, never got any response.
I finally determined that it was because I had used my previous 250 profiles to reload my settings into 255, and something was off in the checksum's in the compiler so it was resetting itself to factory defaults. So entering all of my settings manually was the final work-around. Wasn't a problem this time, lol, as the 258 profile saving error appears to render them completely useless from the beginning.
Aside from the above problems, in future, clearly indicating if previous profiles are, or are not, compatible with the new firmware would be very helpful.
It's hard to post problems without it coming off as negative, and certainly this was a frustrating half day spent just to update firmware, but please don't read it as anything but a little frustration. I like the RSX, and appreciate the new and exciting features you continue to bring out for the existing platform. It's drivability has continued to improve, especially the drive and brake frequencies! I'm looking forward to IOS Hotwire 3, and hope there's some way to save and reload profiles cleanly and quickly and so greatly reduce this firmware update time. I also understand most don't have 9 of these they have to go through. First world problems! Keep up the good work, just maybe a little more beta testing before release, these are some pretty basic features that got missed in this update (unless it's completely some issue on my end, which is always possible).
When you save a profile/program, the firmware version is wrong in the profile log, it's mistyped as Version "2" (in stead of "258"), so now it gives you the incorrect firmware error when you try to reload that profile, and worse, won't actually load any profile settings at all, just leaves you with the default settings again.
Secondly, since the "hold brakes to erase datalog" isn't turned on by default (?), and the setting gets reset during the firmware update, you have to do a run, go back in, and then make the selection. However, when you do this, at least on mine, it then does a complete factory reset, and you have to start over from the beginning. At this point, I am not able to activate the hold brakes to clear feature because of this.
Unfortunately I didn't discover either of these errors until after I updated and reprogrammed all 9 of my RSX's, so that's 2hrs the first time, then almost another 2hrs to redo them all...
I was the guy that had the problem with 255 where they would reset to factory settings after the 255 update and calibration. Sent in the profile data files, etc. that you asked I send, never got any response.
I finally determined that it was because I had used my previous 250 profiles to reload my settings into 255, and something was off in the checksum's in the compiler so it was resetting itself to factory defaults. So entering all of my settings manually was the final work-around. Wasn't a problem this time, lol, as the 258 profile saving error appears to render them completely useless from the beginning.
Aside from the above problems, in future, clearly indicating if previous profiles are, or are not, compatible with the new firmware would be very helpful.
It's hard to post problems without it coming off as negative, and certainly this was a frustrating half day spent just to update firmware, but please don't read it as anything but a little frustration. I like the RSX, and appreciate the new and exciting features you continue to bring out for the existing platform. It's drivability has continued to improve, especially the drive and brake frequencies! I'm looking forward to IOS Hotwire 3, and hope there's some way to save and reload profiles cleanly and quickly and so greatly reduce this firmware update time. I also understand most don't have 9 of these they have to go through. First world problems! Keep up the good work, just maybe a little more beta testing before release, these are some pretty basic features that got missed in this update (unless it's completely some issue on my end, which is always possible).
I only have 2 ESC's to update... it took me over and hour. Lol
#1271
The data logging window can expand to full screen though....
Please?
#1272
Thanks for fixing both the profile files and the resetting to factory defaults when you go into datalogs to enable hold brake to clear?
And please tell me it will read the 258 profiles I've saved and don't have to go back in and manually redo 9 speedo settings! lol
Honestly, because you have to load firmware, input/load your settings, disconnect, then calibrate your radio, then run a bit so there's data, then reconnect, go into datalogs, download, all just to enable the hold brakes to clear function, can you also please just enable it by default?
If people are datalogging, they use that feature and it should be default on. If people aren't, then they just don't care either way, so default on works just fine for them too.
Thanks again for the quick response.
Josh
And please tell me it will read the 258 profiles I've saved and don't have to go back in and manually redo 9 speedo settings! lol
Honestly, because you have to load firmware, input/load your settings, disconnect, then calibrate your radio, then run a bit so there's data, then reconnect, go into datalogs, download, all just to enable the hold brakes to clear function, can you also please just enable it by default?
If people are datalogging, they use that feature and it should be default on. If people aren't, then they just don't care either way, so default on works just fine for them too.
Thanks again for the quick response.
Josh
#1273
Hey all... I'm pretty new to rc cars, and recently got a RSX for my Tekin Gen 3 8.5t motor. Running it in a Losi SCT22 3.0.
The track I'm running at is really small and very slick surface and I've found that I need a lot of brakes. I ran another guy's car and I was able to hit the brakes at times to kick the rear end around. Now, I know in most cases, it's probably better to steer around corners, but on this given track, having the ability to "lock up" the rear end provides really beneficial.
I've been using the Hotwire to program via my laptop but I just can't seem to get it right. What I'm hoping to achieve is if I'm applying throttle, and rapidly push forward (reverse) on the trigger, the brakes apply and stop the wheels. I've got it tuned now so it slows the car in a pretty short distance, but still not quite aggressive enough. Would anyone be willing to point me in the right direction for this?
Any help is greatly appreciated.
The track I'm running at is really small and very slick surface and I've found that I need a lot of brakes. I ran another guy's car and I was able to hit the brakes at times to kick the rear end around. Now, I know in most cases, it's probably better to steer around corners, but on this given track, having the ability to "lock up" the rear end provides really beneficial.
I've been using the Hotwire to program via my laptop but I just can't seem to get it right. What I'm hoping to achieve is if I'm applying throttle, and rapidly push forward (reverse) on the trigger, the brakes apply and stop the wheels. I've got it tuned now so it slows the car in a pretty short distance, but still not quite aggressive enough. Would anyone be willing to point me in the right direction for this?
Any help is greatly appreciated.
#1274
Thanks for fixing both the profile files and the resetting to factory defaults when you go into datalogs to enable hold brake to clear?
And please tell me it will read the 258 profiles I've saved and don't have to go back in and manually redo 9 speedo settings! lol
Honestly, because you have to load firmware, input/load your settings, disconnect, then calibrate your radio, then run a bit so there's data, then reconnect, go into datalogs, download, all just to enable the hold brakes to clear function, can you also please just enable it by default?
If people are data logging, they use that feature and it should be default on. If people aren't, then they just don't care either way, so default on works just fine for them too.
Thanks again for the quick response.
Josh
And please tell me it will read the 258 profiles I've saved and don't have to go back in and manually redo 9 speedo settings! lol
Honestly, because you have to load firmware, input/load your settings, disconnect, then calibrate your radio, then run a bit so there's data, then reconnect, go into datalogs, download, all just to enable the hold brakes to clear function, can you also please just enable it by default?
If people are data logging, they use that feature and it should be default on. If people aren't, then they just don't care either way, so default on works just fine for them too.
Thanks again for the quick response.
Josh
You do not have to make a short run to access the data log adjustments. You simply need to "download data" and you should gain access to any changes you'd like to make, including the "hold brakes to clear data" function. It would go like this:
In the data log GUI, after clicking 'Erase Data', in order to access the 'data remote erase' checkbox the you must disconnect your ESC from the HW, then reconnect. This will power cycle the ESC and reboot it for the affect to take place. I hope that helps.
Last edited by Randy_Pike; 04-04-2017 at 12:07 PM.
#1275
Any chance on future updates, that in windows, the app can be expanded to full screen. I hate the tiny window and tiny buttons on the app. I've only got a 15" laptop and trying to press tiny buttons is a pain for me.
The data logging window can expand to full screen though....
Please?
The data logging window can expand to full screen though....
Please?




95Likes