FHEM crash on FHT80b-3 modules (re-syncing)

[Guest]

Originally posted by: <email address deleted>

Hi,

I'm currently switching from a fhz1000pc to a CUNO device, but fhem
keeps crashing on the FHT80b devices. When I turn them off fhem is
stable, but when I turn them on I get this line in the fhem-2011.log
file:

---
Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/
fhem/FHEM/11_FHT.pm line 417.
Illegal division by zero at /usr/share/fhem/FHEM/11_FHT.pm line 417.
---

I've tried to setup pairing again, but on every signal it sees from a
FHT device, FHEM crashes.
(I have 4 devices in total, and I have made sure that all devices are
switched off (batteries removed) and I turn them on one at time.)

Jelle

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[tostmann]

                                                 

Those characters:

Am 16.01.2011 um 13:44 schrieb Jelle Kalf:

> Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/

may come from not properly calibrated CUNO-clock. If your hosts and CUNOs clock differs too much the serial link will suffer.

You should try manually re-calibrating a CUNO oscillator following the steps:

* run CUNO in Bootloader mode by powering it up with button on its back pressed
* Connect to it with a 38400 baud terminal
* Press 'S' to see if something gets returned
* Then: Press 'C' (capital c) serveral times, or hold it for 5 seconds. This will return something like: "B9 00D0 B8"
* repeat the previous step until the number in the middle is: "?? 00D0 ??"

Than your CUNO osc runs at correct speed to allow proper serial communication with your host.

* Recycle power on CUNO - firmware won't be touched

Luck?

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Small addition. I've run the logfile at verbose 5 now:
--------------------------------------------------------------
2011.01.16 14:16:27 5: CUL/RAW: /TDBDE5A82FC

2011.01.16 14:16:27 4: CUNO1: TDBDE5A82 -76
2011.01.16 14:16:27 5: CUNO1 dispatch TDBDE5A82
2011.01.16 14:16:27 4: FHTTK skipping state 02 as last similar
telegram was received less than 5 (2) secs ago
2011.01.16 14:16:45 5: CUL/RAW: /T594A00A600FF

2011.01.16 14:16:45 4: CUNO1: T594A00A600 -74.5
2011.01.16 14:16:45 5: CUNO1 dispatch 810c04xx0909a001594a0000a600
Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/
fhem/FHEM/11_FHT.pm line 417.
Illegal division by zero at /usr/share/fhem/FHEM/11_FHT.pm line 417.
--------------------------------------------------------------

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Thanks herr Tostmann,

I'll test it right away.
Tip for you: on the plastic casing: make a hole in the back for easier
access to the switch. I have to unscrew the whole casing now

On 16 jan, 14:22, Dirk Tostmann wrote:
> Those characters:
>
> Am 16.01.2011 um 13:44 schrieb Jelle Kalf:
>
> > Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/
>
> may come from not properly calibrated CUNO-clock. If your hosts and CUNOs clock differs too much the serial link will suffer.
>
> You should try manually re-calibrating a CUNO oscillator following the steps:
>
> * run CUNO in Bootloader mode by powering it up with button on its back pressed
> * Connect to it with a 38400 baud terminal
> * Press 'S' to see if something gets returned
> * Then: Press 'C' (capital c) serveral times, or hold it for 5 seconds. This will return something like: "B9 00D0 B8"
> * repeat the previous step until the number in the middle is: "?? 00D0 ??"
>
> Than your CUNO osc runs at correct speed to allow proper serial communication with your host.
>
> * Recycle power on CUNO - firmware won't be touched
>
> Luck?

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Dirk,

I've tried it, but no luck. It works exactly how you told me to do it.
And after getting the 00D0 back, I hooked it off, and put it back in
the casing.
I then realised I had indeed no NTP server set in the CUNO, so I set
it to a dutch NTP source on the internet. Then I turned the CUNO back
on and started fhem. I can define the FHT, but on sending a command
the return command makes my fhem cry and die.

Additional information:
- FHT device hex 594a -> 8974 on the device
- CUNO device FHT T01 code = 1234
- CUNO definition in FHEM: define CUNO1 CUL 192.x.x.x:2323 1234

