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.
Messages - LukeZ
Pages: 1 ... 29 30 31 [32] 33 34 35 ... 78
466
« on: May 30, 2019, 02:21:20 PM »
The XJT is a good module and I use it myself. But it is not necessary to buy, you can use your existing module.
I realize now the setting file I gave you will need to be adjusted. Go into Model Setup on your transmitter, select the Protocol menu, then change the "Proto" setting from XJT (what I was using) to PPM 8CH (what your module uses).
You can confirm whether your radio is working just by plugging a servo into your receiver, ignore the TCB for now. Get your radio working first, then proceed to working on the tank.
467
« on: May 29, 2019, 12:43:41 PM »
Bonjour,
je teste votre fichier, j'ai reflash ma turnigy 9X avec le firmware d'origine, j'ai connu quelques problème hier soir de bind entre la radio et le recepteur FS-A8S.
Donc dès que j'ai réussi d'implanter les paramètres je vous tiendrais au courant.
Cordialement
Legrosminet
Hello,
I test your file, I reflected my turnigy 9X with the original firmware, I had some problem last night bind between the radio and the receiver FS-A8S.
So as soon as I managed to implement the settings I will keep you informed.
cordially
Legrosminet
Ok, if you put your 9X back to "original" firmware then my file will not work. My file will only work with er9x transmitter software, not original software. I am curious, what module are you using in the transmitter? Are you using the stock AFHDS-2A module that comes with the Hobby King transmitter? If so I am not sure it will be possible to bind to the FS-A8S. Hobby King's webpage on the FS-A8S implies that it will work but I think they are wrong. You will probably have to use the stock iA8 receiver, or else upgrade to a new module (I recommend FrSky XJT and FrSky receiver).
468
« on: May 28, 2019, 04:48:01 PM »
Minet, here is a basic er9x model setup that I use. You can load it to your transmitter using the eePe program. On your transmitter you should perform also a perform the Calibration routine once (in er9x the Calibration routine is in the Radio Setup menu - press the left button on the transmitter to enter the Radio Setup menu). A complete tutorial on er9x is beyond my ability. It has many functions and abilities but for our purposes we need only the most basic. On the Model Setup screen, under MIXER you will see that all I have done is create a mix for each of the 14 controls on the 9X transmitter. I am not mixing channels with each other - the terminology is a little confusing, all I am doing is mixing the physical control (switch, knob, stick) to a channel number. Everything else you need can be done in OP Config. I hope this helps.
469
« on: May 28, 2019, 03:42:06 PM »
What this tells me is that your steering channel is not being recognized or processed. I strongly recommend against using Tanker9X. It is designed to perform functions in the transmitter that should instead be left to the TCB. It is also no longer being supported or developed so far as I know. It was never designed for use with the Open Panzer TCB. To eliminate this as a possible factor, can you try a different transmitter? Alternatively try replacing the firmware with with ER9X, OpenTX or any other general-purpose operating system. You want the most basic setup on your transmitter - each channel simply transmits its own values. NO mixes, nothing fancy. That will only create problems.
470
« on: May 28, 2019, 02:20:58 PM »
I am sorry that hasn't been fixed. You might want to follow along with the other thread and try the suggestions there to see if they help you. The other user is French, you are Spanish and I am English so it is kind of crazy but hopefully with Google translate we can all understand each other! Turn and Forward Problem
471
« on: May 28, 2019, 02:14:01 PM »
This problem has me stumped. I loaded your OPZ file onto my own TCB, I connected it to two XCar 45 ESCs same as you, and I have no problems. I am even using a 9X radio as well, although my radio settings are slightly different. I have several 9X radios and I always have to set the channel order for the sticks to 2,4,3,1 (throttle, steering, elevation, rotation). Yours are 1,2,3,4 but maybe you have re-arranged the channel order on the transmitter. You should make sure that your transmitter does NOT have any mixes created. I would suggest you run through Radio Setup one more time just to be sure that is not contributing to the problem. See the YouTube video for a reminder if necessary. Afterwards, can you please load this test firmware onto your TCB. Right-click the link and select "Save link as" to save it to your computer. Then on the Firmware tab of OP Config, click the "Use your own Hex" button to select this file. Now flash to the TCB. 2019_05_28_tcbmk1_TEST_0-93-50.hexIf you were already using a recent version of firmware your settings should be maintained, if you were using an older version (0.93.44 or earlier) they will be reset to default, in that case you will want to write your OPZ file after flashing to restore your settings. The only change in this version is that it will print the actual speed values being sent to each track in real time. To see these values, you will need to keep your TCB connected to the computer in Snoop mode (keep your tank elevated so it doesn't drive off your desk!) I have shown a screenshot below. The left column is the speed of the left track, the right column is the speed of the right track. Values can range from 0 (stopped) to 255 (full speed). Forward speeds are positive and reverse speeds are negative. In this screenshot, you can see that I am going full speed ahead and turning right at the same time (left track speed is maximum 255, right track speed is much slower at around 70). What you describe is that when moving forward, you command a turn but no turn happens. If that is what the TCB is actually doing, Snoop will show that your left and right track speeds are always the same, even when you move the steering stick. That definitely should not be possible but let's see what happens.
472
« on: May 28, 2019, 01:39:09 PM »
Also, that's a beautiful P4! I'm glad to hear it was well-received by the onlookers and I can see why it would be. Good job.
473
« on: May 28, 2019, 01:38:25 PM »
Thanks Rad for reporting that. In fact it is a known issue, and you correctly identified the cause - a long MG stop sound. The TCB doesn't know anything about the stop sound, not how long it is or even that there is one. When you tell the TCB to stop the MG it thinks it happens right away. The TCB is controlling the light so it stops the light, but the sound card is controlling the sound and it keeps going. You can re-start the MG on the TCB and the TCB will happily start blinking the light again, but the sound card says "Wait! You aren't done with the stop sound. I will not comply."
The most direct fix is the thumb fix. The user, knowing he loaded a long stop sound, needs to restrain his thumb from re-starting the MG right away before the stop sound has completed. Also this is a very good example why it is important to eliminate any silence at the end of your sound files, and fade them out very quickly.
Another fix which I will consider is that we instruct the user, when using the OP Sound Card, to move the MG light from the TCB output to one of the outputs on the Sound Card. Your early prototype doesn't have any light outputs but as you know the current version has 3. Since the Sound Card knows how long the stop sound is, it can more accurately control the light output, preventing it fro restarting while the stop sound is still playing.
However even that wouldn't be 100% perfect because the TCB could still be firing the MG IR signal at the wrong times. The perfect fix is either for the user to specify in OP Config the length of their stop sound, so now the TCB is aware of it (which is more work for the user and more settings to clutter OP Config); or most ideally of all have the Sound Card communicate via serial to the TCB on startup this kind of information. That's the best solution but is also the more time-consuming one, and considering only a handful of people in the universe even have one of these devices, I am probably going to postpone it until such a day as they become more widely available.
But thanks for bringing it up and reminding me, I will add it to my long-term to-do list.
474
« on: May 28, 2019, 01:27:51 PM »
Thank you anyway Sub for testing, at least now we can put this test to rest after almost 2 years of wondering!
I have several computers at home running Windows XP, 7, and 10 and for me the TCB almost always connects directly with the Connect button, probably 95% of the time. Every once in a while I will need to use Snoop but for me to really test a fix I would need to have a computer that requires Snoop every single time. Otherwise, I can make some firmware change, but then when it connects with the Connect button I don't really know - would it have connected anyway, since it usually does? Or did I fix something?
In fact there may not be a good fix for this problem. I understand what is going on, Windows is deciding to hold the device in reset mode when we connect and immediately start communicating (this is what happens when we use the Connect button). When we Snoop, we connect but don't immediately start communicating until later you hit the connect button.
I could eliminate entirely Window's ability to reset the device, but in fact this ability is necessary in one situation - when we are flashing new firmware. So if I made that change your Connect would always work, but you would not be able to update the device without manually resetting it during a very brief window of a few seconds by pushing the Reset button on the board. This would probably be inconvenient or impractical for most people, especially after the board is mounted in the model.
So it's kind of a conundrum, but at least the Snoop method works.
Thanks again for testing and reporting back, and especially thank you for figuring out the USB power saving issue earlier.
475
« on: May 27, 2019, 06:49:12 PM »
I am beginning to think the problem could be mechanical. Let us do a very simple test before we proceed any further:
Elevate your tank on a block placed beneath the chassis. The tracks (les chenilles) should be free to turn but not touch the ground.
Now command forward and turn. Does the inner track slow down? For example, if you command left turn, the left track will be the "inner" track and it should decrease speed.
If that is what you observe then your TCB and ESCs are working correctly and the turning command is being issued correctly. In this case the problem is mechanical.
But if you issue a turn command and both tracks continue to move at the same speed, then we have a TCB or firmware problem.
Let me know what you find out! And please tell me if you have problems understanding and I will try to write in French.
476
« on: May 27, 2019, 02:10:06 PM »
Hi Juan, did you ever resolve this problem? Another user has reported the same thing here.
477
« on: May 27, 2019, 02:09:08 PM »
Bonjour Minet, et bienvenue. Votre anglais est excellent, mais mon français n'est pas très bon, so I hope you will understand my English. Interestingly Jaunillor reported this same problem recently, but he has not said whether he fixed it or not. We will have to ask him. My advice to him was to re-check the radio setup. But you have already done that so I will assume that is not the problem. One thing you both have in common is that you are both using ESCs for motor control. Can you tell me what ESC you are using? I wonder if your ESC has brake enabled - that could cause problems with turning.
478
« on: May 23, 2019, 11:42:46 PM »
Good grief, you can barely even see that ESC in there. That makes for a very compact package!
479
« on: May 23, 2019, 10:54:18 PM »
Also, Sub encountered a different issue not related to the Snoop/Connect conundrum. You can read more about his problem over on RCTankWarfare along with the solution he found. His problem was that he couldn't get the connection to work ever when starting with Snoop. He found that Windows defaulted to turning off some USB functionality as a power-saving measure, and by disabling that Windows feature he was then able to connect (albeit he has to use Snoop first). I've posted this information in the Wiki on both the Troubleshooting page and the Connection page, in case anyone else has that same problem in the future. Thanks Sub for figuring that out!
480
« on: May 23, 2019, 10:51:02 PM »
Hi Sub, welcome to the forum. I've moved your post over to this topic so we can have this entire discussion in one place. Here is the testing version of OP Config that you can try: 2019_05_22_OPConfig_Setup_0-93-49_TESTTo download right click the link and select "Save Target As" and save it to your computer. When you install it will overwrite your existing version. This one is 0.93.49 TEST (you can confirm in OP Config by going to Help->About and it should read Version 0.93.49 [TEST]). To reiterate, this version is intended for users who have to use Snoop before connecting. There is only a very minor change made and it probably won't make any difference, but it would be good for someone with that issue to test. See if you are able to Connect with this version by clicking the Connect button directly, rather than going through Snoop first.
Pages: 1 ... 29 30 31 [32] 33 34 35 ... 78
|
Show Posts