Because i need to put it in the box and connecting the leds via wires looks not so professional... It's so simple to do that through pcb that i cannot figure out why they didn't
Hi guys, i'm developing very hard with your WebPlatform and i feel very comfortable with it! Great Product!
Actually i run in a problem with microchip stack that maybe can interest other users: I'm doing a board that collects some values from the real world and send it via http to our server (php page that save the values in the db). In the microchip stack there wasn't the HTTP client so i write my own that send via POST a file from the EEPROM. But the problem was that i was supposed to replace the ~variable~ string with the real value but the microchip's HTTPPrint() function only works with their HTTP2 server.
So i changed it to pass the socket where we need to put our infos: in HTTPClient.h: from
in the HTTPPrint_* functions i passed the TCP_SOCKET skt variable. In this way we can use the HTTPPrint function in our code!
The main problem is that MPFS utility overwrite the HTTPClient.h file everytime a new image is created, so i was wondering about modifying this utility to add this trick. Is there any source code of that application? Anybody can teach me to make a patch file (i never made one)
Ok, i've figured out all. In main.c the original code setup the MISO pin on PORTC8 wich is correct with the schematic. Then on the HardwareProfile.h the TRISC8 is assigned to EEPROM_SDO_TRIS wich is set to zero in SPIEEPROM.c !! This is because microchip stack is ambiguos in that definitions and can easily led to errors. I suggest to swap EEPROM_SDI and EEPROM_SDO to fix this problem!
Hi, i've solved the issue, there was a trouble in code. By setting both MISO and MOSI pins as input the thing is working (both eeprom and shift registers on the same bus). Of course this is not a final solution and i'm trying to figure it out what is really happening, because original code is setting up TRIS registers correctly but for some reason when SPI is disabled dspic is driving MISO line low.
Hi, i'm using EEPROM SPI expansion port to control some shift registers. I've no problem in using output (driving MOSI pin via spi) but when i try to read a shift register looks like the dspic is driving low the MISO line. The CS line is high so the eeprom is in three state...
I've tried to force MISO pin as input and i can get some data from the registers but with some bits missing (maybe due to spi module misconfiguration)
Hi, the project is completed and the hardware is working but i still need some spare time to start working to a decent software. Schematics and pcb were made with orcad so it's not so simple to share, but i can provide gerber and pdf with schematics. I have a couple of spare pcb left, i can send you one if you want to start writing some software.
[quote author="ian"] This looks great. I'm going to post it on the blog. [/quote] Thanks, I appreciate it!
I've started to code. I've successfully enabled CAN mode menu but i'm trying to understand how the inputted text is passed to the routine. I think current menu items are inappropriate for can operation and i want to add a simple separate command set. Is that possible or require a massive coding?
Of course the clock out is useless, but the SOF no! The PIC doesn't have to do anything but monitoring the xcvr, then for debugging purposes i think it's more useful to monitor the start of frame instead of the interrupt. In fact a broken frame will trigger the only SOF, and not the interrupt (if I correctly understood the datasheet).
Unfortunately it isn't like an USART. The transceiver uses SPI protocol to communicate to Bus Pirate. I was able to send CAN packets using SPI mode in Bus Pirate but setting up all the transceiver registers is a mindfucking thing. Thus i was wondering about a separate new mode with the opportunity to add specific CAN commands like filters set up, priorities, can speed and timings set up, in a user-friendly way.
Schematics are on their way, i'm not at the lab right now. I'll post them ASAP
Hi, my name is Stefano and I'm from Italy. I'm playing with the Bus Pirate and it's an amazing helpful tool!
Now I have to send and sniff some CAN data to debug an application, and I tough for a Bus Pirate expansion. I've called it CAN Pirate. It's nothing more than a breakout board for MCP2515 (it can handle both packages) and MCP2551
Now I'm going to implement the code to operate it via the practical serial console. In order to release it back to the community, I want to make the code as user friendly as possible. I'm searching for advices on what features (and how) to implement, and someone good with the Bus Pirate firmware.