xPhcLog, log events on the PHC module bus

Mehr
28 Okt. 2017 19:35 - 28 Okt. 2017 19:50 #61 von haribo
haribo antwortete auf xPhcLog, log events on the PHC module bus
Hi Jan,

yes I have an example for a dimmer. It's still experimental but it works.

item:
Code:
/* Dimmable Light */ Dimmer WZ_Dimmer "Wintergarten Licht" (gWZ, Light) [ "Lighting" ] String WZ_Dimmer_Cmd "Dimmer Command: [%s]" (gWZ) { mqtt="<[mosquitto:myHouse/cmd/dim.1.out0:state:default" }


rule:
Code:
// Variable Declarations // Constants var String base_url = "http://localhost:8081/icontrol.dll?ccmd=" // Diese Regel rechnet den Dimm-Prozenwert in die Range 0-255 fuer PHC um und schickt ein // entsprechendes Set-Kommando ueber xWRC an PHC rule "WZ_Dimmer_command" when Item WZ_Dimmer received command then var Number pVal = receivedCommand logInfo("MyLog.dim", "Received command " + pVal) pVal = pVal / 100 * 255 var String cmdStr = String::format("dim.1.out0.set.%.0f.1", pVal) if (pVal == 0) { cmdStr = "dim.1.out0.off" } if (pVal == 255) { cmdStr = "dim.1.out0.onmem" } sendHttpGetRequest(base_url + cmdStr) logInfo("MyLog.dim", "Send request: " + cmdStr) end // Diese Regel setzt den internen Status des Dimmers, wenn "an openhab vorbei" via // Taster der Dimmwert veraendert wird. Dies wird an den Befehlen "togglemem" und // "stopmem" erkannt. Dazu wird das Item WZ_Dimmer_Command via MQTT gesetzt. // rule "WZ_Dimmer_status" when Item WZ_Dimmer_Cmd received update then logInfo("MyLog.dim", "new state: " + WZ_Dimmer_Cmd.state) if (WZ_Dimmer_Cmd.state == "togglemem" || WZ_Dimmer_Cmd.state == "stopmem") { // nach togglemem warten, da der Dimmer noch "nachläuft" if (WZ_Dimmer_Cmd.state == "togglemem") { Thread::sleep(2000) } var cmdStr = "dim.1.out0.status&terse" var hVal = sendHttpGetRequest(base_url + cmdStr) var int pVal = ( Integer.parseInt(hVal) / 255.0 * 100 +0.5 ).intValue logInfo("MyLog.dim", "Send request: " + cmdStr + " => " + hVal) WZ_Dimmer.postUpdate(pVal) logInfo("MyLog.dim", "postUpdate: " + pVal) } else { logInfo("MyLog.dim","ignore..") } end

Suggestions for enhancements are welcome.

Harald
Letzte Änderung: 28 Okt. 2017 19:50 von haribo. Begründung: Sitemap

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
29 Okt. 2017 00:26 #62 von haribo
haribo antwortete auf xPhcLog, log events on the PHC module bus

Jan schrieb:
For a simple switch function controlled by a 'toggle' I use following solution. The state in OH2 is always represented correctly regardless the switch is operated by OH2 or PHC.

Code:
Switch LE_Wc "WC Boven" <light> {http=">[*:GET:http://localhost:8888/icontrol.dll?ccmd=imd.3.in5.ingt0]", mqtt="<[mosquitto:myHouse/sta/omd.4.out.5:state:MAP(offon.map)]"}


My Switch-Items look like this:
Code:
Switch WC_Ligth "WC Licht" (gWC, Light) { http=">[*:GET:http://localhost:8081/icontrol.dll?ccmd=omd.0.out3.%2$s]", mqtt="<[mosquitto:myHouse/sta/omd.0.out.3:state:MAP(onoff.map)]" }

It' similar but has the following advantages:
  • You need not know the mapping of PHC-Input->PHC-Output
  • You can control outputs that are not associated to any physical switches (PHC-Inputs)
  • You can turn on/off outputs in OH-rules - not only toggle them

Maybe this is an inspiration for you.

Harald

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
19 Nov. 2017 12:15 #63 von Eckert258
Eckert258 antwortete auf xPhcLog, log events on the PHC module bus

haribo schrieb: Hi Jo,

I changed the connection as suggested. It's the same - no traffic is logged.

So I made another approach: I use the following USB - RS485 Converter .

Still no reaction in the logfile.


What about the 'mode' problem. I still have the affect, that xphclogd terminates using mode=1

