Yannick99

fr is for french version... code is the same

The relay is jumping the open/close push button. It doesn't touch the motor directly at all. In other words, the relay can replace the open/close push button.

Very nice enclosure. Thank you for the feedback. Enjoy your new toy.

I can’t sorry. Don’t have time to do this.

Ah sorry my mistake. No problem then.

Hello, The hi resolution picture is already there. Click on schematic, you will see the download arrow at bottom left. I didn't write german too. All is suppose to be in english. Sometime you can see some french. Bye

Hi Andy, it’s not a bad idea. The detector reset the uC when voltage goes lower than 4.3v So yes maybe you had some trouble with your 50 amp psu.

Thank you for the input and advice. Last firmware is 1.56. If you install the jumper you run 1.56c and without 1.56q. Difference between are the pwm step. On quick version step are higher if frequency is too far. Classic it's always the same step until right frequency is achieved. If the vfc of your ocxo is too different of mine, quick mode is maybe not compatible. In this case i suggest classic mode.

Interesting... I checked what changed:-remove phase1,2,3,4,5 and replace it by the pwm value.Add serial data output (pin 3) 9600 8 1 to display same information of lcd 2 lines.The first one is only a lcd display modification. The second is sending serial data on tx pin. It will be hard to find the exact problem because I can't reproduce the problem on my side :(When you program the atmega are you using the same .bat file ? Can you double checked or copy the gpsdo.hex (1.56) to the gpsdo.hex (1.4) and use the .bat of 1.4

This is good new. Yes it's a very sensitive device. It's different from one to another by component choice, enviroment etc but normally it's working.

Yes i could, but it will be try and error. Long process. The source code is available on github. I could show you what to change and you could try by yourself. Will be quicker. But before to do that. I have the 131-100. And I do not have this problem. Both version are working classic and quick. For you, .005 and .006 is looking ok (no jump) but like you said, the pwm correction doensn't correct enough.Also, i'm looking your number 0x7FBE and after 7FBB. Are you really in classic ? Should be +- 1 in classic. so 0x7FBD instead. When you turn on you see 1.56c or q ?Also the OCXO is moving faster than the correction and even on the wrong direction. I dont think it's normal. For example. If you tight the vfc to 2.5v The ocxo frequency shouldn't be moving. Worst case +-.001 or very close.Maybe…

Yes i could, but it will be try and error. Long process. The source code is available on github. I could show you what to change and you could try by yourself. Will be quicker. But before to do that. I have the 131-100. And I do not have this problem. Both version are working classic and quick. For you, .005 and .006 is looking ok (no jump) but like you said, the pwm correction doensn't correct enough.Also, i'm looking your number 0x7FBE and after 7FBB. Are you really in classic ? Should be +- 1 in classic. so 0x7FBD instead. When you turn on you see 1.56c or q ?Also the OCXO is moving faster than the correction and even on the wrong direction. I dont think it's normal. For example. If you tight the vfc to 2.5v The ocxo frequency shouldn't be moving. Worst case +-.001 or very close.Maybe you could try it. Unconnect the ocxo vfc from pwm. Put a 10k potentiometer vcc-- vfc--- gnd and adjust the pot to go 1000s on vfc and do not touch it for a while. uC will count the frequency and this one should be the same because vfc is fix. Are you following me ? If you see frequency jump around it means something is wrong and disturb the frequency. Any software modification will not fix the issue.You can write to me by email. more quick. agaguk_99@hotmail.com

Hi Andy, Yes classic algorithm is only +- 1 of pwm each 1000 second. Normally the frequency isn't moving that far and fast. So +-1 is enough. What is tour ocxo ? I saw a resistor on your picture on ocxo vfc pin. What for ? It's like something is moving the frequency.

Not at home now, sure i have that, why do you want to use 1.53 ? Did you try 1.56 ?

It could this. Probably something disturb the count. Somehow, gps pulse arrive too early or too later. Or clock stuck or booncing, or uC miss some tic i do not know exactly. Plus it's intermittent hard to find. Now, in quick mode uC is doing large step to compensate this error and jump around the wrong frequency. Keep in mind th uC is just looking the 2 last digit. Meaning the frequency must in a range of + or - 128 of each side hz (FF/2). And it's perfect because normally we do not have this huge difference between 2 count right. But if this happen it could explain the problem you have.To do a test, try in classic mode. Put a jumper (see step 11) In classic it's a bit longer to have the frequency right. But at the end, uC is only doing + or - 1 of pwm. So if a huge difference happen. uC …

