incagarcilaso Posted February 10, 2017 Author Share Posted February 10, 2017 14 minutes ago, Don said: No. If your coding is right, you get a value, if is wrong, you don't get a value. Simple as that. Yes but if Axpert in a firmware update make a slight change in the syntax in their coding and ICC coding does not know about this, then this will cause an error - that is what I am referring to. And going back to what I originally referred to, for this reason if you have ICC communicating with different firmware version code this could, potentially, cause different behaviour. Quote Link to comment Share on other sites More sharing options...
Don Posted February 10, 2017 Share Posted February 10, 2017 That is not likely to happen. They do not change where the value comes from slightly. Those things are normally cast in stone. If it should ever happen and a value comes through as an error or a 0, I notify Manie. He has a look at it and fixes it. As I stated before, firmware changes charging times and what to do when a certain value is reached and how to react in other instances. Where the values comes from stays the same. Quote Link to comment Share on other sites More sharing options...
incagarcilaso Posted February 10, 2017 Author Share Posted February 10, 2017 Not very likely no, but also not impossible. So I was just offering to help by letting you know that I was willing to test against a second firmware version to eliminate any doubts but if it's not necessary that's fine. Quote Link to comment Share on other sites More sharing options...
PaulF007 Posted February 10, 2017 Share Posted February 10, 2017 5 hours ago, incagarcilaso said: Not very likely no, but also not impossible. Thats like saying SONA is going to be quiet . Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.