How to perform firmware upgrade on Pentair* controllers

JerryT, I just received the Micro JST 1.25 T-1 6-Pin Connector plug from Hong Kong (very quick shipping) and I need help with the pin-outs in your diagram. I'm not using a board so I'm going to cut the ribbon cable and attach the wires directly from the USB BDM Multilink. Can you look at my images here and let me know what I need to correct.

I'll adjust the images if they need to be corrected.
Is the red line on the ribbon cable VDD or BGND?
Which wire attaches to which wire below (can fix the numbers to match the true pin numbering later).

Pin-out-1.jpg Pin-out-2-IMG_2258.jpg
 
Last edited:
JerryT, I just received the Micro JST 1.25 T-1 6-Pin Connector plug from Hong Kong (very quick shipping) and I need help with the pin-outs in your diagram. I'm not using a board so I'm going to cut the ribbon cable and attach the wires directly from the USB BDM Multilink. Can you look at my images here and let me know what I need to correct.

I'll adjust the images if they need to be corrected.
Is the red line on the ribbon cable VDD or BGND?
Which wire attaches to which wire below (can fix the numbers to match the true pin numbering later).

Pin-out-1_zpscxtyrfqu.jpg

BDM header pinout is correct, you will need to ohm out the wires to verify which is to which pin, it maybe as you have the ribbon cable labeed, but you need to verify.




Pin-out-2-IMG_2258_zpszryufx1m.jpg
These should be labeled according to which pin they attach to on the BDM header, so the order would be "2, not used, not used, 4, 1, 6 " per your picture.

or

Here is another way to view it.
BDM header-------------------Micro JST (per your picture of the pins labeled 1-6)
1-----------------------------------5
2-----------------------------------1
3-----------------------------------Not Used
4-----------------------------------4
5-----------------------------------Not Used
6-----------------------------------6
 
Thanks JerryT
So, If I am interpreting you correctly,
BDM Pin 1 (the red wire labeled '1' on the BDM ribbon) connects to the black wire (labeled '5') on the Micro JST.
BDM Pin 2 (labeled as wire '2' on the BDM ribbon) connects to the white wire (labeled '1') on the Micro JST.
BDM Pin 4 (labeled as wire '4' on the BDM ribbon) connects to the yellow wire (labeled '4') on the Micro JST.
BDM Pin 6 (labeled as wire '6' on the BDM ribbon) connects to the red wire (labeled '6') on the Micro JST

I have verified the ribbon cable order to the pin order. The red wire connects to what I labeled pin '1' then, in order, they alternate sides as shown in the picture.
 
Thanks JerryT
So, If I am interpreting you correctly,
BDM Pin 1 (the red wire labeled '1' on the BDM ribbon) connects to the black wire (labeled '5') on the Micro JST.
BDM Pin 2 (labeled as wire '2' on the BDM ribbon) connects to the white wire (labeled '1') on the Micro JST.
BDM Pin 4 (labeled as wire '4' on the BDM ribbon) connects to the yellow wire (labeled '4') on the Micro JST.
BDM Pin 6 (labeled as wire '4' on the BDM ribbon) connects to the red wire (labeled '6') on the Micro JST

I have verified the ribbon cable order to the pin order. The red wire connects to what I labeled pin '1' then, in order, they alternate sides as shown in the picture.

You got it !!

Have you found a later version of Prog12Z ??
 
My son was able to get it for a steep discount direct from PE Micro because they have a student discount that takes 90% off the price of their software. That worked out well. Search their website for student discounts.

What's the process of upgrading the firmware with regards to the easytouch system. Do I just go into diagnostics mode and select firmware update then run the appropriate Pentair batch file? What about the wireless controller?
 
What's the process of upgrading the firmware with regards to the easytouch system. Do I just go into diagnostics mode and select firmware update then run the appropriate Pentair batch file? What about the wireless controller?

Basically you just run the batch file, BUT many of the links will be wrong. Like the location of the algorithm file, so you have to edit the batch files.