It could this. Probably something disturb the count. Somehow, gps pulse arrive too early or too later. Or clock stuck or booncing, or uC miss some tic i do not know exactly. Plus it's intermittent hard to find. Now, in quick mode uC is doing large step to compensate this error and jump around the wrong frequency. Keep in mind th uC is just looking the 2 last digit. Meaning the frequency must in a range of + or - 128 of each side hz (FF/2). And it's perfect because normally we do not have this huge difference between 2 count right. But if this happen it could explain the problem you have.To do a test, try in classic mode. Put a jumper (see step 11) In classic it's a bit longer to have the frequency right. But at the end, uC is only doing + or - 1 of pwm. So if a huge difference happen. uC doesn't jump to far. So if it's a gps glitch, maybe the second count will be ok because the pwm will stay almost the same (pwm + or -1).Regars Yannick

Hi, Your eeprom idea it's exactly what i tought, write 2 times and compare. But if the problem occur when it's up and running. It's not an eeprom problem. The eeprom is only use when you turn off and on. At first you told me it was occur only when you switch off on on. But in reality, it happen when it's working and the eeprom is updated with a wrong pwm value stuck on a wrong frequency.If you track the frequency with serial monitor, yes it will be more easier to find what's it's going on.this is an exemple: frequency 10,000,000,256 Hz is 0x2540BE500 in hex. You see the 00 at the end ? For uC this frequency is good and pwm value updated. So if you turn off and on... You will restart with a wrong pwm value.Let me know if you find somethingYannick

Yes strange. When you switch on/off it restart at 200 seconds right ? Did you wait the 15 minutes heat time or you bypass by push button ?I do not think it's a display problem. The frequency is really that you read if the gps pulse is good. 0.400 for exemple tell me you have 400 more cycle in 1000 seconds.Are you in quick or classic mode ?Also try to know if the eeprom value (restart value) is good. Each time you have a .000 the pwm value is kept in eeprom. So when you restart the eeprom value should be very close of the eeprom value. If not, the memory is corrupted somehow. I already have this problem on a nixie clock.

Just to be sure. All is ok at 1000 second. And somehow you read 1.282 ? Or it happen only when you switch off and on ?

What version you have installed ?

It's just a display problem. The frequency is ok. uC is looking only the 2 lasts digit to correct the pwm. So for him it's 96, 97 etc... But now, why are you missing some tic, i dont know exactly. The gps pulse is arriving to early somehow of 30E6 cycles ? Hard to tell. But at the end the frequency is good for sure.

Tu as raison le lien de lui qui avait fait un op-amp adaptateur n'existe plus. Mon système est conçu pour une plage de 8hz sur 0-5v. (2Hz/Volt) au lieu de 20Hz comme tu as besoin. Pour toi, est-ce 20Hz de 0 à 5 V ?

Le pas du pwm n'est pas compatible avec le ocxo. Les sauts sont trop grand. Étant donné que le ocxo est supposé de varié de plus ou moins 8 hz, ça ne donne rien de comparer si un million = a un million. Le software compare seulement les 2 dernier digit. Si = 00 = ok on est bon. Et il allonge le temps en augmente ou diminue le pwm et revérifie.En 200 secondes il a compté 1999999488 qui égale a 0x77359200. Remarque les 00 à la fin. Pour lui c'est bon. Voila pourquoi.Je viens de voir que je te l'avais déjà expliqué plus haut les sauts et la diff.rence entre classic ou quick. En classic mode les steps sont court pour être certain d'arrivé dessus et de ne pas passer droit. Mais c'est plus long. En quick les step sont grand mais nécessite un ocxo pareil au mien (le 12v sinus).Si tu as n'impor…

