On 23 Aug 2020, at 21:19, jimmy le <c...@irtankless.com> wrote:
Hi,
--
You received this message because you are subscribed to the Google Groups "CatGenius" group.
To unsubscribe from this group and stop receiving emails from it, send an email to catgenius+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/catgenius/b6fdd006-992b-4f3f-9699-771f55f13db8n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/catgenius/65b91567-29c9-4511-bfe9-06874d6d27cfn%40googlegroups.com.
On my box, it stopped at mode 5 not 6,
And it's not key lock,
it's basically can not press anything other than 2 buttons reset when power on.
Regarding about power down while pressing mode, I don't have successful able do that, sometime I heard the beep like loosen power when remove the plug with pressing mode multiple time but mode still same.
Also, if I stay on mode 1-4 I can press manually start button but as soon I hit to mode 5, then it's done.
I tried all firmware version, binary hex download or compiled myself.
I also do clear reset flash as well.
I tried holding 2 buttons to see if it's unlock but still nothing when it is dead to mode 5.
And yes, my box run the firmware for while before it happened,
And Robert: can you help me point out which line code and where I can hard mode or program the mode instead pressing button? Like a default mode when power on? I want to see if I can start default mode at 7 then power on cycle down to 8,9,1,2,3
I could not find where to overwrite the default mode,
--
You received this message because you are subscribed to a topic in the Google Groups "CatGenius" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/catgenius/W883GOghVJI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to catgenius+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/catgenius/AFFCEFA0-48AD-4AAC-AC61-A4E3B1C43549%40delien.nl.
The buttons becomes unresponsive regardless if box is running or not.1) yet cat mode still flash as normal and led cat flash as normal
2) count down still work as normal
3) I have blue tooth debug on 24hrs so I can see what's going on
4) both button lock and unlock only work when you first reset nvram which somehow I think I got 5 times press allowance. Then yet lock and unlock work.
5) as soon 5 key pressed register which shows in debug mode 5, I'm done, nothing will register unless I clear nvram by both buttons during power on.
What trigger me, is that assume nvram sometime only allow 5 times button, which mean somehow it won't let recycle it.
I switch mode a lot because I have 3 cats, sometime I do time interval 24hrs and sometime cat activate mode 5 or mode 7 scoop only depending...
This never happen before again, and nothing changed other than I probably flashes diagnose firmware to manually unclog stuff and flash back (i do this quite often maybe 1,2 time in 4,5 months) for cleaning.
I have finished the I/O-Tester application. The .hex-file is attached and you and easily flash it into your board using the stand-alone PICkit 2 application that came with you programmer. I have tested it, but on a PIC16F1939, because I have replaced the PIC on my test box, just to see if that works. You PIC16F877A uses different instructions, so I have recompiled it for your PIC. I wasn't able to test the resulting binary but I feel confident it will work right away.
After you have programmed it into your box, connect it's serial port to a computer and used Putty or another good terminal emulator to get access to the integrated command line interpreter. Again, communication parameters are 115200 8 N 1. Local-echo should be off, as the integrated command line interpreter echoes anything you type per default. You may need to configure it to add a <CR> to every <LF> it receives, depending on your terminal emulator.
After you power up the box, the I/O-Tester application will present itself on your terminal:*** I/O Tester ***Brown-out reset#First it's name, then the reset diagnostics and finally the prompt. At the prompt you can type commands, up to 20 characters. After the 20th characters, nothing you type is echoed anymore, so you know you're at the end of the line. No command is that long anyway. On a good terminal emulator <BACKSPACE> is supported too.
To get a list of known commands, type the command 'help', or just a '?', naturally followed by <ENTER>:# helpKnown commands:?helpechogpioBeyond this, no further help is built-in, due to memory restrictions. The command of interest to you is 'gpio'. Per default it dumps all register values related to GPIO pins:# gpioPORTA = 0x03, LATA = 0x00, TRISA = 0x13PORTB = 0x33, LATB = 0x00, TRISB = 0xFBPORTC = 0xD8, LATC = 0x00, TRISC = 0x98PORTD = 0x01, LATD = 0x01, TRISD = 0x00PORTE = 0x00, LATE = 0x00, TRISE = 0x08Your version will not show the latch registers as above, because your processor doesn't have any.
The GPIO command also has a number of sub commands. It allow you to modify the state and direction of a pin. To change pin b5 to an input and read its state, use:# gpio c5 inputPort C, pin 5 = 0To change pin b5 to an output and set its state, use:# gpio c5 setPort C, pin 5 setTo change pin b5 to an output and set its state, use:# gpio c5 clrPort C, pin 5 clearedNaturally, instead of c5 any other valid pin can be used. As you see, all these 3 commands report what they have done, so it's always clear if the command went wrong or the result is not what was expected.It will
To poll all port and report different states automatically, use:# gpio logPORTA = 0x03, LATA = 0x00, TRISA = 0x13
PORTB = 0x33, LATB = 0x00, TRISB = 0xFB
PORTC = 0xD8, LATC = 0x00, TRISC = 0x98
PORTD = 0x01, LATD = 0x01, TRISD = 0x00
PORTE = 0x00, LATE = 0x00, TRISE = 0x08
Press any key to exit logging
PORTB = 0x13
PORTB = 0x33
PORTB = 0x32
PORTB = 0x33
It will first dump the state of all registers, followed by an invitation to press a key to stop logging. After that, it will differences in input pins incrementally. In the example above it first reports a change of PORTB to 0x13 from the initial value of 0x33 in the dump above. This is the result of me pushing a button. The line below reporting PORTB to go back to 0x33 indicates I released the button. Please keep in mind that pins configured as output WILL show here too when shorted down. This is a know PIC shortcoming and the reason why more modern PICs have this LATCH register.
--
You received this message because you are subscribed to the Google Groups "CatGenius" group.
To unsubscribe from this group and stop receiving emails from it, send an email to catgenius+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/catgenius/D671D2D5-D1B8-4327-A4D9-B5AB59F34365%40delien.nl.
<iotester_16F877A.hex>
5) iostest i can do this and report you back
You want me just do gpio log test and print out report?
Yes, I have attached rebuild binaries, for both version CPU versions. Use the ‘gpio log’-command and wait some time. After that, start pressing the buttons in a random fashion and you should get output. But more importantly, after stopping to push, the output should also stop. However, if there’s jitter on the input, it will not stop.