Here's the logfile from the point where try to pair the device:
------
2011.01.16 14:51:23 5: Cmd: >define wz FHT 594a<
2011.01.16 14:51:23 5: Triggering global (1 changes)
2011.01.16 14:51:23 5: global trigger: Checking Benedengang_dblog for
notify
2011.01.16 14:51:23 5: global trigger: Checking
FileLog_CUL_FHTTK_7dd928 for notify
2011.01.16 14:51:23 5: global trigger: Checking
FileLog_CUL_FHTTK_860f67 for notify
2011.01.16 14:51:23 5: global trigger: Checking
FileLog_CUL_FHTTK_abda95 for notify
2011.01.16 14:51:23 5: global trigger: Checking
FileLog_CUL_FHTTK_dabbec for notify
2011.01.16 14:51:23 5: global trigger: Checking
FileLog_CUL_FHTTK_dbde5a for notify
2011.01.16 14:51:23 5: global trigger: Checking FileLog_achterdeur for
notify
2011.01.16 14:51:23 5: global trigger: Checking
FileLog_buitenlamp.voor for notify
2011.01.16 14:51:23 5: global trigger: Checking FileLog_gang_eerste
for notify
2011.01.16 14:51:23 5: global trigger: Checking FileLog_kerstboom for
notify
2011.01.16 14:51:23 5: global trigger: Checking FileLog_piano for
notify
2011.01.16 14:51:23 5: global trigger: Checking FileLog_raam.keuken
for notify
2011.01.16 14:51:23 5: global trigger: Checking FileLog_zithoek for
notify
2011.01.16 14:51:23 5: global trigger: Checking Logfile for notify
2011.01.16 14:51:23 5: global trigger: Checking StaLampBank_dblog for
notify
2011.01.16 14:51:23 5: global trigger: Checking StaLampPiano_dblog for
notify
2011.01.16 14:51:23 5: global trigger: Checking ZolderLamp_dblog for
notify
2011.01.16 14:51:23 5: global trigger: Checking benedengang_log for
notify
2011.01.16 14:51:23 5: global trigger: Checking gangEerste_dblog for
notify
2011.01.16 14:51:23 5: global trigger: Checking zolderlamp_log for
notify
2011.01.16 14:51:24 5: CUL/RAW: /T594A002C1708

2011.01.16 14:51:24 4: CUNO1: T594A002C17 -70
2011.01.16 14:51:24 5: CUNO1 dispatch 810c04xx0909a001594a00002c17
Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/
fhem/
FHEM/
11_FHT.pm line 417.
Illegal division by zero at /usr/share/fhem/FHEM/11_FHT.pm line 417.
--------------------------------------



On 16 jan, 14:22, Dirk Tostmann wrote:
> Those characters:
>
> Am 16.01.2011 um 13:44 schrieb Jelle Kalf:
>
> > Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/
>
> may come from not properly calibrated CUNO-clock. If your hosts and CUNOs clock differs too much the serial link will suffer.
>
> You should try manually re-calibrating a CUNO oscillator following the steps:
>
> * run CUNO in Bootloader mode by powering it up with button on its back pressed
> * Connect to it with a 38400 baud terminal
> * Press 'S' to see if something gets returned
> * Then: Press 'C' (capital c) serveral times, or hold it for 5 seconds. This will return something like: "B9 00D0 B8"
> * repeat the previous step until the number in the middle is: "?? 00D0 ??"
>
> Than your CUNO osc runs at correct speed to allow proper serial communication with your host.
>
> * Recycle power on CUNO - firmware won't be touched
>
> Luck?

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[tostmann]

                                                 

I'm not saying that this is the actual problem, I just told you re-calibrate the clock - just in case. CUNOs have been calibrated before they shipped anyway.

Am 16.01.2011 um 14:56 schrieb Jelle Kalf:

> I've tried it, but no luck. It works exactly how you told me to do it.
> And after getting the 00D0 back, I hooked it off, and put it back in
> the casing.
> I can define the FHT, but on sending a command
> the return command makes my fhem cry and die.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Hi,

I've checked it again, by hooking up the Device again. And when I do
so it reports ?? FFFF ?? back. When I press the C a couple of times
the furthest it goes is 00C4 or 00C7, but after a check it always
returns to "51 FFFF 50".

I've got the CUNO loaded with the release 1.40 firmware.

Jelle