Le pas du pwm n'est pas compatible avec le ocxo. Les sauts sont trop grand. Étant donné que le ocxo est supposé de varié de plus ou moins 8 hz, ça ne donne rien de comparer si un million = a un million. Le software compare seulement les 2 dernier digit. Si = 00 = ok on est bon. Et il allonge le temps en augmente ou diminue le pwm et revérifie.En 200 secondes il a compté 1999999488 qui égale a 0x77359200. Remarque les 00 à la fin. Pour lui c'est bon. Voila pourquoi.Je viens de voir que je te l'avais déjà expliqué plus haut les sauts et la diff.rence entre classic ou quick. En classic mode les steps sont court pour être certain d'arrivé dessus et de ne pas passer droit. Mais c'est plus long. En quick les step sont grand mais nécessite un ocxo pareil au mien (le 12v sinus).Si tu as n'importe lequel autre ocxo tu est mieux en classic. Sinon il faut que tu install un op-amp entre le pwm et le ocxo pour rendre les steps compatibles.Yannick

Very strange... This .bat file is working for me and other probably. Try to -B12 to the programming fusebit line. Look the device signature is different when you program the fuse bit.avrdude -c usbasp -p m328p -B12 -U lfuse:w:0xE0:m -U hfuse:w:0xD9:m -U efuse:w:0xFF:m -F

I dont know... you have done 1, 10, and 60 so you should be almost at 10.000.000.000 not so far. You miss some clock or power supply issues. Hard to tell but something is wrong.

Great, I’ll correct the bat file.On my side I have 3.44vpp without load.I read 195572321 on your counter. It’s very far.

It's maybe your fuse bits not programmed correctly. By default it run at 1 mhz internal or 8 mhz. Fuse bits is to remove the /8 div and enable the external clock. Can you double check this ?

What is your gps receiver ? It's all 9600 bps. Except if you have install the 4800 bps jumper.

Your welcome :)

The esp8266 is the web server. Program it (wifi and password updated) and turn it on. This one is dhcp so the esp8266 will ask for an adresse and your router will provide it. Now you can go in your router to know what is your adresse or more simple is to look the arduino com display. did you read: quote:Start the serial monitor in arduino. Tool, Serial Monitor. You will see more detail and also the web server local ip address. You need the local ip address to enter this in a web browser.The port part, you choose it yourself. You must add the port in the code source i provide just before to program the esp8266. quote:Unzip the file and program your esp8266 with the code Garage_door_yt.inoYou will have some variables to change in the ino file.-SSID and router password to connect in your web…

The esp8266 is the web server. Program it (wifi and password updated) and turn it on. This one is dhcp so the esp8266 will ask for an adresse and your router will provide it. Now you can go in your router to know what is your adresse or more simple is to look the arduino com display. did you read: quote:Start the serial monitor in arduino. Tool, Serial Monitor. You will see more detail and also the web server local ip address. You need the local ip address to enter this in a web browser.The port part, you choose it yourself. You must add the port in the code source i provide just before to program the esp8266. quote:Unzip the file and program your esp8266 with the code Garage_door_yt.inoYou will have some variables to change in the ino file.-SSID and router password to connect in your web server.-Also, you can change the port as you wish. exemple: WiFiServer server(54195)-The password: Find and replace Passw0rd to your password as you wish in the .ino file.Hope this help.

Dont understand German but looks like exactly what i'm talking about.

Hi, maybe it should be possible for you to use a Si5351C https://www.silabs.com/documents/public/data-sheet...This device accept 10mhz to 100mhz frequency reference and by pll can output your 25mhz (or whatever you need it's programmable).So you could use a 10mhz reference gpsdo to this chip and you will have a precise 25 mhz.You need to send i2c config to the chip to program the 2.5x multiplier.A little addon box: coax in,10mhz,attiny uC, Si5351C, coax out, 25 mhz

Hi Andy, thanks for your input. The 129th harmonic... is it very important ? I like the blinking effect :) Is it realy bad for the accuracy ?

Looking very good. Enjoy your new toy :)

Bravo, oui le .1uf c'est pour du filtrage. Ca fait une petite différence que je peux déceler à l'oscilloscope. Mais si il n'est pas la ca va fonctionner quand même. Bye

You can't. A bypass capacitor is on the pin. So there are DC level and some uV 10mhz noise from the OCXO. If you want to know the pwm frequency you must remove the capacitors and unplug the ocxo vfc pin.Yannick

You are in quick mode. The jumps are too large for your ocxo. Try in classic mode.Yannick

