4temp mit neuer Lib kompilieren
-
- Beiträge: 15
- Registriert: 1. Jul 2014, 10:32
Re: 4temp mit neuer Lib kompilieren
https://github.com/selfbus/software/blo ... _V2_02.hex
Should this firmware work already for 4 DS18S20's directly connected to P0_0 P0_1 P0_2 and P0_3 of an LPC on a TS-DIL module?
I have flashed it, and configured it in ETS4, this went OK. (selected 0..5V for 18S20)
It writes updates of all 4 grp addresses to the bus, but only temp1 and temp2 display something (so it seems bogus static values) the other two are always 0, like this.
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/1'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor1' value = '29.76'
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/3'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor2' value = '26.56'
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/5'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor3' value = '0'
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/7'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor4' value = '0'
Thanks.
Should this firmware work already for 4 DS18S20's directly connected to P0_0 P0_1 P0_2 and P0_3 of an LPC on a TS-DIL module?
I have flashed it, and configured it in ETS4, this went OK. (selected 0..5V for 18S20)
It writes updates of all 4 grp addresses to the bus, but only temp1 and temp2 display something (so it seems bogus static values) the other two are always 0, like this.
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/1'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor1' value = '29.76'
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/3'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor2' value = '26.56'
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/5'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor3' value = '0'
2014/11/04 19:28:21 [KNX] Received packet from physical device with address '1.1.10' to '1/4/7'
2014/11/04 19:28:21 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor4' value = '0'
Thanks.
-
- Beiträge: 15
- Registriert: 1. Jul 2014, 10:32
-
- Beiträge: 163
- Registriert: 15. Feb 2014, 13:32
Re: 4temp mit neuer Lib kompilieren
The current firmware is the 4temp, the 4sense is a development version and should not be used. The 4sense will support the same sensors as the 4temp plus the DHT series for temperature / humidity. However this will take some time until it is done and tested.
The 4temp V2.02 uses the same VD file and settings as for V1.0. Up to 4 sensor can be connected directly to the IOs1,2,3,4. They correspond to P0.0, P0.1, P0.2, P0.3 on the LPC 922 pins. Please have a look into the schematic or the Wiki Page for the "Einbaumodul" to find out the adjacent pins for the TS DIL. Please make sure that you also connect VCC (3.3V) and GND for the sensors, the parasitic mode is not supported. If the wire length exceeds a few meters you might need to add a pullup resistor (around 4.7k) from 3.3V to the sensors data line to compensate for the wire capacitance. Make sure you have the correct sensor selected, an incorrect sensor type leads to fake temperature values.
/Stefan
The 4temp V2.02 uses the same VD file and settings as for V1.0. Up to 4 sensor can be connected directly to the IOs1,2,3,4. They correspond to P0.0, P0.1, P0.2, P0.3 on the LPC 922 pins. Please have a look into the schematic or the Wiki Page for the "Einbaumodul" to find out the adjacent pins for the TS DIL. Please make sure that you also connect VCC (3.3V) and GND for the sensors, the parasitic mode is not supported. If the wire length exceeds a few meters you might need to add a pullup resistor (around 4.7k) from 3.3V to the sensors data line to compensate for the wire capacitance. Make sure you have the correct sensor selected, an incorrect sensor type leads to fake temperature values.
/Stefan
-
- Beiträge: 15
- Registriert: 1. Jul 2014, 10:32
Re: 4temp mit neuer Lib kompilieren
I have connected them as described in the schematic attached.
I flashed the 4temp v2.02 hex without watchdog enabled, although there is watchdog related code found in source, it reboots every x secs when enabled, so disabled it.
Programming works, I see the group addresses coming in, but with static/wrong values as described.
Sesnor on P0 and P1 show higher than normal static values, they don't change when temp change, at least not over a minute, P2 and P3 sensor always display 0 value.
I selected 0...5V als sensor type in ETS4, for DS18S20.
Can I debug this via serial/eclipse or something?
I can try to attach my scope to see if there is data on the P0_0 - P0-3 pins.
I will also swap my LPC to make sure it's not damaged electrically.
Any other suggestions?
I flashed the 4temp v2.02 hex without watchdog enabled, although there is watchdog related code found in source, it reboots every x secs when enabled, so disabled it.
Programming works, I see the group addresses coming in, but with static/wrong values as described.
Sesnor on P0 and P1 show higher than normal static values, they don't change when temp change, at least not over a minute, P2 and P3 sensor always display 0 value.
I selected 0...5V als sensor type in ETS4, for DS18S20.
Can I debug this via serial/eclipse or something?
I can try to attach my scope to see if there is data on the P0_0 - P0-3 pins.
I will also swap my LPC to make sure it's not damaged electrically.
Any other suggestions?
- Dateianhänge
-
- 4temp ts-dil schematic.png (49.5 KiB) 6755 mal betrachtet
-
- Beiträge: 15
- Registriert: 1. Jul 2014, 10:32
Re: 4temp mit neuer Lib kompilieren
Wire lengths are 30cm's it's still on the workbench/test lab.
-
- Beiträge: 19
- Registriert: 31. Jul 2013, 19:40
Re: 4temp mit neuer Lib kompilieren
Kann ich meine 4Temp Platine (+2TE LPC) mit der Firmwareversion 2.02 betreiben?
Was bedeutet die alte Version 1.0 ist ohne Lib? Was habe ich dadurch für Nachteile?
Gruß
Flo
Was bedeutet die alte Version 1.0 ist ohne Lib? Was habe ich dadurch für Nachteile?
Gruß
Flo
-
- Beiträge: 15
- Registriert: 1. Jul 2014, 10:32
Re: 4temp mit neuer Lib kompilieren
Some more testing...
I reloaded my 4temp module with exact (german) vd1 file as linked to on 4temp wiki page, doesn't change anything.
I ordered ds18s20's and thats written on the package there were in, but not written on the sensors themselves only "ds1820", replaced the one at IO3 for another one, but value stays 0 for 3rd and 4th sensor, and bogis values for 1st and 2nd sensor, I don't think the are read at all... strange...
If I remove (disconnect all sensors) the module report -0.08 for IO1 and IO2, and still 0 for IO3 and IO4.
So something is done with the first two sensors..
Someone has a hex file for a 100% positive working one?
BTW I'm using an OSC, does that change anything for the timing? And do I need the install the reference circuit for the TS-DIL, I totally forgot about it... (parts are not mounted)
Because it was not clear what it does exactly
I reloaded my 4temp module with exact (german) vd1 file as linked to on 4temp wiki page, doesn't change anything.
I ordered ds18s20's and thats written on the package there were in, but not written on the sensors themselves only "ds1820", replaced the one at IO3 for another one, but value stays 0 for 3rd and 4th sensor, and bogis values for 1st and 2nd sensor, I don't think the are read at all... strange...
If I remove (disconnect all sensors) the module report -0.08 for IO1 and IO2, and still 0 for IO3 and IO4.
So something is done with the first two sensors..
Someone has a hex file for a 100% positive working one?
BTW I'm using an OSC, does that change anything for the timing? And do I need the install the reference circuit for the TS-DIL, I totally forgot about it... (parts are not mounted)
Because it was not clear what it does exactly
-
- Beiträge: 645
- Registriert: 17. Mai 2013, 20:57
- Kontaktdaten:
Re: 4temp mit neuer Lib kompilieren
Hi cyperjunky,
i need the same as you , so you can hope to the best
DS18B20 versus DS18S20 is in result only a differenz in the out value.
The old software works via multiplexing. The new is compiled for directly connection to the io.
The OSC has the same frequecy, but more stable.
Our circuits are nearly all the same, only fit in different cases.
Your circuit is ok, it sent anything.
connection is also ok.
I'm sorry, i'm verry busy this time. I will test all when the time comes.
I hope other user can more help you.
best regards
Andreas
i need the same as you , so you can hope to the best
DS18B20 versus DS18S20 is in result only a differenz in the out value.
The old software works via multiplexing. The new is compiled for directly connection to the io.
The OSC has the same frequecy, but more stable.
Our circuits are nearly all the same, only fit in different cases.
Your circuit is ok, it sent anything.
connection is also ok.
I'm sorry, i'm verry busy this time. I will test all when the time comes.
I hope other user can more help you.
best regards
Andreas
liebe Grüße
Andreas
Andreas
-
- Beiträge: 163
- Registriert: 15. Feb 2014, 13:32
Re: 4temp mit neuer Lib kompilieren
About the firmware versions:
Both, V1 and V2 use the same VD file, the one linked on the 4temp wiki page. The difference is that V1 is based on an older version of our KNX-Bus code, the so called library. There is no need to change from V1 to V2 if its running fine. However we will no longer fix bugs for the V1, since it is depricated and we like to maintain one library code base. There should be no functional difference between V1 and V2.
About the hardware:
The binary for V1 (hex) is compiled to support multiplexing, this requires the additional 4temp PCB. Version 2 instead is compiled for direct I/O, you can directly connect up to 4 sensors to the controller pins and does not need the 4temp PCB.
Both, V1 and V2 use the same VD file, the one linked on the 4temp wiki page. The difference is that V1 is based on an older version of our KNX-Bus code, the so called library. There is no need to change from V1 to V2 if its running fine. However we will no longer fix bugs for the V1, since it is depricated and we like to maintain one library code base. There should be no functional difference between V1 and V2.
About the hardware:
The binary for V1 (hex) is compiled to support multiplexing, this requires the additional 4temp PCB. Version 2 instead is compiled for direct I/O, you can directly connect up to 4 sensors to the controller pins and does not need the 4temp PCB.
-
- Beiträge: 15
- Registriert: 1. Jul 2014, 10:32
Re: 4temp mit neuer Lib kompilieren
Some new LPC chips came in, I reprogrammed and replaced the one on my TS-DIL module, and all ports work now, I had a faulty chip!
The values are also correct now:
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/1'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor1' value = '22.64'
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/3'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor2' value = '22'
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/5'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor3' value = '22.48'
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/7'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor4' value = '23.28'
Very nice, this is a very cheap and small, 4 way sensor for monitoring my heating temps!
I have now successfully build, actor 2in2out, velleman PIR41/goobay 95173 sensor, gira smoke, and the 4temp!
Thanks to all who make this possible
Next up are weatherstation, and raspberrypi board.
The values are also correct now:
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/1'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor1' value = '22.64'
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/3'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor2' value = '22'
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/5'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor3' value = '22.48'
2014/11/07 18:42:57 [KNX] Received packet from physical device with address '1.1.10' to '1/4/7'
2014/11/07 18:42:57 [KNX] Processed received DPT 9.001 data for device 'Temp Sensor4' value = '23.28'
Very nice, this is a very cheap and small, 4 way sensor for monitoring my heating temps!
I have now successfully build, actor 2in2out, velleman PIR41/goobay 95173 sensor, gira smoke, and the 4temp!
Thanks to all who make this possible
Next up are weatherstation, and raspberrypi board.