Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current

[QuesT]

Hallo,

weis nicht genau wohin damit.
Hab seit ein Tagen folgende Meldungen im log:

Was kann ich da tun?

Code: [Auswählen]

2014.10.30 19:22:53 1: 127.0.0.1:1234 disconnected, waiting to reappear (hmusb)
2014.10.30 19:22:53 1: HMLAN_Parse: hmusb new condition disconnected
2014.10.30 19:22:53 1: 127.0.0.1:1234 reappeared (hmusb)
2014.10.30 19:22:53 1: HMLAN_Parse: hmusb new condition init
2014.10.30 19:22:54 1: 127.0.0.1:1234 disconnected, waiting to reappear (hmusb)
2014.10.30 19:22:54 1: HMLAN_Parse: hmusb new condition disconnected
2014.10.30 19:22:54 1: 127.0.0.1:1234 reappeared (hmusb)
2014.10.30 19:22:54 1: HMLAN_Parse: hmusb new condition init
2014.10.30 19:22:55 1: 127.0.0.1:1234 disconnected, waiting to reappear (hmusb)
2014.10.30 19:22:55 1: HMLAN_Parse: hmusb new condition disconnected
2014.10.30 19:22:55 1: 127.0.0.1:1234 reappeared (hmusb)
2014.10.30 19:22:55 1: HMLAN_Parse: hmusb new condition init
2014.10.30 19:22:57 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:22:57 1: 127.0.0.1:1234 disconnected, waiting to reappear (hmusb)
2014.10.30 19:22:57 1: HMLAN_Parse: hmusb new condition disconnected
2014.10.30 19:22:57 1: 127.0.0.1:1234 reappeared (hmusb)
2014.10.30 19:22:57 1: HMLAN_Parse: hmusb new condition init
2014.10.30 19:22:59 1: 127.0.0.1:1234 disconnected, waiting to reappear (hmusb)
2014.10.30 19:22:59 1: HMLAN_Parse: hmusb new condition disconnected
2014.10.30 19:22:59 1: 127.0.0.1:1234 reappeared (hmusb)
2014.10.30 19:22:59 1: HMLAN_Parse: hmusb new condition init
2014.10.30 19:23:02 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:04 1: 127.0.0.1:1234 disconnected, waiting to reappear (hmusb)
2014.10.30 19:23:04 1: HMLAN_Parse: hmusb new condition disconnected
2014.10.30 19:23:04 1: 127.0.0.1:1234 reappeared (hmusb)
2014.10.30 19:23:04 1: HMLAN_Parse: hmusb new condition init
2014.10.30 19:23:05 1: HMLAN_Parse: hmusb new condition ok
2014.10.30 19:23:07 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:12 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:17 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:22 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:27 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:32 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:37 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:42 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:47 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:52 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:23:57 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:02 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:07 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:12 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:17 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:22 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:27 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:32 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:37 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:42 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:47 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:52 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:24:57 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:25:02 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 19:25:07 1: Error in CUL_MAX_SendQueueHandler: CUL SCC1 did not answer request for current credits. Waiting 5 seconds.

[hyper2910]

habe ich auch, es hängt wohl mit einem Update nach dem 10.10. zusammen.

bei mir sieht es so aus:
14.10.30 22:14:41 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 22:14:46 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 22:14:51 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.10.30 22:14:56 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds


und dann läuft es irgendwann wieder.

[QuesT]

Hallo,

stimmt dürfte hinkommen.
Hmm hoffe es hat wer ein Fix dafür.

[hyper2910]

Hi,


so ich hatte jetzt ein Update der MAX Module angeboten bekommen:
habe immer noch folgendes:

2014.11.03 08:30:03 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/14_CUL_MAX.pm line 574.
2014.11.03 08:30:03 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/14_CUL_MAX.pm line 587.


desweiteren bekomme ich immer nach ca. 2Tagen dieses:

Code: [Auswählen]

2014.11.03 07:40:16 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/14_CUL_MAX.pm line 574.
2014.11.03 07:40:16 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/14_CUL_MAX.pm line 587.
2014.11.03 07:40:16 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:21 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:26 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:31 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:36 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:41 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:46 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:51 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:40:56 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:01 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:06 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:12 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:17 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:22 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:27 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:32 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:37 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:42 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:47 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:52 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:41:57 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:02 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:07 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:12 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:17 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:22 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:27 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:32 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.03 07:42:37 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.


