One wire DS18S20 Error

maharadga · Post by **maharadga** » Sat Dec 13, 2014 5:41 pm

Hi all. I use trial version of Flowcode 6 and I decided try "SingleOneWire" with DS18S20 from "Help". And it's not work. I see on display "CRC Error". If I disable CRC, I see on display "-1.-5 C". I try everything, but no result. Most interesting is that in Proteus project work. Project is the same as in "Help". Diferent is only PIC-16F876A and crystal-20MHz.
Anybody have a some idea?

Post by **QMESAR** » Sun Dec 14, 2014 11:48 am

Do I understand you correctly
You are simulating the hex file created in Flowcode in Proteus and then the simulation is working
and the simulation in Flowcode does not work ?

I suppose you should use and injector Component/tool in FC simulation I never used the One Wire in FC but this would be my guess,you should read the help file how to use it and which one too use

maharadga · Post by **maharadga** » Sun Dec 14, 2014 4:59 pm

In Proteus circuit work.
I try real design. With PIC16F876A and crystal 20MHz, device is DS18S20. It not work. I give on display -1.-5 C.
I'm new in Flowcode and not use injector. I don't now how.
But I think this example in "Help"must be work. It's very simple.
I'm shure it's a bug.
I do not understand of programming and this program is a bonus for me. But if somewhere something will not work, but I can not fix it, then does it make sense to buy?

Post by **QMESAR** » Sun Dec 14, 2014 7:54 pm

maharadga wrote: In Proteus circuit work.

What is working in Proteus a Proteus example or the Hex File you generated from FlowCode form the help file example ??
did you try to load the hex file in the Proteus model and check it ?

maharadga wrote:I try real design. With PIC16F876A and crystal 20MHz, device is DS18S20. It not work. I give on display -1.-5 C.

There could be a hardware problem as I assume the help file example is correct

Unfortunately I do not have this hardware to check it out,maybe one of the other guys that used the One Wire will help you

Post by **QMESAR** » Sun Dec 14, 2014 8:18 pm

Hi
Well what i did now I compiled your project in FC and loaded the hex file into Proteus and it working fine
I am quite sure that the FC6 project and hex file are correct you need to check your hardware ,You project settings seem to be correct if you are using 20MHZ Crystal

maharadga · Post by **maharadga** » Mon Dec 15, 2014 1:04 pm

QMESAR wrote:Hi
Well what i did now I compiled your project in FC and loaded the hex file into Proteus and it working fine
I am quite sure that the FC6 project and hex file are correct you need to check your hardware ,You project settings seem to be correct if you are using 20MHZ Crystal

Hi.
Еxactly. Hex file is compiled into the Flowcode and loaded into Proteus. And it works, as you see. But when I program chip- program does not work. There is no hardware problem. I wrote to Flowcode and got the answer:
"Hello,
Unfortunately the One Wire component is bugged at the moment, making a generic One Wire which works with all chip types is proving very tricky for us. It is on our bug list to fix. I am sorry for any inconvenience this may cause.
Regards,
David"

Same problem I see in Flowcode 5. From this site http://flowcode.info/forum/index.php?si ... a20be94f25 I download revised 1-Wire.c file and replace original in FC directory. Then 1-Wire forks perfect. But in FC6 everyting is different.
Hopefully soon to fix this bug.

Post by **QMESAR** » Mon Dec 15, 2014 3:27 pm

maharadga wrote: Unfortunately the One Wire component is bugged at the moment, making a generic One Wire which works with all chip types is proving very tricky for us.
.

Thank you for informing however I will be very surprised with this as my experience with Proteus over the the years is that it is really accurate and it would have shown out this bug,
I have ordered a DS18B20 sensor I want to see this myself

and 876A I will have one laying around

Post by **kersing** » Mon Dec 15, 2014 6:25 pm

QMESAR wrote:I have ordered a DS18B20 sensor I want to see this myself and 876A I will have one laying around

The DS18B20 and the DS18S20 are slightly different devices. Code for one does not work with the other.

Post by **QMESAR** » Mon Dec 15, 2014 9:37 pm

kersing wrote:The DS18B20 and the DS18S20 are slightly different devices. Code for one does not work with the other.

Thank you for pointing this out

Post by **Benj** » Mon Jan 12, 2015 3:36 pm

Hello,

Not sure if this is related but I have had a go at changing the 1-wire component timings to make it more reliable. Anyone with 1-wire hardware please could you try this updated component to see how you get on.

