Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[SOLVED] No values are send to any of my services.
#11
Yeah it was indeed a hardware failure at work here. The wire broke and i could get it to work wen holding it right, but wasnt able to fix it yet.
A bit surprised so, because I handled it well, but maybe its just because of the single core wire.
Reply
#12
yeah.. it was very convenient to use them, but sadly time has shown that when i cut the shielding i corrupt a bit the outside wall  of the copper wire
and at some point of time it breaks
then i started to use multi core wires, but in this design it is much harder to solder them.

if you can solder it - then it would be great - if not then send it back to me, i will fix it and return it.. i will cover the expenses
Reply
#13
I soldered it, but it is still not working and showing me the exact same debug log. Do I have to disable the "missing" value that I wrote with the command you gave me?


[Image: IMG_20170117_210746.jpg]


By the way, wasn´t the module supposed to be the CM1102? On the board it says CM1101 and when I googled the manual to know where I had to solder, it told me it that the 1 Version is single Beam and not dual beam.

Anyhow, I measured 1.6V between the Pin I soldered  and GND. Between the PWM Output(whatever that does) and GND I measured around 1.0V by having the multimeter set to continues voltage. Both values do reach the microcontroller, which I ensured by measuring again.

If you cant tell me a possible solution please give me your shipping information, for the return.

Thanks, Christopher
Reply
#14
you need to do a factory reset after fixing this (from Settings) or again remove the"missing" value. While it is missing the firmware isn't trying to search for the sensor.

As for the 1101 and 1102, this is also what i had asked the manufacturer once i got them, but they confirmed that the sensors are the dual-beam type - 1102, just that the PCBs that they use are exactly the same and this is why the naming
Reply
#15
I did several factory resets, but the missing value is still set, which I can see with debug on. Whats the command for removing the "missing" value? Tried to send "" instead of "present" but i wasnt working out.

Ah ok, that explains the weird number on the PCB.
Reply
#16
(01-18-2017, 02:16 PM)Christopher Wansing Wrote: I did several factory resets, but the missing value is still set, which I can see with debug on. Whats the command for removing the "missing" value? Tried to send "" instead of "present" but i wasnt working out.

Ah ok, that explains the weird number on the PCB.

With "" it should be working. But the fact that even after a factory reset it is not detected, means that something else is wrong unfortunately, you can try setting 
As a last resort, you can set it to "present", and then the firmware will try to search it each time and will dump which ports it tries.
If it doesn't work out we can clarify the refund separately
Reply
#17
i found the bug Smile
it was in the firmware, if you still haven't sent the device, you can give it a try with the latest firmware
Reply
#18
Oh great!!!!! Still havent send it. Its a bit of a hassle to get to the next post office here and had my last examination for the ongoing semester today.
Will try and reach out to you tomorrow. I will send the device ASAP. Sorry for the delay.
Reply
#19
if you like you can update yours and use it
and when the other one comes.. you can decline it ot not take it from the post and they will send it back to me
Reply
#20
Oh yes thats seems to be a lot less hassle Smile
I updated the device, made a factory reset afterwards and now it works like a charm. Thanks again!!!!

I suppose the bug occured because the sensor was disconnected during operation, because the device was not meant to be able to change the connected sensors. Is that right? Would explain why the bug went undetected till now, because that normally does not happen.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)