Hy Andy, It means the uC doesn't receive 1 pulse by second. Be sure to enter 1 pps.

Hi Mike, 0 us it's like 0 lol By default it's 1 pps 50% duty. On my side i setup 20% duty cycle. The pulse on the led is nicer. Glad to have found the problem. Bye

lol yeah, just seeing this. Yes it's 3/4" :)

Yes i use it. On some picture the gnd wire wasn't installed yet. But on the first picture, the black wire is gnd. I took the gnd inside the probe but pretty sure you can use the case itself if the gnd is good.Yannick

Hi, it's not too bad. It depend of many things. Antenna, number of satellites, temperature variation. Can also depend of your ocxo vfc correction range, noise, power supply.But by experience, when my number of satellite is low i can also have these values. The pulse is driven by the gps module. You need of very stable pulse.

Lits all good.!you are seeing the pwn value, the gate time 1000 seconds and satellite number.1000 is run mode. I do not display run anymore.Good word.

Avr Studio 7. In assembler

Ok. But it you are seeing sat = 08. It means the nmea code are realy read by the uC. Have you gnd the gps and gpsdo together ? What is your gps module ? The speed is 9600 ?

Well done Bruce :)

This instructable is the old one. The new one is here: https://www.instructables.com/GPSDO-YT-10-Mhz-Lcd-...You will see my guithub address where the source code is avilable.EnjoyYannick

Hi, it's impossible to do it with an arduino. There are too many limitation out of control. Sorry.

Hi, this is where it goes bad 0x710D, 60s,S=06,06000000060x6E7F, 60s,S=07,0599999979You are in quick mode probably. Have you tried in classic mode with the jumper on. check picture on step 11. Yannick

Yes you right about the switch trace. It's already connected. You do no need the wire. Only needed if it's a prototyping pcb. You all good. Happy New Year :)

Hi Bill, awesome work. Congratulations. Surface mount isn’t too difficult to do. I think 0805 size is a perfect size. Not to little and we can do very little board with it. 0603 is a bit too little. Happy new year. Yannick

Hi Bill, when we do a prototype pcb. We need to put wire to do VIA between bottom and top layer. On professional pcb the VIA is already done. In other word, each time you see a hole on a professional pcb. The top have continuity with the bottom.You aren't suppose to have continuity between the 2 holes near the switch. It's why i have put a jumper. You need to install this wire.We do not see well on picture but yes I used the shielding too. I think i solder the shield with the gnd. So yes if you can do it, do it.Hope this helpYannick

This isn't normal, The atmega is ok. Replace it to be sure. Never saw this before. Yannick

You should see 0x7fff 1s,And if gps module is connected to rx you should see numer of satellite connected too.

I think you brick the atmega. Eeprom memory is corrupt. Not suppose to have 0x008B in it. Reprogram it if not working replace it.Yannick

After push button or 15 min waiting time, You should see 0x7fff 1s,And if gps module is connected to rx you should see numer of satellite connected too.

If the clock wasn't working, you didn't see something on display. So probably this is fine. Unplug completly the gps module to see what happening. Should be have 0x7fff on display after push button.

Yes. The gps pulse is missing.

Hard to tell... normally when you push the button you must see 0x7fff, 1s,Make sure you install all filtering .1uf capacitor.Maybe the clock stays stuck somehow intermittent.Sometime on breadboard weird problem is happening.

Awesome. Great instructable. Thanks for sharing

Bravo, well done :) The boxes are looking very nice.

Hi Bill, trust the schematic. Your c1 1uf is good. Was an old mistake and it's not fixed on my picture. But for C6 and C7 my picture is good. With tantalum capacitor, Mark is the positive side. Hope this help, let me know.

Like i said, your C1 is ok.

Hi, sure. Write to me on my email agaguk_99@hotmail.com

In red! Beautiful. :)

Hi, this is your datasheet for your ocxo: https://datasheet.datasheetarchive.com/originals/d...You can read EFC is -5 to 5v. It's not compatible with the gpsdo you are doing.EFC of this gpsdo provide a correction from 0v to 5v. (0v = 0 and FFFF = 5v)It's why i told you to do the step 22. This is sending EFC 0v and tell you the frequency and then 5v (ffff) and tell you the frequency. You must know if 10mhz is in between. For exemple if 0v = 10000000.1 and 5v = 100000008.2 You know that it will be impossible to reach 10mhz.Hope this help ?Yannick

