• T
    Turbo

    Nope.

    Right now, the device is working fine. If I turn it OFF and ON again within Mango, it just shows the data as uncertain.

    I did disable the events for this, though, as I generally don't need my database flooded with lost poll type numbers.

    That all being said, it's working Fine Now, so long as I don't use the Enable/Disable Data Source buttons.

    posted in User help read more
  • T
    Turbo

    Ok:

    Since I'm logged in anyways, here we go:

    stty -F /dev/ttyUSB1 -a
    speed 9600 baud; rows 0; columns 0; line = 0;
    intr = ^C; quit = ^; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z;
    rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 0; time = 0;
    -parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
    -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8
    -opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
    -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke -flusho -extproc

    After disable inside Mango:
    stty -F /dev/ttyUSB1 -a
    speed 9600 baud; rows 0; columns 0; line = 0;
    intr = ^C; quit = ^; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z;
    rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 0; time = 0;
    -parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
    -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8
    -opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
    -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke -flusho -extproc

    After re-enable inside Mango:
    speed 9600 baud; rows 0; columns 0; line = 0;
    intr = ^C; quit = ^; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z;
    rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 0; time = 0;
    -parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts
    -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff -iuclc -ixany -imaxbel -iutf8
    -opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
    -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt -echoctl -echoke -flusho -extproc

    posted in User help read more
  • T
    Turbo

    Heya:

    I appreciate you looking into this. I also noticed a new update to Mango's Modbus library. Does this address this issue?

    Do you want me to still look into stty output for my configurations?

    Cheers,
    -Greg

    posted in User help read more
  • T
    Turbo

    Greetings, all:

    I've found a new interesting behavior with some of our sites after updating to 3.6 under Linux.

    Brief summary, looking for help:
    (1) Connected to solar inverters, 9600, via optically-isolated RS-485 adapter. This unit works fine (Generally) with all my other modbus devices I've tested it on. This particular inverter is doing something, that sometimes breaks 3.6. It worked fine with 3.5.

    (2) When using the Modbus Tools, Mango never sees that data come back from the inverter. (No Response from Slave XX is the error message)

    (3) When using the Enable/Disable data source option, Mango never sees the data come back from the inverter. (No Response from Slave XX is the error message)

    (4) When just polling the device, Mango DOES see the inverter responses, but only AFTER the system is restarted or the computer is restarted.

    (5) If you disable the data source, and restart the data source, it doesn't see the respones.

    (6) If you restart mango entirely, it DOES see the responses from the inverter.

    This behavior is (apparently) new in 3.6, as I had another site that was working fine with 3.5 and is now showing this behavior with 3.6.

    My hypothesis is that these inverters are maybe responding too quickly (or something), and that's tripping up the RX/TX control circuit in the 485 adapters. I've tried messing with the flow control, and the behavior described above seems dependent on the resetting of Mango entirely.

    I'm using Linux, and the JSSC drivers as we've discussed here before.

    I've got (2) identical serial converters on most of my sites- FTDI chip based devices. They work fine running my other (2) devices that are standard in my install, an electrical meter and a (self-designed) Modbus-talking RS-485 input module.

    These inverters always seem to talk properly using Modscan32 or similar tools, but fail with Mango as described above.

    If I get a chance to visit one of these sites, I'll take a scope out and see what's happening on the bus, to test my RX/TX switching hypothesis.

    Any thoughts?

    Cheers,
    -Greg

    posted in User help read more
  • T
    Turbo

    Greetings, all:

    I've been using USB to Serial converters on my little Linux Based Mango devices for my business. I've had varying luck by brand, and I figured this is as good a place as any to talk about by mest brand so far, and some troubles they've had.

    The ones I use are the DTech USB 2.0 to RS 422/ RS 485 adapters. These units are based on the FTDI Chipset, and I generally have Good Luck. I've probably installed clost to 50 of these things, with so far 3 failures- One due to a direct lightning hit, and the other two Very Odd, Indeed.

    It's this "very odd indeed" one that I want to comment on, as a sort of Use Case for how Super Useful the "Log IO" function can be in Mango. I was doing final testing on a product that was too ship, and found that the Modbus Serial data source was behaving all weirdly-- Sometimes polling correctly, but generally Failing Wholesale.

    I was just about geared about to post a mango thread about wondering if the latest Modbus module had some bugs in it, but lo and behold, the "Log IO" showed me something was weird.

    So:
    The poll should look like this (Using the CAS Modbus Scanning Tool, if you ever need a Modbus Doodad, that's a great little test tool)
    [22:21:24] => Poll: C8 04 00 00 00 14 E1 9C
    [22:21:25] <= Response: C8 04 28 00 6E 00 9A 08 8D 08 84 08 81 08 8F 08 87 08 A1 00 D4 01 AF 20 E2 00 0E 00 21 00 20 00 00 00 6C 00 00 00 00 00 00 09 28 AD 11

    Mango was seeing this:
    2019/08/29-22:12:21,943 O c80400000014e19c
    2019/08/29-22:12:21,955 I 6feeffffffd73d8efe
    2019/08/29-22:12:22,023 I c80428006e00a708da08d808da
    2019/08/29-22:12:22,025 I 08e708da
    2019/08/29-22:12:22,026 I 08f5
    2019/08/29-22:12:22,027 I 00
    2019/08/29-22:12:22,027 I d401
    2019/08/29-22:12:22,028 I c320
    2019/08/29-22:12:22,049 I e1000a002a00250000007000000000000008f8eb71

    I was thinking-- OKay, maybe there's a bug in the serial driver? You can see Mango originating the proper request "c80400000014e19c " which is a read input registers starting at 0 for 20.

    Then, Mess starts coming back into the device almost immediatly after. You can see the start of my Slave device talking back, "c80428006e00a708da08d808da" .. But before that is this "6feeffffffd73d8efe"

    Turns out that Mess was coming from the RS485 chip-- It looks almost as if the Serial device server isn't actually swapping RX/TX direction (It's a single duplex, 19200 link for this connection), and is scrambling itself up. So I plugged in that USB adapter into my Windows Box, and CAS Modbus Scanner says the same mess:
    [22:19:12] => Poll: C8 04 00 00 00 14 E1 9C
    [22:19:12] <= Response: 6F EE FF FF FF D7 3D 8E FE C8 04 28 00 6E 00 8F 08 6E 08 69 08 5E 08 71 08 65 08 7E 00 D4 01 B6 20 E2 00 0B 00 11 00 0D 00 00 00 6E 00 00 00 00 00 00 09 20 B2 34

    There's the valid poll, followed by the Huge Mess of Whatever.

    This was a brand new converter, right out of the box. If I have a chance, I'll look at it under the microscope and see if I can figure out why it's broken, just for my own edification.

    So: Anyways, lesson learned here: If Mango is showing Bizarre Things with Serial, check your USB adapter first.. I had another one of these adapters fail sort of randomly, and that one is here on the floor next to me. I'll see if this one has the same random problem.

    Speaking of this, does anyone have any other trustworthy but sub $50 USB to Serial 485 devices? There seems to be a certain lack of these things out there that don't suck, and I use a LOT of 485... I've used several brands, and these DTech ones are the least achy-breaky of the ones I've tried. If my projects had higher budgets, I'd be getting Name Branded Units , but I can't justify $300 converters on these devices...

    Cheers,
    -Greg Linder

    posted in How-To read more
  • T
    Turbo

    Yeah. I'm a clown.

    I disabled "Enable checking for upgrades"-- I don't want these instances auto-upgrading (since most are on cell plans, and I need to keep my Cell data budget under control), so I'll just have to remember to re-enable that box before checking.

    posted in User help read more
  • T
    Turbo

    Upgrade Release Channel shows Production. I've never configured the release channel for Dev.

    posted in User help read more
  • T
    Turbo

    This is a new one for me.

    Fresh Mango install, and the Modules -> Check for Upgrades says this instantly when I click the "check for upgrades" button.

    ma.log doesn't record anything when this happens.

    Checked out my DNS settings, and I can ping/nslookup etc from my command line, but Mango seems to have trouble checking for updates.

    Not a big deal, since I can manually upgrade stuff, but I dunno why this is happening. First time I've seen this on a dozen Mango installs here now.

    posted in User help read more
  • T
    Turbo

    Greetings, all:

    We're running Mango on embedded machines with 1 Gig of RAM and 16 Gigs of storage. I wonder if someone more knowledgeable could through some stuff up here about the best way to optimize systems with limited RAM and Hard Disk.

    To whit, I understand purge settings of data to keep disk usage under control, but I'm not sure what to do for memory.

    We're running ~300 point systems with 5-sec polling on most points, nearly all of which is getting sent up via the persistent TCP publisher. I'm not quite sure how to minimize Mango's memory footprint. Generally, TOP shows of the 1001.5 total, 35.4 free, 317.4 free, and 648.6 buff/cache on a freshly running instance on live data.

    I was browsing the Forum here, and have seen many things about memory leak solutions and whatever else. So: Any advice on keeping Mango Happy with limited Memory and Disk resources?

    Cheers,
    -Greg

    posted in User help read more
  • T
    Turbo

    Thanks for the quick updates: @CraigWeb @Jared-Wiltshire

    This fixed the Modbus tools, and I just tested it, so we're good to go. Thanks for that. These tools are Super Useful, as even thought Modbus has been around for longer than I've been alive, people who implement it still can't agree if it's 0-indexed or 1-indexed, or what the actual difference is between holding and input registers are.

    Also, I verified the flashing save Icon issue with multiple tabs... I think I noticed this before, but in my exhausted stupor the previous night I was sort of not thinking straight.

    Thanks!

    posted in User help read more