MaxScanner - what are credits?

[malc_b]

As I new, hi everyone.

A bit of challange trying to register, isn't it, with all the questions in german.  Google translate to the rescue, though.

I'm playing around with a raspberry pi for a home automation system.  This is a B+ running at standard clock speed, comand line only.  I've got a max cube and 1 radiator head installed (and physically there is only one head at the moment).

I've installed fhem but lately it seemed to be running rather slow so I tried taking stuff out by editing fhem.cfg and putting # at the front of lines but that doesn't seem to work for attr lines as rereadfg then moans about no define for that attr.  Is there a trick for this?

But for now I've just copied fhem.cfg and deleted the lines.  This has made it a lot faster so something I've messed.  I've taken out usb as I won't be using that and a dashboard I started to try and a svg plot which I think I messed up as it wouldn't plot anything.  When I look in edit files there seems to be a lot of plots for devices I don't have.  I assume these are templates and this is normal, yes?

I've look at the Max wiki (http://www.fhemwiki.de/wiki/MAX) and at the maxscanner (http://www.fhemwiki.de/wiki/MAX!_Temperatur-Scanner) and I'm now trying to set up maxscanner.  I don't understand the wiki.  What are credits?  And I'm not sure I understand what scnMinInterval, scnModeHandling, and scnProcessByDesiChange exactly do, which is probably down to google translate's efforts.

[fruit]

A bit of challange trying to register, isn't it, with all the questions in german.

I've installed fhem but lately it seemed to be running rather slow so

It shouldn't be, especially with just Cube and one device. Sounds as though something else is using resources.
I had many dozens of devices/definitions on a B along with many plots, it began to get unresponsive at that stage - after about a year.

I tried taking stuff out by editing fhem.cfg

Don't do it that way! Use the web interface. Sooner or later you will break something doing that way and may not be easy to fix - been there!

When I look in edit files there seems to be a lot of plots for devices I don't have.  I assume these are templates and this is normal, yes?

Normal, they are default plot files you can use if you wish or self-defined variants too.

I've look at the Max wiki (http://www.fhemwiki.de/wiki/MAX) and at the maxscanner (http://www.fhemwiki.de/wiki/MAX!_Temperatur-Scanner) and I'm now trying to set up maxscanner.  I don't understand the wiki.

Google translate can make a real mess at times! Try a phrase at a time.
I've not used the scanner but many do

What are credits?

If you look at the Cube web page you will see something like

Code Auswählen Erweitern

dutycycle 1 %
Wireless devices have to follow the 1% rule - ie. spend no more than 1% of time transmitting in order to avoid congestion./interference with others - part of the regs
My example above shows that my current rate is low at 1% of that 1% rule. If I were to send a weekprofile then dutycycle would increase dramatically. If the amount is exceeded, commands are queued.

And I'm not sure I understand what scnMinInterval, scnModeHandling, and scnProcessByDesiChange exactly do

No idea I'm afraid but try searching the forum for each individual term

[John]

some clarifications:

   
• MaxScanner is now a official part of FHEM (module 98_MaxScanner)
• the idea of MaxScanner is to get more often information from the thermostat (radiator head)

see this image without scanner: (Raumtemperatur = current temperature, Soll-Temperatur = desired Temp., Ventilstellung = valve position)

(http://www.fhemwiki.de/w/images/6/6e/2013_12_MaxScanner_Vorher.png)

and that image with scanner

(http://www.fhemwiki.de/w/images/1/19/13_12_01_Scanner_ModeChange.png)
As you can see we get more information about the temperature using the scanner.

How does it work ?
Some people found the following rules to force the thermostat to send more often information:

   
• when you change the desired temperature, the thermostat sends the current temperature and the valve position (within 3 minutes)
• the same happens, when you change the mode of the thermostat (AUTO,MANU)

if scnProcessByDesiChange=1 the scanner will use the first trigger method.
if scnprocessByDesiChange=0 the scanner will use the second trigger mode.
In case of scnProcessByDesiChange=1 you can decide, which mode should be used (AUTO,MANUAL,NoChange)
If case of scnProcessByDesiChange=1 you will get an image like following:(http://www.fhemwiki.de/w/images/c/ca/13_12_01_Scanner_DesiredChange.png)

John

[malc_b]

Thanks for the replies.  I still don't know what credits are.  It's in the fhem command reference for MaxScanner

scnCreditThreshold: the minimum value of available credits; when lower, the scanner will remain inactive; possible values: 150..600; default: 300

I guess it is something to do with the 1% rule.  Maybe it means time slots i.e. 300 time slots (of x ms)  in some period?