The softstart is plug in the wall outlet. The switch saw is off. A few voltage is present on the softstart outlet. When you turn on the saw, some current if flowing in T4. This do a spike through D2 and trig the uC interrupt.I will add a step to explain how the circuit is working in more detail.

Hi Trevor, I know what you mean. And you right about this (3041 have 0 crossing) But i'm sending a wave form from 2% to 100% duty cycle in 3 seconds. And I didn't want to have a "hi" when the opto wasn't to 0. Even I know the opto (3041) will wait until it reach 0 before the start. I have more control like that and it's something else.I needed this 0 crossing detection to know the speed of the line. 50 or 60 Hz. Again you will tell me that if i was using 3041 no need to know this. In fact, it's handy to know this because this tell us the voltage I'm dealing with. The starting voltage is different with 120v or 220v.So, one schematic, one code for everybody. And it's why i decide to go with a 0 crossing detection circuit.Hope this help to understand.Yannick

D'accord laisse moi savoir par email c'est plus rapide. agaguk_99 a hotmail point com.

Sometime the esp8266 need to be reboot. I think this is more hardware related.To install garageDoor2 it's the same hardware. Just program the esp8266 with this.On my side when i reboot the the think, the door isn't opening.Try the garageDoor2. it's closing the door at 10pm each day if this is open. Maybe this can help.

Wow looking very good :) nice work

Hi, yes ocxo need more than 0.5 amp to work correctly. Sorry for the delay. Instructable doesn't always send an email when someone ask a question.

The triacs aren't completely off. A starting voltage is present. This one trig a pulse in T4 and detected bu the mcu.

No you wrong. The mcu need to know exactly when to trig the mosfet. So we need to have a zero crossing detection circuit.

Soit, le voltage de départ ne doit pas être assez haut pour votre scie. Cela fait que le peak de démarrage est marginal et souvent trop bas pour être détecté.Ou soit que le circuit du tranfo T6 n'est pas assez performant.Ce que vous pouvez faire. Remplacer r6 par une 1k et/ou d2 avec une schoky diode. Vous gagnerez quelque milivolt ce qui peut être suffisant.Sinon on modifie un peu le programme pour avoir une tension de départ plus grande. Je peux le faire ou vous donner le code source.Yannick

Hi, sorry for the delay. instructable doesn't always an email when someone is writing something.For your problem, maybe your ocxo is at the end on his range. Try step 22. You will know exactly the range of your ocxo. If the range isn't good. you can add a op amp to correct this.Yannick

Nice... perfectly fine. The hexadecimal number is the pwm value. I do not write run anymore. The pwm value is more handy. Plus, we do not need to see run that much because we have the real frequency anyway. Good job Yannick

Beautiful. A cigar case, what a good idea! Thanks for sharing your work.

Personally I'm good but if anyone need it, it's good to know. great idea. Your welcome and you can click on I made it :)

Hi, download the part list. I added a lot of part number. Look for part on Digikey. To buy the nixie i think the best way is on ebay. Other part without number are just regular resistor and capacitor. any will do. Just buy the good package.You can also all buy on ebay at best price but can be longer shipping and fake part but i already tried and it was working.

I fixed the link, refresh and go to step 11. Sorry for that. I dont know why the files wasn't in my onedrive anymore.

Oh yeah, very nice. Thank you. I know my sine wave wasn't perfect in particular with coax cable. It was ok but if your add on is best, i can transfer this on my schematic. So you remove the original filter to install this one or you have put this one after ?

Salut Charles, sur mon simple ocxo isotemp j'ai utilisé le pulse de mon autre gps module soir le neo m8n. Avec celui la j'ai toujours 11-12 satellite et j'ai vraiment de meilleurs résultats. En fait j'ai toujours 000 avec quelque 999 et 001. Avant, J'avais même eu moi aussi un 9.985Le module et le nombre de satellite sont donc très important pour avoir des bons résultats.Yannick

https://github.com/YannickTurcotte/GPSDO-YT I finally release my code. Enjoy it.

