Unused address

Started by dgd, March 01, 2015, 12:50:18 PM

Previous topic - Next topic

dgd

After changing my classic 150 from id 11 to id 10 using local ap I now have a message that says unused address 11 replacing the normal status display on the MNGP.
It is not going away and there seems no way to go back to the normal status display. I prefer not to power cycle the classic so is there some sequence of keys to restore the normal status screen?

Is this a known bug and has it been fixed in this latest firmware?

Dgd
Classic 250, 150,  20 140w, 6 250w PVs, 2Kw turbine, MN ac Clipper, Epanel/MNdc, Trace SW3024E (1997), Century 1050Ah 24V FLA (1999). Arduino power monitoring and web server.  Off grid since 4/2000
West Auckland, New Zealand

atop8918

You have to remember that the MNGP is also requesting status from the Classic using MODBUS so that it is now necessary to point the MNGP to the Classic's new MODBUS address at 10. To do this hold the left arrow on the MNGP and tap the down arrow to change the MODBUS address that the MNGP is requesting from. That should do the trick.
You can point the MNGP to any Classic networked together using the Master Slave jacks using this method. 

atop8918

Sorry, I should have mentioned that this should be done on the status screen.
You can also set the MNGP request address to 255 which will always request from the attached Classic.

dgd

Thanks Andrew.
I now understand. The local App actually changes the Classic ID but the Mngp only changes the ID it is looking for. This would probably explain why sometimes, probably after a midnight reset the classic went back to 11 as it gets reset by the mngp.
Dgd
Classic 250, 150,  20 140w, 6 250w PVs, 2Kw turbine, MN ac Clipper, Epanel/MNdc, Trace SW3024E (1997), Century 1050Ah 24V FLA (1999). Arduino power monitoring and web server.  Off grid since 4/2000
West Auckland, New Zealand

atop8918

Yeah, that is correct. It's all unnecessarily complicated, really. Next product I'll try to incorporate some less esoteric comm standards at least UI-wise. MODBUS is great for industrial controls, but it's been a PITA for almost everything else.



boB

Modbus works fine as long as things are implemented OK.  There is still work to do on the Classic but
no time to fix little things like this.

The address thing is working exactly as intended.  The whole thing ~COULD~ change the MNGP
address it is looking at when you change a Classics' modbus address with the Local App but
then that would complicate many other people's systems.  Probably shouldn't be able to
change the Classics' modbus address with the LA.  Why did we do that, Andrew ?  Must
have had something to do with Classic Lites ?  Every system should have at least one
MNGP.  It's a PITA without an MNGP to know what is going on and it makes it very
hard for customer support.

The Classic and MNGP DOES remember its address after a reset as long as it is saved to EEprom.

Not sure what you mean bu the LA changes the Classic ID but the MNGP only changes the ID it
is looking for  ?   Do you mean the 8 character name of the Classic ?

The MNGP and LA look for a modbus address and not an ID name.  There is an 8 character name
you can give a Classic but that has no coordination with the modbus address itself.

boB
K7IQ 🌛  He/She/Me