Firmware Revisions for P3-550
Firmware Revisions for P3-550
Latest shipping version:
Recent Firmware History:
Version: 1.2.10.9
Details:
New feature:
1.) Changed to allow Modbus access to a single Modbus address within an S32/F32 tag
Version: 1.2.7.66
Details:
P3-550
Firmware 1.2.7.66
Release Date: January 22nd, 2021
Bugs fixed:
1.) This firmware modification resolves a factory test issue and should have no impact on customer applications.
Version: 1.2.7.65
Details:
P3-550
Firmware 1.2.7.65
Release Date: September 17th, 2020
Bugs fixed:
1.) Modbus TCP Server. When writing a block of mixed 32-bit and 16-bit integers
to the PLC, the data can get written to the wrong location and return an illegal
data address exception in certain situations
Version: 1.2.7.39
Details:
Release date: 6/10/19
Bugs fixed:
1.) CPU may lockup with serial Modbus instructions when transitioning Run-Stop.
Version: 1.2.7.37
Details:
Release Date: 12/12/18
Improvements:
1.) Added support for new features:
a. Secure integrated Email
b. Network Time Service
c. Domain Name Server
Bugs fixed:
1.) Modbus RTU, as slave, does not show exception for unknown Function Codes.
2.) CPU date not changing correctly if set to some older time frames.
3.) First containing ModBus/TCP non-existing devices in call task takes 2x longer than subsequent scans.
4.) Retentive data backup behavior does not complete as user specification if set to minimum.
Version: 1.1.15.114
Details:
Version: 1.1.15.114
Details:
P3-550 Release Notes
Firmware 1.1.15.114
February 13, 2018
Bugs fixed:
1) Digital Inputs may not be available on first scan for the local base or any remote bases set to local.
Version: 1.1.15.111
Details:
Release: 1/3/2018
Hardware:
1) Support for new USB chip on P3 backplanes.
Bugs fixed:
1) Mitigate effects on CPU when the external Ethernet port on the CPU experiences irregular Ethernet traffic.
Version: 1.1.15.108
Details:
Release: 12/5/2017
Bugs fixed:
1.) System discovery and project transfer fails resulting in E01201 Sema Obtain error. This may happen when on a network with other devices using broadcast messages.
2.) Repeated consecutive power cycles may force CPU to stop mode and corrupt NAND flash.
Version: 1.1.15.104
Details:
P3-550
Firmware 1.1.15.104
Release: 7/10/17
Bugs fixed:
1.) Incurring drop packets during project transfer via Ethernet may cause the transfer to fail.
Version: 1.1.15.101
Details:
February 16, 2016
Bugs fixed:
1.)When using a P3-SCM module with CPI/CPO instructions a stop mode transfer can cause the P3-550 to stop communication to the SCM and create an E1005 error.
Version: 1.1.15.99
Details:
P3-550 Release Notes
Firmware 1.1.15.99
November 10, 2014
Bugs fixed:
1.)Data Logging .csv files can lose data after a power cycle.
2.)Any Data Logging file created since last power up cannot be deleted by the web server.
3.)Web server may cause possible E01005 ‘System Restart’ error.
Version: 1.1.15.98
Details:
P3-550 Release Notes
Firmware 1.1.15.98
September 29, 2014
Bugs fixed:
1.) Quick disconnect and reconnect from Modbus Master device(s) may cause PAC E01005 System Restart error.
Version: 1.1.15.97
Details:
P3-550
FW 1.1.15.97 Release Notes
Improvements:
1.) GS-EDRV100 discovery did not disable DHCP thus not allowing IP address to be permanently changed.
2.) Allow project download process from USB storage device to P3-CPU to continue even if .adpro file is missing to support
Binary Only project loads for OEM's.
3.) Saving project from P3-CPU to removable USB storage device should save .csv file as well.
4.) P3-CPU needs to send flush project message to a specific Remote after remote heart beat timeout is triggered.
5.) Added support for P3-SCM (Serial Control Module).
6.) Full Duplex now supported on P3-CPU RS-232 port in ASCII mode.
7.) Support for Ethernet IP protocol.
Bug Fixes:
1.) GS Drive(s) not discovered after 1st read of the system configuration.
2.) When scantime increases beyond negligible then response failures from Modbus RTU Slave(s)may occur.
3.) Modbus RTU using MRX instructions are currently being queued but should not be.
4.) MST 95% full bit(s) is not reset by Run-Stop-Run transition.
5.) When doing a "Remove PAC Project " with the GUI the "Eanble Project Transfer to/from USB" remains enabled and the password for this function is not cleared.
6.) Serial ASCII, RTS On/Off setting can cause port lockup.
7.) CPU null error when HSO module is located in the last slot of the 8 or 5 slot bases.
8.) AOUT/CPO, RTS drops one byte early.
9.) RTS timing affected by long scantimes only on RS-232 port (Modbus RTU).
10.) RS485 timeouts increase with scan times.
11.) P3-CPU E01005 errors, caused by MODBUS TCP service.
12.) System Tags for Ethernet Speed are populated backwards.
13.) ModbusTCP Server inbound connection handling problem due to failed outbound TCP connection.
14.) Portable Memory Device, Critical Error E02204 after USB thumb drive remove.
15.) ModbusRTU instructions fail to Complete during runtime project transfer.
Version: 1.1.14.39
Details:
FW 1.1.14.39 Release Notes
December 17, 2013
Bugs
1) After upgrading FW to 1.1.14.38 the serial com port settings reset to default.
Version: 1.1.14.38
Details:
FW 1.1.14.38 Release Notes
December 4, 2013
Improvements:
1) Apple iOS support for new PacData app.
2) Support for new P3-550 LCD hardware.
3) Modbus RTU/TCP improvements.
Bugs fixed:
1) Resolved Remote Slave IO data delivery instability on large system set up.
Notes:
1) This version of firmware is supported with 1.9.0.13 and higher of the Productivity Suite software.
2) Revision D1 & higher of the P3-550 downgrading firmware to older than 1.1.14.38 will cause LCD to display incorrectly. Please contact tech support for additional support @ 1(800)633-0405.
3) Revision D & lower of the P3-550 upgrading to 1.1.14.38 firmware may cause LCD display issue. Please power cycle P3-550 to fix this issue.
Version: 1.1.13.24
Details:
FW 1.1.13.24 Release Notes
June 17, 2013
Improvements
1) Increase multicast TTL default to 30.
2) Web Server page support for new system tags along with behavior check
First Scan Interval [x100=usec] SWR-001530
Portable Memory Device Ready SBR-000001
Portable Memory Device Eject SBRW-001006
Bugs
1) Extended Modbus reply to block requests of 2 dimension arrrays of BCD16 and BCD32 data types are wrong.
2) P3-CPU Enet interface becomes invalid if set up improperly (such as 255.255.255.255 or 127.0.0.1)
3) Repair DHCP functionality.
4) P3-CPU(P3-550 Rev. D) fail to download the 2nd base firmware along with the certain size of the PAC project.
5) Portable Memory Device Ready bit stays on after power down and removal of usb device.
6) Portable Memory Device Ready bit not initialized correctly when an invalid value is passed to it.
Version: 1.1.13.17
Details:
FW 1.1.13.17 Release Notes
December 6, 2012
Improvements:
1. Support for SRAM retentive memory increased to 492K on Rev D or higher P3-550 & all P3-530.
2. New 'First Scan Interval [x100=usec]' systen tag that holds the value of the First Scan Time.
3. New Logout button added to Web server page.
4. Added selectable timeout for web server in Hardware Configuration.
5. Event log is now logged onto pen drive if option selected in Data Logger.
6. Two new system tags 'Portable Memory Device Ready' & 'Portable Memory Device Eject'.
7. New Remote Slave MST bit 'Module Ready' that indicates good communication to the P3-550.
8. Support for new P3-RX remote slave module
Bugs fixed:
1. Critical Base Comm Errors reported (after power up/soft reset) with multiple P3-08THM(on two or more bases).
2. P3-550 485 serial port states that it can have node addresses from 1-247, but only 1-127 work.
3. Each stop mode project transfer causes a small of memory leak.
4. P3-550 External Ethernet port IP setting can not be the same subnet to its other Etheernet interface.
5. Remote Slave not responding after CPU power cycle.
Version: 1.1.12.14
Details:
FW 1.1.12.14 Release Notes
April 25, 2012
Improvements:
1. Support for new P3-HSO, P3-HSI & P2-16TD3P now supported.
2. New Web Server feature that allows viewing of read only system tags & the ability to open, save or delete files from USB pen drive (if installed).
3. Support for new P3 firmware packages (.adfw)
4. Data Logger 'Log System Errors' file now stored in logs folder for access by Web Server.
Bugs fixed:
1. MRX and MWX do not work correctly with more than 255 tags.
2. Clock set tags extended Modbus address are broken.
Follow the below steps to gain access to the new Web Server pages.
Note: if upgrading from version 1.1.11.28 or older a second upgrade with the same 1.1.12.x firmware file is needed in order to use the web server.:
1.) Open Productivity Software 1.6.
2.) Go to PAC > Check/Upgrade Firmware.
3.) Select a valid firmware file.
4.) Put the P3-550 cpu run/stop switch in stop.
5.) Upgrade the P3-550 with 1.1.12.14 firmware.
6.) Once firmware update has finished, reboot the P3-550.
7.) Repeat steps 2 - 4. (This step loads the web pages into the P3-550)
8.) Place the run/stop switch back into run.
Refer to help topic P195 for enabling the Web Server.
Note: Additional Web Server information is available in help topic P248.
Version: 1.1.11.28
Details:
Version 1..1.11.28
December 21, 2011
Bugs fixed:
1. PAC project with ASCII communications at a baud rate of 115.2k with an Ethernet Modbus TCP/IP client/server connected can cause P3-550 to crash.
Version: 1.1.11.27
Details:
Version 1..1.11.27
November 29, 2011
Improvements:
1. Improvement made for internal quality control procedures.
Version: 1.1.11.26
Details:
Note: Version 1.5.0.21 software or higher must be used with this firmware.
Note: There is a product advisory associated with this firmware version. Please see the advisory here before installing the updated software and firmware.
Improvements:
1. USB 1.0/1.1 support for USB OUT port no longer supported.
2. Non-critical error E02406 "GS Config Failed" is generated if both GS Drive and EDRV-100 are missing.
3. Firmware version string tag and integer tags for major and minor FW version.
Bugs fixed:
1. When RX or WX instruction is setup to use the Ethernet Port, and the end device does not exist, the "InProgress" will get stuck and will never timeout.
2. Inactivity with DataWorx will close TCP connection, thus closing other unrelated TCP connections.
3. Modbus read instruction may stop working under extremely high traffic conditions.
4. P3-RS Firmware version not returned if connected to GUI through remote slave usb.
5. During upload software may report "No valid project file"
6. Analog modules in certain configurations may show Module Failed bit ON.
7. System tag data types SWR & SWRW, the extended Modbus addresses are broken on FW 1.0.10.21.
Version: 1.0.10.21
Details:
Bugs fixed:
1. P3-550 Battery Voltage System Word shows zero with good battery. (135)
2. Using DHCP option without DHCP server causes PAC to retain 10.10.10.10 address even after new IP address is set in project. (1062)
3. Modbus RTU: Getting false exception response for valid query from a connected Master device. (1200)
4. P3-RS Remote Slave RS485 port can sometimes lockup/lost if any communications instruction fails to complete. (1172)
5. CPU can lock up with heavy TCP/IP traffic. (1163)
6. Greater than 30 Modbus instructions can cause memory allocation errors. (1143)
7. USB Pen drive project transfer of bad project does not generate error message. (1135)
8. 65 or more analog input channels in a base can cause loss of data. (128)
9. P3-RS LCD clock is not updated with correct time after a stop mode transfer. (1111)
10. Modbus, No exception response when Function code 16 write to any non-existent address. (1094)
11. P3-550 is allowing the AOUT instruction to be queued before the AIN instruction has been disabled.(1025)
12. RS232 using ASCII Out instruction with replies coming in, with no ASCII IN instruction causes port to lock up.(969)
Version: 1.0.9.23
Details:
Bugs fixed:
1. Data Logger would not properly log on the DOW or DOM, as configured. DOW logging would only occur Sunday. DOM logging would only occur on the 4th. Selecting multiple entries could prevent data from logging altogether. (1039)
2. In certain situations, the PAC would receive Modbus TCP writes that were larger than expected and would give an exception response. The size allowance has been increased to accommodate these situations. (1091)
3. MWX over serial to slave node 0 (broadcast) would wait for a response to update its status bits. No response arrives for broadcasts, so the instruction’s status bits would never indicate successful completion of the message. (1071)
4. With the HW Config Modbus port setting ‘Timeout between data query and response’ set to >1sec, the timeout would occur at 18sec. Also, the initial connection attempt timeout was always 18sec regardless of the value specified in the setting. (938)
5. As a Modbus server, the PAC would respond to erroneous broadcast messages with an exception. No response should be generated for erroneous broadcast messages. (1072)
6. When the PAC was a Modbus RTU serial master and issued broadcast writes (Node 0), it was not properly adding the 3.5 character delay between messages. The lack of delay between messages could cause slave devices to reject the messages. (1097)
7. In certain situations, when the PAC was receiving Modbus writes to Strings, the PAC would inadvertently add an invalid character to the end of the String. (1107)
8. During project transfer, the Ethernet default gateway could revert to a value specified in a previous project. (1052)
9. In the H/W Configuration, if the "RTS On Delay Time" is near or greater than the Response Timeout, the PAC will exception the response. If the time is 1000ms or greater the request will never be sent out and the port will lock up. (1008)
10. If the TCP/IP setting “Use the following†were checked, the PAC’s IP would incorrectly retain any temporary edit made to these values, even at power up or stop to run transition. Correct behavior: If “Use the following†is selected, the values specified will be applied at each power up or stop to run transition. The values may be changed manually using ProductivitySuite temporarily, but they will revert to those specified in the project at power up and stop to run. If edits to these values should always be retained, “Use current settings†should be selected instead. (1051)
11. Removing the PAC project would revert the Default Gateway to 0.0.0.0. (1041)
12. Hostname field was missing from email send, causing some servers to reject the message. (1053)
13. Battery Voltage tag could go for extended periods without an update. Since the tag was zeroed during a stop mode transfer, it could incorrectly show 0V for quite some time. It is now updated immediately after stop mode transfer and every few seconds thereafter. (1049)
Improvements:
1. A connection to ProductivitySuite programming software through an unreliable network was not tolerated well. Improvements were made to firmware, and the next version of Productivity Suite to be released will also have improvements in this area. Current Productivity Suite as of August 2010 is 1.3.0.13. (1066, 1076)
Version: 1.0.8.28
Details:
P3-550 & P3-RS Firmware Release Notes
Version 1.0.8.28
Apr 5, 2010
Bugs fixed:
1. Fixed an obscure issue with forcing. (1046)
2. CPU would respond to Productivity Suite over Ethernet with incorrect source port. Was an issue if connecting through a router. (1042)
3. Enabling M6: in the LCD menu without a tag specified would cause loss of function of LCD. (989)
4. CPU could temporarily get stuck in load state after stop mode transfer. (1003)
5. Default IP Gateway would revert to 0.0.0.0 after power cycle, regardless of settings in the project. (1013)
6. Increased scan times could cause erroneous timeouts on Modbus RTU. (1023)
7. Comms into P3-RS serial ports might not update number of characters received. (1027)
8. CPU could respond improperly to a Modbus TCP request for too large a selection. (551)
9. CPU could allow an improperly formed Modbus packet to write into memory. (888)
10. Very short power interruption could disable system until a full power cycle is done. (929)
11. Simultaneous receive and transmit on serial ports has a chance to lock up ports. (969)
12. Removing the data log file from the USB storage device and re-installing device could halt data logging. (972)
13. Use of MWX and GSW together in a project would reset the CPU. (981)
14. Modbus writes to bits for I/O of the PAC could roll over to I/O for the next slot if excessive length specified. (755)
15. File system error on USB storage device not immediately reported upon insertion. (814)
16. P3-RS with no data traffic could be disconnected but not detected as such. (966)
17. A tag added to a project with a runtime transfer not populated with the initial value. (958)
18. 'DL write failed' error could be erroneously logged when going from run to stop mode. (971)
19. P3-RS serial port buffer not cleared on stop to run transition. (945)
20. One Modbus TCP connection will never clear, allowing only 31 connections (should allow 32) on subsequent attempts. (926)
21. Memory leak when EMAL instruction fails repeatedly. (931)
22. Using CPI instruction on P3-RS can infrequently reset system. (943)
Version: 1.0.7.23
Details:
This firmware corrects possible issues with forcing that could be seen during run time transfer of projects.
Only the P3-550 requires upgrade to 1.0.7.23.
P3-RS units need not be upgraded from 1.0.7.20 to 1.0.7.23. P3-RS firmware revisions 1.0.7.20 and 1.0.7.23 are identical excepct for the revision.
Version: 1.0.7.20
Details:
First release.