https://github.com/YannickTurcotte/GPSDO-YTI finally release my code. Enjoy it.

C'est fait, si tu vas sur github tu vas tout trouver. https://github.com/YannickTurcotteAmuse toi bien

Si jamais tu veux t'amuser. J'ai mis le code source public. https://github.com/YannickTurcotte/GPSDO-YT

Salut Jean-François,Je ne peux me servi de la pin input capture. Pour ce faire le clock d'entrer doit être supérieur de 2.5x le clock mesuré. On roule a 10mhz donc le max que je peux mesurer avec ce moyen est de 10mhz/2.5.Je me sert donc du timer 8 bit en interrupt qui incrémente et je compte les coups d'horloge durant 1000s ou 10000s. Tous est compté. Il overflow a chaque 256 clock. J'incrémente un registre, quand il est plein j'en incrémente un autre etc... A la fin, tu multiplies tes registres tu additionnes ce qui reste dans le compteur 8bits (tcnt0) Donc quand tu doute du résultat, c'est le pps qui la plupart du temps n'est pas bon. Ou problème d'alimentation (moins fréquent).J'ai gardé le compteur 16bits pour le pwm. Sur le compteur de Paul il ne varie pas mais sur mon gpsdo (lui ci…

Salut Jean-François,Je ne peux me servi de la pin input capture. Pour ce faire le clock d'entrer doit être supérieur de 2.5x le clock mesuré. On roule a 10mhz donc le max que je peux mesurer avec ce moyen est de 10mhz/2.5.Je me sert donc du timer 8 bit en interrupt qui incrémente et je compte les coups d'horloge durant 1000s ou 10000s. Tous est compté. Il overflow a chaque 256 clock. J'incrémente un registre, quand il est plein j'en incrémente un autre etc... A la fin, tu multiplies tes registres tu additionnes ce qui reste dans le compteur 8bits (tcnt0) Donc quand tu doute du résultat, c'est le pps qui la plupart du temps n'est pas bon. Ou problème d'alimentation (moins fréquent).J'ai gardé le compteur 16bits pour le pwm. Sur le compteur de Paul il ne varie pas mais sur mon gpsdo (lui ci-haut) j'en ai de besoin.Le secret est de tout contrôler. C'est pour cela que je l'ai fait en assembler. En C c'est possible aussi mais moins évident et a la fin moins précis. Parce que le compiler met plein de push et pop qui prennent un cycle et tu dois balancer. Si ca te prend 8 cycles pour entrer en interruption et partir le compteur, tu dois prendre 8 cycle pour entrer à nouveau et arrêter le compteur. Faut que ca soir égale. Et des fois tu recompiles et ca change.De plus en C quand tu entres ou sors d'un interruption ca prend soit 1 ou 2 coup d'horloge et il n'y a pas moyen de savoir. Donc a la fin tu peux te retrouver avec 10,000,002 quand tu roules a 10mhz pile.Je vais peut-être envoyé mon code source sur github. Je te ferai signe. Yannick

Done, available at step 11.

Ok i know what you mean now. Your boars is just fine. All will be ok. Use a little knife and remove the green soldermask where you need to do solder. It's easy to do. On my side I'll modify my gerber to fix that. Like that:

You probably miss to send a file. The file Carlson's probe2.sol is the bottom. Download the gerber file. Unrar it in a folder and sent it to the pcbway viewer. You will see exactly what you should have.This is the viewer to upload the gerbers files:https://www.pcbway.com/project/OnlineGerberViewer....

Yes almost ready... I'll do that soon. Probably beginning of the week

Your welcome. Your gpsdo is looking very good. I'm thinking to keep the adjustment i did to you for the isotemp 0131-100. The ending step is a bit smaller and run nice on my side too. Best regards, Yannick.

Salut Charles, très bizarre car je n'ai aucunement touché à l'algo du timing. Pour etre sur j'ai donwloadé le fichier d'ici et il roule depuis 3 heures sans problème. Push button est ok. Pour ce qui est du run mode c'est aussi une question de chance pour l'atteidre avant une heure. Si tu le manque de de peu et passe souvent à coté ca retarde a coup de 16 minutes ca monte vite.Quel gps module utilises-tu ? Hier sur mon simple ocxo avec mon neo 6m je recevais que 7 satellites et j'ai même passé à .985 et c'est remonté tranquillement par la suite car je roulais en classique +-1. Je suis persuadé que quand je ne reçois pas au moins 9 satellites le pulse n'est pas autant précis. Présentement j'ai 11 satellites et tout est beau.Sur mon autre j'utilise un ublox n8m qui capte aussi les satellites…

Salut Charles, très bizarre car je n'ai aucunement touché à l'algo du timing. Pour etre sur j'ai donwloadé le fichier d'ici et il roule depuis 3 heures sans problème. Push button est ok. Pour ce qui est du run mode c'est aussi une question de chance pour l'atteidre avant une heure. Si tu le manque de de peu et passe souvent à coté ca retarde a coup de 16 minutes ca monte vite.Quel gps module utilises-tu ? Hier sur mon simple ocxo avec mon neo 6m je recevais que 7 satellites et j'ai même passé à .985 et c'est remonté tranquillement par la suite car je roulais en classique +-1. Je suis persuadé que quand je ne reçois pas au moins 9 satellites le pulse n'est pas autant précis. Présentement j'ai 11 satellites et tout est beau.Sur mon autre j'utilise un ublox n8m qui capte aussi les satellites russe. Je suis toujours a 12 satellites. Oui c'est un double ocxo mais je pense bien que le module y est pour quelque chose.Prochaine étape, je remplace mon neo6 pour un 8 je verrai bien.Tu as bien un condensateur sur la pin de ton push button ?

Hi neunziger,You already tried it. It's the quick mode. In quick mode pwm is moving of +-8 x miss clock.If it's 10,000,000.000 doesn't moveIf it's 10,000,000.001 move +- 1If it's 10,000,000.004 move +-32 (decimal) in one shot.If it's 10,000,000.020 move +- 160 (decimal) in one shot.Also what you asked is almost the same in classic mode phase 5 just before you reach run mode. It's exactly +- 3 on 1000 seconds and it take you many time to go throw.That said, maybe +- 8 in quick mode was too much. I replaced it by +-4. Try it in quick mode (jumper removed)https://1drv.ms/u/s!AnKLPDy3pII_wADYR0Kh2ia2kWiG?e...Let me know.

Hi, you were right. I correct the file. The bottom was too large. Refresh the page. Should be good now let me know.

Let me know

The speed isn't good.The frequency drift of the pulse is not accurate. Voltage, temperature and antenna could be the problem. A cover can help, reinsulate the ocxo too but the more recurring problem is power and antenna. Keep looking you almost there.good ocxo: https://www.ebay.ca/itm/OCXO-Oscillator-C-MAC-STP2...But you can have not too bad result with ISOTEMP. Look mine it's right now. Using a chromecast psu.

quote:Yesterday I made another test. After about 5 hours stuck in phase 5, I pushed the button. Could see UTC and location and then the device went into run mode.No it wasn't. After coming back of time and config. The gpsdo display 10,000,000.000 It is assuming of you are very close of that because you was in 1000 seconds gate. You need to wait another 1000s to know your real frequency.Isoterm is working but it's a simple ocxo. Less accurate. the temperature need to be more stable. Also it talk 0.6 amp. Be sure to have enough power.On my isoterm, i have also sometime +- 0.003quote:About 3,5 Hz away... What is the problem?This is very huge and not normal. Try a reset to default and restart the whole thing. Number of satellite is important. On my side with 5, it's not accurate and i dont …

quote:Yesterday I made another test. After about 5 hours stuck in phase 5, I pushed the button. Could see UTC and location and then the device went into run mode.No it wasn't. After coming back of time and config. The gpsdo display 10,000,000.000 It is assuming of you are very close of that because you was in 1000 seconds gate. You need to wait another 1000s to know your real frequency.Isoterm is working but it's a simple ocxo. Less accurate. the temperature need to be more stable. Also it talk 0.6 amp. Be sure to have enough power.On my isoterm, i have also sometime +- 0.003quote:About 3,5 Hz away... What is the problem?This is very huge and not normal. Try a reset to default and restart the whole thing. Number of satellite is important. On my side with 5, it's not accurate and i dont know why. between 9-12 it's better. I hope this help. Let me know.