On 16 jan, 15:03, Dirk Tostmann wrote:
> I'm not saying that this is the actual problem, I just told you re-calibrate the clock - just in case. CUNOs have been calibrated before they shipped anyway.
>
> Am 16.01.2011 um 14:56 schrieb Jelle Kalf:
>
> > I've tried it, but no luck. It works exactly how you told me to do it.
> > And after getting the 00D0 back, I hooked it off, and put it back in
> > the casing.
> > I can define the FHT, but on sending a command
> > the return command makes my fhem cry and die.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

*cough* a little bit more stress now.
The CUNO is unresponsive in normal and in this bootloader state. it's
unresponsive to a S or C command. Trying to flash it in bootloader
mode, can't get any contact to it.

Any suggestions Dirk?


Kind regards,

jelle

On 16 jan, 15:43, Jelle Kalf wrote:
> Hi,
>
> I've checked it again, by hooking up the Device again. And when I do
> so it reports ?? FFFF ?? back. When I press the C a couple of times
> the furthest it goes is 00C4 or 00C7, but after a check it always
> returns to "51 FFFF 50".
>
> I've got the CUNO loaded with the release 1.40 firmware.
>
> Jelle
>
> On 16 jan, 15:03, Dirk Tostmann wrote:
>
> > I'm not saying that this is the actual problem, I just told you re-calibrate the clock - just in case. CUNOs have been calibrated before they shipped anyway.
>
> > Am 16.01.2011 um 14:56 schrieb Jelle Kalf:
>
> > > I've tried it, but no luck. It works exactly how you told me to do it.
> > > And after getting the 00D0 back, I hooked it off, and put it back in
> > > the casing.
> > > I can define the FHT, but on sending a command
> > > the return command makes my fhem cry and die.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[rudolfkoenig]

                                                   

> 2011.01.16 14:51:24 4: CUNO1: T594A002C17 -70
> 2011.01.16 14:51:24 5: CUNO1 dispatch 810c04xx0909a001594a00002c17
> Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/
> fhem/
> FHEM/
> 11_FHT.pm line 417.
> Illegal division by zero at /usr/share/fhem/FHEM/11_FHT.pm line 417.

I don't think this is a CUNO bug, it is either a fhem or a perl problem.
The message T594A002C17 is completely normal, it should be converted to
  synctime: 10

Could you please modify 11_FHT.pm, and insert following line before line 417:
Log 1, "VAL: $val";

$val should be 17, and line 417 is
    my $fv = sprintf("%d%%", int(100*$val/255+0.5));
in the fhem 5.0 version of 11_FHT.pm. I see no reason (yet) why it aborts.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

Thanks Rudolf,

I will test this as soon as I have a working CUNO again.
The device is now totally unresponsive. After having done the
procedure as described by Dirk Tostmann twice the device DIDN'T
respond to bootloader messages anymore.
I've unpowered and booted the device in normal mode, CULFW does not
start.
I've restarted bootloader mode (poweron with the back switch pressed),
every letter according to the procedure above pressed results in a
single ? being returned.

*help!* it seems to die on me.


on the FHEM crash part, a kind friend remarked that fhem might crash
due to the fact that I don't have a powered on actuator attached to
the FHT device. Might this be an issue as well? I'm currently still
building my FHT system and I have no FHT8v installed right now.


Kind regards,

Jelle Kalf

On 16 jan, 16:36, Rudolf Koenig wrote:
> > 2011.01.16 14:51:24 4: CUNO1: T594A002C17 -70
> > 2011.01.16 14:51:24 5: CUNO1 dispatch 810c04xx0909a001594a00002c17
> > Argument "\x{ff}\x{0}..." isn't numeric in division (/) at /usr/share/
> > fhem/
> > FHEM/
> > 11_FHT.pm line 417.
> > Illegal division by zero at /usr/share/fhem/FHEM/11_FHT.pm line 417.
>
> I don't think this is a CUNO bug, it is either a fhem or a perl problem.
> The message T594A002C17 is completely normal, it should be converted to
>   synctime: 10
>
> Could you please modify 11_FHT.pm, and insert following line before line 417:
> Log 1, "VAL: $val";
>
> $val should be 17, and line 417 is
>     my $fv = sprintf("%d%%", int(100*$val/255+0.5));
> in the fhem 5.0 version of 11_FHT.pm. I see no reason (yet) why it aborts.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[rudolfkoenig]

                                                   

