-
Notifications
You must be signed in to change notification settings - Fork 2
Problems
ThiagoCM edited this page Nov 18, 2016
·
3 revisions
- We had several problems with the USART(UART, actually) communication. At a first glance, everything was working fine when we were using the Printer with the Arduino. When trying to translate the Arduino Code to a PIC compatible code, we've found a lot of problems. Basically, the wrong doing was the baud rate value. We're setting the wrong baud rate generator, so the printer was getting a lot of trash and just printing it.
- When using the Printer with the Arduino, it seems that a lot of the capabilities of the printer was reduced. We couldn't print a whole line, neither use different formats on our texts. Using the PIC, it seems that everything is working well and we have no problems with it.
- The printer doesn't have a good enough datasheet, there's a lot of information missing.
- The I2C should be working fine with the parameters set on the simulation but that was never the case. When simulating using the Proteus software, everything seemed to be fine but that wasn't the case.
- Slave's clock was being set to 0, so there was no possible communication.
- We didn't find the problem with I2C. So we changed the serial communication from I2C to SPI.
- Lack of organization, on either software (using duplicated names on codes) and hardware (on protoboard).