adccommunitymod (AutomationDirect) asked a question.

P3K E02204 when using USB Memory stick

Created Date: March 27,2019

Created By: kewakl

**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****

I am using a Sony MicroVault Classic 4gb D33021 memory stick with a P3-550. I am testing this using FW1.1.14.39 SW1.9.2.0 . YES! I KNOW that there are newer SW/FW releases. Occasionally *AFTER* removing the memstick, I get an error E02204 - and the CPU exits run mode. The help file says that this means that the P3-EX or P3-RS is not communicating. This project does not have an expansion module or remote base. Base configuration The code will wait for PMDR, then copy data to a LOG array, trigger the log event (blah blah) and then assert the PMDE. There is a lamp attached to DO-0.1.3.1. The lamp lights on PMDR and does not go out until one second after falling edge of PMDE I do not remove the USB stick until the lamp goes out. Even with NO user program, I see the same error/code Further notes: I changed FW/SW (1.1.15.114/3.4.1.1) cannot duplicate in this rev set. BUT, I cannot (as yet) qualify our test machine to these revisions. I downgraded to (1.1.14.39/1.9.2.0) problem did not return until I spam the memstick in/out quickly. The issue persists until I remove project , cycle power and transfer the project to the CPU. I can reproduce this issue on this CPU.


  • adccommunitymod (AutomationDirect)

    Created Date: March 27,2019

    Created by: kewakl

    I am using a Sony MicroVault Classic 4gb D33021 memory stick with a P3-550. I am testing this using FW1.1.14.39 SW1.9.2.0 .

    YES! I KNOW that there are newer SW/FW releases.

    Occasionally *AFTER* removing the memstick, I get an error E02204 - and the CPU exits run mode.

    The help file says that this means that the P3-EX or P3-RS is not communicating.

    This project does not have an expansion module or remote base.

    Base configuration

    The code will wait for PMDR, then copy data to a LOG array, trigger the log event (blah blah) and then assert the PMDE.

    There is a lamp attached to DO-0.1.3.1.

    The lamp lights on PMDR and does not go out until one second after falling edge of PMDE

    I do not remove the USB stick until the lamp goes out.

    Even with NO user program, I see the same error/code

    Further notes:

    I changed FW/SW (1.1.15.114/3.4.1.1) cannot duplicate in this rev set. BUT, I cannot (as yet) qualify our test machine to these revisions.

    I downgraded to (1.1.14.39/1.9.2.0) problem did not return until I spam the memstick in/out quickly.

    The issue persists until I remove project , cycle power and transfer the project to the CPU. I can reproduce this issue on this CPU.

    Expand Post
  • adccommunitymod (AutomationDirect)

    Created Date: March 28,2019

    Created by: kewakl

    FW 1.2.7.37 SW 3.4.1.1 does not fault the PAC, it just fails to assert PMDR after several spam insert/removals.

    Stop/run does not recover. Requires a power cycle.