I have never put the board in diagnostic mode, one of the first commands prepares the board for programming.

I have never programmed a wireless controller, is that firmware included in Pentair's download ?? if Yes, then look for a programming header ??

Check your PM
 
My son was able to get it for a steep discount direct from PE Micro because they have a student discount that takes 90% off the price of their software. That worked out well. Search their website for student discounts.

https://www.pemicro.com/contact_us/index.cfm
"P&E also has available special student packages. Students may obtain full versions of P&E Integrated Assemblers, Simulators and other software products at a 90% discount from the full commercial price. Students may also obtain individual pieces of hardware at a 10% discount from the full commercial price. A copy of a valid current student ID is necessary."

Awesome find there Geobrick !!!
 
Basically you just run the batch file, BUT many of the links will be wrong. Like the location of the algorithm file, so you have to edit the batch files.

I have never programmed a wireless controller, is that firmware included in Pentair's download ?? if Yes, then look for a programming header ??

Check your PM

Yes. Inside the easytouch folder it has 3 batch files. 1) easytouch_outdoor2, 2) easytouch_wireless2, and 3) easytouch_indoor2. I have the outdoor panel and the wireless controller. There is a 6 pin header in the battery compartment of the wireless controller.
I checked my PM and didn't see anything.
 
I just tried to load the firmware into the wireless controller and got "Cannot Enter Background mode. Check connection" Error 34. It's the same error when header is disconnected. Maybe I have the micro jst pins reversed. Maybe 1 should be the red wire and 6 should be the white wire.
 
I just tried to load the firmware into the wireless controller and got "Cannot Enter Background mode. Check connection" Error 34. It's the same error when header is disconnected. Maybe I have the micro jst pins reversed. Maybe 1 should be the red wire and 6 should be the white wire.

Pin 6 should be 5 volts and pin 1 should be "Ground" at the Micro JST and any programming port that has the same configuration.

I would try your cable on the Easytouch Outdoor board before changing any wiring, the wireless unit may have a different pin out on the header (Different cable)

You should have two PM's now
 

Enjoying this content?

Support TFP with a donation.