[deune]

Hallo Zusammen,

den beschriebenen Fehler habe ich auch - MAX ist bei mir nicht mehr prozesssicher.

WAF = -1000.

Auf dem CUL habe ich die aktuellste Firmware, aber dennoch wird nach einem fhem Neustart
das Max System immer träger, bis es dann nach ca. 18h ausfällt und mir das Log mit tausenden
Zeilen voll müllt.

Mach ich da was falsch?

Liebe Grüße aus der Eifel

Holger

[hyper2910]

Hi,

ich glaube das der Verantwortliche Matthias vom Modul nichts mehr macht.

Bei mir lief es jetzt auch ca. 18Std. durch und der Fehler war wieder da. Neustart und alles gut.

Vielleicht kann sich mal ein Programmierer das ansehen.!

[Palm_Maniac]

Hallo,

das gleiche Problem mit den selben Meldungen stellt sich auch b ei mir dar. Ich denke seit einer knappen Woche kommt es erst zu diesen Meldungen bei mir. Mal abgesehen davon, dass sich das Log File extrem schnell füllt, werden in dieser Phase auch keine Logfiles der Komponenten mehr geführt. Ich sehe das daran, dass die Grafen der Temp-Verläufe dann leer sind. Hoffentlich gibt es dafür bald eine Lösung, denn sonst muß ich erst mal wieder Back tu the Roots, also zum Cube.

[Palm_Maniac]

Hallo,

ich hab vorgestern mal meinen Raspi eine Rundumpflege verpasst, in dem ich das Linux aktualisiert habe. Alte Log-Files und Backups gelöscht usw. Dann bin ich in FHEM mal einem rumzickenden HT auf den Grund gegangen und habe ihn wieder zum "Mitspielen" bewegen können. Zuletzt habe ich die Firmware im CUL uf V1.61 aktualisiert. Alles in der Hoffnung, dass sich diese Meldungen verabschieden.

Heute dann die ernüchterung. Es hat nichts gebracht. Das Log ist wieder voll, das Interface reagiert extrem träge und es werden keine neuen Daten die grafischen Logfiles geschrieben.

Das ganze Elend wird mit folgendem Eintrag eingeleitet:

Code: [Auswählen]

2014.11.08 12:04:18 2: CULMAX: unknown message 21  900
Z0F0104600363C10000000098482C00CA25

2014.11.08 12:04:21 1: /dev/ttyACM0 disconnected, waiting to reappear (CULMAX)
Und danach dann wieder nur noch diese hier:

Code: [Auswählen]

2014.11.08 12:04:21 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:23 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:28 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:33 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:38 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:43 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:48 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:53 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:04:58 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:03 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:08 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:13 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:18 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:23 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:28 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:33 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:38 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:43 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:48 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:53 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:05:58 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:06:03 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
2014.11.08 12:06:08 1: Error in CUL_MAX_SendQueueHandler: CUL CULMAX did not answer request for current credits. Waiting 5 seconds.
Das bläht die Logfiles gigantisch auf. In diesen Momenten geht hier Steuertechnisch alles nur noch im Zeitlupentempo oder garnicht. Ein Shutdown Restart Befehl löst das Problem bis zum nächsten Mal.

Gibt es denn dafür keine Lösung, keinen Lösungsansatz? Was kann ich tun, was können wir tun um das Problem los zu werden?

[gero]

Ich habe das Problem seit ca. 4 Wochen, dass mein CUL sich ca. einmal am Tag aufhängt. Vorher lief er mit derselben Firmware 1 Jahr ohne Probleme. Zuerst dachte ich an einen Hardware-Defekt, aber da sich die Meldungen häufen, liegt es vielleicht doch an einer Änderung in FHEM. Zur Info: Der CUL wird bei mir zur Ansteuerung von MAX Komponenten verwendet. Nachdem fhem ein  disconnect von ttyACM0 meldet hilft bei mir meist nur ein stromlosschalten vom Raspberry. Im syslog bzw. dmesg Output wird nichts verdächtiges vom USB-Treiber gemeldet. Führe ich nur ein reboot durch, schlägt das Enumerieren von CUL auf USB-Ebene fehl. Der Raspberry ist nicht Schuld. Den habe ich schon ausgetauscht. Strom Versorgungsprobleme kann ich auch ausschließen.