> on the FHEM crash part, a kind friend remarked that fhem might crash
> due to the fact that I don't have a powered on actuator attached to
> the FHT device. Might this be an issue as well?

1. As the 8v does not report back (RX only), the FHT80b does not actually know
   if there is an FHT8v or not. The FHT80b only might get confused, as the
   temperature wont change according to the commands sent out

2. Fhem should not crash, no matter how confused an FHT80b is.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[tostmann]

                                                 

Am 16.01.2011 um 15:52 schrieb Jelle Kalf:

> Any suggestions Dirk?

In worst case you have changed cpu clock this much you're now completely unable to talk serial to it anymore, because bitrate drift has become too big. Than you would need to erase the eeprom and restart.

Again: All CUNOs are shipped calibrated.


--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

ok,

what do I do now?
When I open up "screen /dev/ttyACM0 38400" I do get a prompt, but I
get ? signs back on any command I send to it.
What can I do to test, reset or anything?

I'm not a programmer, I'm just "fhem user". But I can press buttons


Jelle

On 16 jan, 16:58, Dirk Tostmann wrote:
> Am 16.01.2011 um 15:52 schrieb Jelle Kalf:
>
> > Any suggestions Dirk?
>
> In worst case you have changed cpu clock this much you're now completely unable to talk serial to it anymore, because bitrate drift has become too big. Than you would need to erase the eeprom and restart.
>
> Again: All CUNOs are shipped calibrated.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

I'm wondering.. would erasing the eeprom require me to use the dfu-
programmer program? (No, I've not done so yet, just asking before
bashing the buttons...)
Reason is, if I have to, the ubuntu version only supports up to the
atmega32u4 or the atmega32u6. I don't see the atmega644p in the list,
or should I stick with the exact line that's in the README file for
the CUN device?:

dfu-programmer at90usb162 erase
dfu-programmer at90usb162 flash CUL.hex


Jelle

On 16 jan, 17:01, Jelle Kalf wrote:
> ok,
>
> what do I do now?
> When I open up "screen /dev/ttyACM0 38400" I do get a prompt, but I
> get ? signs back on any command I send to it.
> What can I do to test, reset or anything?
>
> I'm not a programmer, I'm just "fhem user". But I can press buttons
>
> Jelle
>
> On 16 jan, 16:58, Dirk Tostmann wrote:
>
> > Am 16.01.2011 um 15:52 schrieb Jelle Kalf:
>
> > > Any suggestions Dirk?
>
> > In worst case you have changed cpu clock this much you're now completely unable to talk serial to it anymore, because bitrate drift has become too big. Than you would need to erase the eeprom and restart.
>
> > Again: All CUNOs are shipped calibrated.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.

[Guest]

Originally posted by: <email address deleted>

I've been reading up a bit and ofcourse found the Bootloader part in
the culfw. I've carefullly read through the readme and the makefile.
All seems to be filled in correctly but for the /dev/ttyUSB0 being
ttyACM0 ofc.

When I boot up the CUNO board in bootloader mode by pressing the
button while powering it on, I can run the "make program" to load the
main.hex file to the device. Except that it won't work. It was set to
the stk500v2, but it couldn't connect to the programmer. I tried to
switch it to avr109, as that's what the cuno.hex firmware needs to be
uploaded with as well. But no luck with that either.

The main difference between the two programmers btw. When I run it
with the original setting of stk500v2, it'll turn off the red light on
the board. and the led on the main pcb will start blinking. but then I
still get a message:

----
avrdude: ser_rec(): programmer is not responding
avrdude: stk500_2_ReceiveMessage(): timeout
----

This message keeps scrolling over my screen and never stops.

--
Sie haben diese Nachricht erhalten, da Sie der Google Groups-Gruppe FHEM users beigetreten sind.
Wenn Sie Nachrichten in dieser Gruppe posten möchten, senden Sie eine E-Mail an fhem-users@googlegroups.com.
Wenn Sie aus dieser Gruppe austreten möchten, senden Sie eine E-Mail an fhem-users+unsubscribe@googlegroups.com.
Besuchen Sie die Gruppe unter http://groups.google.com/group/fhem-users?hl=de, um weitere Optionen zu erhalten.