Hi Hans, The reason that they re-assigned the programming pins - I think - is because the 'original' programming pins are also the USB pins. For debugging it is much more convenient that you can both use the programmer and the USB port at the same time.
For example if you use an 18f14k50 you are constantly disconnecting the USB port when programming the device. Very unhandy. You asked if it worked for an NRF24L01 and that it the case 🙂. It will work with any other PIC as long it has sufficient ROM and RAM. Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens Hans van Veldhuizen <[email protected]> Verzonden: zondag 12 november 2023 11:14 Aan: jallib <[email protected]> Onderwerp: Re: [jallib] Camera_Gimbal Hello Rob, I don't think it will work. I need two ad inputs and pin_A2 is Vusb. I also don't understand why the programming pins are C0 and C1 instead of A0 and A1. regards hans Op zaterdag 11 november 2023 om 17:02:34 UTC+1 schreef Rob CJ: Hi Hans, I think you can. Is has sufficient ROM and RAM and a SPI interface. Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens Hans van Veldhuizen <[email protected]> Verzonden: zaterdag 11 november 2023 15:49 Aan: jallib <[email protected]> Onderwerp: Re: [jallib] Camera_Gimbal Hello Rob, I have killed one of my 16F15325, is it possible to use the16F1455 for this nrf24101 project? I have two of them. Hans Op vrijdag 10 november 2023 om 08:17:30 UTC+1 schreef Hans van Veldhuizen: Hello Matthew, More than 10 years ago I made Marieke with your lib, 8 servos and a very expensive wireless command set . (see https://youtu.be/U3uuH1cK8Dk) I used a 16F1827 as transmitter and a 16F648a as receiver. I am now trying to use this old set for this, but as always my old programs no longer work in the changed JAL world. Time and again I experience that a sample only works in that sample environment and as soon as I want to use another PIC I have to complain to you. For me, electronics is still a tool to achieve something and not a goal in itself. I'll see what I can do with your advice, Thank you Hans Op vrijdag 10 november 2023 om 00:27:13 UTC+1 schreef Matthew Schinkel: Check your clock frequency. If it is half what it is supposed to be your servo's would only get half pulses and half movement. Not sure if it helps here but I suggest you try the slip library sometime for sending data packets. See samples 18f4620_slip_isr.jal or 18f4620_slip_poll.jal. Matt. On Thursday, November 9, 2023 at 11:15:43 AM UTC-5 [email protected] wrote: Hi Mathew, I've used your lib dozens of times on all kinds of servos and they always worked perfectly!!!! These servos also work on the special tester that also works on your lib. I'm pretty sure there is a conflict with the PIC here. If I now go from 0 to max with the potentiometer, the servo only moves half a turn. I just don't know what part of the frequency range they get. In any case, very nice that you responded. regards Hans Op donderdag 9 november 2023 om 15:12:13 UTC+1 schreef Matthew Schinkel: Hi Hans, Servo's move depending on the PWM signal sent to them. It is possible your servo's are expecting a different signal depending on the manufacturer. Do you have other servo's to test? Do your servo's work correctly an un-modified Jallib sample? Do you have an oscilloscope you can test the signal with? The PWM signal should be between 0.5ms and 2.5ms. Thanks, Matt. On Wednesday, November 8, 2023 at 7:12:07 AM UTC-5 [email protected] wrote: I have now adapted both circuits for WiFi. (So the transmitter has a WiFi master and the receiver a slave) The data received is identical to the transmitter . However, the servos only move half a turn. Apparently the Servo-lib can't handle the pic. Or I have to set something else. The programs are attached again. Op zaterdag 4 november 2023 om 10:50:22 UTC+1 schreef Hans van Veldhuizen: Hi Rob, It has to do with the pin A2. If i change it to C2 the both are working Op zaterdag 4 november 2023 om 07:56:20 UTC+1 schreef Rob CJ: Hi Hans, The only difference that I see is the looptime. Instead of 1 second it is 1 ms but it depends on how fast the data is received. If that is too fast will that disturb the servo movement? Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens Hans van Veldhuizen <[email protected]> Verzonden: vrijdag 3 november 2023 22:13 Aan: jallib <[email protected]> Onderwerp: Re: [jallib] Camera_Gimbal Have changed with attached basic. Same result. Changed 325 for 324 same result Op vrijdag 3 november 2023 om 21:27:23 UTC+1 schreef Hans van Veldhuizen: Hi Rob, If I add this before the original forever loop then just servo 2 moves. Changed servo's same result forever loop servo_move(60,1) servo_move(60,2) delay_1S(2) servo_move(150,1) servo_move(150,2) delay_1S(2) end loop Op vrijdag 3 november 2023 om 19:11:13 UTC+1 schreef Rob CJ: Hi Hans, I cannot see any errors. So the data is received correctly but the servo's do not work? Have you tried to get the servo's working without the receive routines? So just hard-code some values to see if the servo's are working? Kind regards, Rob ________________________________ Van: [email protected] <[email protected]> namens Hans van Veldhuizen <[email protected]> Verzonden: donderdag 2 november 2023 13:09 Aan: jallib <[email protected]> Onderwerp: [jallib] Camera_Gimbal Hello all, My question again. I'm trying to make a two-way camera Gimbal. I have modified working programs. The transmitter now has two ADC inputs and the receiver must control two servos. The signals arrive correctly at the receiver in fits and starts. I can't get the servos to work. Attached are the two files. Please respond again, regards Hans -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/ff970ccd-ffb8-473f-991f-1441f768da3cn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/ff970ccd-ffb8-473f-991f-1441f768da3cn%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/8093b573-4fb8-492a-ab0f-5db352424ffcn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/8093b573-4fb8-492a-ab0f-5db352424ffcn%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/b592656c-ad20-4c53-a1f2-0557e960c26an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/b592656c-ad20-4c53-a1f2-0557e960c26an%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/7d895e93-7337-448d-a123-a91d2afdb9d1n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/7d895e93-7337-448d-a123-a91d2afdb9d1n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/GVXP195MB1637DCB3875C2A9913610171E6ACA%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.