Code:
pi@raspberrypi ~/xphclog $ ./xphclogd.raspi --ini xphclogd.ini --loglevel 0xFFFFFFFF + xPhcLogd (Linux/RbPI) ------ v4.0.0.4, Sep 16 2016, Jo Simons (c) 2007-2016 + ============================================================================= Press CTRL-C to quit... 2016-12-03,19:19:59,00090000,A,version=4.0.0.4,Sep 16 2016 2016-12-03,19:19:59,00090010,A,legend: 2016-12-03,19:19:59,00090011,A, o0=out0-7,o1=out8-15 2016-12-03,19:19:59,00090012,A, i0=in0-7,i1=in8-15 2016-12-03,19:19:59,00090013,A, l0=out0,l1=out1,l2=out2,l3=out3 (amd/ebd/dim) CTRL-C pressed,terminating app - 0 (Success) pi@raspberrypi ~/xphclog $

But I did not press CTRL-C. Do you have an explanation for this? Should I be able to see logging activity using mode=0?

Harald


Hi,

ich habe das selbe Problem bei Version 4.0.0.4
Was mich wundert, mit Version 1.0.6.0 funktioniert xPhcLog einwandfrei. Weiß jemand an was das liegen könnte?

Grüße
Eckert258

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
20 Nov. 2017 10:48 - 20 Nov. 2017 10:49 #64 von Biland
Biland antwortete auf xPhcLog, log events on the PHC module bus
Hallo,
zur Zeit nutze ich xwrc mittels des moxa nport 5110a dies funktioniert sehr zuverlässig.
Nun plane ich zum Abgreifen der Schaltzustände diverser Ausgansmodule xPhcLog / MQTT / ioBroker zu nutzen.
An meinem Raspi habe ich noch alle USB Ports frei und würde xPhcLog am liebsten mittels einem USB RS485 Adapter in Betrieb nehmen.

Kann mir hierzu einer von euch einen USB - RS 485 Adapter empfehlen?

Gruß,
Michel
Letzte Änderung: 20 Nov. 2017 10:49 von Biland.

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
21 Nov. 2017 10:09 #65 von simonjo
simonjo antwortete auf xPhcLog, log events on the PHC module bus
Hallo Eckert,

The problem is that my code is not complete for using the "--ini xphclogd.ini" parameter, I need to add code for that.

You can use inidividual command line params to get by for now.


mvg, Jo

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
21 Nov. 2017 20:17 #66 von haribo
haribo antwortete auf xPhcLog, log events on the PHC module bus
Hallo Michel,

leider kann ich dir keinen konkreten USB-Stick empfehlen - ich kann nur über Erfahrungen berichten.

Ich habe an die 10 verschiedene USB-Serial-Konverter für den Einsatz von xPhcLog getestet - RS485 und RS232. Einige aus China, andere von deutschen Ebay-Verkäufern. Dabei funktionierten einige gar nicht, einige blockierten das Steuermodul und 2 bis 3 funktionierten schließlich halbwegs zuverlässig. Nachdem ich dann auch xwrc über USB betreiben wollte, funktionierte keiner der RS232-Konverter.
Schließlich habe ich mir bei Ebay einen gebrauchten Moxa Nport 5210 (für 20€) gekauft - eine gute Wahl! Der läuft seit Wochen auf Anhieb stabil. Ich nutze einen RS232-Port für xwrc und den anderen für xPhcLog.

Gruß, Harald

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
22 Nov. 2017 07:51 #67 von Biland
Biland antwortete auf xPhcLog, log events on the PHC module bus
guten Morgen Harald,
vielen Dank für deine Rückmeldung.
Dein Bericht hinsichtlich der Erfahrungen mit den USB-Serial-Konverter bestätigt meine Bedenken und ich denke die stabilste Lösung wird es sein, auch für xPhcLog ein Moxa Nport zu verwenden. Mit dem habe in Verbindung mit xwrc bisher auch Null Probleme!
Ich denke ich werde mich mal nach einem günstigen 5210A umschauen und meinen 5110A durch diesen ersetzten und ggf. Verkaufen.
Danke nochmal für dein Feedback.
Gruß,
Michel

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
28 Nov. 2017 10:11 #68 von Eckert258
Eckert258 antwortete auf xPhcLog, log events on the PHC module bus
Hi Jo,

ich verwende die INI-Funktoin nicht. Habe alles über die Aufrufparameter geregelt.

@Biland: Ich habe folgenden USB-Adapter Einsatz: LINK
Dieser funktioniert mit 1.0.6.0 und bei Version 4.0.0.4 hoffe ich das Jo wieder einen genialen Tipp hat ;)

Grüße
Eckert

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
05 Dez. 2017 19:00 #69 von simonjo
simonjo antwortete auf xPhcLog, log events on the PHC module bus
Can you provide me the command line that you use, with all parameters specified, so I can try it here.