Give Support
I was able to load the firmware into the outdoor system. It now says ver 2.140 but it says UWC unknown (That's where the wireless firmware version would be listed).

I tried loading firmware into the wireless controller again. This time I noticed the yellow light on the BDM came on but as soon as I ran the batch file, and just before the RE command was sent, the wireless controller turned off, resulting in error 34. There must be a key sequence or some procedure for loading the firmware into the wireless controller. It may be a power issue. The wireless controller runs on batteries.
 
OK, I'll measure pins 1 and 6. Should I see the 5v as soon as I plug in the usb cable or do I need to run the program?

If the yellow light is coming on, I believe the wireless unit has the same "Micro JST" header configuration as the outdoor unit.

- - - Updated - - -

I was able to load the firmware into the outdoor system.
Did you have to edit the batch file ??

It may be a power issue. The wireless controller runs on batteries.
My guess would be power issues, did you try new batteries ?? Does it have provisions for an external power supply ??

Edited first post with your cable pictures, Thanks Geobrick
 
If the yellow light is coming on, I believe the wireless unit has the same "Micro JST" header configuration as the outdoor unit.

- - - Updated - - -

I Agree. There would be no reason to design it differently than the rest of their equipment.

Did you have to edit the batch file ??
No it just ran through the sequence without a hitch then the program closed itself. It took a while (minute or two) for the controller to go back into a usable state without indicating what was going on. After that, it was all good.


My guess would be power issues, did you try new batteries ?? Does it have provisions for an external power supply ??
I did try new batteries. I may try again with some Ni-MH rechargeables because they can handle higher currents than alkaline batteries. After that, I may try to figure out a way to power it from an external supply.

I wonder if I can try to set up the configuration manually though PROG12z. When I try to run it without the BDM plugged in, there's a popup connection manager that lets you configure the connection to the BDM and the target CPU. One of the options is to provide power to the target.

Using the batch file, the wireless controller seems to shut down as soon as the line "CPROG12Z ? 1 IO_DELAY_CNT 12 C:\pemicro\pkg12z\cfg\OLD_EZTUWC2.CFG FREQ 8000000 Interface=USBMultilink PORT=USB1" is executed. The first 2 lines of "OLD_EZTUWC2.CFG" are "RE" and "CM C:\pemicro\prog12z\Algorithms\Freescale_9S12DT128_1x16x64k_128k_Linear_16k_page.12P" but it never gets through the RE command because the controller turns off (and the yellow light goes out) before the RE command is ever sent resulting in the error message. Something in the configuration setup is causing it to turn off but what can it be? "CPROG12Z ? 1 IO_DELAY_CNT 12"?

Edited first post with your cable pictures, Thanks Geobrick
Cool.
 
I wonder if I can try to set up the configuration manually though PROG12z. When I try to run it without the BDM plugged in, there's a popup connection manager that lets you configure the connection to the BDM and the target CPU. One of the options is to provide power to the target.

The Batch file runs the command line version of Prog12Z

See post 39 for the procedure of manually programming.
Open Prog12Z directly by double clicking, you with get the "Connection Assistant" window.

Open each of the .bat, and .cfg files for the wireless unit, by dragging on top of notepad icon. Save all these steps as the manual programming steps as in post 39.
 
I tried doing it manually. Same result. As soon as the connection was attempted using the 'connection assistant', the wireless controller shut down.

If the NiMH batteries don't work, I'll considered building a connector that connects to the outdoor header without the BKGN and Reset lines connected (so I'd only use the VDD and GND) and splice it into the connector going to the wireless controller. Before I do any of that, I'll see if there's a setting to increase the power coming from the USB port.

I found something interesting on the PEMicro page for the USB-ML-12. http://www.pemicro.com/products/product_viewDetails.cfm?product_id=33
Under the section "Which Hardware Interface is the Best Fit?". For Power Management it says: "Target must be powered separately". So no power is being supplied to the target processor.
 
I did try it. As soon as the connection is attempted using the connection assistant, the wireless controller shuts down.

If the NiMH batteries don't work, I'll considered building a connector that connects to the outdoor header without the BKGN and Reset lines connected (so I'd only use the VDD and GND) and splice it into the connector going to the wireless controller. Before I do any of that, I'll see if there's a setting to increase the power coming from the USB port.

I found something interesting on the PEMicro page for the USB-ML-12. http://www.pemicro.com/products/product_viewDetails.cfm?product_id=33
Under the section "Which Hardware Interface is the Best Fit?". For Power Management it says: "Target must be powered separately". So no power is being supplied to the target processor.

Cyclone Pro is the programmer which can provide power to the target.
 
That's probably why I was never able to measure the 5V from the BDM ribbon cable.
I measured the power from the header on the outside controller and it's exactly 5v between pin 1 and 6. I'm going to try using that as a power source to the wireless controller.
 
It worked!!! I used the 5v power from the outside controller to feed the connector going into the wireless controller. Both lights on the BDM came on. I ran the batch file and it ran all the way through without a hitch. It was nice that the Micro JST connectors were sold in packs of 10. Having an extra connector made this much easier.

FirmwareUG_Wireless_Controller_IMG_2263.jpg

UrmiiZE.jpg


tmZTTd8.jpg


Thanks to Tinyavian for pointing out the relitively inexpensive programmer available from P&E Micro and Jerryt for expanding on the topic in great detail while helping anyone who needed it and keeping track of what worked and didn't work. We can now add the wireless controller to the list of upgrades that worked.
 
Last edited:

Enjoying this content?

Support TFP with a donation.

Give Support
Thread Status
Hello , This thread has been inactive for over 60 days. New postings here are unlikely to be seen or responded to by other members. For better visibility, consider Starting A New Thread.