Issue(s) with NSX 2.6.0.191

Stephen Bolton
Stephen Bolton Junior Member
in NetLinx Studio
I have found that the reported bug fix below appears to still not be quite right.
NSX What's new wrote:
BUG FIX - The problem with truncated strings/unpredictable messages being displayed in the Notification and Diagnostic panes has been corrected. This was occurring when a $00 value was imbedding in the string being sent/received from a device.
This string is part of a polling sequence for a barco vp...

send_string dev,"$FE,$01,$67,$68,$FF"

but in the diagnostics window it displays as follows...

Line 716 (17:21:10):: String To [5001:1:1]-[$FE$01gh$FF]

$67 (ascii g)
$68 (ascii h)

Not a single $00 to be seen.
· Share on FacebookShare on Twitter

Comments

  • Marc Scheibein
    Marc Scheibein Junior Member
    This was and is the way diagnostics displays the bytes. If the byte value is printable ASCII, the corresponding character is shown (like the $67->g and $68->h). If it is a nonprintable character, the hex value is shown (i.e. $0D ). The hex values are always indicated with $ and have 2 digits.
    · Share on FacebookShare on Twitter
  • Stephen Bolton
    Stephen Bolton Junior Member
    I thought (and hoped) from the bug fix text that this issue of misrepresentation, and I consider it a significant issue, was fixed also.

    ;-)

    This is a diagnostics window and in my view it should show EXACTLY what is being sent, not a representation or interpretation of the packet because it is printable or non-printable.

    If we spit out a '$67' in a string, I would fully expect to see just that, not 'g'.

    Outbound strings can generally be vouched for from your code, but inbound strings - this can be very tedious reading some bytes as hex and some as ASCII.

    If this window can display '$03' as '$03' and not '♥', then there should be no reason to display 'g' and not '$67'!!

    There is generally enough to do already without having to interpret the bytes back to their native form in your head (and usually whilst under pressure)!

    I hope it is put on the list for next time...it certainly erks me when it shows up.
    · Share on FacebookShare on Twitter
  • mpullin
    mpullin Obvious Troll Account, Marked for Deletion
    Stephen Bolton wrote:
    If this window can display '$03' as '$03' and not '♥', then there should be no reason to display 'g' and not '$67'!!

    That would indicate that ♥ is 3, but in my experience ♥ <3
    · Share on FacebookShare on Twitter
  • Daniel Tehan
    Daniel Tehan Junior Member
    In the Preferences Diagnostics settings you can choose to Display Control Codes as Hex or Decimal.

    It would be nice to also be able to select if printable chars show up as their ASCII representation or to show all characters in HEX, or Decimal for that matter, since there are several devices that would be much easier to debug that way.
    · Share on FacebookShare on Twitter
  • ryanww
    ryanww Junior Member
    Another thing I noticed is that when your writing code which is indented in any more then the first level and you hit enter, it goes back to the beginning level far left. That drives me nuts.. where can I download a previous version? either that or fix it..
    · Share on FacebookShare on Twitter
  • Stephen Bolton
    Stephen Bolton Junior Member
    mpullin wrote:
    That would indicate that ♥ is 3, but in my experience ♥ <3
    According to the All Character Chart (437), it is exactly $03 or ASCII 3.

    :-)
    · Share on FacebookShare on Twitter
  • Marc Scheibein
    Marc Scheibein Junior Member
    ryanww wrote:
    Another thing I noticed is that when your writing code which is indented in any more then the first level and you hit enter, it goes back to the beginning level far left. That drives me nuts.. where can I download a previous version? either that or fix it..

    Hm, can not reproduce this.....
    In Studio's preferences, check in EDITOR tab the setting of "Intend before text with..." and also "Enable auto intendation" Maybe while the update process your previous settings were lost.
    · Share on FacebookShare on Twitter
  • ryanww
    ryanww Junior Member
    That was it.. oh well.. guess it got messed up in the update.. thanks..
    · Share on FacebookShare on Twitter
  • DHawthorne
    DHawthorne Junior Member
    dtehan@unitedvi wrote:
    In the Preferences Diagnostics settings you can choose to Display Control Codes as Hex or Decimal.

    It would be nice to also be able to select if printable chars show up as their ASCII representation or to show all characters in HEX, or Decimal for that matter, since there are several devices that would be much easier to debug that way.

    It's the automatic display of ASCII that causes the problems. ASCII for $00 is nothing at al, so of course it doesn't display. Let it be Hex, decimal or ASCII, and not some jumbled combination. And for that matter, give us a way to change the display type on the fly instead of needing to do it in Settings. With all the types of devices out there, no one way is sufficient.
    · Share on FacebookShare on Twitter
  • Stephen Bolton
    Stephen Bolton Junior Member
    Issue(s) with NSX 2.6.0.191

    The What's New text advises
    FEATURE - Launches the new AMX-PI (Production Information) application from
    the Tools menu. This project contains technical information about all available
    AMX products. This replaces the "Software History 2" application. Please visit
    www.amx.com for the latest version of this new application.
    I don't seem to be able to run this...only Software History is visible within Studio. Is it just my install?
    · Share on FacebookShare on Twitter

Categories