2015 BadBoy iS Crew 72 Volt - PDO Timeout Curtis Controller Help

[Role]

2015 Badboy buggie 72 volt with DUAL AC 1236 Curtis controllers.

One of the controllers was blinking an error code. "traction throttle mismatch"

I did something stupid and plugged my programmer into the driver side controller and copied the .cpf file.

I then took the .cpf file from the driver controller and cloned it to the passenger controller.

Now, when I turn the ignition key ON, I'm getting a PDO TIMEOUT message and it's causing the solenoid not to audibly click when turning the key ON.

I guess my assumption was both controllers were the same, with the same settings.

But apparently they are not.

Any idea where in the settings I can go to fix the PDO TIMEOUT error and to get the solenoid to audibly click on start up like it normally would?

Any help is appreciated!

[Role]

Here's an update*
May have found someone with the original BadBoy firmware files to be loaded and flashed back to each controller to fix the PDO timeout problem. Hopefully, I can get that and resolve the issue.

[Role]

Still have not been able to find anyone who has the factory firmware for the Curtis 1236-6305 AC Controllers. Not even local EZGO badboy dealer has these files. And they won't let me take my OEM programmer and plug it in to just copy the firmware to my programmer. Screwed? Should I just tell my buddy to throw his cart away?

[BobBoyce]

I guess it's too late to tell you that the first thing you EVER do is to save the original .cpf file from both controllers PRIOR to making any changes on either.

One controller is defined as master and the other is defined as slave. When you cloned the settings, you defined both as either master or slave, hence no Comms between them.

I don't blame them for not trusting you to pull files from another cart. You had proven yourself incompetent with your actions with the cart you corrupted the controller in. Besides, a save of those controllers files would probably not help you one bit. Every little variance in programming from your programming, through the years to the most current model, will not have "homes" in the older versions OS/VCL to save that data to. You must pull the files from an identical pair of controllers to yours. OS and VCL Version/Revision.

Besides, you're really going to need a minimum of a Factory level programming station to get complete saves of the controllers, beyond just the parameter settings. Remember the question in advanced cloning? Where it asked you if you wished to overwrite settings above your access level? That is where the reading software would have actually been able to save those settings, had it been of high enough level. OEM level cannot access everything contained in a controller.

Bob

[Role]

Originally Posted by BobBoyce

I guess it's too late to tell you that the first thing you EVER do is to save the original .cpf file from both controllers PRIOR to making any changes on either.

I don't blame them for not trusting you to pull files from another cart. You had proven yourself incompetent with your actions with the cart you corrupted the controller in.

Besides, you're really going to need a minimum of a Factory level programming station to get complete saves of the controllers, beyond just the parameter settings. Remember the question in advanced cloning? Where it asked you if you wished to overwrite settings above your access level? That is where the reading software would have actually been able to save those settings, had it been of high enough level. OEM level cannot access everything contained in a controller.

Bob

Thanks for your input Bob, but do not be condescending, incompetent? I think not. I'm well versed and build some of the finest carts in the industry, you can drop your ego.

Saving a .cpf file from another controller without touching any settings is not a difficult task.

I do realize that I should have saved both .cpf files from each controller although, I did save one controllers .cpf file.

I did see the screen from advanced clone settings on my OEM level programmer.

[BobBoyce]

Originally Posted by Role

Thanks for your input Bob, but do not be condescending, incompetent? I think not. I'm well versed and build some of the finest carts in the industry, you can drop your ego.

Saving a .cpf file from another controller without touching any settings is not a difficult task.

I do realize that I should have saved both .cpf files from each controller although, I did save one controllers .cpf file.

I did see the screen from advanced clone settings on my OEM level programmer.

Being able to build fine carts has no bearing on controller programming competence. I had been a custom EV manufacturer for 17 years. I spent the last 10 years of that business as a Factory level (beyond OEM level) Curtis programmer. I now use my Development level programmer for reflashing controllers and bringing many of them back from the "dead" so to speak. I wrote controller OS and programming software, so I have a bit of experience when it comes to Curtis controllers. I'm not intending to insult you. I just pointed out the obvious.

What every competent programmer should do... Make a backup of EVERY controller that is connected to, and place it into an archive, just in case something goes wrong or gets messed up. Verify the backup was saved and is a good file, prior to making any changes. Then archive a changed controller file, prior to shutting down the programming station or handset. This way, you have a before and after save. This comes in handy for more than just CYA in case you make a mistake. This allows you to go back and look at a customers vehicle, in detail, for error codes that were saved in that file, to identify most issues that had occured prior to you making changes. This way, you can tell if errors were caused by your changes, or were indicated in the prior data as a pre-existing condition. I have given customers lists of their error codes, when they occured, and many times what they indicated as the cause and when/if the fault(s) causing the errors were corrected. There are many dozens of members on this forum that can confirm what I say here, because they experienced this level of interaction with me. I treat each and every cart as an EV, because it is. I'm an engineer, at multiple levels. My highest degree is in AeroSpace. I worked in a highly classified environment most of my life, so I lack a lot of people skills.

Again, I was not trying to insult you. I just want you to understand where I am coming from.

Bob

[Role]

Originally Posted by BobBoyce

Being able to build fine carts has no bearing on controller programming competence. I had been a custom EV manufacturer for 17 years. I spent the last 10 years of that business as a Factory level (beyond OEM level) Curtis programmer. I now use my Development level programmer for reflashing controllers and bringing many of them back from the "dead" so to speak. I wrote controller OS and programming software, so I have a bit of experience when it comes to Curtis controllers. I'm not intending to insult you. I just pointed out the obvious.


Again, I was not trying to insult you. I just want you to understand where I am coming from.

Bob

No harm done, Bob. I appreciate the insight and information.

Any idea how I can get this fixed? Could you help fix it? I would be happy to pay you for your time and for the experience of learning from my mistake.

[reeseman44]

I know this is old, but where the heck is the programming port on these buggies? Lol

[kgsc]

Square molex port on the face of the controller.

[reeseman44]

Thank you!