Search found 10 matches
- October 28th, 2018, 2:10 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Anyway, good job guys!
- October 26th, 2018, 8:39 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Ok it works, the ATtiny45 I used was broken somewhere. Thank you for your help guys!
I stuck on the point: Code should have .h for modifying parameters and adding hysteresis parameters in it too.
And.. goto in C in 2018? =))
Cheers
I stuck on the point: Code should have .h for modifying parameters and adding hysteresis parameters in it too.
And.. goto in C in 2018? =))
Cheers
- October 26th, 2018, 3:33 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
- October 26th, 2018, 3:24 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Add this line to see what is your F_CPU define. DEBUG_PRINT(F_CPU); If you have a discrepancy between chip / pc baud rate (it's exactly 8x times in your case), F_CPU define and oscillator mode might be different, make sure it's all the same (8MHz internal oscillator and F_CPU is 8000000). I compile...
- October 25th, 2018, 10:09 pm
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Ok.. by using mySerial.begin at 9600 instead of 115200 AND monitoring at 1200, I have my "START" debug print the result: START m 0 340A88880AC0900AA1183C01 202804113C81001822010420 001080108E402C01200AC6C0 00A24202DAA880CA86180E00 906CA4058760041CC6101D07 34D8400E86504CC6E4130CC1 893113594...
- October 25th, 2018, 9:52 pm
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
(with #define PSNEEDEBUG and #define USINGSOFTWARESERIAL)
I tryed with 4 softwares, all give me the same not correct symbols like the baudrate is wrong.
The wires are like this:
USB TTL TX -> ATtiny pin 2 (PD3)
USB TTL GND -> ATtiny pin 4 (GND)
I tryed with 4 softwares, all give me the same not correct symbols like the baudrate is wrong.
The wires are like this:
USB TTL TX -> ATtiny pin 2 (PD3)
USB TTL GND -> ATtiny pin 4 (GND)
- October 25th, 2018, 11:20 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Maybe I'm doomed...
When I monitor the pin 2 (PB3) of the Tiny45, I can't get correct values from psnee baudrate (115200 or 500000)
When I monitor the pin 2 (PB3) of the Tiny45, I can't get correct values from psnee baudrate (115200 or 500000)
- October 25th, 2018, 10:23 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Yes, it can be automatic but just for debugging I suggest to force it. You can debug on ATtiny 45 by using physical IC pin 2. 84 is supported only in my branch for now. EDIT: you can also try reducing hysteresis level to 10 and 7 respectively, maybe that will help: if (hysteresis >= 14) { hysteresi...
- October 25th, 2018, 10:04 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Hi superg, thanks for your reply.
It says PSnee 7 is automatic for multiRegion right? If I read I can see only the PSone have to set the region?
Is debug via serial possible on ATtiny45/84?
It says PSnee 7 is automatic for multiRegion right? If I read I can see only the PSone have to set the region?
Is debug via serial possible on ATtiny45/84?
- October 25th, 2018, 8:48 am
- Forum: Hardware
- Topic: PSNee further development
- Replies: 570
- Views: 950488
Re: PSNee further development
Hello everyone. I can't get PSnee working, I explain my problem: -I use ATtiny45 with internal 8mHz clock programmed via Arduino UNO as ISP -In the code, I use only #define ATTINY_X5 -Wires are perfectly like the README on GitHub -IC is decoupled with 100nF capacitor (tryed with and without, but I k...