I think that's going cause an issue, I remember there's a limit on sd car size that can't be used and it must be formatted fat32, I think the requirements are in the manual.

Wasn't able to open the ini file with android notebook, could only open, choose, and listen to sounds. Pc wouldnt open card at all, said it needed to be reformated.

Format the file fat32. Be sure when you remove it you right click the drive and select eject.

I've been following but staying out of this conversation, I suppose that's troll like but there it is.

I will say this, I have been poking around the 'net for references to damage to electronics due to scanning
and so far I've not come across any examples that have proof. I won't rule it out but I can't see why IBU electronics would be any more vulnerable to scanning than any other of the thousands of electronics shipped all over.

The reason I've decided to stop selling IBU items is not that I believe them to be deficient in any way. Simply put
I don't have the time to invest to determine the nearly limitless possible combinations of what end users can do; what
RC system( both receiver and Xmitter ), rc system software and the variations of same, the configuration choices that
can be made of the IBU units themselves and as you guys just indicated possible variation id SD format and capacity.
There's just no way to control it. I could say I will only support the unit with brand X RC system configured precisely this
way which is why I realize some sellers sell complete systems - for their own simplicity of control. I've been a software developer for many years, once upon a time when choices were fewer we had a more DIY attitude towards design and implementation but now with hundreds of thousands of user devices in our network at my company, the company controls just what can be done, especially by developers, with an absolute iron hand, choices are kept artificially few just for the above reasons. There isn't the resources available and it would be a logistics nightmare to maintain a free for all approach.
I'm not saying anyone is doing wrong or bad things but with the possibility of being able to shoot oneself in the foot it can happen...

Which is what we have here sadly. We want plug and play but that isn't so simple. I hate to say it and I first hated the constraints of limited choices but I've come to see the wisdom of it. I read with interest the Open Panzer project. As a experimenter I think it is slicker than sno....... you get the idea. But in the real world I fear it won't fly well, hope I'm wrong.

Even though I'm pretty cavalier about tweaking, soldering and making changes to my personal stuff I think I know when to
say when. I go strictly by the book and I mean I do everything the way the maker says when I know my insights into the lower level function of a system is minimal or non existent- in other words if I'm unsure I can't back out of a hole I want to dig I'm not going to dig it. For instance I wouldn't consider fooling around with the SD card format or capacity... I mean why? First think I ever did when I got my hands on an IBU was to make a copy of a card on my home network so I could make changes and look at files. I use a tool called TextPad; something I use at work almost daily.

I'm sorry you guys have had problems with the units. If you need to have your sd cards reset send them to me and I'll overlay them with my reference copy. Make sure you can account for every change you've made or deviation from Ivano's instructions no matter how trivial it seems, check all dip switches and ensure the servo cables are working correctly. If your rc system is one of those running advanced software please make sure to begin with it is as vanilla as is possible- get clever only after everything is working. And make backups!

Jerry

Jerry, I appreciate the insight but making a seperate SD card and keeping the original for backup wasn't a bad idea. The board just can't address the entire volume and thus it didn't work. No biggie. It isn't like we hacked the firmware. . I processed the points of failure and that lead me to the card size. JS/PHP/VB/C# I'm not over my head with an INI.


But I get what you mean with user variables. It's not the PnP device that most are looking for. Radio differences alone can be a problem. My IBU3 won't load an IBU sound file. Thats not a user problem. As you stated this is why there are packages / bundles. Clark loads his sounds and you can't change them without the utility he uses to flash the units.