Can you send me the logging when xPhcLog starts

Which MQTT broker are you using?

About the USB stick, are all dip switches open? You can try and play with switches 2, 3 and 4


mvg, Jo

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
06 Dez. 2017 18:01 - 06 Dez. 2017 18:14 #70 von haribo
haribo antwortete auf xPhcLog, log events on the PHC module bus
Hi Jo,

I have detected the following problem with xphclogd in my living room scenario:

I have a group of 5 sockets connected to OMDs. To control and synchronize this group, I made one output the "master" (OMD.2.2) and the "slaves" (OMD.2.3, OMD.2.6, OMD.2.7 and OMD.7.6) follow the master, when it's output state changes.

The problem is that xphclogd does not propagate the right states:
Code:
2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out2,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.2,payload=1 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out3,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out6,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out7,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.7.out6,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.7,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.6,payload=1 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.1,payload=1 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.2,payload=0 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.6,payload=1 2017-12-06,09:12:25,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.7,payload=1

As you can see, myHouse/sta/omd.2.out.2,payload=0 is wrong and myHouse/sta/omd.2.out.3,payload=1 is missing.

Then I changed the behaviour and put some delays to the slaves. Now xphclogd reports correctly:
Code:
2017-12-06,09:07:55,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out2,payload=on 2017-12-06,09:07:55,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on 2017-12-06,09:07:55,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.2,payload=1 2017-12-06,09:07:55,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out3,payload=ondelayed..1 2017-12-06,09:07:55,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out6,payload=ondelayed..2 2017-12-06,09:07:55,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out7,payload=ondelayed..3 2017-12-06,09:07:55,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.7.out6,payload=ondelayed..4 2017-12-06,09:07:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on 2017-12-06,09:07:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.3,payload=1 2017-12-06,09:07:57,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on 2017-12-06,09:07:57,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.6,payload=1 2017-12-06,09:07:58,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on 2017-12-06,09:07:58,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.7,payload=1 2017-12-06,09:07:59,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.7,payload=on 2017-12-06,09:07:59,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.6,payload=1

Do you have any idea what's going wrong in the first scenario?

Harald
Anhänge:
Letzte Änderung: 06 Dez. 2017 18:14 von haribo.

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
07 Dez. 2017 21:29 #71 von simonjo
simonjo antwortete auf xPhcLog, log events on the PHC module bus
Hi Harald,

xPhclogd maintains an internal cache with the states of the outputs, this is cleared when xPhclogd is started. When status packets are captured, the value is compared to the cache and differences are reported. After that the cache is updated.

If for some reason the cache is not in synch with the real state of the outputs, then things are not reported correctly.

After starting xPhclogd it would be good to query each output module for its status (i.e. omd.0;omd.1;omd.2; ...) this way xPhclogd can update it's cache.

Another point of problems can be that xPhclogd puts all MQTT messages on a queue first, then later the msgs are sent to the broker. It could be that the queue is too small (now set to 64), but then an error msgs would be logged.

mvg, Jo

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
08 Dez. 2017 14:43 #72 von haribo
haribo antwortete auf xPhcLog, log events on the PHC module bus

simonjo schrieb: Hi Harald,

xPhclogd maintains an internal cache with the states of the outputs, this is cleared when xPhclogd is started. When status packets are captured, the value is compared to the cache and differences are reported. After that the cache is updated.

If for some reason the cache is not in synch with the real state of the outputs, then things are not reported correctly.

After starting xPhclogd it would be good to query each output module for its status (i.e. omd.0;omd.1;omd.2; ...) this way xPhclogd can update it's cache.

Hi Jo,
I did another test after restart of xPhclogd and forced omd status updates:
Code:
# Restart xphclogd # query status omd.2 and omd.7 via xwrc 2017-12-08,13:26:26,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2,payload=status 2017-12-08,13:26:32,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.7,payload=status # toggle omd.2.2 from off to on (and iniate commands for slaves via PHC) 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out2,payload=toggle 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on # the following states are correct 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.0,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.1,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.2,payload=1 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.3,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.4,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.5,payload=1 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.6,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.7,payload=0 # the commands for slaves (correct) 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out3,payload=on 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out6,payload=on 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out7,payload=on 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.7.out6,payload=on # further states: 2.1 false, 2.2 false, 2.5 false, 2.6 OK, 2.7 OK 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=on 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.1,payload=1 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.2,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.5,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.6,payload=1 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.7,payload=1 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.7,payload=on 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.0,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.1,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.2,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.3,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.4,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.5,payload=0 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.6,payload=1 2017-12-08,13:26:49,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.7,payload=1 # toggle omd.2.2 from on to off (and iniate commands for slaves via PHC) 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out2,payload=toggle 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=off # the following states are correct 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.1,payload=0 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.3,payload=1 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.5,payload=1 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out3,payload=off 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out6,payload=off 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.2.out7,payload=off 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/cmd/omd.7.out6,payload=off # further states: 7.6 OK, 2.0, 2.1 FALSE, 2.3 OK, 2.5 FALSE, 2.6 MISSING 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.7,payload=off 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.6,payload=0 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/evt/omd.2,payload=off 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.0,payload=1 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.1,payload=1 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.3,payload=0 2017-12-08,13:29:56,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.2.out.5,payload=0 2017-12-08,13:30:44,00010010,CPhclogd::_decodeEnhModPublish,topic=myHouse/sta/omd.7.out.6,payload=1