Gruß,
Gero

P.S. Zur Zeit läuft der CUL seit 3 Tagen ohne disconnect!

[hyper2910]

Heute war nach ca. 6Stunden Schluss,  gestern lief es bald 20 Stunden.   So sieht es immer im log aus.

Code: [Auswählen]

2014.11.09 02:26:55 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/14_CUL_MAX.pm line 574.
2014.11.09 02:26:55 1: CUL_MAX_Parse: len mismatch
2014.11.09 02:26:55 1: CUL_MAX_Parse: len mismatch
2014.11.09 02:26:58 1: /dev/ttyACM0 disconnected, waiting to reappear (CUL868)
2014.11.09 02:26:59 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.09 02:26:59 1: PERL WARNING: Use of uninitialized value in numeric eq (==) at ./FHEM/14_CUL_MAX.pm line 587.
2014.11.09 02:27:00 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.09 02:27:06 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5

Code: [Auswählen]

14.11.08 20:17:01 1: sendEmail Text: Arbeitszimmer battery: low
2014.11.08 20:17:05 1: sendEmail returned: Nov 08 20:17:05 raspberrypi sendEmail[17165]: Email was sent successfully! 2014.11.08 20:17:05 3: Arbeitszimmer: Batteriewarnung battery: low
2014.11.08 20:17:10 1: CUL_MAX_Parse: len mismatch
2014.11.08 20:17:13 1: /dev/ttyACM0 disconnected, waiting to reappear (CUL868)
2014.11.08 20:17:14 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.08 20:17:15 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.08 20:17:20 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.08 20:17:25 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.
2014.11.08 20:17:30 1: Error in CUL_MAX_SendQueueHandler: CUL CUL868 did not answer request for current credits. Waiting 5 seconds.

[hyper2910]

Vielleicht kann Matthias mal was dazu sagen, ist das Modul noch am Leben?  Oder muss man zurück auf den Cube?

[Rince]

Ich schließe mich mal dem Problem an,

Error in CUL_MAX_SendQueueHandler: CUL CUL0 did not answer request for current credits. Waiting 5 seconds.

[John]

Das Ausgabe kommt wohl von diesem Code-Fragment in 14_CUL_MAX

Code: [Auswählen]

    my ($credit10ms) = (CommandGet("","$hash->{IODev}{NAME} credit10ms") =~ /[^ ]* [^ ]* => (.*)/);
    if($credit10ms eq "No answer") {
      Log 1, "Error in CUL_MAX_SendQueueHandler: CUL $hash->{IODev}{NAME} did not answer request for current credits. Waiting 5 seconds.";
      $timeout += 5;
Das Modul versucht die credits vom CUL zu ermitteln, dies entspricht:

Code: [Auswählen]

get CUL credit10msund erhält als Antwort "No answer". Also versucht es das 5 Sekunden später nochmals.
Es gibt auch einen Grund dafür, das Modul will eine Sendung absetzen und vergewissert sich,
ob ausreichend Credits vorhanden sind.

Wenn ihr also den Fehler bemerkt könnt ihr das über eure CUL-Seite selbst ausprobieren, mit dem erwähnten GET-Befehl.

Das Modul 14_CUL_MAX nutzt hierbei die Funktionen von 00_CUL.pm.
14_CUL_MAX ist also nur Symptom-Träger aber nicht die Ursache.
Die Frage ist, warum CUL permanent diese Meldung zurückliefert.
Und diese Frage müsst ihr Rudolf König stellen. Er ist der Betreuer von 00_CUL.pm.

John

[hyper2910]

Hi John,

Ich glaube das ist ein Schritt zu weit. 

Der Fehler wird meiner Meinung nach verursacht durch den disconnect des cul,  und hier ist die frage warum

2014.11.08 12:04:21 1: /dev/ttyACM0 disconnected, waiting to reappear (CULMAX)

[John]

Das kommt von DEVIO.pm und ist auch von Rudolf.

John