Anyone with currently working 1-wire hardware please let us know what 1-wire device(s) your using and make a backup of the current component so you can revert back if the changes break the existing functionality.

One_Wire.fcpx: (11.68 KiB) Downloaded 307 times

jgu1 · Post by **jgu1** » Wed Jan 14, 2015 8:39 pm

Hi Ben!!

Anyway, after such a great job you deserve an answer. I am a little bysy at the monent, but soon I will test your .fcpx file, and you hear.

Is it for a DS18B20 or DS 18S20 or both?? I have both.

Best regard

Jorgen

Post by **Benj** » Thu Jan 15, 2015 12:52 pm

Hello Jorgen,

Cheers for replying

Hopefully the 1-wire routines should work with both sensor types. I'll also do some testing here when my new sensors come in.

maharadga · Post by **maharadga** » Thu Jan 15, 2015 6:15 pm

Hi. I will try this component and reply soon. Therefore I found that example in help files for One_wire work only if DS1820 is connected in port A0. If I try change pin for example C4 it not work.
Incidentally anyone have any idea why I can't reset WDT in example? And how can I prescale it?
I looks in forum but I do not understand programming and be happy if anybody explane me with simple example.
Also I reading incorectly temperature under 0C. How can I calculating minus temperature?
Beer be from me

jgu1 · Post by **jgu1** » Thu Jan 15, 2015 8:12 pm

Sorry To fast submit...

jgu1 · Post by **jgu1** » Thu Jan 15, 2015 8:14 pm

Hi Ben!

Sorry i have no luck with your new .fcpx file doesn´t Work.

I hope the following may be helpful:

I thought I have a DS18S20 but I only have DS1820 and a DS18B20 none of them Work with old .fcpx file and new file.

Info to you for troubleshooting:

I have (att.) FC5 program with where I use a pic16886 with internal osc set to 8 MHz. Work perfect. But ONLY with datapin conneted to pin A0 ??

If I make the same program in FC6 I only get CRC error. With both .fcpx file.

I see that Rudi and Martin managed to get it Work with 16f1937. I think it seems to be a very critical component.

***Allow me just a second question.
When I use the Arduino with FC6 it works perfectly and is very fast to compile. Pic is very slow to compile, something new concerning speedup for pic udring compile?*

jgu1 · Post by **jgu1** » Tue Jan 20, 2015 2:15 pm

Hi all!

Since I am very interested in this component (maybe also other), I am a little curious, stopped the thread concerning Ds18x20 here?.

When you look araound in the forum here, I can see there have always been problems with this component as both single, and as multiple device. I think many FC user would be happy for a One-Wire component that just works, regardless of the port, crystal, or type Pic to use. It is guaranteed not easy to fix, but Ben you turned a little light on when you tried to make a new .fcpx file

.

Unfortunately it did not work, but I should like to test again if you can make magic

Best regard

Jorgen...

Mikat · Post by **Mikat** » Thu Jan 29, 2015 9:30 am

Hi.

Hi I have been playing those devices, and never get them working really reliable (burned one Eberspächer chamber, because of sensor jamming -> back to the ntc temp sensing). Those devices seems to be very sensitive of timings and noise. With the noise in bus, it could jam, only way to get it working was power off the device. And I have broke many of those devices, some the way that I don't understand could work for months, and suddenly it's dead..
There is thread in FC5 forum, where I and Ben was trying to get DS sensors working at dsPIC, with no luck, with 8-bit same code works fine, so I someone is interested, there is some information..
One thing is that one some devices seems to work at some code, and some need to tweak timings, thats really nice..
There probably should use some series resistor in the bus, to prevent bus ringing and over and undershoot, the edges of modern pics are quite fast..
The S and B version uses same code, only the temp calculation is different, so any case you should see some logical change the temp, b uses 12 bit and s 9 bit temp message, no other difference..

T:Mika

Post by **keejay** » Mon Feb 23, 2015 11:02 am

Hi all,

I have the DS18B20 temp sensor working very reliable with FC5 component macro's on a PIC18F46K22 on pin A3, but when I try and use the FC6 macros in exactly the same way as in FC5 then it no longer works. It always reads -1.-6. What's the difference (under the bonnet) between the FC5 and FC6 component macro for the DS18B20? If the FC6 macro could be changed to be exactly the same as the FC5 then at least the DS18b20 would work?

Benj...any possibilities of doing that?

Matrix user forums

One wire DS18S20 Error

One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error

Re: One wire DS18S20 Error