#436 NCE Packet Analyser Broken V3.3.2

System_specific
open
nobody
None
5
2013-02-24
2013-02-13
Dave Heap
No

The NCE Packet Analyser appears to have broken (at least for OS X 10.6.8).

Traced back through builds and it appears to have broken in r22622 Build #684.
http://builds.jmri.org/jenkins/job/Development/job/Packages/684/changes#detail0
"added an option to the Communications Monitor windows to allow users to filter out unwanted message types"

Still broken in r22768.

Discussion

  • Dave Heap
    Dave Heap
    2013-02-24

    I have now checked Windows XP Professional 32 bit and Windows 7 Ultimate 32 bit. Same result.

    Ben O'Malley has checked Mac OS 10.8.2 and Windows 7 Ultimate 64 bit. Same result.

    Have tested with both Prolific and FTDI USB-Serial adaptors.

     
  • Bob Jacobsen
    Bob Jacobsen
    2013-02-24

    What's not working?

     
  • Dave Heap
    Dave Heap
    2013-02-24

    Nothing appears in the output window, no matter what you do.

     
  • Dave Heap
    Dave Heap
    2013-02-24

    On 25/02/2013, at 1:25 AM, "Bob Jacobsen" jacobsen@users.sf.net wrote:

    What's not working?

    Nothing appears in the output window, no matter what you do.

     
  • Bob Jacobsen
    Bob Jacobsen
    2013-02-24

    I don't have a way to test this. I looked at the code and see a possible problem (though I don't understand why that wouldn't generate error logs). The fix for that is now in SVN. Could you try it and let me know? Thanks.

     
  • Dave Heap
    Dave Heap
    2013-02-24

    Apologies for not checking the system console log. Put that down to a senior moment. On my development machine it is in my face with Xcode, but on the train room computer it was a case of out-of-sight-out-of-mind. Added Start Up Action to "Open JMRI System Console" on train room computer. Muses ... wonder what governs the list of what does or does not appear in the list of available Start Up Actions. "Open NCE Monitor" is available, but not "DCC Packet Analyser". Must look into that sometime...

    Yes, it is fixed in r22816, thanks.

     
    Attachments