Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

How to flash PXC00-PE96.A's firmware again

Created by: july008 at: 6/19/2018 12:12 PM (13 Replies)

Rating (0)

Thanks 1

Result pages:: |; 1 | 2; |

14 Entries

Entries per page: 10 | all

6/19/2018 12:12 PM	Rate (0)
july008 Regular Member Joined: 3/22/2016 Last visit: 5/17/2024 Posts: 20 Rating: (0)	I have a PXC00-PE96.A, version number is v2.8.2, in order to support modbus to refresh the new firmware, refresh PXC00 to v2.8.5 Driver MBC 3.2 by tcp/ip connection. Refresh the firmware successfully. Continue to test the refresh firmware, but accidentally brushed 3.2 driver MBD v2.9, an error occurred at the end of the refresh, the firmware failed to start. FLT software and HyperTerminal software can not connect to PXC00 via ip or usb or RS232, but can access PXC's IP address (192.168.1.100) through ping, PXC's communication and other RUNs are always on, and COM light is connected to the back light of PXC's switch. Flashes. I know that firmware version 2.x is for P2, firmware version 3.x is for bacnet, because the wrong version of the firmware causes the firmware to fail to boot in PXC. My problem is how to re-download the firmware of v2.8.5 Driver MBC 3.2. ? Look at the PXC's PDF description, press the button FW and Reset, you can force download the firmware to the PXC through the D-MAP program, do not know where this D-MAP program is downloaded, this program does not seem FLT software in the CommTool. Can anyone tell me how to deal with it? PXC00-PE96.A has passed the warranty period. Attachment AA.png (1917 Downloads)
	Last edited by: july008 at: 6/19/2018 12:22:02 PM
Suggestion To thank Quote Answer

6/19/2018 5:14 PM	Rate (0)
Jay. Posts: 1283 Rating: (105)	july008 I have a PXC00-PE96.A, version number is v2.8.2, in order to support modbus to refresh the new firmware, refresh PXC00 to v2.8.5 Driver MBC 3.2 by tcp/ip connection. Refresh the firmware successfully. Continue to test the refresh firmware, but accidentally brushed 3.2 driver MBD v2.9, an error occurred at the end of the refresh, the firmware failed to start. FLT software and HyperTerminal software can not connect to PXC00 via ip or usb or RS232, but can access PXC's IP address (192.168.1.100) through ping, PXC's communication and other RUNs are always on, and COM light is connected to the back light of PXC's switch. Flashes. I know that firmware version 2.x is for P2, firmware version 3.x is for bacnet, because the wrong version of the firmware causes the firmware to fail to boot in PXC. My problem is how to re-download the firmware of v2.8.5 Driver MBC 3.2. ? Look at the PXC's PDF description, press the button FW and Reset, you can force download the firmware to the PXC through the D-MAP program, do not know where this D-MAP program is downloaded, this program does not seem FLT software in the CommTool. Can anyone tell me how to deal with it? PXC00-PE96.A has passed the warranty period. You mean even the recover option in the FLT tool is not helping? Jay
Jay. Posts: 1283 Rating: (105)
Suggestion To thank Quote Answer

6/19/2018 6:14 PM	Rate (0)
july008 Regular Member Joined: 3/22/2016 Last visit: 5/17/2024 Posts: 20 Rating: (0)	Yes,The FLT tool cannot find the device. It does not work through the recovery wizard. Confirm the PXC IP address is 192.168.1.100 with the ping.exe tool

Suggestion To thank Quote Answer

6/26/2018 4:15 PM	Rate (0)
Justin Cornell Member Joined: 4/15/2011 Last visit: 9/3/2025 Posts: 4 Rating: (0)	Try running recovery from the MMI port

Suggestion To thank Quote Answer

6/26/2018 6:10 PM	Rate (0)
july008 Regular Member Joined: 3/22/2016 Last visit: 5/17/2024 Posts: 20 Rating: (0)	Justin Cornell Try running recovery from the MMI port FLT software and HyperTerminal software can not connect to PXC00 via ip or usb or MMI, but can access PXC's IP address (192.168.1.100) through ping, PXC's communication and other RUNs are always on, and COM light is connected to the back light of PXC's switch.

Suggestion To thank Quote Answer

6/27/2018 6:56 AM	Rate (0)
Jay. Posts: 1283 Rating: (105)	Did you run FLT inside Commissioning Tool(CT) or as a separate application? Thanks, Jay july008 Justin Cornell Try running recovery from the MMI port FLT software and HyperTerminal software can not connect to PXC00 via ip or usb or MMI, but can access PXC's IP address (192.168.1.100) through ping, PXC's communication and other RUNs are always on, and COM light is connected to the back light of PXC's switch.
Jay. Posts: 1283 Rating: (105)
Suggestion To thank Quote Answer

6/27/2018 9:11 AM	Rate (0)
july008 Regular Member Joined: 3/22/2016 Last visit: 5/17/2024 Posts: 20 Rating: (0)	Jaya1189 Did you run FLT inside Commissioning Tool(CT) or as a separate application? Thanks, Jay july008 Justin Cornell Try running recovery from the MMI port FLT software and HyperTerminal software can not connect to PXC00 via ip or usb or MMI, but can access PXC's IP address (192.168.1.100) through ping, PXC's communication and other RUNs are always on, and COM light is connected to the back light of PXC's switch. Compared to a separate flt installation program or ct's own flt program, the program is the same, but the software package is different. After I power on this pxc ip address, it is estimated that the built-in embedded operating system is operating normally, but the controller firmware can not run. Do not know what the official solution is good. If users download firmware across versions, flt should stop, but flt does not give a hint.

Suggestion To thank Quote Answer

4/21/2020 6:25 AM	Rate (0)
behi.sh Advanced Member Joined: 4/6/2019 Last visit: 9/4/2025 Posts: 53 Rating: (0)	HI dear me for download a firmware on pxc desigo you should first open a xwork software . after that you set a ip address to pxc . and chose a direct connect with ip connection Best regards

Suggestion To thank Quote Answer

4/21/2020 6:26 AM	Rate (0)
behi.sh Advanced Member Joined: 4/6/2019 Last visit: 9/4/2025 Posts: 53 Rating: (0)	this port use for op panel and pxm and you can use this port for firmware upgrade and downgrade

Suggestion To thank Quote Answer

12/29/2020 10:53 PM	Rate (0)
behi.sh Advanced Member Joined: 4/6/2019 Last visit: 9/4/2025 Posts: 53 Rating: (0)	hi every body Many friends said it could not be done! we downgrade pxc version 6 to version 5 after that connect to it and program pxc with xwork5 if you have a PXC with firmware 6 but you have a xwork 5 ! This can be done

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on