As you can see there is still something going wrong.

simonjo schrieb: Another point of problems can be that xPhclogd puts all MQTT messages on a queue first, then later the msgs are sent to the broker. It could be that the queue is too small (now set to 64), but then an error msgs would be logged.



No error was logged.

Harald

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
11 Dez. 2017 23:06 #73 von simonjo
simonjo antwortete auf xPhcLog, log events on the PHC module bus
xPhclogd uses a datadriven command decoder version 1, it seems that some parts of that internal data is wrong and uses data from version 2 of the decoder (improved version for an PHC-2-MQTT gateway).

Looking further in the coming days... takes some time as it was quiet some time ago :)

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
04 Jan. 2018 05:42 - 04 Jan. 2018 06:43 #74 von Biland
Biland antwortete auf xPhcLog, log events on the PHC module bus
Hello together, yesterday I got the Moxa nport 5210a to install the xphclog in addition to the xwrc program.

So after a few steps I connected the Pin 2 (RX) – black wire of my RS232 cable to the “B” port of the PHC power supply device and the Pin 5 (Ground) – brown wire of the RS232 cable to the “A” port of the power supply unit.

After installing I start the program with: /xwrc/xphclog/xphclogd.raspi --ini /xwrc/xphclog/xphclogd.ini

In the next step I try to create some traffic by using some hardware switches or some switches of my visualisation. And it works.

Thanks a lot but after some minutes I recognized that the e.g. omd.0 (port 3) doesn’t react to my hardware Switches (e.g. imd.1 port 2). Interesting is, that the port of the outputmodule can be toggled by using a switch of my visualisation.

Here is a short logfile.
I hope that somebody can help me:


Code:
root@raspi /xwrc/bin > /xwrc/xphclog/xphclogd.raspi --ini /xwrc/xphclog/xphclogd.ini + xPhcLogd (Linux/RbPI) ------ v4.0.0.4, Sep 16 2016, Jo Simons (c) 2007-2016 + ============================================================================= Press CTRL-C to quit... 2018-01-04,06:05:03,00090000,A,version=4.0.0.4,Sep 16 2016 2018-01-04,06:05:03,00090010,A,legend: 2018-01-04,06:05:03,00090011,A, o0=out0-7,o1=out8-15 2018-01-04,06:05:03,00090012,A, i0=in0-7,i1=in8-15 2018-01-04,06:05:03,00090013,A, l0=out0,l1=out1,l2=out2,l3=out3 (amd/ebd/dim) 2018-01-04,06:05:06,00010130,M,imd.1.in2.ingt0 2018-01-04,06:05:06,00010150,M,imd.1.stmAck 2018-01-04,06:05:09,00010130,M,imd.1.in2.ingt0 2018-01-04,06:05:09,00010150,M,imd.1.stmAck 2018-01-04,06:05:17,00010130,M,imd.1.in2.ingt0 2018-01-04,06:05:17,00010150,M,imd.1.stmAck 2018-01-04,06:05:22,00010210,M,omd.1.status 2018-01-04,06:05:22,00010240,M,omd.1.modAck,o0=1 2018-01-04,06:05:25,00010210,M,omd.0.out3.toggle 2018-01-04,06:05:25,00010240,M,omd.0.modAck,o0=64 2018-01-04,06:05:25,00010210,M,omd.1.status 2018-01-04,06:05:25,00010240,M,omd.1.modAck,o0=1

XWRC works well.
Anhänge:
Letzte Änderung: 04 Jan. 2018 06:43 von Biland.

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Mehr
04 Jan. 2018 05:47 - 04 Jan. 2018 06:38 #75 von Biland
Biland antwortete auf xPhcLog, log events on the PHC module bus
sorry double post
Letzte Änderung: 04 Jan. 2018 06:38 von Biland.

Bitte Anmelden oder Registrieren um der Konversation beizutreten.

Ladezeit der Seite: 0.725 Sekunden